Source record · tier 1 standards and regulators
RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Networks
- Publisher
- IETF / RFC Editor
- URL
- https://www.rfc-editor.org/rfc/rfc7989.html
- Published
- 2016-10-01
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- IETF Trust Legal Provisions; IETF text may be quoted with attribution; short excerpts and locators only
Source notes citing this source
- RFC 7989 states that intermediaries such as session border controllers alter call identifiers in signaling, so the SIP Call-ID is not suitable for tracking a session end to end. in context
- RFC 7989 obsoletes RFC 7329, the earlier pre-standard Session-ID specification. in context
- RFC 7989 requires B2BUAs to preserve Session-ID values when forwarding messages so identifiers stay consistent across dialog legs. in context
- A Session-ID value is a local UUID with an optional remote parameter carrying the peer UUID, each written as 32 lowercase hexadecimal characters, with an all-zero nil UUID used when the peer is unknown. in context
- The SIP Session-ID header defined in RFC 7989 lets endpoints, intermediaries and management systems identify a session end to end, including across redirection. in context
- Because SBCs and B2BUAs change the Call-ID between legs, an escalation to a carrier should quote the identifiers seen on the carrier-facing leg (its Call-ID, numbers and UTC-or-zoned timestamp) rather than an internal platform ID such as a Teams Correlation ID. inferred in context
Cite this source record
APA
WarmTransfer. (2016, October 1). RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Networks. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-7989-sip-session-id
BibTeX
@misc{warmtransfer-rfc-7989-sip-session-id,
title = {RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Networks},
author = {{WarmTransfer}},
year = {2016},
url = {https://warmtransfer.net/knowledge/sources/rfc-7989-sip-session-id},
note = {IETF / RFC Editor, accessed 2026-09-24}
}