| Summary: | ASTERISK-29052: res_pjsip_session: Deferred re-INVITE without SDP results in a=sendonly | ||
| Reporter: | Patrick Verzele (n0tiz) | Labels: | |
| Date Opened: | 2020-08-28 08:26:24 | Date Closed: | 2020-09-03 08:16:41 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip_session |
| Versions: | 16.12.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Centos 7 with asterisk 16.12.0 Archlinux with asterisk 16.12.0 | Attachments: | ( 0) extensions.conf ( 1) packet_trace_broken_sdp.pcap ( 2) packet_trace_patched_sdp.pcap ( 3) pjsip.conf ( 4) uac.xml ( 5) uas.xml |
| Description: | This is related to ASTERISK-25854
When the device requests hold by sending SDP with attribute recvonly, asterisk correctly places the session in sendonly mode. When the device later requests to resume the call with a deferred re-INVITE excluding SDP, asterisk continues in sendonly mode, however it should return to sendrecv, and allow the device to decide further. The current result with PJSIP is for a one-way audio stream. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-08-28 08:26:26.085-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. By: Patrick Verzele (n0tiz) 2020-08-28 08:27:27.466-0500 Adding sipp test scenarios, and my extensions.conf and pjsip.conf By: Patrick Verzele (n0tiz) 2020-08-28 08:32:15.987-0500 Adding packet trace of the broken SDP. Adding packet trace of patched SDP. Also adding patch to get the correct SDP. By: Joshua C. Colp (jcolp) 2020-08-28 08:46:41.420-0500 As the patch was not marked as a contribution I've had to remove it. If you fill out the license agreement you can then upload it, and also put it up for review for inclusion. By: Patrick Verzele (n0tiz) 2020-08-28 10:01:36.175-0500 Signed the license agreement, waiting for e-mail notification of approval. By: Patrick Verzele (n0tiz) 2020-09-01 11:54:16.977-0500 I've submitted the patch for review in branches 13, 16, 17, 18, master. | ||