Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

With SIP, the equivalent of the SetTransferLabel command is the Send to Originator configuration under 
the SIP Service. If the Network VRU label is 5551000, the Send to Originator pattern would be 
5551000>. The > is a wildcard pattern representing one or more digits. The SIP Service determines the 
originating gateway by looking at the Remote-Party-ID header in the SIP INVITE message.

Other wildcard characters can be used. Refer to the topic Valid Formats for Dialed Numbers in the 
Operations Console online help for complete wildcard format and precedence information.

In this configuration, the gateway that processes the incoming call from the PSTN is separated from the 
Unified CVP servers by a low-bandwidth connection such as a WAN, and the VoiceXML gateway that 
is used is different than the ingress gateway but located at the same site as the ingress gateway. The 
purpose of this configuration is to keep the media stream at the same site and not consume bandwidth 
on the WAN and to optimize VoiceXML gateway sizing when it is appropriate to separate ingress and 
VoiceXML gateways. In this case, setTransferLabel and Send to Originator cannot be used because you 
would not want the IVR leg of the call to go back to the ingress gateway. Additionally, it is also 
impractical to use a gatekeeper or SIP Proxy to control the call routing because you would have to 
configure separate Network VRUs, Network VRU labels, and customers in ICM for each remote site. 
Instead, use SetSigDigits functionality.

With this method, the Call Server strips the leading significant digit(s) from the incoming DNIS number. 
The value that is stripped is saved and prepended when subsequent transfers for the call occur.

When H.323 is used, the significant digit is prepended with a # sign so that the gatekeeper treats it as a 
technology prefix. The VoiceXML gateway at the remote site should register to the gatekeeper with the 
same technology prefix as the leading significant digit(s) that were stripped from the DNIS number. The 
gatekeeper then routes the IVR leg of the call to the correct VoiceXML gateway. If you are using Cisco 
Unified Communications Manager (Unified CM), remember that Unified CVP indiscriminately 
prepends the sigdigits value to all transfers, including those to Unified CM. Therefore, when using 
Unified CM in this scenario, it is necessary to define a gatekeeper-controlled trunk for each of the 
VoiceXML gateway tech-prefixes and to add zone prefix configuration to the gatekeeper for the 
Unified CM agents, as illustrated in the following example.

dial-peer voice 1000 voip

 tech-prefix 2#  (gets the call to CVP)

 translate-outgoing called 99

Apply a translation-rule to the incoming DNIS number to prepend the value 3:

translation-rule 99

 Rule 1 8002324444 38002324444

Assuming the DNIS number is 8002324444, the final DNIS string routed to Unified CVP is 
2#38002324444.

setTechPrefix 2#