| Summary: | ASTERISK-28688: Matching SIP TCP peer by IP with insecure=port regression | ||||
| Reporter: | rsw686 (rsw686) | Labels: | |||
| Date Opened: | 2020-01-13 21:14:10.000-0600 | Date Closed: | 2020-01-14 05:02:41.000-0600 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | Channels/chan_sip/TCP-TLS | ||
| Versions: | 13.21.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | The changes in ASTERISK-27457 create a regression where invites from a SIP TCP peer are matched by IP and port even though insecure=port,invite is configured. Reverting this commit on Asterisk 13.21-cert5 restores the expected behavior. Prior to this I was running 13.8-cert4 which correctly matched a TCP peer by IP ignoring the port. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-01-13 21:14:11.214-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]. 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: rsw686 (rsw686) 2020-01-13 21:30:43.043-0600 I just realized this was fixed by ASTERISK-27881. Any chance this can get included into the next certified asterisk 13.21 release? By: Joshua C. Colp (jcolp) 2020-01-14 05:02:41.634-0600 Certified releases only receive changes as a result of issues filed by support agreement customers. If you have a support agreement please contact Sangoma Technical Support to create an official ticket so it can go through the proper process. If you do not have a support agreement then we are unable to include the change. By: Joshua C. Colp (jcolp) 2020-01-14 05:03:05.515-0600 I should also add that certified 16.3 has been released, and certified 13.21 is unlikely to receive any further updates or releases. | ||||