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

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp closed ASTERISK-28688.
-------------------------------------

    Resolution: Suspended

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.

> 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)