DTMF not working/being stripped

[amriddle01]

Has anyone seen this issue, It is a 500 running v4.0.5 software and 8 channels on PRI, from any handset making an outgoing call you cannot send DTMF to make menu selections etc!! AS far as I know thtere is no setting to stop this by default...any ideas? Any help appreciated!!

 

[intrigrant]

CQ 35590 DTMF digits pressed during call are added to the re-dial number
CQ 35536 SIP RFC2833 DTMF transport fails when call transferred over the same SIP trunk
CQ 52146 SIP problems with HOLD and inband DTMF - RFC2833 dropped from negotiation after un-HOLD
CQ 47028 Cloned from ipo throws away the DTMF across scn VOIP line unless out of band is selected for line
CQ 42687 IP-Phones with direct media: No DTMF inband signalization of dialed digits (always send outband)

These will be fixed in the next 4.0 GA release

 

[amriddle01]

Solved it!!!! You need to power down the DS expansion modules then the main unit. Then power up expansion modules one at a time then the main unit finally do a immediate reboot and it works. Thanks all for your contributions!!!

 

[binxwalker]

This is a problem with the way that Avaya has implemented SIP, not a problem with your SIP trunking provider. They do not have the appropriate expertise in the IPO group to understand the RFCs, so they have made errors in their interpretation of the SIP RFCs, one of them being how DTMF volume levels are identified and transmitted. They have implemented DTMF volume backwards, but refuse to admit that they have made an error even though it is very clear that they have! Because of their unwillingness to admit their errors and work with the top SIP providers, customers are limited to a small group of providers, most of whom are either too small (AGN) or too big (AT&T-is there anyone who thinks that AT&T would be a good choice for SIP trunking for their customers?) to be a reasonable option. Also, if you have read any of the forum threads regarding the issues with turning-up any of these providers, you know that Avaya does not have their act together. To add insult to injury, Avaya wants potential SIP trunking providers to pay them $20,000 for the honor of working with them!!! If you have a customer that wants to implement SIP, be very wary of making any commitments of audio quality or even being able to successfully turn-up the service at all because there are too many compatibility issues between Avaya and the SIP RFCs.