RFC 6432: Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses

Publisher

IETF / RFC Editor

URL

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

Published

2011-11-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust; BCP 78 and the Trust Legal Provisions; excerpts permitted with attribution under IETF Trust terms; short excerpts and locators only

Source notes citing this source

• RFC 6432 allows any SIP response except 100 (Trying) to carry a Reason header field with a Q.850 cause code. in context
• RFC 6432 states that the presence of a Reason header field in a response does not affect the treatment of the response. in context
• RFC 6432 allows any SIP response other than 100 Trying to carry a Reason header field with a Q.850 cause code. in context
• RFC 6432 permits any SIP response except 100 Trying to carry a Reason header with a Q.850 cause code; it permits but does not mandate this. in context
• RFC 6432 recommends integrity protection (for example TLS or IPsec) for Reason headers carrying Q.850 codes because a wrong code could trigger the wrong announcement. in context

Cite this source record

APA

WarmTransfer. (2011, November 1). RFC 6432: Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6432-q850-in-responses

BibTeX

@misc{warmtransfer-rfc-6432-q850-in-responses,
  title  = {RFC 6432: Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses},
  author = {{WarmTransfer}},
  year   = {2011},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6432-q850-in-responses},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}