[asterisk-bugs] [JIRA] (ASTERISK-28828) NOTIFY sequence upsets MS Teams SIP trunk

[lvl (JIRA)]

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

lvl commented on ASTERISK-28828:
--------------------------------

You could add some debugging (ast_log and/or ast_log_backtrace) at https://github.com/asterisk/asterisk/blob/master/res/res_pjsip_refer.c#L235 and https://github.com/asterisk/asterisk/blob/master/res/res_pjsip_refer.c#L256 to check if & why the NOTIFY 200 OK is indeed sent too early.

Not completely sure that it relates to the problem you're experiencing, but it's worth a try.

> NOTIFY sequence upsets MS Teams SIP trunk
> -----------------------------------------
>
>                 Key: ASTERISK-28828
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28828
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_refer
>    Affects Versions: 17.3.0
>         Environment: Ubuntu 18.04 install from sources
>            Reporter: Carlos Mendioroz
>            Assignee: lvl
>            Severity: Minor
>
> Resuming an on hold call from MS Teams side often results in the call going to limbo. Trace shows out of order NOTIFYs and 500 response to a Trying event.
> On Joshua's advise, rolled back https://gerrit.asterisk.org/c/asterisk/+/13852 and even though the out of order Trying subsists, it does not gerenate a 500 and the call resumes correctly.
> Discussion here:
> https://community.asterisk.org/t/sip-xfers-via-reinvite-refer-and-order-of-notifys/83572



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