[asterisk-bugs] [JIRA] (ASTERISK-28688) Matching SIP TCP peer by IP with insecure=port regression

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Jan 13 21:15:25 CST 2020


    [ https://issues.asterisk.org/jira/browse/ASTERISK-28688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249344#comment-249344 ] 

Asterisk Team commented on ASTERISK-28688:
------------------------------------------

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.

> Matching SIP TCP peer by IP with insecure=port regression
> ---------------------------------------------------------
>
>                 Key: ASTERISK-28688
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28688
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 13.21.1
>            Reporter: rsw686
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list