Summary:	ASTERISK-29716: Dtmf Problem With Payload 96
Reporter:	Leonardo Cella (leocella)	Labels:
Date Opened:	2021-11-02 06:38:42	Date Closed:	2021-11-02 06:38:43
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	. I did not set the category correctly. Core/RTP
Versions:	18.4.0 19.0.0	Frequency of Occurrence
Related Issues:
Environment:	Debian 10	Attachments:
Description:	I've installed asterisk 19 and I use pjsip. My voip provider gives me the dtmp with rtp payload 96 and the dtmf doesn't works. With other providers that send them with rtp payload 101 the dtmf works. In the sources, in the main / rtp_engine.c file I found add_static_payload (96, ast_format_slin192, 0). How can I make the digits work when they arrive with rtpmap 96?
Comments:	By: Asterisk Team (asteriskteam) 2021-11-02 06:38:43.479-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2021-11-02 06:38:45.370-0500 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2021-11-02 06:38:45.645-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].