RtpPacket Properties |
The RtpPacket type exposes the following members.
Name | Description | |
---|---|---|
CreationTime |
Gets the CreationTime property.
| |
DataPointer |
A pointer to the payload data that will be attached to the RTP packet.
| |
DataSize |
The size of the payload attached to the RTP packet.
| |
EndBitOffset |
Gets or sets the Offset of the last valid bit.
| |
HeaderExtension |
Gets or sets optional header extension to transport additional profile defined information.
| |
HeaderSize |
The RTP Header Length in bytes.
| |
IsValidPacket |
Indicates whether this packet is valid.
This is especially useful when the parsing of data is done through the constructor of the object. | |
Marker |
This represents the Marker bit. This is mostly used for framing.
| |
PayloadType |
The PayloadType of the packet. (http://www.iana.org/assignments/rtp-parameters)
| |
PresentationTime |
When used together with PlayoutBuffer this will contain the presentation time of the
packet.
| |
SequenceNumber |
The sequence number increments by one for each RTP data packet sent, and may be used by
the receiver to detect packet loss and to restore packet sequence. The initial value of
the sequence number SHOULD be random (unpredictable) to make known-plaintext attacks on
encryption more difficult. The sequence number is originally 16-bit signed. An extended
Sequence number scheme CAN be used to avoid frequent wrap around (See class
ExtendedSequenceNumber).
| |
Ssrc |
The Ssrc field identifies the synchronization source. It is chosen randomly.
| |
StartBitOffset |
Gets or sets the Offset of the first valid bit.
| |
Timestamp |
The timestamp reflects the sampling instant of the first octet in the RTP data packet.
The sampling instant MUST be derived from a clock that increments monotonically and
linearly in time to allow synchronization and jitter calculations. The resolution of the
clock must be sufficient for the desired synchronization accuracy and for measuring
packet arrival jitter (one tick per video frame is typically not sufficient). The clock
frequency is dependent on the format of data carried as payload and is specified
statically in the profile or payload format specification that defines the format, or may
be specified dynamically for payload formats defined through non-RTP means. If RTP
packets are generated periodically, the nominal sampling instant as determined from the
sampling clock is to be used, not a reading of the system clock. As an example, for
fixed-rate audio the timestamp clock would likely increment by one for each sampling
period.
| |
Version |
Contains the Version Number of the RTP packet. The value should always be 2.
|