[SR-Users] rare impossibility to send requests to TLS connected peer

Vasiliy Ganchev vancecezar at gmail.com
Tue Jan 26 13:14:39 CET 2016


Hi Daniel, thanks for quick reply!

e.g.
10.100.1.24 - sip phone
10.100.1.85 - server

- sip phone is configured to register to 10.100.1.85:443
- tcp proxy listen on 443
- when SIP request comes, tcp proxy open connect to Kamailio 127.0.0.1:5061,
and send request there
- tcp proxy does not modify sip traffic
- there is pure tcp proxy, it stores pairs outer_ip:port <=> 127.0.0.1:port
(make bind of 2 TCP connects)

the kamctl ul show example for such AOR:

	AOR:: 251
		Contact:: sip:251 at 10.100.1.24:4165;transport=TLS Q=
			......
			Received:: sip:127.0.0.1:39370;transport=tls
			......
			Socket:: tls:127.0.0.1:5061
			
is this explanation clear enough, or need to add smth?

Cheers!



--
View this message in context: http://sip-router.1086192.n5.nabble.com/rare-impossibility-to-send-requests-to-TLS-connected-peer-tp144986p144996.html
Sent from the Users mailing list archive at Nabble.com.



More information about the sr-users mailing list