[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=250325#comment-250325 ] 

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

All is happening in a very short time. 
The NOTIFY/OK can not possible happen before the actual call answer, which is the trace next message. 
Tracing has for sure some locking mech that is making the received OK follow the sent NOTIFY. Multithreded magic.

I don't understand the upset, nor am I an expert SIP person. I do know about protocols in general :)
But as I said in the forum, I do have this end's control. Not the other one.
I'm open to help dig this out. Teams is going to be a big player in the not so distant future, IMHO. 


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