[asterisk-bugs] [Asterisk 0016292]: [patch][regression] DTMF Not Recognized with Exchange UM
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jan 5 10:48:17 CST 2010
The following issue has been UPDATED.
======================================================================
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: closed
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:
Resolution: fixed
Fixed in Version: 1.6.1.12
======================================================================
Date Submitted: 2009-11-20 09:53 CST
Last Modified: 2010-01-05 10:48 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.
======================================================================
----------------------------------------------------------------------
(0116064) lmadsen (administrator) - 2010-01-05 10:48
https://issues.asterisk.org/view.php?id=16292#c116064
----------------------------------------------------------------------
Closing this issue as the reporter states DTMF is fixed in a later version.
For the faxing issue, please look to see if a later version (i.e. from SVN
directly from the branch) has fixed your issue. If not, please search for
an existing fax issue that matches your problem, or if not found, open a
new issue for tracking fax.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-05 10:48 lmadsen Note Added: 0116064
2010-01-05 10:48 lmadsen Status ready for testing =>
closed
2010-01-05 10:48 lmadsen Resolution open => fixed
2010-01-05 10:48 lmadsen Fixed in Version => 1.6.1.12
======================================================================
More information about the asterisk-bugs
mailing list