[OpenSIPS-Users] t_relay

[johan]

yeah you are right.

I changed my script to go to sems.  Caller is tls, sems is udp. Hence I 
need to use udp socket.

The problem was that I forgot to call rewriteuri. Below is the 
solution.  Maybe it helps for somebody in the future.


     rewriteuri("5556 at x.y.z.t:5060");
     subst_uri('/transport=tls/transport=udp/i');
     subst_uri('/transport=TLS/transport=udp/i');
     t_relay(,"udp:x.y.z.t:5060");


On 8/09/2020 19:23, Bogdan-Andrei Iancu wrote:
> Hi Johan,
>
> The socket used for receiving the REGISTER is stored in the OpenSIPS 
> registration. And used/forced when doing the lookup(). So, if the 
> REGISTER was received via TLS, the TLS interface should be forced 
> after the lookup.
>
> So how comes that opensips tries TLS (TLS Registration??) while the 
> user is on UDP ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 2020 online
>   https://www.opensips.org/events/Summit-2020Distributed/
>
> On 9/7/20 3:45 PM, johan wrote:
>> Hi,
>>
>> when a user is not reachable, I want to reroute my call to sems.
>>
>> the user is on tls, but sems is on udp.
>>
>> as I use rtpengine after doing lookup(location), I need to re relay 
>> the original message on the tls connection. However this fails.
>>
>> how can I do t_relay to tls socket ?
>>
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> callid=onsLR0MAH9Bae6f8XJTgug..: Branch_route[per_branch_ops]: new 
>> branch at sip:5556 at x.y.z.t:5061;transport=TLS
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:proto_tls:tls_conn_init: no TLS client domain found
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:core:tcp_conn_new: failed to do proto 3 specific init for conn 
>> 0x7fa91e354ff0
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:proto_tls:tls_sync_connect: tcp_conn_create failed, closing the 
>> socket
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:proto_tls:proto_tls_send: connect failed
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:tm:msg_send: send() to x.y.z.t:5061 for proto tls/3 failed
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:tm:t_forward_nonack: sending request failed
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> ERROR:tm:w_t_relay: t_forward_nonack failed
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15772]: 
>> callid=onsLR0MAH9Bae6f8XJTgug..: failure_route[missed_call]: t_relay 
>> doesn't work.
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15774]: 
>> ERROR:proto_tls:tls_accept: New TLS connection from x.y.z.t :53369 
>> failed to accept
>>
>> Sep  7 12:40:09 ns365555 /data/opensips/sbin/opensips[15774]: 
>> ERROR:proto_tls:tls_read_req: failed to do pre-tls reading
>>
>> if this is not possible, then how do I need to re relay the original 
>> message ?
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>