| Summary: | ASTERISK-26636: pjsip stopped workinh on lastest update | ||||
| Reporter: | Private Name (falves11) | Labels: | |||
| Date Opened: | 2016-12-03 12:54:32.000-0600 | Date Closed: | 2016-12-03 13:00:47.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
| Versions: | 13.13.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Linux 64 | Attachments: | ( 0) asterisk-bug.txt | ||
| Description: | There is a mistake on version 13.13.0. I have an application on a multihomed box, the calls ingress via one IP and egress via the second IP. It does not work with version 13.13.0.
[Dec 3 18:31:56] DEBUG[188823]: rtp_engine.c:454 ast_rtp_instance_new: Using engine 'asterisk' for RTP instance '0x7fd0080046e0' [Dec 3 18:31:56] WARNING[188823]: res_rtp_asterisk.c:2400 create_new_socket: Unable to allocate RTP socket: Address family not supported by protocol [Dec 3 18:31:56] WARNING[188823]: res_rtp_asterisk.c:2665 ast_rtp_new: Failed to create a new socket for RTP instance '0x7fd0080046e0' [Dec 3 18:31:56] DEBUG[188823]: rtp_engine.c:458 ast_rtp_instance_new: Engine 'asterisk' failed to setup RTP instance '0x7fd0080046e0' [Dec 3 18:31:56] DEBUG[188823]: rtp_engine.c:397 instance_destructor: Destroyed RTP instance '0x7fd0080046e0' [Dec 3 18:31:56] ERROR[188823]: res_pjsip_sdp_rtp.c:184 create_rtp: Unable to create RTP instance using RTP engine 'asterisk' [Dec 3 18:31:56] DEBUG[188823]: res_pjsip_session.c:2494 handle_outgoing_response: Method is INVITE, Response is 488 Not Acceptable Here I repeat, if I compile version 13.12.2, ceteris paribus, the app works fine. I am uploading a trace | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-12-03 12:54:34.317-0600 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) 2016-12-03 12:54:34.760-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: Private Name (falves11) 2016-12-03 13:16:54.907-0600 Sorry for the question, should we wait for new release 13.13.1? A patch was committed for this issue. What comes next? By: Asterisk Team (asteriskteam) 2016-12-03 13:16:55.129-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2016-12-03 13:26:20.811-0600 A point release has not yet been decided. If it occurs it will be done next week, and your issue has been noted in regards to it. | ||||