Telestream PRISM MPI, User Manual

Page: 220 / 304

Application Information
IP Session Application
PRISM MPI-MPX User Manual
220
•
L5 RTP: Lists these parameters of the L5 RTP (Real Time Protocol) layer. RTP
Datagrams are defined in IETF RFC 3550.
– Version: Identifies the version of RTP and should be a value of 2.
– Padding: Indicates whether padding bytes are present. Possible values are:
false: Indicates no extra padding bytes are at the end of the RTP packet.
true: Indicates that padding octets have been added to the RTP packet that are
not part of the payload.
– Extension: Indicates whether an extension is present. Possible values are:
false: Indicates no extension is present.
true: Indicates an extension is present.
– CSRC: Identifies the Contributing Source IDs. This value should be set to zero.
– Marker: This value should be set to 1 to indicate the last Media Datagram of the
video frame. The value is set to 0 for all other Media Datagrams and should be 0
for most packets.
Note:
For 2022-6 signals, the status indicator turns red if the Marker Bit Frequency
does not match the frame rate indicated in the HBRMT header. For 2110 signals, the
status indicator turns red if the Marker Bit Frequency does not match the measured
field rate of the detected format.
– Payload type: Identifies the type of RTP payload.
– Sequence Number: RTP sequence counter changes in increments of one for each
RTP Media Datagram that is sent.
– Time Stamp: The timestamp reflects the sampling instant of the first octet in the
RTP datagram. This value can be used to determine packet sequence errors and
jitter calculations to be made.
Note:
For 2022-6 signals, the status indicator turns red if the Time Stamp field does
not change at the rate of 27 MHz on every packet. For 2110 signals, the status indicator
turns red if the Time Stamp field does not change at the start of every field or frame at
the rate of 90 kHz on every packet.
– SSRC: Identifies the Synchronization Source ID and is set in compliance with
RFC3550. This identifier is chosen randomly and should be unique so no two
SSRC have the same value with an RTP session.