DTMF problem with Cisco 7300 VOIP gateway

I am taking in a call from a VOIP customer through a Cisco 7300 and terminating this out to a Tier 1 carrier.  It appears the the DTMF tones are being distorted or not recognized and the problem is arising in my Cisco.  I have heard that it is recommended that I use g711, unfortunately this is not possible.  I have also ensured that the command:  dtmf-relay h245-alphanumeric is being used in the corresponding dial-peer.  Can anyone help me with this problem?  Any input is gladly appreciated.

Who is Participating?
shadeytreesConnect With a Mentor Author Commented:
I found the answer.  I just added  "rtp-nte sip-notify" to my "dtmf-relay  h245-signal  h245-alphanumeric"  string in the customers dial-peer and DTMF passed without fault.  teh command looks as follows:

dial-peer voice 1 voip
dtmf-relay rtp-nte h245-signal sip-notify h245-alphanumeric

Router(config-dial-peer)# dtmf-relay rtp-nte
Allows DTMF relay using NTE RTP packets. DTMF tones are encoded in the NTE format and transported in the same RTP channel as the voice.

  Thanks all for your tips.

Alex BaharCommented:
Hi Chris,
With the limited information provided, it is not possible to provide a solution.
Can you provide details about your network topology end-to-end? Please describe the voip endpoints between the caller and called parties, and the the type of signalling types used along the path. Then provide your router's voip configuration, including transcoders etc.
shadeytreesAuthor Commented:
Thanks for your attention Abahar,

This is an Internet VOIP connection using SIPv2 the customer has a Sonus and is sending DTMF tones to my cisco 7300 (C7301-ADVENTERPRISEK9-M), Version 12.4(11)T4 we then pass the call onto a Sansay VSX-S2-2U integrated session switch which then is connected to the local PTT though a cisco 5300.  The calls seem to work fine when I test from a Cisco 2600>Cisco 7300>Sansay>Cisco 5300>PTT.  However calls from the Sonus to my network do not pass DTMF, but they do through the second providers network.  Any thoughts?
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Alex BaharConnect With a Mentor Commented:
Apparently there are some RTP timestamp issues communicating with Sonus gateways.
On Cisco I have found The following explanantion. But this bug CSCtd68173 seems to be for the opposite direction. Cisco DTMF is not recognized by Sonus.
Timestamp not accurate in the DTMF sent by CME Symptoms: Outbound DTMF may fail intermittently over a SIP Trunk from Cisco
UC 500.

Conditions: This symptom is observed when the following conditions are
- Using Cisco IOS Release 12.4.22YB4 or Release 15.0.1XA on Cisco UC 500
- SIP trunk uses RFC2833 for DTMF
- Call is outbound from Cisco IP Phone to PSTN over SIP Trunk
- SIP Trunk provider gateway is Sonus GXS (v6.4).

- Use Cisco IOS Release 12.4(11)XW10 on the Cisco UC 500 if possible; or,
- SIP trunk provider Sonus GXS gateway should be upgraded to v6.5.5 or higher.
I had found this explanation on http://wiki.freeswitch.org/wiki/RTP_Issues there is an Asterisk patch for Sonus as well.
Sonus wrongly expects that, when sending a multi-packet 2833 DTMF event, the sender should
increment the RTP timestamp in each packet when, in reality, the sender should send the
same exact timestamp and increment the duration field in the 2833 payload. This allows a
reconstruction of the duration if any of the packets are lost.

final_duration - initial_timestamp = total_samples

However, if the duration value exceeds the space allocated (16 bits), the sender should
increment the timestamp one unit and reset the duration to 0.

Always sending a duration of 0 with a new timestamp should be tolerated but is rarely
intentional and is mistakenly done by many devices. The issue is that the Sonus expects
everyone to do it this way instead of tolerating either way. Sonus will actually ignore
every packet with the same timestamp before concluding if it's DTMF.
shadeytreesAuthor Commented:

  I appreciate your insight into this.  My customer with the Sonus gateway is investigating this now.  I will advise upon our correspondence.  Thank you again for you assistance this is very helpful.

Alex BaharCommented:
Hi Chris,
I hope it is caused by a software issue and upgrading the software will get it working. Fingers crossed.
Alex BaharCommented:
Hi Chris,
Thanks for sharing the solution. I am sure other people will find that useful as well.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.