On 5/22/13 3:49 PM, Fabian Borot wrote:
Thank you Klaus, good idea, but I forgot to mention that when I configure the
client w/o TLS using regular SIP/UDP/5060 I dont have that problem. When the
BYE from the called side comes it is sent to the calling side without any
problems.
But I do see that the Contact and VIA reach the Proxy with Public IP:Ports (our
NAT automatically changes the internal IP/ports by the Public ones really
well). The IP:Port in the VIA, CONTACT are the same that the request brings at
layer3 and 4 as well. So I don't bother doing the extra NAT configuration in
the office.
Maybe since the actual content of the TLS SIP call is encrypted the firewall
does not change the and then they should reach the proxy with the private
IP:Ports, causing this problem.
I will try TCP and also adding some extra NAT handling configuration to the
proxy.
you can also try using NULL cypher for tls in order to see the content
in clear text.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
_______________________________________________
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
