Hi, i am using Kamailio as an outbound proxy for Translating between TLS (public network) and UDP (internal network). When testing with a client, that uses a SIPS scheme, i've noticed the following behaviour, which broke my setup: Due to the sips:-URI in the Request URI and the two different interfaces (UDP and TLS), the RR module adds two new Record-Route headers like this: Record-Route: <sips:mt@46.101.100.26:5061;transport=tls;r2=on;lr=on;ftag=7BABD31B-59F04202000E785C-AD96E700;rm=1;did=f81.f88> Record-Route: <sips:mt@46.101.100.26;r2=on;lr=on;ftag=7BABD31B-59F04202000E785C-AD96E700;rm=1;did=f81.f88> This however breaks the internal routing, as the server is internally only reachable via UDP and not via TLS, as the internal network components only have UDP interfaces. Is this a bug? I've temporarily created a workaround, so RR will always use "sip" instead of "sips" (which solved my issue), but I wonder if this in general should be considered a bug??? Thanks, Carsten -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Millerntorplatz 1 20359 Hamburg / Germany http://www.ng-voice.com mailto:carsten@ng-voice.com Office +49 40 5247593-40 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/