[asterisk-bugs] [JIRA] (ASTERISK-29520) chan_pjsip: Sometimes no ringback after change of handling 180/SDP in ASTERISK-29105

[Mark Petersen (JIRA)]

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

Mark Petersen commented on ASTERISK-29520:
------------------------------------------

this may be related to ASTERISK-29842
but if the provider send 180/SDP and do not send any RTP then it is not an Asterisk issue
and you need to contact your provider to get them to fix not sending any RTP

> chan_pjsip: Sometimes no ringback after change of handling 180/SDP in ASTERISK-29105
> ------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29520
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29520
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 18.5.0
>         Environment: Linux/arm
>            Reporter: Sven Andersen
>
> ASTERISK-29105 changed the way 180/SDP-responses are handled by chan_pjsip. If there is a SDP, pass 183/SDP and the belonging audio-stream to a-leg instead of just passing 180 without SDP.
> This change seems to be problematic in some situations. I digged a "no ringback-tone"-issue down to this change, reverting fixed it.
> Calling T-Mobile germany from o2 germany sometimes (~1 out of 5 times) responds with 180/SDP but actually does not send the expected/announced audio-stream. So there is no indication that the remote party is ringing and suddenly the call is established (If the caller waits long enough and does not hang up due to missing ringback). The other 4 of 5 times the response is just 180 without SDP and all is fine.
> Can this be made configurable? 
> I could try and submit an according patch (though I am not an asterisk/SIP developer or c-expert so don't expect it to be perfect...).



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