<div dir="ltr">Thanks!!!<br>Yeah, <b>set_forward_no_connect()</b> was in the script ...<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">чт, 8 дек. 2022 г. в 12:23, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hello,</p>
<p>check to see if the set_forward_no_connect() is used.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div>On 08.12.22 10:28, Denys Pozniak wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello!
<div><br>
</div>
<div>We use trunk with Twilio through a SIP/TLS.</div>
<div>They establish incoming calls from random ports, like:</div>
<div>(Twilio)<a href="http://3.3.3.3:54321" target="_blank">3.3.3.3:54321</a> --> (Kamailio)<a href="http://2.2.2.2:5061" target="_blank">2.2.2.2:5061</a><br>
</div>
<div><br>
</div>
<div>In case of sending in-dialog requests to them, Kamailio
should establish an outgoing connection to the dst port 5061
(as per Route), like:</div>
<div>(Kamailio)2.2.2.2 --> (Twilio)<a href="http://3.3.3.3:5061" target="_blank">3.3.3.3:5061</a><br>
</div>
<div><br>
</div>
<div>But as per tcpdump traces and logs, Kamailio does not even
try to establish an outgoing connection to Twilio.</div>
<div>There should be no problems with routes and the network on
that server, as regular telnet to Twilio shows that 5061 is
open.<br>
</div>
<div><br>
</div>
<div>What could be the reason and how to debug?</div>
<div><br>
</div>
<div><u>Script:</u><br clear="all">
<div>onsend_route {<br>
</div>
<div> xlog("L_ERR","[$cfg(route)]*RELAY ONSEND* $rm /
$du / $fs / $fsn / [$ci]\n");<br>
}<br>
</div>
<div><br>
</div>
<div><u>Syslog:</u><br>
DEBUG <core> [core/resolve.c:1259]:
srv_sip_resolvehost(): <a href="http://3.3.3.3:5061" target="_blank">3.3.3.3:5061</a> proto=3<br>
DEBUG <core> [core/resolve.c:1371]:
srv_sip_resolvehost(): returning 0x55acd63a63c0 (<a href="http://3.3.3.3:5061" target="_blank">3.3.3.3:5061</a>
proto=3)<br>
ERROR <script>: [DEFAULT_SEND]*RELAY ONSEND* REFER /
<a>sip:3.3.3.3:5061;transport=tls</a> / tls:<a href="http://10.1.1.1:5061" target="_blank">10.1.1.1:5061</a>
/ sip_wan_tls / [123]<br>
DEBUG tm [../../core/forward.h:277]: msg_send_buffer():
sending to: <a href="http://3.3.3.3:5061" target="_blank">3.3.3.3:5061</a>, force_socket=4,
send_sock=0x7f090049b8e8<br>
DEBUG tm [../../core/forward.h:292]: msg_send_buffer():
tcp_send failed<br>
DEBUG tm [t_fwd.c:1568]: t_send_branch(): send to <a href="http://3.3.3.3:5061" target="_blank">3.3.3.3:5061</a>
(3) failed<br>
WARNING: tm [t_fwd.c:1588]: t_send_branch(): sending request
on branch 0 failed<br>
DEBUG tm [t_funcs.c:335]: t_relay_to(): t_forward_nonack
returned error -1 (-477)<br>
DEBUG tm [t_funcs.c:353]: t_relay_to(): -477 error reply
generation delayed<br>
DEBUG sl [sl_funcs.c:558]: sl_run_callbacks(): execute
callback for event type 1<br>
<br>
<u>Software:</u><br>
- Kamailio is listening on (+udp, +tcp):<br>
</div>
<div> tls: <a href="http://10.1.1.1:5061" target="_blank">10.1.1.1:5061</a> name sip_wan_tls
advertise <a href="http://2.2.2.2:5061" target="_blank">2.2.2.2:5061</a><br>
</div>
<div><br>
</div>
<div>- OS is Debian 11.5</div>
<div><br>
</div>
<div>- # kamailio -v<br>
</div>
<div> version: kamailio 5.6.2 (x86_64/linux)<br>
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK,
SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC,
DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
USE_DST_BLOCKLIST, HAVE_RESOLV_RES,
TLS_PTHREAD_MUTEX_SHARED<br>
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB <br>
poll method support: poll, epoll_lt, epoll_et, sigio_rt,
select.<br>
id: unknown<br>
compiled with gcc 10.2.1<br>
</div>
<div><br>
</div>
<div>
<div>- # dpkg -l | grep ssl<br>
</div>
<div> ii libssl1.1:amd64
1.1.1n-0+deb11u3 amd64 Secure Sockets
Layer toolkit - shared libraries<br>
ii openssl 1.1.1n-0+deb11u3
amd64 Secure Sockets Layer toolkit -
cryptographic utility<br>
</div>
<div><br>
</div>
<br>
</div>
-- <br>
<div dir="ltr">
<div dir="ltr"><br>
<div>
<div>BR,</div>
<div>Denys Pozniak<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre cols="72">--
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">www.asipto.com</a>
<a href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a></pre>
</div>
__________________________________________________________<br>
Kamailio - Users Mailing List - Non Commercial Discussions<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not reply only to the sender!<br>
Edit mailing list options or unsubscribe:<br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><br><div><div>BR,</div><div>Denys Pozniak<br></div><div><br></div><div><br></div></div></div></div>