Cisco Cisco Unified Customer Voice Portal 10.5(1)
8-19
Cisco Customer Voice Portal (CVP) Release 3.0(0) Configuration and Administration Guide
Chapter 8 VoIP Configuration
CVP Endpoint Limitations
Step 4
Define at lease one other dial-peer with lower preference (preference 1) that uses a static CVP voice
browser address instead of a gatekeeper lookup (e.g. session target ipv4:10.86.137.68).
browser address instead of a gatekeeper lookup (e.g. session target ipv4:10.86.137.68).
Call Manager
Step 1
Under Device > Gatekeeper, set the gatekeeper name to the HSRP VIP of the gatekeeper failover pair.
Step 2
Set “Registration Request Time to Live” to 30 seconds. Set “Registration Retry Timeout” to 30 seconds.
.
ICM Script
Step 1
Enable the router requery on all “Queue to Skill Group” nodes.
Step 2
Coming off the X path from the Queue to Skill Group node, add an “IF” node that checks the value of
the variable Call.RequeryStatus. If the value is 1, play a 60 second prompt and go to a second “Queue
to Skill Group” node. If the value is not “1”, immediately go to the second “Queue to Skill Group Node”.
the variable Call.RequeryStatus. If the value is 1, play a 60 second prompt and go to a second “Queue
to Skill Group” node. If the value is not “1”, immediately go to the second “Queue to Skill Group Node”.
IP Transfer Example (IPCC Routing)
An IP transfer to an IPCC agent is very similar to an IP transfer to an ACD (TDM) agent with the
following exceptions:
following exceptions:
•
The egress Gateway for this case is a Call Manager. In the Gatekeeper, the agent extensions are
configured to point to the Call Manager’s IP address.
configured to point to the Call Manager’s IP address.
•
When Call Manager receives the new call, it uses the “Skinny protocol” to connect to the agent at
an IP phone. The voice channels are then connected from the ingress Gateway to the IP phone.
an IP phone. The voice channels are then connected from the ingress Gateway to the IP phone.
CVP Endpoint Limitations
Table 8-2
CVP Endpoint Limitations
Limitation
Description
Gatekeeper single point failure.
If a Gatekeeper fails and no hot standby is configured, the
following features of call routing will be affected:
following features of call routing will be affected:
•
If Gatekeeper is used for inbound call routing, it is not
clear which Voice Browser would route the call to.
clear which Voice Browser would route the call to.
•
No switch transfers will succeed.
Registering to different H.323 zones on a
single Gatekeeper is not implemented.
single Gatekeeper is not implemented.
The Voice Browser is lacking a parameter that would
permit it to register into different zone on the same physical
Gatekeeper box.
permit it to register into different zone on the same physical
Gatekeeper box.