Hi
I think I got the tcp_crlf_ping and the tcp_keepalive parameters mixed up.
So for tcp_crlf_ping, Kamailio will only respond. While for tcp_keepalive parameters, if enabled on both server and client, both will be sending the keepalives, and the receiver will respond.
In order to use tcp_crlf_ping, client's app level rather than TCP level would have to send the crlfcrlf (pings) and process the crlf (pongs) in order to detect if Kamailio is up. Is this right?
Yufei
On 03/02/12 11:00, sr-users-request@lists.sip-router.org wrote:
Send sr-users mailing list submissions to sr-users@lists.sip-router.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request@lists.sip-router.org
You can reach the person managing the list at sr-users-owner@lists.sip-router.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..."
Today's Topics:
- TCP keepalive on server and client (Yufei Tao)
Message: 1 Date: Fri, 3 Feb 2012 10:33:11 +0000 From: Yufei Tao yufei.tao@redembedded.com Subject: [SR-Users] TCP keepalive on server and client To: sr-users@lists.sip-router.org Message-ID: 4F2BB7E7.2090601@redembedded.com Content-Type: text/plain; charset="ISO-8859-1"
Hi
I want to use TCP keepalive to detect dead connections between Kamailio and my SIP clients. I've got some questions about this:
- If I enable it on Kamailio by setting for example:
tcp_crlf_ping = yes tcp_keepalive = yes tcp_keepidle = 60 tcp_keepintvl = 10 tcp_keepcnt = 3
From what I read by gooling, that means Kamailio only responds to the
crlfcrlf sent by the client, but can't be configured to send the crlfcrlf. Is this right?
- On my client, if I use setsockopt to set the corresponding values:
SO_KEEPALIVE TCP_KEEPCNT TCP_KEEPIDLE TCP_KEEPINTVL
would it make the client send crlfcrlf?
The reason I'm confused is, with these settings, if Kamailio can only respond to crlfcrlf, but not send, then would the client only respond too, as in 1. and 2., they seem to configure the same set of parameters? Please help me clarify this. Thanks very much!
Yufei
-- Yufei Tao Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 81, Issue 7
-- Yufei Tao Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
On 03.02.2012 12:06, Yufei Tao wrote:
Hi
I think I got the tcp_crlf_ping and the tcp_keepalive parameters mixed up.
So for tcp_crlf_ping, Kamailio will only respond.
Yes.
While for tcp_keepalive parameters, if enabled on both server and client, both will be sending the keepalives, and the receiver will respond.
I have not tried it yet, but I think it is sufficiemt if only one side activates the keep-alive (a socket option). But of course only the party which set the keep-alive option on the socket is capable of detecting the connection loss.
In order to use tcp_crlf_ping, client's app level rather than TCP level would have to send the crlfcrlf (pings) and process the crlf (pongs) in order to detect if Kamailio is up. Is this right?
Yes.
regards Klaus
Yufei
On 03/02/12 11:00, sr-users-request@lists.sip-router.org wrote:
Send sr-users mailing list submissions to sr-users@lists.sip-router.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request@lists.sip-router.org
You can reach the person managing the list at sr-users-owner@lists.sip-router.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..."
Today's Topics:
1. TCP keepalive on server and client (Yufei Tao)
Message: 1 Date: Fri, 3 Feb 2012 10:33:11 +0000 From: Yufei Taoyufei.tao@redembedded.com Subject: [SR-Users] TCP keepalive on server and client To:sr-users@lists.sip-router.org Message-ID:4F2BB7E7.2090601@redembedded.com Content-Type: text/plain; charset="ISO-8859-1"
Hi
I want to use TCP keepalive to detect dead connections between Kamailio and my SIP clients. I've got some questions about this:
- If I enable it on Kamailio by setting for example:
tcp_crlf_ping = yes tcp_keepalive = yes tcp_keepidle = 60 tcp_keepintvl = 10 tcp_keepcnt = 3
From what I read by gooling, that means Kamailio only responds to the
crlfcrlf sent by the client, but can't be configured to send the crlfcrlf. Is this right?
On my client, if I use setsockopt to set the corresponding values:
SO_KEEPALIVE TCP_KEEPCNT TCP_KEEPIDLE TCP_KEEPINTVL
would it make the client send crlfcrlf?
The reason I'm confused is, with these settings, if Kamailio can only respond to crlfcrlf, but not send, then would the client only respond too, as in 1. and 2., they seem to configure the same set of parameters? Please help me clarify this. Thanks very much!
Yufei
-- Yufei Tao Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 81, Issue 7
-- Yufei Tao Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users