RFC 5658: Addressing Record-Route Issues in the Session Initiation Protocol (SIP)

Publisher

IETF / RFC Editor

URL

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

Published

2009-10-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 5658 recommends that a proxy insert two Record-Route header values, one for the inbound interface and one for the outbound interface, instead of rewriting Record-Route in responses. in context
• A proxy that forwards between interfaces with different properties, such as TCP to UDP or IPv4 to IPv6, cannot write one Record-Route value that is correct for both sides of the dialog. in context
• If a proxy puts a numeric-IP Record-Route without a transport parameter, later in-dialog requests such as ACK or BYE default to UDP under RFC 3263 procedures. When the other side of the proxy used TCP, those requests fail. in context

Cite this source record

APA

WarmTransfer. (2009, October 1). RFC 5658: Addressing Record-Route Issues in the Session Initiation Protocol (SIP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-5658-record-route-issues

BibTeX

@misc{warmtransfer-rfc-5658-record-route-issues,
  title  = {RFC 5658: Addressing Record-Route Issues in the Session Initiation Protocol (SIP)},
  author = {{WarmTransfer}},
  year   = {2009},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-5658-record-route-issues},
  note   = {IETF / RFC Editor, accessed 2026-09-25}
}