RFC 5626 keeps UDP SIP flows alive with periodic STUN Binding Requests sent over the flow.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- NAT traversal
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 5626
- Checked
- 2026-10-02
Sources
- RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) — IETF / RFC Editor · tier 1 standards and regulators · Section 4.4.2
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc5626-stun-keepalive. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5626-stun-keepalive
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-rfc5626-stun-keepalive,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-rfc5626-stun-keepalive},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-rfc5626-stun-keepalive},
note = {Source note sip-trunk-authentication-models-rfc5626-stun-keepalive, checked 2026-10-02}
}