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

Friendly Automation (JIRA) noreply at issues.asterisk.org
Mon Aug 27 07:03:55 CDT 2018


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

Friendly Automation commented on ASTERISK-27881:
------------------------------------------------

Change 9861 merged by Jenkins2:
chan_sip: improved ip:port finding of peers for non-UDP transports.

[https://gerrit.asterisk.org/9861|https://gerrit.asterisk.org/9861]

> 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
>         Attachments: patch-channels-chan_sip.c
>
>
> 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)



More information about the asterisk-bugs mailing list