I think it is encouraged this way so that the SIP stack can
have its own timeout.  Some TCP/IP stacks take a while to timeout
and the timeout on a TCP/IP stack isn't always configurable 
on a "per TCP connection" basis.



 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Iñaki Baz 
Castillo
Sent: 06 November 2008 11:40
To: SIPImplementors Mailing list
Subject: [Sip-implementors] Why TCP keep-alive (PingPong) requires 
registrarreplyng single CRLF?

Hi, TCP keep-alive (PingPong) works as follows:
- The client, after registering, sends periodically double CRLF to the 
registrar.
- The registrar replies single CRLF.

Why is required the registrar replying single CRLF in order to mantain the TCP 
connection open?
Wouldn't be enough with the client sending CRLF CRLF?

Thanks.

--
Iñaki Baz Castillo
<[EMAIL PROTECTED]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to