[asterisk-bugs] [Asterisk 0016292]: [patch] DTMF Not Recognized with Exchange UM

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16292 
====================================================================== 
Reported By:                rsw686
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16292
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.10 
JIRA:                        
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-20 09:53 CST
Last Modified:              2009-11-25 10:11 CST
====================================================================== 
Summary:                    [patch] DTMF Not Recognized with Exchange UM
Description: 
I just upgraded my Asterisk 1.6.1.4 version to 1.6.1.10 and the DTMF tones
are not being recognized by the Exchange UM server. I tested out the RC
release and found that it worked in 1.6.1.7-rc1 and broke in 1.6.1.7-rc2.

What happens is Exchange UM will say to enter your mailbox number. I enter
8532 and it will say that 8 is not a valid entry. It appears Asterisk is
only detecting the first DTMF tone.
====================================================================== 

---------------------------------------------------------------------- 
 (0114278) rsw686 (reporter) - 2009-11-25 10:11
 https://issues.asterisk.org/view.php?id=16292#c114278 
---------------------------------------------------------------------- 
Upon further digging I found in the changelog that there was a new setting
in sip.conf that allows you to disable this new behavior and keep a
constant ssrc. I added constantssrc=true like mentioned in the changelog in
sip.conf and am not getting the expected change. I also tried =false, =yes,
and =no. I'm not sure why this has no affect, but my attached patch
defiantly resolves the problem.

Looks like the logic for constantssrc in sip.conf needs to be fixed and
maybe a note made in UPGRADE.txt that this changes the behavior. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-25 10:11 rsw686         Note Added: 0114278                          
======================================================================