Source note · SIP call forwarding and routing loops
RFC 3261 requires a SIP UAC to insert a Max-Forwards header field into each request it originates, with an initial value that should be 70.
Checked 2026-09-25
- Vendor
- IETF
- Product
- SIP
- Subsystem
- Max-Forwards
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261 (June 2002)
- Checked
- 2026-09-25
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 8.1.1.6 Max-Forwards
Cite this note
APA
WarmTransfer. (2026, September 25). SIP call forwarding and routing loops: source note sip-forwarding-loops-uac-max-forwards-70. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-forwarding-loops-uac-max-forwards-70
BibTeX
@misc{warmtransfer-claim-sip-forwarding-loops-uac-max-forwards-70,
title = {SIP call forwarding and routing loops: source note sip-forwarding-loops-uac-max-forwards-70},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-forwarding-loops-uac-max-forwards-70},
note = {Source note sip-forwarding-loops-uac-max-forwards-70, checked 2026-09-25}
}