[SR-Users] How does Kamailio decide which protocol to use when fwding to another proxy?

[Daniel-Constantin Mierla]

Hello,

On 25/01/2017 00:11, Pranathi Venkatayogi wrote:
>
> In the case below though TLS session is established between proxy1 and
> proxy2, invite is fwded on UDP.
>
> 1.      How to force Kamailio to use existing tls session to
> communicate? (proxy1)
>

you can force the destination of a packet with:

$du = "sip:ip:port;transport=tls";
t_relay();

or use t_relay_to(...) or t_relay_to_tls(...) functions from tm module
(see its README).

> 2.      What is the command to look at if existing tls sessions are
> present from proxy1
>
> a.      kamcmd tls.list does it, but I need one which works from
> within config.
>

You can execute a RPC command from config file using jsonrpc module and
then can access the response using a json module like jansson:

http://kamailio.org/docs/modules/4.4.x/modules/jsonrpc-s.html#jsonrpc-s.f.jsonrpc_exec

Cheers,
Daniel

>  
>
> *From:*Pranathi Venkatayogi
> *Sent:* Tuesday, January 24, 2017 11:02 AM
> *To:* 'Kamailio (SER) - Users Mailing List'
> <sr-users at lists.sip-router.org>
> *Subject:* How does Kamailio decide which protocol to use when fwding
> to another proxy?
>
>  
>
> Hi,
>
>   I have two instances of Kamailio acting as edge proxies. One on the
> customer side and one on the agent side.
>
>   Like: customer -> proxy1 -> proxy2 -> agent.
>
>   Both customer and agent are registered to proxy1/proxy2 via TLS.
>
>  
>
>   However when proxy1 forwards to proxy2, it is using UDP. How can I
> force it to use TLS?
>
>   Attached is the result of nslookup on the domain:
> translation.sms-test.cyracom.com.
>
>  
>
> Thanks
>
> Pranathi
>
>  
>


-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20170125/2fa8ecb9/attachment.html>