Summary:	ASTERISK-11247: DTMF received through rfc2833 having double digits, missing digits, wrong information
Reporter:	unservices (unservices)	Labels:
Date Opened:	2008-01-16 10:05:41.000-0600	Date Closed:	2008-01-16 10:18:08.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	We have a sip trunk connected with a origination/termination provider. We receive and make calls through SIP, therefore no dialogic cards or any other trunks are directly connected to our server. Everything in registration, authentication, answering, dialing out and talking/voice are working fine. They do support ulaw, alaw and g729 codecs. When calling from a standard phone into their SIP, if we press digits in the standard phone we get erratically them in the asterisk. Sometimes is better, sometimes worse. Obviously we tested with different standard phone lines and phone device. Sometimes we have a digit that we pressed once appearing 2 or 3 times, other times a digit is missing. The dtmfmode=rfc2833, they don't seem to support inband (at least, when we turn inband nothing comes in). To our understanding, with the rfc2833 the dtmf detection would be on their side, and any de-bouncing would be done there. They have sonus switches and keep saying everything is okay on their end. So we are basically looking into a mod/diff that might be able to adjust better the dtmf detection in our end through rfc2833, if possible.
Comments:	By: Jason Parker (jparker) 2008-01-16 10:18:08.000-0600 Closing, as 1.2 is in security maintenance mode.  Only security related bug fixes will be looked at. Also, the DTMF situation is immensely better in 1.4.