[asterisk-bugs] [JIRA] (ASTERISK-25568) 180 Ringing not sent after 183 Session Progress

[Olle Johansson (JIRA)]

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

Olle Johansson commented on ASTERISK-25568:
-------------------------------------------

I think the assumption that we should not move to ringing state when early media is already active is wrong. This seems to be copied to a few other places in chan_sip. Early media is independent of ringing.

> 180 Ringing not sent after 183 Session Progress
> -----------------------------------------------
>
>                 Key: ASTERISK-25568
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25568
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.6.0
>            Reporter: Morten Tryfoss
>            Severity: Minor
>         Attachments: chan_sip.patch
>
>
> We've got a simple scenario with a SIP call through Asterisk.
> sip.conf
> progressinband=no (default setting)
> The remote switch sends a 100 Trying and a 183 Session Progress immediately after we send the INVITE. When the remote destination starts ringing (CPG received on ISUP-side of the switch), the switch sends a 180 Ringing to Asterisk. This is not forwarded to the other side, which I think is wrong.
> This can cause lack of ringback tone or wrongly mapped release causes in the originating switch. For example, a 480 temp unavailable is mapped to "20 - subscriber absent" if it has not started to ring, or "19 - no answer from user" if it has.
> The attached patch solves the problem for me.



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