Re: [SR-Users] Routing Problems

Hi Klaus! Your hint to use add_contact_alias and handle_ruri_alias to fix the contact solved the problem! Thank you very much! again! regards Andreas -----Ursprüngliche Nachricht----- Von: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Gesendet: Donnerstag, 4. Februar 2010 16:19 An: Andreas Rehbein Cc: sr-users(a)lists.sip-router.org Betreff: Re: [SR-Users] Routing Problems Hi Andreas! Not sure, but I think the RURI might be incorrect. Some theory: The proxy can only forward if there is an established TLS connection to the client, and the address information in the RURI is correct. Consider a scenario where the UA (which is supposed to receive the BYE) is behind a NAT router having the local ip:port 1.1.1.1:11111. When this client opens a TCP/TLS connection to the SecurityGateway, the proxy will see the request coming from the public ip and another port, e.g. 2.2.2.2:22222. Thus, for the proxy to be able to send the BYE to this UA, the RURI of the BYE request must contain the hostpart 2.2.2.2:22222 (as this is the address the proxy has an open TCP connection to). Usually, even if the UA is not behind NAT, the Contact provided by the UA is not correct and must be fixed by the proxy. Thus, for SIP messages coming from the UA you should call the function add_contact_alias(), and for messages sent to the UA you should call the function handle_ruri_alias() to fix the contact. See examples in the README. http://www.kamailio.org/docs/modules/3.0.x/modules_k/nathelper.html#id251306 2 regards klaus PS: If possible, ngrep traces are preferred (but unfortunately not part of RHEL): ngrep -t -q -P "" -W byline port 5060 or 5061 Am 04.02.2010 15:18, schrieb Andreas Rehbein: