[asterisk-bugs] [Asterisk 0013209]: DTMF RFC2833 via SIP is not working
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Dec 6 10:53:55 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13209
======================================================================
Reported By: ip-rob
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 13209
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.4.21.2
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-07-31 08:23 CDT
Last Modified: 2008-12-06 10:53 CST
======================================================================
Summary: DTMF RFC2833 via SIP is not working
Description:
Using provider bandwidth.com which support RFC2833. Configure outbound
trunk to use dtmfmode=rfc2833 and we receive double digits on a different
asterisk servers IVR. American Express IVR does not accept any digits
(used main customer service line to test entering credit card number).
Other IVR functions do not work.
Changing to inband works but inband should not be required by
bandwidth.com, they support rfc2833.
Configuration is using SIP devices and SIP trunks only. A search in issue
tracker found similar problems in January of 2008 but no currently open
issues.
======================================================================
----------------------------------------------------------------------
(0095901) Yourname (reporter) - 2008-12-06 10:53
http://bugs.digium.com/view.php?id=13209#c95901
----------------------------------------------------------------------
Guys, I think we've provided enough information to the Asterisk developers
to get this rectified. Although I think it's taken too long and it's still
not responded to (leave alone fixed), maybe we should now give it a rest
and wait for some response.
At this point, I doubt they need more info than more time to fix it. May
the force be with with developers.
Issue History
Date Modified Username Field Change
======================================================================
2008-12-06 10:53 Yourname Note Added: 0095901
======================================================================
More information about the asterisk-bugs
mailing list