Attribute key value.

Represents an SDP attribute.

Sdp bandwidth.

Abstract base class for all SDP fields.

A session announcement must contain one Connection field in each media description (see below) or a Connection field at the session-level. It may contain a session-level Connection field and one additional Connection field per media description, in which case the per-media values override the session-level settings for the relevant media.

Contact Type Email.

The Info field is information about the session. There may be at most one session-level "i=" field per session description, and at most one Info field per media. Although it may be omitted, this is discouraged for session announcements, and user interfaces for composing sessions should require text to be entered. If it is present it must contain ISO 10646 characters (but see also the 'charset' attribute below).
A single Info field can also be used for each media definition. In media definitions, Info fields are primarily intended for labeling media streams. As such, they are most likely to be useful when a single session has more than one distinct media stream of the same media type. An example would be two different whiteboards, one for slides and one for feedback and questions.

A session description may contain a number of media descriptions. Each media description starts with an "m=" field, and is terminated by either the next "m=" field or by the end of the session description.

Provides the creation of SDPMedia objects by passing video or audio encoder interfaces.

SDPMessage is responsible for parsing or compiling all Fields contained in a SDP Message.

The Origin field gives the originator of the session (their username and the address of the user's host) plus a session id and session version number.

Contact Type Phone.

The Session field is the session name. There must be one and only one Session field per session description, and it must contain ISO 10646 characters (but see also the `charset' attribute below).

Time fields specify the start and stop times for a conference session. Multiple "t=" fields may be used if a session is active at multiple irregularly spaced times; each additional "t=" field specifies an additional period of time for which the session will be active. If the session is active at regular times, an "r=" field (see below) should be used in addition to and following a "t=" field - in which case the "t=" field specifies the start and stop times of the repeat sequence.

o A URI is a Universal Resource Identifier as used by WWW clients
o The URI should be a pointer to additional information about the conference
o This field is optional, but if it is present it should be specified before the first media field
o No more than one URI field is allowed per session description

The Version field gives the version of the Session Description Protocol. There is no minor version number.

Interface for message appendix.

Values that represent the available fields in an SDP message.