RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc5626.html

Published

2009-10-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions; RFC text may be reproduced under IETF Trust terms; excerpts kept short regardless

Source notes citing this source

• RFC 5626 defines a keepalive for connection-oriented transports in which the client sends a double CRLF and the server answers with a single CRLF. in context
• RFC 5626 says the upper bound for CRLF keepalive intervals should be 120 seconds, with 95 seconds as the lower bound. in context
• In RFC 5626, a Flow-Timer header in a successful registration response gives the number of seconds the server will wait without seeing keepalives. in context
• For connectionless transports such as UDP, RFC 5626 uses STUN Binding Requests over the flow as the keepalive, sent at random intervals of 24 to 29 seconds. in context

Cite this source record

APA

WarmTransfer. (2009, October 1). RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-5626-sip-outbound

BibTeX

@misc{warmtransfer-rfc-5626-sip-outbound,
  title  = {RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)},
  author = {{WarmTransfer}},
  year   = {2009},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-5626-sip-outbound},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}