[asterisk-bugs] [JIRA] (ASTERISK-30454) res_pjsip_refer: NOTIFY sipfrag may terminate early depending on conditions

[David Middleton (JIRA)]

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

David Middleton commented on ASTERISK-30454:
--------------------------------------------

I wasn't sure whether to raise this as a separate issue (please advise), but asterisk is also sending those initial NOTIFYs so close together (e.g frame 18 and 19 are 0.3mS apart) that they often arrive at the destination SIP server out of order and so rejections are frequently seen (e.g. frame 20 SIP/2.0 500 Server Internal Error).
It's also not clear to me what/why the NOTIFY with the sipfrags 100, 183 and 180 are being generated, before anything has happened with the upstream INVITE.
Thanks.

> res_pjsip_refer: NOTIFY sipfrag may terminate early depending on conditions
> ---------------------------------------------------------------------------
>
>                 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: Unassigned
>         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)