RFC 6314: NAT Traversal Practices for Client-Server SIP

Publisher

IETF / RFC Editor

URL

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

Published

2011-07-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 6314 notes that NAT policy can close connections after a period of inactivity. It points to RFC 5626 (SIP Outbound) keep-alives, rather than SIP signaling itself, as the way to keep NAT bindings open. in context
• RFC 6314, an Informational RFC from July 2011, assumes NATs without SIP-aware ALGs. It notes that ALGs have limits, including needing signaling and media to pass through the same device and failing with encrypted signaling. in context

Cite this source record

APA

WarmTransfer. (2011, July 1). RFC 6314: NAT Traversal Practices for Client-Server SIP. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6314-nat-traversal-sip

BibTeX

@misc{warmtransfer-rfc-6314-nat-traversal-sip,
  title  = {RFC 6314: NAT Traversal Practices for Client-Server SIP},
  author = {{WarmTransfer}},
  year   = {2011},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6314-nat-traversal-sip},
  note   = {IETF / RFC Editor, accessed 2026-09-25}
}