Mapping Payload Numbers To Coders; Table 7-25: Table 32: Megaco Mapping Payload Numbers To Coders - AudioCodes Mediant 2000 User Manual

The negotiation results in an error if there is no supported SDP at the end of it. This
can be caused by one of the following:
1. The MGC requests a secured connection ONLY, but the Gateway does not
support it.
2. The Gateway supports SRTP, but not the suite requested by the MGC.
3. The remote side sends SDP with a secured connection ONLY and the Gateway
does not support it.
4. The suites sent by the remote side are not supported by the Gateway.
5. The suite (sent by MGC or remote side) is supported, but there are session
parameters that are not support or contains more than one key.
7.2.5

Mapping Payload Numbers to Coders

The table below shows the default mapping between payload numbers and coders
when the dynamic payload assignment is not used. Note that this is a general table
and only the DSP template that is loaded to a Mediant 2000 defines which coder is
supported on this Mediant 2000.
These values can be overridden by the external CoderTbl.

Table 7-25: Table 32: MEGACO Mapping Payload Numbers to Coders

Default Payload Encoding Name
Number
0 "PCMU"
2 "G726-32"
3 "GSM"
84 "GSM-EFR"
4 "G723"
80 "G723"
8 "PCMA"
15 "G728"
18 "G729"
35 "G726-16"
36 "G726-24"
38 "G726-40"
39 "X-G727-16"
40 "X-G727-24-16"
41 "X-G727-24"
42 "X-G727-32-16"
43 "X-G727-32-24"
User's Manual
Coder
G711Mulaw
G726_32
GSM
GSM-EFR
G723 (High)
G723 (Low)
G711Alaw_64
G728
G729
G726_16
G726_24
G726_40
G727_16
G727_24_16
G727_24
G727_32_16
G727_32_24
142
Mediant 2000
Document # LTRT-69805