SIP - Message Body Header Fields

Content-Encoding

The Content-Encoding header field is used to indicate that the listed encoding scheme has been applied to the message body. It allows the UAS to determine the decoding scheme necessary to interpret the message body.

• Only those encoding schemes listed in an Allow-Encoding header field may be used.

• The compact form is e.

Examples:
Content-Encoding: text/plain
e: gzip

Content-Disposition

The Content-Disposition header field is used to describe the function of a message body. Values include session, icon, alert, and render.

The value session indicates that the message body contains information to describe a media session.

Content-Language

The Content-Language header field is used to indicate the language of a message body. It contains a language tag, which identifies the language.

Example:
Content-Language: en

Content-Length

The Content-Length is used to indicate the number of octets in the message body.

A Content-Length: 0 indicates no message body.

Content-Type

The Content-Type header field is used to specify the Internet media type in the message body.

• Media types have the familiar form of type/sub-type.

• If this header field is not present, application/sdp is assumed.

• If an Accept header field was present in the request, the response Content-Type must contain a listed type, or a 415 Unsupported Media Type response must be returned.

• The compact form is c.

Example:
Content-Type: application/sdp

MIME-Version

The MIME-Version header field is used to indicate the version of MIME protocol used to construct the message body.

SIP, like HTTP, is not considered MIME compliant because parsing and semantics are defined by the SIP standard, not the MIME specification. Version 1.0 is the default value.

Example:
MIME-Version: 1.0