[Home]

Summary:ASTERISK-28027: Call Setup Crash ILBC -> ULAW
Reporter:Joshua Elson (joshelson)Labels:
Date Opened:2018-08-27 13:59:52Date Closed:2020-01-14 11:14:02.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:15.2.2 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:Attachments:( 0) core.den-media-10.2018-08-27T11-08-45-0600-brief.txt
( 1) core.den-media-10.2018-08-27T11-08-45-0600-full.txt
( 2) core.den-media-10.2018-08-27T11-08-45-0600-locks.txt
( 3) core.den-media-10.2018-08-27T11-08-45-0600-thread1.txt
Description:Have seen several crashes on call setup with ILBC -> ULAW with dialplan output of the following:

[2018-08-27 11:08:45] VERBOSE[11774][C-00000486] app_dial.c: Called PJSIP/3035551212@FC-DFW-PROXY
[2018-08-27 11:08:45] WARNING[11774][C-00000486] translate.c: no samples for ilbctolin
[2018-08-27 11:08:45] VERBOSE[21350] netsock2.c: Using SIP RTP Audio TOS bits 184
[2018-08-27 11:08:50] Asterisk 15.2.2 built by root @ den-media-99.com on a x86_64 running Linux on 2018-08-22 17:43:49 UTC
Comments:By: Asterisk Team (asteriskteam) 2018-08-27 13:59:54.225-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.

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].
By: Joshua Elson (joshelson) 2018-08-27 14:00:24.158-0500

Backtrace attached
By: Benjamin Keith Ford (bford) 2018-08-29 14:24:30.557-0500

I could not reproduce this with an ILBC endpoint calling a ULAW endpoint, and the nothing seems out of the ordinary in the backtrace. What phones are you using to produce the crash? Are you able to get any other details about the call setup, or is it an immediate crash? Does this happen every time an ILBC endpoint attempts to call ULAW endpoints? Also, what is the output of "core show translation paths ilbc" (and same for ulaw)? What does your dialplan look like for this scenario?
By: Asterisk Team (asteriskteam) 2018-09-13 12:00:01.310-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines