[asterisk-bugs] [Asterisk 0016292]: [patch][regression] 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:                   block
Priority:                   normal
Status:                     ready for testing
Target Version:             1.6.1.19
Asterisk Version:           SVN 
JIRA:                       SWP-463 
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:              2010-03-12 18:58 CST
====================================================================== 
Summary:                    [patch][regression] 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0119319) twilson (administrator) - 2010-03-12 18:58
 https://issues.asterisk.org/view.php?id=16292#c119319 
---------------------------------------------------------------------- 
Ok, the constantssrc stuff was just a broken idea in general. It has been
fixed so that the default behavior is to never change the ssrc unless we
see the other side has changed it.  If you update to the latest 1.4, 1.6.0,
1.6.1, 1.6.2 or trunk from svn, this will probably be fixed. rsw686 can you
confirm? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-12 18:58 twilson        Note Added: 0119319                          
======================================================================