Cisco Cisco Unified Customer Voice Portal 10.0(1)
8-11
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Chapter 8 VoIP Configuration
Call Transfers and Outbound Routing
dial-peer voice 5 pots
* \ Routes calls to a third trunk group
destination-pattern 888802….
port 2:1
preference 0
destination-pattern 888802….
port 2:1
preference 0
dial-peer voice 6 pots
* \ Backup voice port for third trunk group
destination-pattern 888802….
port 2:2
preference 1
destination-pattern 888802….
port 2:2
preference 1
h323-gateway voip tech-prefix 1# * \ Registers the GW with the GK with the tech-prefix 1#
To define the codec to be used during the transfer:
dial-peer voice <some label> voip
incoming called-number 888800….
codec g729r8
Note
If necessary, more dial-peers may be added for additional destination patterns.
Label Definition for Outpulse Transfer
Labels for ISN calls which will require outpulse transfer mode must be pre-pended with the characters
DTMF. By configuring the target label with the form DTMFnnnnn (where nnnnn are the digits to
outpulse) the ISN will send the digits to the ingress endpoint for outpulsing.
DTMF. By configuring the target label with the form DTMFnnnnn (where nnnnn are the digits to
outpulse) the ISN will send the digits to the ingress endpoint for outpulsing.
For example, to use the AT&T Transfer Connect feature to transfer the call to the number “4441234” the
label would be configured as DTMF*84441234.
label would be configured as DTMF*84441234.
Note
In outpulse transfer mode, the ISN will send whatever digits are in the label to the Gateway for
outpulsing. It is the customer’s responsibility to confirm interoperability with the target switch.
outpulsing. It is the customer’s responsibility to confirm interoperability with the target switch.
Codec Support
There is a codec used for IVR prompting in ISN and a codec used for transfers (actually it is possible,
though not likely, that a different codec could be used by each transfer during the life of a call). As
depicted in the examples above, the ingress gateway dial-peer was configured for all possible codecs that
may be used in the life of the call (in this case we limited it to g711alaw, g711ulaw and g729r8).
though not likely, that a different codec could be used by each transfer during the life of a call). As
depicted in the examples above, the ingress gateway dial-peer was configured for all possible codecs that
may be used in the life of the call (in this case we limited it to g711alaw, g711ulaw and g729r8).
Codec Support differs somewhat between ISN Queue and Transfer mode and ISN Comprehensive mode.
Queue and Transfer: All prompts are played by the ISN Voice Browser. Therefore, it is the ISN Voice
Browser itself which defines the IVR codec through the SetCodec CLI command. It is the egress gateway
dial-peer that defines the codec that will be used during the transfer. In our example above, we chose
g729r8.
Browser itself which defines the IVR codec through the SetCodec CLI command. It is the egress gateway
dial-peer that defines the codec that will be used during the transfer. In our example above, we chose
g729r8.