Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
6-8
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 6 Calls Originated by Cisco Unified Communications Manager
KPML Support
[CVP routing client VRU label + correlation-id]: pointing to VXML gateway(s)
For discusions of the Cisco Gatekeeper and the Cisco SIP Proxy Server refer to
and
Sizing
Most customer implementations are not primarily designed for calls originated by Unified CM. The
main driver is usually incoming customer calls, although calls originated by Unified CM are frequently
a component, particularly in the case of warm transfers. Remember to consider those calls when sizing
equipment.
main driver is usually incoming customer calls, although calls originated by Unified CM are frequently
a component, particularly in the case of warm transfers. Remember to consider those calls when sizing
equipment.
Gateways
Calls originated by Unified CM do not use ingress gateways at all. Calls are delivered directly from
Unified CM to the Unified CVP Call Server. They do, however, use VoiceXML gateways whenever a
VRU leg is in use. Therefore, for the purposes of sizing VoiceXML gateways, consider each Unified CM
call that is either in queue or conducting self-service activities.
Unified CM to the Unified CVP Call Server. They do, however, use VoiceXML gateways whenever a
VRU leg is in use. Therefore, for the purposes of sizing VoiceXML gateways, consider each Unified CM
call that is either in queue or conducting self-service activities.
KPML Support
KPML is an out-of-band dtmf method that passes key press information through SIP signaling instead
of through the RTP stream.
of through the RTP stream.
Typical Unified CVP Comprehensive call flows use the inband RFC2833 DTMF configuration on
endpoints. However, there are some endpoints that do not support inband RFC2833, such as the 7985
video phone, and CTI Ports used in UCCE Mobile Agent deployments.
endpoints. However, there are some endpoints that do not support inband RFC2833, such as the 7985
video phone, and CTI Ports used in UCCE Mobile Agent deployments.
For these endpoints, when the destination behind the SIP Trunk is set with RFC2833, Cisco Unified CM
allocates an MTP resource because the line side and the trunk side require a translation of the inband
packets to the out-of-band signaling messages for DTMF.
allocates an MTP resource because the line side and the trunk side require a translation of the inband
packets to the out-of-band signaling messages for DTMF.
To avoid MTP allocation, the destination of the SIP Trunk needs to be configured using the SIP KPML
DTMF method (that is, the No Preference setting). Also, the VXML bootstrap dial peer requires SIP and
KPML settings.
DTMF method (that is, the No Preference setting). Also, the VXML bootstrap dial peer requires SIP and
KPML settings.
The Unified CVP SIP subsystem can pass through Subscribe and Notify events related to KPML DTMF
digits (out-of-band DTMF).
digits (out-of-band DTMF).
MTP Usage on UCM Trunk
When using the UCM SIP Trunk with certain unique call flows, such as Unity Voice Mail or Mobile
Agent, there may be a requirement to use an MTP resource.
Agent, there may be a requirement to use an MTP resource.
The requirement occurs when the negotiated media capabilities of the endpoints do not match, such as
with DTMF in-band versus out-of-band capability. In this case, the UCM may dynamically allocate an
MTP due to the DTMF media capabilities mismatch.
with DTMF in-band versus out-of-band capability. In this case, the UCM may dynamically allocate an
MTP due to the DTMF media capabilities mismatch.
MTP may also be required when interoperating with third party devices.