Hello,
I am trying to play with domain names in the Record-Route header. This is for a case when kamailio is doing the translation between UDP and TLS, so it is doing double record routing. I want to use the ip addresses on inbound UDP leg and domain names on the outbound TLS leg in record-route headers. I'm doing this by calling the following function -- record_route_preset("xyz.com;transport=tls", "1.1.1.1"); ---- This does the trick of adding a Record-Route in initial TLS invite on the outbound leg: ----------------- Record-Route: sip:xyz.com;transport=tls;lr=on Record-Route: sip:1.1.1.1;lr=on ----------------
My problems start when the calling party sends a ACK to kamailio over UDP with the Route header Route: sip:1.1.1.1;lr=on,sip:xyz.com;transport=tls;lr=on
I call loose_route() function in config file and as per my expectation, Kamailio should see that both these Route headers belong to Kamailio and it should use Request URI for forwarding the ACK, but unfortunately, Kamailio thinks that xyz.com is some other entity and tries to forward the ACK to xyz.com doing a DNS query. What can i do to avoid this problem, i need kamailio to recognize that "xyz.com" is kamailio as i have a defined an alias in the config file too as follows: alias=xyz.com:5060
Thanks for your help in advance, Nitesh
Hello,
you have to add the parameter "r2=on" in order for kamailio to check for double record-routing addresses. Also, note that the default port for tls is 5061.
Cheers, Daniel
On 21/05/15 18:27, NITESH BANSAL wrote:
Hello,
I am trying to play with domain names in the Record-Route header. This is for a case when kamailio is doing the translation between UDP and TLS, so it is doing double record routing. I want to use the ip addresses on inbound UDP leg and domain names on the outbound TLS leg in record-route headers. I'm doing this by calling the following function -- *record_route_preset("xyz.com;transport=tls", "1.1.1.1");* ---- This does the trick of adding a Record-Route in initial TLS invite on the outbound leg: -----------------* Record-Route: sip:xyz.com;transport=tls;lr=on Record-Route: sip:1.1.1.1;lr=on*
My problems start when the calling party sends a ACK to kamailio over UDP with the Route header *Route: sip:1.1.1.1;lr=on,sip:xyz.com;transport=tls;lr=on*
I call loose_route() function in config file and as per my expectation, Kamailio should see that both these Route headers belong to Kamailio and it should use Request URI for forwarding the ACK, but unfortunately, Kamailio thinks that xyz.com is some other entity and tries to forward the ACK to xyz.com doing a DNS query. What can i do to avoid this problem, i need kamailio to recognize that "xyz.com" is kamailio as i have a defined an alias in the config file too as follows: alias=xyz.com:5060
Thanks for your help in advance, Nitesh
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On Thursday 21 May 2015 18:27:13 NITESH BANSAL wrote:
...
What can i do to avoid this problem, i need kamailio to recognize that "xyz.com" is kamailio as i have a defined an alias in the config file too as follows: alias=xyz.com:5060
Just a guess: tls implies 5061, try adding xyz.com:5061 (and any other ports you might use) as extra aliases.
Thanks Daniel, adding r2=on seems to have fixed the issue.
From: d.tryba@pocos.nl To: sr-users@lists.sip-router.org Date: Fri, 22 May 2015 10:10:49 +0200 Subject: Re: [SR-Users] issues with domain names in the record route
On Thursday 21 May 2015 18:27:13 NITESH BANSAL wrote:
...
What can i do to avoid this problem, i need kamailio to recognize that "xyz.com" is kamailio as i have a defined an alias in the config file too as follows: alias=xyz.com:5060
Just a guess: tls implies 5061, try adding xyz.com:5061 (and any other ports you might use) as extra aliases.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users