| Summary: | ASTERISK-29107: IP address in SDP written as hex | ||||
| Reporter: | Morten Sølvberg (Soelvberg) | Labels: | |||
| Date Opened: | 2020-10-05 08:52:17 | Date Closed: | 2020-10-05 09:08:44 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 13.18.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | We experience disconnected calls when re-Inviting due to Session timer.
Finally tracked it down to the IP mentioned in the SDP. In the original Invite, and the first re-invite, the IP is written correctly: v=0 o=- 2020588353 2020588353 IN IP4 10.1.10.91 s=Asterisk c=IN IP4 10.1.10.91 t=0 0 m=audio 58460 RTP/AVP 8 101 - but in the second reInvite suddenly a hex value is shown instead: v=0 o=- 2020588353 2020588353 IN IP4 fe401eb98 s=Asterisk c=IN IP4 fe401eb98 t=0 0 m=audio 58460 RTP/AVP 8 101 The reInvite is then rejected with 415 Unsupported Media Type - which seems fair. Is this a known issue? | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-10-05 08:52:18.844-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/]. | ||||