Unity Connection Not Responding to Key Presses
When Unity Connection is integrated with Cisco Unified Communications Manager using SCCP, Unity Connection may not respond to key presses. In such situations, DTMF digits are not recognized when processed through VoIP dial-peer gateways. To avoid this problem, certain gateways must be configured to enable DTMF relay available in Cisco IOS software version 12.0(5) and later.
In Cisco IOS software-based gateways that use H.245 out-of-band signaling, you need to enable DTMF relay. However, in the Catalyst 6000 T1/PRI and FXS gateways, DTMF relay is enabled by default.
Enabling DTMF Relay
Procedure
Step 1 |
On a VoIP dial-peer servicing Unity Connection, use the following command: dtmf-relay h245-alphanumeric |
Step 2 |
Create a destination pattern that matches the Cisco Unified CM voicemail port numbers. For example, if the system has voicemail ports 1001 through 1016, enter the dial-peer destination pattern 10xx. |
Step 3 |
Repeat Step 1 and Step 2 for all remaining VoIP dial-peers servicing Unity Connection. |
Verifying DTMF settings
Procedure
Step 1 |
In Cisco Unity Connection Administration, navigate to Telephony Integrations > Port Group. |
Step 2 |
On the Search Port Groups page, select the port group of which you want to verify the DTMF settings. |
Step 3 |
On the Port Group Basics page, navigate to Edit > Advanced Settings. |
Step 4 |
On the Edit Advanced Settings page, verify that the Use DTMF KPML and Use DTMF RFC 2833 check boxes are checked. |