[asterisk-bugs] [Asterisk 0018611]: inband DTMF cannot be detected and trigger service execute when A and B both use u-law (the same codec)
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 19 10:46:22 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18611
======================================================================
Reported By: shihchuan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18611
Category: Core/RTP
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.8.1.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-01-13 05:04 CST
Last Modified: 2011-01-19 10:46 CST
======================================================================
Summary: inband DTMF cannot be detected and trigger service
execute when A and B both use u-law (the same codec)
Description:
1. A and B both use the same codec (u-law, a-law).
When A enter *96(transfer feature key), transfer service don't be executed
but B hear dtmf tone.
2. If A and B use different codec.(A use u-law, B use a-law)
When A enter *96(transfer feature key), transfer sevice is executed.
======================================================================
----------------------------------------------------------------------
(0130701) lmadsen (administrator) - 2011-01-19 10:46
https://issues.asterisk.org/view.php?id=18611#c130701
----------------------------------------------------------------------
Please re-upload your data as text files attached to the issue and not as
an archive file.
Issue History
Date Modified Username Field Change
======================================================================
2011-01-19 10:46 lmadsen Note Added: 0130701
======================================================================
More information about the asterisk-bugs
mailing list