Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in SIP

Publisher

IETF / RFC Editor

URL

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

Published

2010-10-01

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

IETF Trust legal provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 6044 maps Diversion reason unconditional to History-Info cause 302, user-busy to 486 and no-answer to 408. in context
• RFC 6044 states that new implementation and deployment of the Diversion header is strongly discouraged. in context
• Diversion entries are in reverse chronological order (the first entry is the last diverting user), whereas History-Info entries are chronological. in context

Cite this source record

APA

WarmTransfer. (2010, October 1). Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in SIP. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6044-diversion-history-info

BibTeX

@misc{warmtransfer-rfc-6044-diversion-history-info,
  title  = {Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in SIP},
  author = {{WarmTransfer}},
  year   = {2010},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6044-diversion-history-info},
  note   = {IETF / RFC Editor, accessed 2026-10-02}
}