Pedro,

Let's discuss the two options you suggested:

• Send the call to the application via trunk group (Complicated)
• From a SIP Server that is not the IVR SIP Server define a trunk/trunk group to the IVR SIP Server:
• Create a strategy that will transfer IVR calls to this SIP server under whatever conditions you deem fit
• Once calls transfer to this IVR SIP Server, define an incoming trunk from whatever your source IP would be.  Provide it with the following configurations:
• dial-plan=DP_Trunk_General
• Create a Voice Over IP Service DN named "DP_Trunk_General"
• Configure the Voice Over IP Service DN with the following:
• [TServer]
• dial-plan-rule-1= X!=>GVPDN # This will tell any number 0-9 of any length to be redirected to the object GVPDN
• service-type=dial-plan
• Create a GVP DID DN Object named GVPDN
• In the Annex tab, define the following
• [TServer]
• auto-redirect-enabled=false
• contact=::msml
• oosp-transfer-enabled=false
• refer-enabled=true
• userdata-map-filter=*
• userdata-map-trans-prefix=X-Genesys-*
• sip-uri-params=gvp-tenant-id=[<Tenant>].<IVR Profile Name>

The incoming call will be matched to the trunk, which will redirect the call via dial plan to the GVP DID named "GVPDN".  This, in turn, will trigger your IVR with whatever parameters you've configured in the "GVPDN" object, which should include the specific IVR Profile you're looking to have parse.  This is by far the more complicated of the two setups, and not something I'd recommend unless you're going to transfer ANI/DNIS as part of the attached data payload to your IVR and are normalizing the operation of your IVR that way.

• PlayApplication block in URS routing strategy
• (https://genesyspartner.force.com/customercare/pkb_Home?id=kA4U00000008d7sKAA&l=en_US&fs=Search&pn=1)
• Define the following attached data:
• gsw-ivr-profile-name=<Profile>
• You must do this prior to the Play Application block.
• In the Play Application block:
• Define {s}APP_URI=http://<server>/<path_to_file>/<file>.vxml
• On your IVR trunk or MSML DN (depending on how you're configured)
• userdata-map-filter=X-Genesys-*
• or
• userdata-map-filter=*

​-Ivan

http://demosrv:7422/fish-vui/start/GenesysGVP8_NR9_Vocalizer5.jsp?testsiteid=3966&istestcall=true

Pedro,

Let's discuss the two options you suggested:

• Send the call to the application via trunk group (Complicated)
• From a SIP Server that is not the IVR SIP Server define a trunk/trunk group to the IVR SIP Server:
• Create a strategy that will transfer IVR calls to this SIP server under whatever conditions you deem fit
• Once calls transfer to this IVR SIP Server, define an incoming trunk from whatever your source IP would be.  Provide it with the following configurations:
• dial-plan=DP_Trunk_General
• Create a Voice Over IP Service DN named "DP_Trunk_General"
• Configure the Voice Over IP Service DN with the following:
• [TServer]
• dial-plan-rule-1= X!=>GVPDN # This will tell any number 0-9 of any length to be redirected to the object GVPDN
• service-type=dial-plan
• Create a GVP DID DN Object named GVPDN
• In the Annex tab, define the following
• [TServer]
• auto-redirect-enabled=false
• contact=::msml
• oosp-transfer-enabled=false
• refer-enabled=true
• userdata-map-filter=*
• userdata-map-trans-prefix=X-Genesys-*
• sip-uri-params=gvp-tenant-id=[<Tenant>].<IVR Profile Name>

The incoming call will be matched to the trunk, which will redirect the call via dial plan to the GVP DID named "GVPDN".  This, in turn, will trigger your IVR with whatever parameters you've configured in the "GVPDN" object, which should include the specific IVR Profile you're looking to have parse.  This is by far the more complicated of the two setups, and not something I'd recommend unless you're going to transfer ANI/DNIS as part of the attached data payload to your IVR and are normalizing the operation of your IVR that way.

• PlayApplication block in URS routing strategy
• (https://genesyspartner.force.com/customercare/pkb_Home?id=kA4U00000008d7sKAA&l=en_US&fs=Search&pn=1)
• Define the following attached data:
• gsw-ivr-profile-name=<Profile>
• You must do this prior to the Play Application block.
• In the Play Application block:
• Define {s}APP_URI=http://<server>/<path_to_file>/<file>.vxml
• On your IVR trunk or MSML DN (depending on how you're configured)
• userdata-map-filter=X-Genesys-*
• or
• userdata-map-filter=*

​-Ivan

http://demosrv:7422/fish-vui/start/GenesysGVP8_NR9_Vocalizer5.jsp?testsiteid=3966&istestcall=true

Pedro,

Let's discuss the two options you suggested:

• Send the call to the application via trunk group (Complicated)
• From a SIP Server that is not the IVR SIP Server define a trunk/trunk group to the IVR SIP Server:
• Create a strategy that will transfer IVR calls to this SIP server under whatever conditions you deem fit
• Once calls transfer to this IVR SIP Server, define an incoming trunk from whatever your source IP would be.  Provide it with the following configurations:
• dial-plan=DP_Trunk_General
• Create a Voice Over IP Service DN named "DP_Trunk_General"
• Configure the Voice Over IP Service DN with the following:
• [TServer]
• dial-plan-rule-1= X!=>GVPDN # This will tell any number 0-9 of any length to be redirected to the object GVPDN
• service-type=dial-plan
• Create a GVP DID DN Object named GVPDN
• In the Annex tab, define the following
• [TServer]
• auto-redirect-enabled=false
• contact=::msml
• oosp-transfer-enabled=false
• refer-enabled=true
• userdata-map-filter=*
• userdata-map-trans-prefix=X-Genesys-*
• sip-uri-params=gvp-tenant-id=[<Tenant>].<IVR Profile Name>

The incoming call will be matched to the trunk, which will redirect the call via dial plan to the GVP DID named "GVPDN".  This, in turn, will trigger your IVR with whatever parameters you've configured in the "GVPDN" object, which should include the specific IVR Profile you're looking to have parse.  This is by far the more complicated of the two setups, and not something I'd recommend unless you're going to transfer ANI/DNIS as part of the attached data payload to your IVR and are normalizing the operation of your IVR that way.

• PlayApplication block in URS routing strategy
• (https://genesyspartner.force.com/customercare/pkb_Home?id=kA4U00000008d7sKAA&l=en_US&fs=Search&pn=1)
• Define the following attached data:
• gsw-ivr-profile-name=<Profile>
• You must do this prior to the Play Application block.
• In the Play Application block:
• Define {s}APP_URI=http://<server>/<path_to_file>/<file>.vxml
• On your IVR trunk or MSML DN (depending on how you're configured)
• userdata-map-filter=X-Genesys-*
• or
• userdata-map-filter=*

​-Ivan

http://demosrv:7422/fish-vui/start/GenesysGVP8_NR9_Vocalizer5.jsp?testsiteid=3966&istestcall=true

Pedro,

Let's discuss the two options you suggested:

• Send the call to the application via trunk group (Complicated)
• From a SIP Server that is not the IVR SIP Server define a trunk/trunk group to the IVR SIP Server:
• Create a strategy that will transfer IVR calls to this SIP server under whatever conditions you deem fit
• Once calls transfer to this IVR SIP Server, define an incoming trunk from whatever your source IP would be.  Provide it with the following configurations:
• dial-plan=DP_Trunk_General
• Create a Voice Over IP Service DN named "DP_Trunk_General"
• Configure the Voice Over IP Service DN with the following:
• [TServer]
• dial-plan-rule-1= X!=>GVPDN # This will tell any number 0-9 of any length to be redirected to the object GVPDN
• service-type=dial-plan
• Create a GVP DID DN Object named GVPDN
• In the Annex tab, define the following
• [TServer]
• auto-redirect-enabled=false
• contact=::msml
• oosp-transfer-enabled=false
• refer-enabled=true
• userdata-map-filter=*
• userdata-map-trans-prefix=X-Genesys-*
• sip-uri-params=gvp-tenant-id=[<Tenant>].<IVR Profile Name>

The incoming call will be matched to the trunk, which will redirect the call via dial plan to the GVP DID named "GVPDN".  This, in turn, will trigger your IVR with whatever parameters you've configured in the "GVPDN" object, which should include the specific IVR Profile you're looking to have parse.  This is by far the more complicated of the two setups, and not something I'd recommend unless you're going to transfer ANI/DNIS as part of the attached data payload to your IVR and are normalizing the operation of your IVR that way.

• PlayApplication block in URS routing strategy
• (https://genesyspartner.force.com/customercare/pkb_Home?id=kA4U00000008d7sKAA&l=en_US&fs=Search&pn=1)
• Define the following attached data:
• gsw-ivr-profile-name=<Profile>
• You must do this prior to the Play Application block.
• In the Play Application block:
• Define {s}APP_URI=http://<server>/<path_to_file>/<file>.vxml
• On your IVR trunk or MSML DN (depending on how you're configured)
• userdata-map-filter=X-Genesys-*
• or
• userdata-map-filter=*

​-Ivan

Pedro,

Let's discuss the two options you suggested:

• Send the call to the application via trunk group (Complicated)
• From a SIP Server that is not the IVR SIP Server define a trunk/trunk group to the IVR SIP Server:
• Create a strategy that will transfer IVR calls to this SIP server under whatever conditions you deem fit
• Once calls transfer to this IVR SIP Server, define an incoming trunk from whatever your source IP would be.  Provide it with the following configurations:
• dial-plan=DP_Trunk_General
• Create a Voice Over IP Service DN named "DP_Trunk_General"
• Configure the Voice Over IP Service DN with the following:
• [TServer]
• dial-plan-rule-1= X!=>GVPDN # This will tell any number 0-9 of any length to be redirected to the object GVPDN
• service-type=dial-plan
• Create a GVP DID DN Object named GVPDN
• In the Annex tab, define the following
• [TServer]
• auto-redirect-enabled=false
• contact=::msml
• oosp-transfer-enabled=false
• refer-enabled=true
• userdata-map-filter=*
• userdata-map-trans-prefix=X-Genesys-*
• sip-uri-params=gvp-tenant-id=[<Tenant>].<IVR Profile Name>

The incoming call will be matched to the trunk, which will redirect the call via dial plan to the GVP DID named "GVPDN".  This, in turn, will trigger your IVR with whatever parameters you've configured in the "GVPDN" object, which should include the specific IVR Profile you're looking to have parse.  This is by far the more complicated of the two setups, and not something I'd recommend unless you're going to transfer ANI/DNIS as part of the attached data payload to your IVR and are normalizing the operation of your IVR that way.

• PlayApplication block in URS routing strategy
• (https://genesyspartner.force.com/customercare/pkb_Home?id=kA4U00000008d7sKAA&l=en_US&fs=Search&pn=1)
• Define the following attached data:
• gsw-ivr-profile-name=<Profile>
• You must do this prior to the Play Application block.
• In the Play Application block:
• Define {s}APP_URI=http://<server>/<path_to_file>/<file>.vxml
• On your IVR trunk or MSML DN (depending on how you're configured)
• userdata-map-filter=X-Genesys-*
• or
• userdata-map-filter=*

​-Ivan