RTP Payload Formats » History » Revision 4
Revision 3 (laforge, 04/24/2018 03:24 PM) → Revision 4/5 (laforge, 04/24/2018 03:39 PM)
h1. RTP Payload Formats There are plenty different RTP payload formats around h2. Known Formats h3. GSM-FR as per IETF RFC 3551 h3. GSM-FR as per ETSI TS 101 318 h3. GSM-EFR as per IETF RFC 3551 h3. GSM-EFR as per ETSI TS 101 318 h3. GSM-HR as per IETF RFC 5993 h3. GSM-HR as per ETSI TS 101 318 h3. AMR as per IETF RFC 4867 h3. AMR-WB as per IETF RFC 4867 h2. Audio at various Interfaces h3. SIP-I based CS This is closest to what osmo-sip-connector offers to the outside world, and hence what we'd have to support from the msc-colocated MGW. See 3GPP TS 26.103 Section 7 _3GPP Codecs for OoBTC in a SIP-I -based Circuit Switched Core Network_ * AMR as per RFC 4867 ** The bandwidth efficient mode of RFC 4867 shall be used. CRC and robust sorting shall not be applied. * EFR as per RFC 3551 * FR as per RFC 3551 * HR as per RFC 5993 * PCMA as per RFC 5993 * PCMU as per RFC 3551 * audio/telephone-event as per RFC 4733 h3. 3GPP AoIP It's surprisingly hard to find where the RTP payload details for AoIP are specified... It's in 3GPP TS 48.103 Section 5.4.2.2 |_.Codec|_.RTP PT|_.Spec|_.Clock Freq| |uLaw|0|RFC 3551|8 kHz| |aLaw|8|RFC 3551|8 kHz| |GSM FR|3|RFC 3551|8 kHz| |GSM EFR|110|RFC 3551|8 kHz| |GSM HR|111|RFC 5993|8 kHz| |AMR-NB|113|RFC 4867|8 kHz| |AMR-WB|120|RFC 4040|16 kHz| |CSD|121|RFC 4040 + RFC 2198|8 kHz| AMR: According to TS 26.102 Section 9.2: "The bandwidth efficient mode of RFC 4867 shall be used. CRC and robust sorting shall not be applied. "
