Specify which IVR Profile using Play Treatment Block in IRD

[clemouk]

We have GVP 8.1.5 deployed and currently all apps run via a Trunk DN and associated Profile which RM looks up based on DNIS. We are now looking to use the Play Treatment block in IRD for smaller VoiceXML apps, however whilst the treatment works the VAR reporting is pegged against the default IVR profile. According to the Genesys documentation, we can add userdata to specify the profile with "gsw-ivr-profile-id", but this doesn't seem to work. Has anyone been able to get this to work?

[Kubig]

Yes, it works as expected - I have tested it, but not against VAR. Did you see in logs that the KVP (gsw-ivr-profile-id) is used for SIP communication or is ignored?

[clemouk]

I can see the userdata showing the profile name, but RM still then selects the default IVR profile. I also noticed in the Genesys Docs that we can use gvp-tenant-id with the profile name, so I have tried that as well with the same result.

[LOG EXTRACTS REMOVED - SOLUTION FOUND]

Cheers,
Clemo

[clemouk]

Ok, we've identified the solution. What wasn't clear in the documentation was the prefix being used, we had decided early in the deployment that we would use a custom user data prefix to identify our data from the Genesys attributes. Restoring this back to the standard "X-Genesys-" prefix has resolved the issue and now when we add "gsw-ivr-profile-name" user data before calling the Play Treatment block, the call is pegged against the correct profile.

[CK]

This was really helpful, thank you very much!

However, I quote Genesys [quote]NOTE: This cannot be used in an Apply treatment, as the request will be overwritten with the IVR Profile once the call is established with MCP by the INFO message.[/quote]

Still haven't managed to get this working

[PFCCWA]

Ive not been able to make it work either, think it is related to URS centric routing deployments, see note from gvp deployment guide below:

[b][i]Note: GVP reporting is unable to track Media Server services use at the
tenant level (by tenant or by application). Applications that use URS
centric routing have the following reporting issue:
During an MSML call into GVP, if SIP Server changes the
X-Genesys-gsw-ivr-profile-name or the X-Genesys-gvp-tenant-id
parameters in the middle of the call (e.g. applying different treatments
that use different IVR profiles), the change is reflected by Resource
Manager, Media Control Platform or Reporting Server. All reporting
for the call will be against the original IVR profile.[/i][/b]

My extract from SIP below:

AttributeUserData [356] 00 06 00 00..
'X-Genesys-gsw-ivr-profile-name' 'PROFILE_IVR'
'GVP-Session-ID' '2F65E933-6402-43C5-4A86-334E96284570;gvp.rm.datanodes=2;gvp.rm.tenant id=101_PROFILE_HELLO_WORLD'
'GVP-Session-Data' 'callsession=2F65E933-6402-43C5-4A86-334E96284570;2;0;sip:[sipserverip]:5060;;;Resources;PROFILE_HELLO_WORLD;'

PROFILE_IVR is what I want the call to be pegged against.
PROFILE_HELLO_WORLD is the default profile at tenant level, and what the call is pegged against.

Operation is URS (8.1.3) centric routing SIP 8.1 -> RM 8.1.7 -> MCP 8.1.5.
In routing strategy I have attach data block prior to play application block.

thanks.

[Kubig]

Is the prefix "X-Genesys" added by URS within strategy or is it prefix added by SIP server according to the option "userdata-map-trans-prefix"? What about option "userdata-map-filter" on Voice over IP Service object with "msml" service-type?

[PFCCWA]

thanks for the tip
It worked for me by doing the following.

section=TServer for all below:
SIP Server option userdata-map-trans-prefix=X-Genesys.
voip msml option userdata-map-filter=*.
rm runkgroup option userdata-map-filter=*.

IRD strategy multi attach block:
key=gsw-ivr-profile-name.
value=[ivr profile name].

[Kubig]

Yes, it is a right steps to achieve it. Or are there someone else what is not working for you yet?