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

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Mon Mar 6 12:03:03 CST 2023


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

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

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Additionally this behavior is not guaranteed, because it can depend on the dialplan as well.

> 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: pjproject/pjsip
>    Affects Versions: 18.14.0
>            Reporter: 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)



More information about the asterisk-bugs mailing list