DTMF fails towards the telco using SIP trunk

[Eivind Jonassen]

Hi,

I´ve having some difficulties with a telco who uses Sonus GW. DTMF doesn´t work. The telco is reffering to this document;

http://supportwiki.cisco.com/ViewWiki/index.php/The_DTMF-relay_of_the_Cisco_CallManager_SIP_trunk_fails_to_work_with_the_SIP_VoIP_Telco_because_the_terminating_side_does_not_receive_the_DTMF_digits

I see that this is related to version 4.1 of the callmanager and don´t know if this is in any way related to UC500 ver 7.0.3

Any help or suggetions on how to relsolv this would be great.

Thanks,

Eivind

[Maulik Shah]

Hi Eivind

   When they say it fails to agree with Sonus on RFC2833 - what is the exact behavior? Do you traces etc? I think I showed in my previous post that changing the payload type works fine for me as long as the right dial peer is chosen. Also, we have tested internally with various SPs in the drop down that use Sonus and RFC2833 and seen no issues there. Seems to me like there is a config issue on Sonus or UC500 but unless I can get some detailed info its hard to nail this down.

[Eivind Jonassen]

Maulik,

I'm not allowed by the SP to post the debugs here. Could you please provide your email in a PM??

Thanks

Eivind

Message was edited by: Eivind Jonassen

[Eivind Jonassen]

Update from Maulik,

The log shows this:

//212/0984D90280E7/SIP/Media/sipSPIAddSDPMediaPayload:                                                     

Preferred method of dtmf relay is: 6 but the payload value 100 is already used for NSE, so DTMF-RELAY method will not be advertised

which implies the NSE payload type was not moved from 100 to 105 in the UC500 config. What IOS is this? Can they send a capture of when they configure this on the UC500 if any errors show up and the complete show run after they have configured the box. I have this working on my UC500 as mentioned before so its puzzling to me.

Thanks

Maulik

[Eivind Jonassen]

Maulik,

The telco has provided a workaround on the Sonus. So problem solved.

One thing I noticed is that they used ver4.2 IOS (a XW version, can´t quite remember which one) and 7.0.3 for the phone loads, I asked them to do the upgrade on the IOS and CUE so that they had a complete 7.0.3 version, but they made a workaround instead.

Thanks,

Eivind