When a user calls Unity Connection directly and unexpectedly hears the Opening Greeting or another prompt rather than the sign-in prompt, the problem can be caused by either of the following: Users Do Not Hear Sign-in or Desired Prompt When Calling Unity Connection On the Edit Advanced Settings page, verify that the Use DTMF KPML and Use DTMF RFC 2833 check boxes are checked. On the Port Group Basics page, navigate to Edit > Advanced Settings. On the Search Port Groups page, select the port group of which you want to verify the DTMF settings. In Cisco Unity Connection Administration, navigate to Telephony Integrations > Port Group. Repeat Step 1 and Step 2 for all remaining VoIP dial-peers servicing Unity Connection.What to do next
For example, if the system has voicemail ports 1001 through 1016, enter the dial-peer destination pattern 10xx. On a VoIP dial-peer servicing Unity Connection, use the following command:dtmf-relay h245-alphanumericĬreate a destination pattern that matches the Cisco Unified CM voicemail port numbers. However, in the Catalyst 6000 T1/PRI and FXS gateways, DTMF relay is enabled by default. In Cisco IOS software-based gateways that use H.245 out-of-band signaling, you need to enable DTMF relay. 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 such situations, DTMF digits are not recognized when processed through VoIP dial-peer gateways. When Unity Connection is integrated with Cisco Unified Communications Manager using SCCP, Unity Connection may not respond to key presses. Unity Connection Not Responding to Key Presses
0 kommentar(er)
