[asterisk-bugs] [JIRA] (ASTERISK-18298) (Call Completion / SIP) SUBSCRIBE fails using TLS

Joshua Colp (JIRA) noreply at issues.asterisk.org
Tue Dec 19 06:37:07 CST 2017


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

Joshua Colp updated ASTERISK-18298:
-----------------------------------

    Affects Version/s: 13.18.4

> (Call Completion / SIP) SUBSCRIBE fails using TLS
> -------------------------------------------------
>
>                 Key: ASTERISK-18298
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18298
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/CallCompletionSupplementaryServices
>    Affects Versions: 1.8.4, 13.18.4
>            Reporter: George Konopacki
>         Attachments: messages
>
>
> Using 1.8.4.rc2
> When we SUBSCRIBE for call completion, we receive a 404 Not Found. The asterisk server trace reports that the URI we provided in the SUBSCRIBE message cannot be found.
> The difference between using TLS and UDP seems to be the URI provided in the180 Ringing (Call-Info section).
> e.g
> sip:xxxxxxx for UDP
> sips:xxxxxxx for TLS
> I don't think the asterisk server should be adding the extra 's' character. This is the only time we see 'sips' in any trace.
> Problem also exists on 1.8.5.0



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



More information about the asterisk-bugs mailing list