Hi, Rodrigo!
The logs you are tracing are printed when OpenSIPS receives something
from the client, and then immediately responds back. Due to the fact
that we don't see any other debug messages, like SIP parsing & stuff,
makes me think that it is a CRLF pinging - the client periodically sends
a CRLFCRLF TCP message to OpenSIPS, and OpenSIPS responds with a single
CRLF. Note that this is different from a TCP keep-alive, where each peer
send a 0-length TCP message, without any body. That message doesn't even
get to the application layer.
However, tracing the communication between OpenSIPS and the client
should confirm the above :).
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 10/26/2016 05:10 PM, Rodrigo Pimenta Carvalho wrote:
Dear OpenSIPS users,
In the OpenSIPS log I see:
Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38
[3451] DBG:core:tcp_read_req: Using the global ( per process ) buff
Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38
[3451] DBG:core:tcp_handle_req: content-length= 0
Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38
[3451] DBG:core:async_tsend_stream: Async successful write from first
try on 0x74e13548
Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38
[3451] DBG:core:tcp_read_req: tcp_read_req end
The frequency is 1 time at each 1,5 minute. There is only one client
online. I suspect that OpenSIPS uses the socket 0x74e13548 to send
messages to such client. The client became online using TCP.
Just to confirm, is this log a result of a TCP keep alive function
enabled?
Best regards.
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
