RTP Payload Formats » History » Version 2
laforge, 04/24/2018 03:20 PM
| 1 | 1 | laforge | h1. RTP Payload Formats |
|---|---|---|---|
| 2 | |||
| 3 | There are plenty different RTP payload formats around |
||
| 4 | |||
| 5 | h2. Known Formats |
||
| 6 | |||
| 7 | h3. GSM-FR as per IETF RFC 3551 |
||
| 8 | |||
| 9 | h3. GSM-FR as per ETSI TS 101 318 |
||
| 10 | |||
| 11 | h3. GSM-EFR as per IETF RFC 3551 |
||
| 12 | |||
| 13 | h3. GSM-EFR as per ETSI TS 101 318 |
||
| 14 | |||
| 15 | h3. GSM-HR as per IETF RFC 5993 |
||
| 16 | |||
| 17 | h3. GSM-HR as per ETSI TS 101 318 |
||
| 18 | |||
| 19 | h3. AMR as per IETF RFC 4867 |
||
| 20 | |||
| 21 | h3. AMR-WB as per IETF RFC 4867 |
||
| 22 | |||
| 23 | h2. Audio at various Interfaces |
||
| 24 | |||
| 25 | 2 | laforge | h3. SIP-I based CS |
| 26 | 1 | laforge | |
| 27 | 2 | laforge | 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. |
| 28 | |||
| 29 | See 3GPP TS 26.103 Section 7 _3GPP Codecs for OoBTC in a SIP-I -based Circuit Switched Core Network_ |
||
| 30 | |||
| 31 | 1 | laforge | * AMR as per RFC 4867 |
| 32 | * EFR as per RFC 3551 |
||
| 33 | * FR as per RFC 3551 |
||
| 34 | * HR as per RFC 5993 |
||
| 35 | * PCMA as per RFC 5993 |
||
| 36 | * PCMU as per RFC 3551 |
||
| 37 | * audio/telephone-event as per RFC 4733 |
||
| 38 | |||
| 39 | h3. 3GPP AoIP |
||
| 40 | |||
| 41 | 2 | laforge | 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 |
| 42 | |||
| 43 | |_.Codec|_.RTP PT|_.Spec|_.Clock Freq| |
||
| 44 | |uLaw|0|RFC 3551|8 kHz| |
||
| 45 | |aLaw|8|RFC 3551|8 kHz| |
||
| 46 | |GSM FR|3|RFC 3551|8 kHz| |
||
| 47 | |GSM EFR|110|RFC 3551|8 kHz| |
||
| 48 | |GSM HR|111|RFC 5993|8 kHz| |
||
| 49 | |AMR-NB|113|RFC 4867|8 kHz| |
||
| 50 | |AMR-WB|120|RFC 4040|16 kHz| |
||
| 51 | |CSD|121|RFC 4040 + RFC 2198|8 kHz| |
