RFC 3204: MIME media types for ISUP and QSIG Objects

Publisher

RFC Editor / IETF

URL

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

Published

2001-12-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• The application/ISUP media type requires a version parameter identifying the ISUP variant and allows an optional base parameter. in context
• RFC 3204 registers the MIME media types application/ISUP and application/QSIG for carrying those signalling objects in SIP bodies. in context
• RFC 3204 registers the MIME media types application/ISUP and application/QSIG for carrying ISUP and QSIG objects in SIP message bodies. in context
• RFC 3204 says that when the Content-Disposition handling parameter is absent on an ISUP or QSIG body, handling=required is assumed, so a UAS that does not understand the body returns 415 Unsupported Media Type; with handling=optional the UAS ignores it. in context
• The application/ISUP media type requires a version parameter identifying the ISUP variant and allows an optional base parameter naming a fallback specification. in context

Cite this source record

APA

WarmTransfer. (2001, December 1). RFC 3204: MIME media types for ISUP and QSIG Objects. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-3204-isup-qsig-mime

BibTeX

@misc{warmtransfer-rfc-3204-isup-qsig-mime,
  title  = {RFC 3204: MIME media types for ISUP and QSIG Objects},
  author = {{WarmTransfer}},
  year   = {2001},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-3204-isup-qsig-mime},
  note   = {RFC Editor / IETF, accessed 2026-09-24}
}