: Users on behalf of John Quick
Date: Wednesday, February 17, 2021 at 9:58 AM
To: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] To-tag value in ACK
I took a fresh look at this case and found that the To-tag used in the ACK
matches the To-tag that was in the first 180 Ringing
I took a fresh look at this case and found that the To-tag used in the ACK
matches the To-tag that was in the first 180 Ringing.
However, Teams has returned different To-tags in the 180 Ringing and in the 183
Session Progress and 200 OK.
This appears to be common behaviour for Teams as I can
t; Cc: Johan De Clercq
> Subject: Re: [OpenSIPS-Users] To-tag value in ACK
>
> Good day John,
> it looks like your own deduction is absolutely right!
>
> If we talk about the SIP protocol in terms of RFC 3261, then I guess it's
> clear that the acknowledgement which has
the ACK as it
> was in the 200 OK?
>
> John Quick
> Smartvox Limited
> Tel: +44-1727-221221
>
>
> > From: Johan De Clercq
> > Sent: 02 February 2021 14:42
> > To: John Q ; OpenSIPS users mailling list <
> users@lists.opensips.org>
> > Subject: R
as it was in
the 200 OK?
John Quick
Smartvox Limited
Tel: +44-1727-221221
> From: Johan De Clercq
> Sent: 02 February 2021 14:42
> To: John Q ; OpenSIPS users mailling list
>
> Subject: Re: [OpenSIPS-Users] To-tag value in ACK
>
> is contact an fqdn ?
>
is contact an fqdn ?
If not, look no further.
Op di 2 feb. 2021 om 15:06 schreef John Quick :
> I am seeing a problem in calls made to MS Teams via OpenSIPS configured as
> an SBC.
> The usual INVITE, 180, 183, 200 OK sequence looks okay, but the ACK request
> is not accepted by MS Teams.
> When
I am seeing a problem in calls made to MS Teams via OpenSIPS configured as
an SBC.
The usual INVITE, 180, 183, 200 OK sequence looks okay, but the ACK request
is not accepted by MS Teams.
When I say "not accepted", I mean an ACK is sent to the Teams Proxy, but
Teams responds after 30 seconds with
