| Summary: | ASTERISK-28184: Asterisk hangs up receiving unexpected frame format | ||||
| Reporter: | Denis Lebedev (coredumped) | Labels: | pjsip | ||
| Date Opened: | 2018-11-27 04:31:57.000-0600 | Date Closed: | 2020-01-14 11:13:39.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 15.4.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | CentOS Linux 7 (Core) Linux *** 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Asterisk versions: 15.4.0 | Attachments: | ( 0) pjsip.conf | ||
| Description: | 2 days in a row we have the following problem.
Asterisk receives {{g729}} frames from our partner while allowed formats are {{alaw,ulaw}}. Logfile contains the following: {noformat} ... Channel PJSIP/partner-000164c6 asked to send alaw frame when native formats are (g729) (rd:g729->g729; wr:alaw->alaw;) (chan_pjsip.c:927) ... HTTP session count exceeded 100 sessions. (http.c:1910) {noformat} Right after that asterisk stops to process incoming traffic, takes up all free memory. Unfortunately we don't have any additional info (no core dumps or any other stuff) because we're forced to restart asterisk. {{pjsip.conf}} attached. What can we do with it? | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-11-27 04:31:58.832-0600 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 C. Colp (jcolp) 2018-11-27 05:00:43.019-0600 You have two issues, the RTP one is already reported in the linked issue. The HTTP one you'd need to provide more information, such as what you are using HTTP for. By: Denis Lebedev (coredumped) 2018-11-27 05:25:09.096-0600 Joshua, thanks a lot. We'll test {{asymmetric_rtp_codec=yes}} option. {{HTTP}} errors in our logs are the consequence rather than the cause. By: Asterisk Team (asteriskteam) 2018-12-11 12:00:02.048-0600 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 | ||||