[asterisk-bugs] [JIRA] (ASTERISK-30454) NOTIFY with sipfrag 200 sent before transferred call is answered

[David Middleton (JIRA)]

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

David Middleton updated ASTERISK-30454:
---------------------------------------

    Attachment: 2023030602_ASTERISK-30454_anon.pcap
                2023030602_debug_log_ASTERISK-30454.txt

PSTN (+447700900000) calling DDI (+441632960000) for exten (319-astpjsip).
PJSIP/proxy-00000070 - PSTN -> asterisk
PJSIP/proxy-00000071 - asterisk -> exten

Exten (319-astpjsip) puts call on hold and blind transfers to PSTN +441632960001
PJSIP/proxy-00000072 - asterisk -> PSTN

Frame 16 shows the REFER arriving at asterisk.
Before the INVITE to the transferred party is sent upstream, asterisk has already sent:
Frame 18 - NOTIFY with Sipfrag SIP/2.0 100 Trying
Frame 19 - NOTIFY with Sipfrag SIP/2.0 183 Session Progress
Frame 21 - NOTIFY with Sipfrag SIP/2.0 180 Ringing

Then asterisk sends the INVITE upstream
Frame 22 - INVITE to the transferred destination
But after only a '100 Trying' has been received, asterisk sends
Frame 25 - NOTIFY with Sipfrag SIP/2.0 200 OK 

> NOTIFY with sipfrag 200 sent before transferred call is answered
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-30454
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30454
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_refer
>    Affects Versions: 18.14.0
>            Reporter: David Middleton
>            Assignee: David Middleton
>         Attachments: 2023030602_ASTERISK-30454_anon.pcap, 2023030602_debug_log_ASTERISK-30454.txt
>
>
> Party A calls Party B (and call is answered).
> Party B puts Party A on hold and blind transfers to Party C.
> Asterisk sends a SIP NOTIFY with a sipfrag 200 OK (after various NOTIFY with 1xx progress sipfrags) before the transferred call (to Party C) has been answered.
> The expected behaviour is for the all the NOTIFYs to be sent with sipfrags reflecting the upstream progress of the transferred call.



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