Cisco Cisco Customer Voice Portal 8.0(1)

h.

Click: Save

Configuration on your TDM Ingress gateway(s).

a.

For voice class code x (where x is some number), add g722-64 as the preferred codec and
add g711ulaw as a secondary codec.

Example:

 voice class codec 1

  codec preference 1 g722-64

  codec preference 2 g711ulaw

b.

On the voip dial peer(s), add the voice class you configured for G.722

Example:

 dial-peer voice XXXXX voip

 description CVP SIP Comprehensive dial-peer

  destination-pattern XXXXXXXX

  session target XXXXXXX

  session protocol sipv2

  dtmf-relay rtp-nte h245-signal h245-alphanumeric

  voice-class codec 1

  no vad

!

dial-peer voice XXXXXXX pots

 description CVP TDM dial-peer

 service survivability

KPML Support

Starting in release 8.0(1), Unified CVP supports Key Press Markup Language (KPML) for SIP.
KPML is a SIP feature that enables monitoring of DTMF signals "out-of-band" (OOB), as
opposed to the (RFC2833) in-band DTMF monitoring method that Unified CVP typically uses.

Not all endpoints (such as CTI Ports) support in-band DTMF monitoring. For these endpoints,
the "DTMF Signaling Method" on the SIP Trunk can be set with RFC2833. In this case, the
Unified Communications Manager must allocate an MTP resource to translate DTMF from the
in-band packets to the OOB signaling for the end points that do not support in-band DTMF.

Using KPML enables you to avoid having to set RFC2833 on the SIP trunk (and thus having
Unified CM dynamically allocate an MTP resource due to the DTMF mismatch on endpoints).
Instead, you set the DTMF Signaling Method to no preference on the SIP trunk and set the
bootstrap dial-peer on the gateway to use SIP and KPML.

 (http://www.cisco.com/

Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 8.0(1)