[asterisk-bugs] [JIRA] (ASTERISK-27881) PBX calls via chan_sip TCP trunk now get authentification error

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-27881:
--------------------------------------------

Yep.  Looks like ASTERISK-27457 causes the regression.  Probably the only solution is to change the matching to optionally match port regardless of transport using the insecure=port option.

Please be aware that chan_sip is in extended support and only supported by the community so response times will reflect that.

> PBX calls via chan_sip TCP trunk now get authentification error
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-27881
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27881
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 13.21.0
>         Environment: Ubuntu 16.04
>            Reporter: Ian Gilmour
>            Assignee: Unassigned
>
> I have a PBX (type=peer) with a few extensions that forwards calls on to an Asterisk and from there the calls get routed to an external server. All worked fine with 13.20.0 but after upgrading to 13.21.0 I now see the call being rejected by Asterisk with authentification failures.
> The PBX doesn't register with Asterisk - calls are accepted because they come from the defined PBX host IP address. The port the call originates from does not match the defined PBX port (it didn't when using 13.20.0 either and that worked fine).
> I tried adding "insecure=port,invite" to the PBX trunk config with no effect.
> The change in behaviour between 13.20 and 13.21 looks to be related to mods made for ASTERISK-27457.



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