2) I tried to set mhomed=1, but it has become even worse - No out socket. <br>So I tried to disable it again and force kamailio to listen on physical address as well (so simultaneously on virtual and physical). The error disappeared, but the BYE message is not forwarded, it is processed and onsend event-route is triggered as usually , but the packet is not sent anywhere. I used tcpdump -i any. I will investigate if it is some network issue, however, is there any way how to debug it further ? <br>
<br><div class="gmail_quote">On Mon, Feb 13, 2012 at 4:28 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
for 1) Is the device behind nat? Do you have tcp connection lifetime
parameter value long enough?<br>
<br>
for 2) is the physical IP a public space IP? Do you have mhomed
parameter set? It is a warning saying that the interface returned by
OS for connecting to the destination is not in the listen list.<br>
<br>
for 3) yes it is expected behaviour, you just need to do record
routing as usual, nothing special.<br>
<br>
Cheers,<br>
Daniel<div><div></div><div class="h5"><br>
<br>
On 2/13/12 11:43 AM, Mino Haluz wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">Hi,<br>
<br>
our customers are using mostly UDP but some of them want to use
TCP. The problem is, I get various TCP errors in kamailio log and
I do not understand what they mean<br>
<br>
1) ERROR: <core> [tcp_main.c:4130]: connect
<customerIP:port> failed<br>
This means kamailio is trying to connect with TCP to the customer
??<br>
2) WARNING: tcp_do_connect <customerIP:port> : could not
find corresponding listening socket for IPaddress , using
default... ( where IPaddress is kamailio physical IP address)<br>
Kamailio has one virtual IP address (heartbeat IP address) and one
physical. It listens on the virtual IP address but I do not
understand why it is trying to use the physical IP address ?<br>
<br>
I was investigating this thing because the BYE message is not
being relayed if the TCP is used (everytime the 2. error message
is printed), so that's why I have to understand what it really
means...<br>
<br>
And the last question,<br>
<br>
3) If kamailio is relaying the traffic to the PSTN gateway, and
the customer is using TCP, kamailio uses TCP as well for
connecting to the PSTN gw. Is this behaviour normal ? I would
expect that <br>
<br>
customer -- TCP --> kamailio --- UDP --> GW, <br>
<br>
and not<br>
<br>
customer -- TCP --> kamailio --- TCP --> GW, <br>
<br>
Thanks,<br>
Mino<br>
<br>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a></pre>
</font></div>
</blockquote></div><br>