[asterisk-bugs] [JIRA] (ASTERISK-29842) Do not change 180 Ringing to 183 Progress even if early_media already enabled

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-29842:
--------------------------------------

    Status: Open  (was: Triage)

> Do not change 180 Ringing to 183 Progress even if early_media already enabled
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-29842
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29842
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 16.23.0, 18.9.0, 19.1.0
>            Reporter: Mark Petersen
>
> Currently if we receive a 180 Ringing and we previously have received a 183 Progress with SDP, asterisk is send as 183 Progress with SDP
> but it should be send as 180 Ringing with SDP
> RFC-3960 3.2.  Ringing Tone Generation
> SIP User Agent (UA) could implement the following
>    local policy:
>       1. Unless a 180 (Ringing) response is received, never generate
>          local ringing.
>       2. If a 180 (Ringing) has been received but there are no incoming
>          media packets, generate local ringing.
>       3. If a 180 (Ringing) has been received and there are incoming
>          media packets, play them and do not generate local ringing.
>          Note that a 180 (Ringing) response means that the callee is
>          being alerted, and a UAS should send such a response if the
>          callee is being alerted, regardless of the status of the early
>          media session.



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