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

[Carlos Mendioroz (JIRA)]

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

Carlos Mendioroz commented on ASTERISK-28828:
---------------------------------------------

Ivi,
It is not stated here, but in the forum discussion, that reverting did make the call work but did not fix the ordering. 
I was at first convinced that the order was generating the 500, but it seems there is something else.
Also, during my tests I prevented the generation of the Trying and that also did not work.
(work, as in Teams completing the resume process)

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