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

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-30454:
-------------------------------------------

The res_pjsip_refer module attempts to deduce what is happening based on various things happening to the channel. There is no explicit Asterisk interface to receive notifications or to know what is really going on, and things can get even more complicated because your call may not even end up at another device - it may just end up in the dialplan. It's not an exact science, so sometimes it gets it wrong or not as one would expect. I'll leave this issue open in case there are any enhancements to improve it.

> 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)