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

[Daniel-Constantin Mierla]

Hello,

so practically all registration appear to come from 127.0.0.1:xyz, where
xyz is some port value.

My guess is that the connection to the tcp proxy is cut and the kamailio
tries to open one.

Is the tcp proxy routing traffic to other apps? Why not using another
Kamailio that does bridging from port 443 to internal kamailio? Should
be simple outbound proxy config, using Path for registrations.

Cheers,
Daniel

On 26/01/16 13:14, Vasiliy Ganchev wrote:
> 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.
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu