Re: [SR-Users] No ACK from MS Teams

Perfect, adding advertise domain name to the listen parameter fixed the issue. Thank you On Thu, 25 Feb 2021 at 12:01, Daniel-Constantin Mierla wrote: > Hello, > > sockets are matched only on address/ip or advertised value, if you want to > match on domain, you have to add advertised address to

Re: [SR-Users] No ACK from MS Teams

Hello, sockets are matched only on address/ip or advertised value, if you want to match on domain, you have to add advertised address to listen global parameter. There is no dns done on route header to do the match, that can have significant on performance, security and routing impact (e.g., a

Re: [SR-Users] No ACK from MS Teams

Hello, I do have 2 network interfaces in 2 different networks, so I don't know if disabling this warning will be the best option here, it's just like a workaround. The weird thing is that the 'rr' Kamailio is complaining ( sbc-fqdn:5067) is actually the IP address (socket) he is listening on:

Re: [SR-Users] No ACK from MS Teams

Hello, there is a rr modparam to turn of that warning, if you do not have many network interfaces/sockets that would require to select a specific one, then should be enough. Otherwise, see the archive in the past two weeks or so, there was a discussion about using socket names with record routes.

Re: [SR-Users] No ACK from MS Teams

Hello, The loose_route function from the rr module is always getting an error in the logs that's not able to find the socket when the BYE request is coming from Kam to the Teams: Feb 24 18:20:58 kamailio kam[24681]: WARNING: {BYE (1) | Seq=102 | Source IP=192.1668.1.1 (udp) | Call

Re: [SR-Users] No ACK from MS Teams

Changing enable_full_lr parameter from the rr module fixed the issue. Now I'm getting ACK from MS to 200OK. Thank you On Wed, 24 Feb 2021 at 15:12, Juha Heinanen wrote: > > > SIP/2.0 200 OK > > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 > > Record-Route: > > > > > Record-Route:

Re: [SR-Users] No ACK from MS Teams

> SIP/2.0 200 OK > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 > Record-Route: > > Record-Route: I have ;r2=on in both R-R headers. And also you have ;lr=on in one and ;lr in the other. -- Juha ___ Kamailio (SER) - Users Mailing

Re: [SR-Users] No ACK from MS Teams

Hello, I have the same issue, did you manage to fix it? tag: snd pid: 9737 process: 6 time: 1614177689.185257 date: Wed Feb 24 14:41:29 2021 proto: tls ipv4 srcip: 1.1.1.1 srcport: 5067 dstip: 52.114.75.24 dstport: 5061 SIP/2.0 200 OK Via: SIP/2.0/TLS

Re: [SR-Users] No ACK from MS Teams

For sure there can be R-R headers in 200 OK to Teams Microsoft.PSTNHub.SIPProxy. -- Juha ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] No ACK from MS Teams

If it can help you ... this is a working example: tag: snd pid: 19012 process: 1 time: 1612951019.957348 date: Wed Feb 10 10:56:59 2021 proto: tls ipv4 srcip: SBC-IP-ADDR srcport: 5061 dstip: 52.114.76.76 dstport: 5061 SIP/2.0 200 OK Via: SIP/2.0/TLS

Re: [SR-Users] No ACK from MS Teams

Hi Guys Thanks for all your recommendations. I did the change and rr headers only show the fqdn of Kamailio as you can see below in the 200 OK sent back to MS Teams, however still the same issue no ACK. tag: snd pid: 31232 process: 6 time:

Re: [SR-Users] No ACK from MS Teams

Henning Westerholt writes: > not 100% sure what the other blog post is suggesting - but in my > setups there is no need for a special record_route(..) in reply > handling (like reply route). Its is not question about reply handling, but direction of INVITE. See my earlier message. -- Juha

Re: [SR-Users] No ACK from MS Teams

Daniel-Constantin Mierla writes: > What exactly do you need to do for R-R in replies? > > The R-R headers are mirrored in replies, so if you add R-R for requests > using the right order of parameters based on the direction, there is > nothing to be done for replies, or at least I haven't had to

Re: [SR-Users] No ACK from MS Teams

Pepelux writes: > Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route: > > Record-Route: :5060;ftag=c3da9477e05d45fca31c24a155af3318;lr=on> Also, it better to follow OpenSIPS tips on the matter https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ since it also mentions

Re: [SR-Users] No ACK from MS Teams

- https://gilawa.com -Original Message- From: sr-users On Behalf Of Juha Heinanen Sent: Thursday, February 11, 2021 9:35 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] No ACK from MS Teams Pepelux writes: > Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Ro

Re: [SR-Users] No ACK from MS Teams

On 11.02.21 09:34, Juha Heinanen wrote: > Pepelux writes: > >> Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route: >> >> Record-Route: > :5060;ftag=c3da9477e05d45fca31c24a155af3318;lr=on> > Also, it better to follow OpenSIPS tips on the matter > >

Re: [SR-Users] No ACK from MS Teams

Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route: Record-Route: On Thu, 11 Feb 2021 at 08:32, Phillman25 Kyriacou wrote: > Dear List > > Hope this email finds you all well. > > I have followed the below tutorial on how to integrate Kamailio with MS > Teams > >

[SR-Users] No ACK from MS Teams

Dear List Hope this email finds you all well. I have followed the below tutorial on how to integrate Kamailio with MS Teams https://skalatan.de/en/blog/kamailio-sbc-teams However i have been facing an issue with MS Teams with direct routing where MS Teams does not send back an ACK after a 200