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: 1613047849.768857 date: Thu Feb 11 14:50:49 2021 proto: tls ipv4 srcip: 82.102.42.58 srcport: 5061 dstip: 52.114.132.46 dstport: 5061 ~~~~~~~~~~~~~~~~~~~~ SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bK4f5c9b66 Record-Route: sip:sbc.intelligentsupport.eu:5060 ;ftag=dcea3c9546914ff8826afca13260da1c;lr=on Record-Route: sip:sbc.intelligentsupport.eu:5061 ;transport=tls;ftag=dcea3c9546914ff8826afca13260da1c;lr=on Record-Route: sip:sip-du-a-us.pstnhub.microsoft.com:5061;transport=tls;lr From: Phillip Kyriacousip:+35722010058@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=dcea3c9546914ff8826afca13260da1c To: sip:+35796552237@sbc.intelligentsupport.eu:5061 ;user=phone;tag=as63d965d3 Call-ID: 43f0f0be2fa05b408c81736dbe392aef CSeq: 1 INVITE Server: MediaGW V1.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: sip:+35796552237@82.102.42.52:5060 Content-Type: application/sdp Require: timer Content-Length: 339
v=0 o=root 601931926 601931926 IN IP4 82.102.42.52 s=ASTERISK c=IN IP4 82.102.42.52 t=0 0 m=audio 16360 RTP/SAVP 0 8 101 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:IyrJsjVV0w5ORJQ3OJB0r8iyRZU+1lMjg4i9vzC2 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=maxptime:150 a=sendrecv |||||||||||||||||||| ====================
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 52.114.76.76:5061;branch=z9hG4bK9984dd75 Record-Route: sip:SBC-DNS-DOMAIN:5060;r2=on;lr Record-Route: sip:SBC-DNS-DOMAIN:5061;transport=tls;r2=on;lr Record-Route: sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr From: Pepeluxsip:+YYYYYYYYYYY@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=20cc826cdb36430089baeefcaa846f4a To: sip:+XXXXXXXXXXX@SBC-DNS-DOMAIN:5061;user=phone;tag=as075f399f Call-ID: b81c3635f25b55a8b6aa2d4943624a16 CSeq: 1 INVITE Server: Asterisk PBX Allow:sINVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces Contact: sip:+XXXXXXXXXXX@ASTERISK-IP-ADDR:5060 Content-Type: application/sdp Content-Length: 614
v=0 o=root 794961255 794961255 IN IP4 SBC-IP-ADDR s=Asterisk PBX c=IN IP4 SBC-IP-ADDR t=0 0 m=audio 36834 RTP/SAVP 0 8 101 a=maxptime:150 a=mid:1 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:36835 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:iPGdIbVhkYq+7b4QU7selA9ymifeEN07VTVSfhmR a=ptime:20 a=ice-ufrag:y9FpiQul a=ice-pwd:IBAulXNNVx2fqpFE1K9BzLYbuG a=candidate:MLkUNexgYqowLxtY 1 UDP 2130706431 SBC-IP-ADDR 36834 typ host a=candidate:MLkUNexgYqowLxtY 2 UDP 2130706430 SBC-IP-ADDR 36835 typ host
Cheers
On Thu, 11 Feb 2021 at 14:28, Phillman25 Kyriacou phillman25@gmail.com wrote:
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: 1613047849.768857 date: Thu Feb 11 14:50:49 2021 proto: tls ipv4 srcip: 82.102.42.58 srcport: 5061 dstip: 52.114.132.46 dstport: 5061
SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bK4f5c9b66 Record-Route: <sip:sbc.intelligentsupport.eu:5060 ;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sbc.intelligentsupport.eu:5061 ;transport=tls;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sip-du-a-us.pstnhub.microsoft.com:5061 ;transport=tls;lr> From: Phillip Kyriacou<sip:+35722010058@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=dcea3c9546914ff8826afca13260da1c To: <sip:+35796552237@sbc.intelligentsupport.eu:5061 ;user=phone>;tag=as63d965d3 Call-ID: 43f0f0be2fa05b408c81736dbe392aef CSeq: 1 INVITE Server: MediaGW V1.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:+35796552237@82.102.42.52:5060> Content-Type: application/sdp Require: timer Content-Length: 339 v=0 o=root 601931926 601931926 IN IP4 82.102.42.52 s=ASTERISK c=IN IP4 82.102.42.52 t=0 0 m=audio 16360 RTP/SAVP 0 8 101 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:IyrJsjVV0w5ORJQ3OJB0r8iyRZU+1lMjg4i9vzC2 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=maxptime:150 a=sendrecv |||||||||||||||||||| ==================== _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
For sure there can be R-R headers in 200 OK to Teams Microsoft.PSTNHub.SIPProxy.
-- Juha
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 52.114.75.24:5061;branch=z9hG4bK6b5ac083 Record-Route: sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on Record-Route: sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr From: Adminsip:+123456789@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=7a6409ee42ac48a897be110166a2bb0b To: sip:+987654321@fqdn:5067;user=phone;tag=as7ae795fd Call-ID: dc62c921f9ad5879b00a74c6bb8a466a CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: sip:+9876654321@192.168.1.1:5060 Content-Type: application/sdp Require: timer Content-Length: 336 Server: SIP Server
v=0 o=SIP 1094517697 1094517697 IN IP4 1.1.1.1 s=PBX c=IN IP4 1.1.1.1 t=0 0 m=audio 14068 RTP/SAVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:GocrDpJ7F/MCwQq9RLJad+K1/bAMplS1HRAB0jo6 |||||||||||||||||||| ====================
On Thu, 11 Feb 2021 at 13:28, Phillman25 Kyriacou phillman25@gmail.com wrote:
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: 1613047849.768857 date: Thu Feb 11 14:50:49 2021 proto: tls ipv4 srcip: 82.102.42.58 srcport: 5061 dstip: 52.114.132.46 dstport: 5061
SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bK4f5c9b66 Record-Route: <sip:sbc.intelligentsupport.eu:5060 ;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sbc.intelligentsupport.eu:5061 ;transport=tls;ftag=dcea3c9546914ff8826afca13260da1c;lr=on> Record-Route: <sip:sip-du-a-us.pstnhub.microsoft.com:5061 ;transport=tls;lr> From: Phillip Kyriacou<sip:+35722010058@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=dcea3c9546914ff8826afca13260da1c To: <sip:+35796552237@sbc.intelligentsupport.eu:5061 ;user=phone>;tag=as63d965d3 Call-ID: 43f0f0be2fa05b408c81736dbe392aef CSeq: 1 INVITE Server: MediaGW V1.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:+35796552237@82.102.42.52:5060> Content-Type: application/sdp Require: timer Content-Length: 339 v=0 o=root 601931926 601931926 IN IP4 82.102.42.52 s=ASTERISK c=IN IP4 82.102.42.52 t=0 0 m=audio 16360 RTP/SAVP 0 8 101 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:IyrJsjVV0w5ORJQ3OJB0r8iyRZU+1lMjg4i9vzC2 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=maxptime:150 a=sendrecv |||||||||||||||||||| ==================== _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 Record-Route: sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on Record-Route: sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr
I have ;r2=on in both R-R headers. And also you have ;lr=on in one and ;lr in the other.
-- Juha
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 jh@tutpro.com wrote:
SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 Record-Route:
sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on
Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061
;transport=tls;lr>
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 List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 ID=2e701c07f99c5cb89fc72db225a6e309} rr [loose.c:800]: rr_do_force_send_socket(): no socket found to match second RR (sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on)
This is the BYE message:
|||||||||||||||||||| ==================== tag: rcv pid: 24681 process: 3 time: 1614190858.750938 date: Wed Feb 24 18:20:58 2021 proto: udp ipv4 srcip: 192.168.1.2 srcport: 5060 dstip: 192.1668.1.1 dstport: 5060 ~~~~~~~~~~~~~~~~~~~~ BYE sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=58a922ac-934d-49cb-93b0-a7b435a36ea5;x-c=2e701c07f99c5cb89fc72db225a6e309/d/8/7776d3cf84d340a79f0a433d743e7a1a SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK24411a29;rport Route: sip:192.168.1.1:5060 ;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on,sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on,sip:sip-du-a-eu.pstnhub.microsoft.com:5061 ;transport=tls;lr Max-Forwards: 70 From: sip:+1234566789@sbc-fqdn:5067;user=phone;tag=as72ae570b To: user1sip:+87654321@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=4ccd608c55e94f4aa094151dfd9e23a4 Call-ID: 2e701c07f99c5cb89fc72db225a6e309 CSeq: 102 BYE User-Agent: COMPANY Content-Length: 0
|||||||||||||||||||| ====================
The domain from the second rr (sbc-fqdn:5067) it's perfectly valid and resolved from the kam server and from outside.
version: kamailio 5.4.4 (x86_64/linux) bdf4e0
Any thought here? Thanks
On Wed, 24 Feb 2021 at 21:40, Ilie Soltanici iliusha.md@gmail.com wrote:
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 jh@tutpro.com wrote:
SIP/2.0 200 OK Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 Record-Route:
sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on
Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061
;transport=tls;lr>
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 List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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.
Cheers, Daniel
On 25.02.21 10:51, Ilie Soltanici wrote:
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 ID=2e701c07f99c5cb89fc72db225a6e309} rr [loose.c:800]: rr_do_force_send_socket(): no socket found to match second RR (sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on)
This is the BYE message:
||||||||||||||||||||
tag: rcv pid: 24681 process: 3 time: 1614190858.750938 date: Wed Feb 24 18:20:58 2021 proto: udp ipv4 srcip: 192.168.1.2 srcport: 5060 dstip: 192.1668.1.1 dstport: 5060
BYE sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=58a922ac-934d-49cb-93b0-a7b435a36ea5;x-c=2e701c07f99c5cb89fc72db225a6e309/d/8/7776d3cf84d340a79f0a433d743e7a1a SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK24411a29;rport Route: <sip:192.168.1.1:5060;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>,<sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>,<sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> Max-Forwards: 70 From: <sip:+1234566789@sbc-fqdn:5067;user=phone>;tag=as72ae570b To: user1<sip:+87654321@sip.pstnhub.microsoft.com:5061;user=phone>;tag=4ccd608c55e94f4aa094151dfd9e23a4 Call-ID: 2e701c07f99c5cb89fc72db225a6e309 CSeq: 102 BYE User-Agent: COMPANY Content-Length: 0 |||||||||||||||||||| ==================== The domain from the second rr (sbc-fqdn:5067) it's perfectly valid and resolved from the kam server and from outside. version: kamailio 5.4.4 (x86_64/linux) bdf4e0 Any thought here? Thanks On Wed, 24 Feb 2021 at 21:40, Ilie Soltanici <iliusha.md@gmail.com <mailto:iliusha.md@gmail.com>> wrote: 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 <jh@tutpro.com <mailto:jh@tutpro.com>> wrote: > SIP/2.0 200 OK > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 > Record-Route: > <sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on> > Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> 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 List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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:
ping sbc-fqdn 64 bytes from kamailio (1.1.1.1): icmp_seq=1 ttl=64 time=0.041 ms
kamcmd corex.list_sockets { PROTO: tls NAME: 1.1.1.1 ADDRLIST: { ADDR: 1.1.1.1 } PORT: 5067 MCAST: no MHOMED: no SOCKNAME: - ADVERTISE: - }
(IP Address is replaced)
I was trying to enable sockname_mode for the rr module ( modparam("rr", "sockname_mode", 1) ), but didn't notice any changes in the RR header. Still missing the 'sn' parameter:
INVITE sip:+123456789@sbc-fqdn:5067;user=phone;transport=tls SIP/2.0 Record-Route: sip:192.168.1.1:5060 ;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on Record-Route: sip:sbc-fqdn:5067;transport=tls;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on
I'm missing something else here? Thank you.
On Thu, 25 Feb 2021 at 10:18, Daniel-Constantin Mierla miconda@gmail.com wrote:
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.
Cheers, Daniel On 25.02.21 10:51, Ilie Soltanici wrote:
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 ID=2e701c07f99c5cb89fc72db225a6e309} rr [loose.c:800]: rr_do_force_send_socket(): no socket found to match second RR ( sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on )
This is the BYE message:
||||||||||||||||||||
tag: rcv pid: 24681 process: 3 time: 1614190858.750938 date: Wed Feb 24 18:20:58 2021 proto: udp ipv4 srcip: 192.168.1.2 srcport: 5060 dstip: 192.1668.1.1 dstport: 5060
BYE sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=58a922ac-934d-49cb-93b0-a7b435a36ea5;x-c=2e701c07f99c5cb89fc72db225a6e309/d/8/7776d3cf84d340a79f0a433d743e7a1a SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK24411a29;rport Route: <sip:192.168.1.1:5060;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>, <sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on> ,<sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> Max-Forwards: 70 From: <sip:+1234566789@sbc-fqdn:5067;user=phone>;tag=as72ae570b To: user1<sip:+87654321@sip.pstnhub.microsoft.com:5061;user=phone> ;tag=4ccd608c55e94f4aa094151dfd9e23a4 Call-ID: 2e701c07f99c5cb89fc72db225a6e309 CSeq: 102 BYE User-Agent: COMPANY Content-Length: 0 |||||||||||||||||||| ==================== The domain from the second rr (sbc-fqdn:5067) it's perfectly valid and resolved from the kam server and from outside. version: kamailio 5.4.4 (x86_64/linux) bdf4e0 Any thought here? Thanks On Wed, 24 Feb 2021 at 21:40, Ilie Soltanici <iliusha.md@gmail.com> wrote: > 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 <jh@tutpro.com> wrote: > >> >> > SIP/2.0 200 OK >> > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 >> > Record-Route: >> > >> <sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on> >> > Record-Route: >> <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> >> >> 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 List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla
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 bad actor controlling whatever dns record can point a domain to your sip server address and then your server believes that route headers are added by itself).
You can eventually do it yourself in the config using ipops module and select the socket based on the result.
Cheers, Daniel
On 25.02.21 12:16, Ilie Soltanici wrote:
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:
ping sbc-fqdn 64 bytes from kamailio (1.1.1.1): icmp_seq=1 ttl=64 time=0.041 ms
kamcmd corex.list_sockets { PROTO: tls NAME: 1.1.1.1 ADDRLIST: { ADDR: 1.1.1.1 } PORT: 5067 MCAST: no MHOMED: no SOCKNAME: - ADVERTISE: - }
(IP Address is replaced)
I was trying to enable sockname_mode for the rr module ( modparam("rr", "sockname_mode", 1) ), but didn't notice any changes in the RR header. Still missing the 'sn' parameter:
INVITE sip:+123456789@sbc-fqdn:5067;user=phone;transport=tls SIP/2.0 Record-Route: sip:192.168.1.1:5060;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on Record-Route: sip:sbc-fqdn:5067;transport=tls;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on
I'm missing something else here? Thank you.
On Thu, 25 Feb 2021 at 10:18, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
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. Cheers, Daniel On 25.02.21 10:51, Ilie Soltanici wrote: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 ID=2e701c07f99c5cb89fc72db225a6e309} rr [loose.c:800]: rr_do_force_send_socket(): no socket found to match second RR (sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on) This is the BYE message: |||||||||||||||||||| ==================== tag: rcv pid: 24681 process: 3 time: 1614190858.750938 date: Wed Feb 24 18:20:58 2021 proto: udp ipv4 srcip: 192.168.1.2 srcport: 5060 dstip: 192.1668.1.1 dstport: 5060 ~~~~~~~~~~~~~~~~~~~~ BYE sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=58a922ac-934d-49cb-93b0-a7b435a36ea5;x-c=2e701c07f99c5cb89fc72db225a6e309/d/8/7776d3cf84d340a79f0a433d743e7a1a SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK24411a29;rport Route: <sip:192.168.1.1:5060;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>,<sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>,<sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> Max-Forwards: 70 From: <sip:+1234566789@sbc-fqdn:5067;user=phone>;tag=as72ae570b To: user1<sip:+87654321@sip.pstnhub.microsoft.com:5061;user=phone>;tag=4ccd608c55e94f4aa094151dfd9e23a4 Call-ID: 2e701c07f99c5cb89fc72db225a6e309 CSeq: 102 BYE User-Agent: COMPANY Content-Length: 0 |||||||||||||||||||| ==================== The domain from the second rr (sbc-fqdn:5067) it's perfectly valid and resolved from the kam server and from outside. version: kamailio 5.4.4 (x86_64/linux) bdf4e0 Any thought here? Thanks On Wed, 24 Feb 2021 at 21:40, Ilie Soltanici <iliusha.md@gmail.com <mailto:iliusha.md@gmail.com>> wrote: 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 <jh@tutpro.com <mailto:jh@tutpro.com>> wrote: > SIP/2.0 200 OK > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 > Record-Route: > <sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on> > Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> 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 List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>-- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Funding: https://www.paypal.me/dcmierla <https://www.paypal.me/dcmierla>
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 miconda@gmail.com 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 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 bad actor controlling whatever dns record can point a domain to your sip server address and then your server believes that route headers are added by itself).
You can eventually do it yourself in the config using ipops module and select the socket based on the result.
Cheers, Daniel On 25.02.21 12:16, Ilie Soltanici wrote:
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:
ping sbc-fqdn 64 bytes from kamailio (1.1.1.1): icmp_seq=1 ttl=64 time=0.041 ms
kamcmd corex.list_sockets { PROTO: tls NAME: 1.1.1.1 ADDRLIST: { ADDR: 1.1.1.1 } PORT: 5067 MCAST: no MHOMED: no SOCKNAME: - ADVERTISE: - }
(IP Address is replaced)
I was trying to enable sockname_mode for the rr module ( modparam("rr", "sockname_mode", 1) ), but didn't notice any changes in the RR header. Still missing the 'sn' parameter:
INVITE sip:+123456789@sbc-fqdn:5067;user=phone;transport=tls SIP/2.0 Record-Route: sip:192.168.1.1:5060;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on Record-Route: sip:sbc-fqdn:5067;transport=tls;ftag=98c057b8808f44c48900f71f51443eeb;lr;r2=on
I'm missing something else here? Thank you.
On Thu, 25 Feb 2021 at 10:18, Daniel-Constantin Mierla miconda@gmail.com wrote:
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.
Cheers, Daniel On 25.02.21 10:51, Ilie Soltanici wrote:
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 ID=2e701c07f99c5cb89fc72db225a6e309} rr [loose.c:800]: rr_do_force_send_socket(): no socket found to match second RR ( sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on )
This is the BYE message:
||||||||||||||||||||
tag: rcv pid: 24681 process: 3 time: 1614190858.750938 date: Wed Feb 24 18:20:58 2021 proto: udp ipv4 srcip: 192.168.1.2 srcport: 5060 dstip: 192.1668.1.1 dstport: 5060
BYE sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=58a922ac-934d-49cb-93b0-a7b435a36ea5;x-c=2e701c07f99c5cb89fc72db225a6e309/d/8/7776d3cf84d340a79f0a433d743e7a1a SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK24411a29;rport Route: <sip:192.168.1.1:5060;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on>, <sip:sbc-fqdn:5067;transport=tls;ftag=4ccd608c55e94f4aa094151dfd9e23a4;lr;r2=on> ,<sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> Max-Forwards: 70 From: <sip:+1234566789@sbc-fqdn:5067;user=phone>;tag=as72ae570b To: user1<sip:+87654321@sip.pstnhub.microsoft.com:5061;user=phone> ;tag=4ccd608c55e94f4aa094151dfd9e23a4 Call-ID: 2e701c07f99c5cb89fc72db225a6e309 CSeq: 102 BYE User-Agent: COMPANY Content-Length: 0 |||||||||||||||||||| ==================== The domain from the second rr (sbc-fqdn:5067) it's perfectly valid and resolved from the kam server and from outside. version: kamailio 5.4.4 (x86_64/linux) bdf4e0 Any thought here? Thanks On Wed, 24 Feb 2021 at 21:40, Ilie Soltanici <iliusha.md@gmail.com> wrote: > 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 <jh@tutpro.com> wrote: > >> >> > SIP/2.0 200 OK >> > Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083 >> > Record-Route: >> > >> <sip:fqdn:5067;transport=tls;r2=on;ftag=7a6409ee42ac48a897be110166a2bb0b;lr=on> >> > Record-Route: >> <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr> >> >> 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 List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla --Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla
-
Daniel-Constantin Mierla -
Ilie Soltanici -
Juha Heinanen -
Konrad Górski -
Pepelux -
Phillman25 Kyriacou