Difference between revisions of "RTP"
(→RTP) |
(→RTP) |
||
| Line 11: | Line 11: | ||
- PT (Payload Type) tags the content of the packet. Some standardized values exist, but for other codecs, the type must be described in a service description protocol, SDP (Session DescriptionProtocol); | - PT (Payload Type) tags the content of the packet. Some standardized values exist, but for other codecs, the type must be described in a service description protocol, SDP (Session DescriptionProtocol); | ||
The following table shows the defined RTP payload types. | The following table shows the defined RTP payload types used in Barix firmware. | ||
Note that Payload types 0, 8, 10, 11 and 14 are defined by the RTP standard while types 96 to 112 (dynamic payload types) are Barix specific. | |||
Revision as of 17:50, 26 March 2009
RTP
RTP (Real-time Transport Protocol) has been designed for the transport of multimedia streams over IP networks. It works on top of UDP. It was developed by the Audio-Video Transport Working Group of the IETF [1] and first published in 1996 as RFC 1889, and superseded by RFC 3550 in 2003.
IP networks are asynchronous and may lose or reorder packets.
Some fields in RTP are defined to address these problems:
- PT (Payload Type) tags the content of the packet. Some standardized values exist, but for other codecs, the type must be described in a service description protocol, SDP (Session DescriptionProtocol);
The following table shows the defined RTP payload types used in Barix firmware. Note that Payload types 0, 8, 10, 11 and 14 are defined by the RTP standard while types 96 to 112 (dynamic payload types) are Barix specific.
| μ-Law, 8bit, mono, 8kHz | |
| A-Law, 8bit, mono, 8kHz | |
| PCM 16bit, MSB first, signed, 44.1kHz stereo, left channel first | |
| PCM 16bit, MSB first, signed, 44.1kHz mono | |
| MPEG audio | |
| PCM, 16bit, MSB first, signed, 8kHz mono | |
| μ-Law, 8bit, mono, 24kHz | |
| A-Law, 8bit, mono, 24kHz | |
| PCM, 16bit, MSB first, signed, 24kHz mono | |
| μ-Law, 8bit, mono, 32kHzreserved | |
| A-Law, 8bit, mono, 32kHzreserved | |
| PCM, 16bit, MSB first, signed, 32kHz monoreserved | |
| PCM 16bit, MSB first, signed, 48kHz stereo, left channel first | |
| PCM, 16bit, LSB first, signed, 8kHz mono | |
| PCM, 16bit, LSB first, signed, 24kHz mono | |
| PCM, 16bit, LSB first, signed, 32kHz monoreserved | |
| PCM 16bit, LSB first, signed, 44.1kHz stereo, left channel first | |
| PCM 16bit, LSB first, signed, 48kHz stereo, left channel first | |
| μ-Law, 8bit, mono, 12kHz | |
| A-Law, 8bit, mono, 12kHz | |
| PCM, 16bit, MSB first, signed, 12kHz mono | |
| PCM, 16bit, LSB first, signed, 12kHz mono | |
| Generic (see below) |
- sequence number is primarily used to identify and detect lost packets and secondly to reconstruct the order in which packets where sent, which may make loss detection easier;
- the timestamp is the sampling instant for the first octet of media data in a packet. It can be used to help recover the clock frequency at the receiving side, if it is not given by other means.
RTP does not include a loss recovery mechanism in case of packet losses.
Check the Wikipedia for an introduction to the topic [2].
