<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>what are the sockets kamailio is listening on? See `kamcmd help`
for the command that lists the sockets.</p>
<p>Also, what is the log messages before the first one you pasted,
there should be another one printed from <span
style="font-family:monospace,monospace">get_out_socket().</span></p>
It is always important to provide kamailio version (kamailio -v) and
the operating system you are using.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 14.08.17 14:41, Patrick Wakano
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPu3kNXbQARp-1ZoR1=VKJ2ZM+4tki0fHYSxcdjenBM1UwxtPg@mail.gmail.com">
<div dir="ltr">
<div>Hello Kamailio list,<br>
</div>
<div><br>
Hope you all doing well!<br>
<br>
</div>
<div>I am stuck with one problem that should be incredibly easy
to be done, but apparently it is not.... I want my dispatcher,
LCR and nathelper modules to always SIP ping my SIP clients. I
have a Kamailio based SBC that is separating two networks, and
so I am using the 'mhomed' flag, but none of these SIP pings
are working.... for now I will only ask about the
dispatcher....<br>
</div>
<div>My dispatcher module has to talk with SIP servers in both
networks, the thing is when I enable SIP ping for it (<span
style="font-family:monospace,monospace">modparam("dispatcher",
"ds_probing_mode", 1)</span>), it gives me this type of
error:<br>
<span style="font-family:monospace,monospace">/usr/sbin/kamailio[6164]:
ERROR: <core> [core/forward.c:181]: get_out_socket():
no socket found<br>
/usr/sbin/kamailio[6164]: ERROR: <core>
[core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:<a href="http://192.168.33.110:6060"
moz-do-not-send="true">192.168.33.110:6060</a>)<br>
/usr/sbin/kamailio[6164]: ERROR: tm [ut.h:317]: uri2dst2():
no corresponding socket found for "192.168.33.110" af 2
(udp:<a href="http://192.168.33.110:6060"
moz-do-not-send="true">192.168.33.110:6060</a>)<br>
/usr/sbin/kamailio[6164]: ERROR: tm [uac.c:443]:
t_uac_prepare(): no socket found<br>
/usr/sbin/kamailio[6164]: ERROR: dispatcher
[dispatch.c:2652]: ds_ping_set(): unable to ping [sip:<a
href="http://192.168.33.110:6060" moz-do-not-send="true">192.168.33.110:6060</a>]<br>
</span><br>
</div>
<div>After research it seems I need to manually set a "socket"
attribute for each of my GWs in dispatcher list. After putting
the socket parameter for the GW, I got another error:<br>
<span style="font-family:monospace,monospace">/usr/sbin/kamailio[14190]:
ERROR: <core> [core/socket_info.c:2046]:
parse_protohostport(): bad port number in udp:<a
href="http://192.168.33.100:5060" moz-do-not-send="true">192.168.33.100:5060</a><br>
/usr/sbin/kamailio[14190]: ERROR: <core>
[core/forward.c:181]: get_out_socket(): no socket found<br>
/usr/sbin/kamailio[14190]: ERROR: <core>
[core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:<a href="http://192.168.33.110:6060"
moz-do-not-send="true">192.168.33.110:6060</a>)<br>
/usr/sbin/kamailio[14190]: ERROR: tm [ut.h:317]: uri2dst2():
no corresponding socket found for "192.168.33.110" af 2
(udp:<a href="http://192.168.33.110:6060"
moz-do-not-send="true">192.168.33.110:6060</a>)<br>
/usr/sbin/kamailio[14190]: ERROR: tm [uac.c:443]:
t_uac_prepare(): no socket found<br>
/usr/sbin/kamailio[14190]: ERROR: dispatcher
[dispatch.c:2652]: ds_ping_set(): unable to ping [sip:<a
href="http://192.168.33.110:6060" moz-do-not-send="true">192.168.33.110:6060</a>]</span><br>
<br>
What can be wrong in my port info in the socket config? (I
tried the socket with and without quotes but had no luck...)<br>
<span style="font-family:monospace,monospace">select * from
dispatcher where id=2;<br>
id | setid | destination | flags | priority
| attrs |
description <br>
----+-------+-------------------------+-------+----------+---------------------------------------------+---------------------<br>
2 | 2 | sip:<a href="http://192.168.33.110:6060"
moz-do-not-send="true">192.168.33.110:6060</a> | 0
| 0 | socket="udp:<a
href="http://192.168.33.100:5060" moz-do-not-send="true">192.168.33.100:5060</a>";rweight=50
| <br>
(1 row)<br>
</span><br>
</div>
<div>Anyhow, I was expecting the 'mhomed' parameter to do the
socket selection for me. Regular call routing either by the
dispatcher or by LCR, also seems to require me to explicitly
set the socket otherwise Kamailio (or the OS) may end up using
the wrong socket. So, another question is why 'mhomed' does
not dictate the whole socket selection Kamailio has to do
regardless the module it is using to send SIP requests?<br>
<br>
</div>
<div>Sorry for the long e-mail....<br>
</div>
<div>Best regards,<br>
</div>
<div>Patrick Wakano<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kamailio (SER) - Development Mailing List
<a class="moz-txt-link-abbreviated" href="mailto:sr-dev@lists.kamailio.org">sr-dev@lists.kamailio.org</a>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
Kamailio World Conference - <a class="moz-txt-link-abbreviated" href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>
</body>
</html>