Cisco Cisco Customer Voice Portal 8.0(1)
key 8 target-destination cvp-call-servers.cisco.com netA
key 7 target-destination vxml-gws.cisco.com netA
key 700699 target-destination cvp-call-servers.cisco.com netA
key 2 target-destination cucm-cluster.cisco.com netA
key 1 target-destination cucm-cluster.cisco.com netA
key 7000 target-destination 172.19.151.41 netA
key 777333 target-destination cvp-call-servers.cisco.com netA
key 1004 target-destination 10.86.139.84 netA
key 7105 target-destination dialer-gws netA
end route table
!
policy lookup cvp-policy
sequence 1 cvp-route-table request-uri uri-component user
rule prefix
end sequence
end policy
!
trigger routing sequence 1 by-pass condition mid-dialog
trigger routing sequence 10 policy cvp-policy condition in-netA
!
server-group sip ping-options netA 10.86.129.200 5038
method OPTIONS
ping-type adaptive 5000 10000
timeout 500
end ping
!
server-group sip global-ping
sip listen netA udp 10.86.129.200 5060
!
end
REFER Transfers Using "RFXXXX" Type Unified ICME Labels
Unified CVP SIP Service can perform a SIP REFER transfer instead of using SIP re-invites,
which allows Unified CVP to remove itself from the call, thus freeing up licensed Unified CVP
ports. (Unified CVP cannot execute further call control operations after this kind of label has
been executed; for example, it cannot perform subsequent transfers back to Unified CVP for
self service or queuing to another agent.)
which allows Unified CVP to remove itself from the call, thus freeing up licensed Unified CVP
ports. (Unified CVP cannot execute further call control operations after this kind of label has
been executed; for example, it cannot perform subsequent transfers back to Unified CVP for
self service or queuing to another agent.)
However, if the transfer fails, configure survivability to transfer the call elsewhere. This process
is not the same as an ICM router requery; for example, as it will appear as a new call to Unified
ICME, but it is a way to take an alternate action, if the transfer fails.
is not the same as an ICM router requery; for example, as it will appear as a new call to Unified
ICME, but it is a way to take an alternate action, if the transfer fails.
Note:
• This feature can be used in Comprehensive (SIP only), Call Director, and Standalone call
flow models.
• Router requery can be performed with a REFER transfer only if the NOTIFY messages are
sent back to Unified CVP with the result of the REFER operation. Since Unified CVP does
not hang up the call after sending REFER, it is possible to requery Unified ICM and get
another label, and send another REFER.
not hang up the call after sending REFER, it is possible to requery Unified ICM and get
another label, and send another REFER.
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 8.0(1)
351
Chapter 11: Configuring the SIP Devices
REFER Transfers Using "RFXXXX" Type Unified ICME Labels