<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
yes, quick connect message is ok. It is an INFO level, messages to
worry about start at level WARNING, ERROR or lower.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 27/01/16 12:41, david wrote:<br>
</div>
<blockquote cite="mid:1453894865.2989.7.camel@bts.io" type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.8.4">
hello Daniel<br>
<br>
thanks for the explanation.<br>
then i understand the "quick connect" message is also normal? seen
in version 4.2.2 or 4.4?<br>
<br>
best regards<br>
david<br>
<br>
<br>
El mar, 26-01-2016 a las 12:45 +0100, Daniel-Constantin Mierla
escribió:<br>
<blockquote type="CITE"> Hello,<br>
<br>
the pending write message is due to asynchronous tcp --
practically, even if the tcp connection is not ready, the SIP
routing process is not blocked.<br>
<br>
If the connection is found or the connection was setup quickly,
then is not a risk of blocking and the message is sent
immediately.<br>
<br>
I guess all went ok with sip routing, right?<br>
<br>
Also, tcp is separate layer from sip transactions, so no
relation between them here, probably you will get the same by
using the forward*() functions, which don't create sip
transactions.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
</blockquote>
<blockquote type="CITE"> On 25/01/16 15:28, david escartin wrote:<br>
<br>
</blockquote>
<blockquote type="CITE">
<blockquote type="CITE"> hello all<br>
<br>
i'm facing some weird log from kamailio (i think they are
weird) when using sip tcp in the caller side and udp in the
callee side.<br>
<br>
seems like the tcp socket is active in the caller side and the
call is connected, since the invite transaction completes.<br>
After that, if we receive an in-dialog request from the callee
side, the kamailio doesnt find the tcp connection created and
it has to create again the socket by SYN procedure for the
other conn way.<br>
up to this point i think it's everything correct.<br>
<br>
<b>A----the thing i dont understand, is that checking version
4.2.6, the logs i have when the request in-dialog comes from
UAS, are like these</b><br>
<br>
5(2979) DEBUG: <core> [tcp_main.c:1820]: tcp_send():
tcp_send: no open tcp connection found, opening new one<br>
5(2979) DEBUG: <core> [ip_addr.c:243]: print_ip():
tcpconn_new: new tcp connection: 79.170.68.171<br>
5(2979) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new():
tcpconn_new: on port 5063, type 2<br>
5(2979) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add():
tcpconn_add: hashes: 1522:2178:0, 4<br>
<b>5(2979) DEBUG: <core> [tcp_main.c:2699]:
tcpconn_1st_send(): pending write on new connection
0x7fac1168f028 (-1/968 bytes written)</b><br>
5(2979) DEBUG: tm [t_funcs.c:395]: t_relay_to(): SER: new
transaction fwd'ed<br>
<br>
<b>B----while when using 4.2.2 or 4.4</b><br>
1(791) DEBUG: <core> [tcp_main.c:1818]: tcp_send():
tcp_send: no open tcp connection found, opening new one<br>
1(791) DEBUG: <core> [ip_addr.c:243]: print_ip():
tcpconn_new: new tcp connection: 79.170.68.171<br>
1(791) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new():
tcpconn_new: on port 5063, type 2<br>
1(791) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add():
tcpconn_add: hashes: 1522:3421:0, 4<br>
<b>1(791) INFO: <core> [tcp_main.c:2753]:
tcpconn_1st_send(): quick connect for 0x7f880540f758</b><br>
1(791) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new
transaction fwd'ed<br>
<br>
the difference between A and B is that in B i use dialog flags
to do the t_relay_to_tcp for the indialog requests (and not in
A), and in A i use the advertised IP in the listen addresses
since kamailio is behind a NAT, while B machine scenario has
public IPs.<br>
could those 2 things explain the ebhaviour difference?<br>
<br>
is there anything abnormal in the case B?<br>
<br>
thanks a lot and regards<br>
david escartin <br>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre>--
Daniel-Constantin Mierla
<a moz-do-not-send="true" href="http://twitter.com/#%21/miconda">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a moz-do-not-send="true" href="http://www.asipto.com">http://www.asipto.com</a>
<a moz-do-not-send="true" href="http://miconda.eu">http://miconda.eu</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://miconda.eu">http://miconda.eu</a></pre>
</body>
</html>