[asterisk-bugs] [JIRA] (ASTERISK-28322) desync in 183 behavior between chan_sip and chan_pjsip

[Torrey Searle (JIRA)]

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

Torrey Searle commented on ASTERISK-28322:
------------------------------------------

That is up to debate, in the case I'm encountering customer generates a 180 followed by a 183 w/o sdp.

According to the SIP-I spec, 183 with no sdp (just ISUP) payload can be generated for ss7 internetworking.  However it says that if you are not using profile-c (e.g. not sending ss7 messages) then the 183 is "not internetworked" which I interpret as dropping the 183 fully as a legitimate response.

I agree that chan_pjsip should probably be enhanced to add support for fowarding 183 w/o sdp at some point in the future, but at this stage I'm only seeking to keep feature parity.

> desync in 183 behavior between chan_sip and chan_pjsip
> ------------------------------------------------------
>
>                 Key: ASTERISK-28322
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28322
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.20.0
>            Reporter: Torrey Searle
>              Labels: pjsip
>
> chan_sip is designed to explicitly ignore 183 messages if no sdp is found.  chan_pjsip however will instead forward a 183 with sdp instead.  This results in a lack of a ringback tone for impacted users.
> This patch adds a new flag to endpoints allowing the user to have the chan_sip behavior if desired.



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