Hello All,
I have setup the Kamailio 3.1.0 behind a NAT/firewall. I'm using record_route_preset() function to keep the Public IP(advertised_address) in the Route header. I have to setup a where TLS->UDP and UDP->TLS to work. The sip clients do TLS and we have third party sip clients that only do UDP. The problem, Kamailio does not do double record-route when I provide record_route_preset().
This is leading to a problem where the call is either hung on TLS or UDP. I'm unsure how to go around this problem. I had posted earlier about this problem, is there a way I could use the advertised_address in the record route headers in this case?
Regards Gnani
Gnani, since version 3.2.0 kamailio accepts several arguments to record_route_preset() function: http://www.kamailio.org/docs/modules/3.2.x/modules_k/rr.html#id2542169 In 3.1.0 you can call insert_hf directly, but IMO it's worth upgrading. Andrew
On 12/08/2011 08:50 PM, Gnaneshwar Gatla wrote:
Hello All,
I have setup the Kamailio 3.1.0 behind a NAT/firewall. I’m using record_route_preset() function to keep the Public IP(advertised_address) in the Route header.
I have to setup a where TLS->UDP and UDP->TLS to work. The sip clients do TLS and we have third party sip clients that only do UDP.
The problem, Kamailio does not do double record-route when I provide record_route_preset().
This is leading to a problem where the call is either hung on TLS or UDP. I’m unsure how to go around this problem.
I had posted earlier about this problem, is there a way I could use the advertised_address in the record route headers in this case?
Regards
Gnani
-
Andrew Pogrebennyk -
Gnaneshwar Gatla