![background image](http://html1.mh-extra.com/html/3com/v6100/v6100_user-manual-manual_3139483191.webp)
V6100 and V7122 User Guide
191
ini File Field Name
Web Parameter Name
Valid Range and Description
The coder name is case-sensitive.
If silence suppression is not defined (for a specific coder), the
value defined by the parameter EnableSilenceCompression is
used.
The value of several fields is hard-coded according to well-
known standards (e.g., the payload type of G.711 U-law is
always 0). Other values can be set dynamically. If no value is
specified for a dynamic field, a default value is assigned. If a
value is specified for a hard-coded field, the value is ignored.
Only the ptime of the first coder in the defined coder list is
declared in INVITE / 200 OK SDP, even if multiple coders are
defined.
If the coder G.729 is selected and silence suppression is
disabled (for this coder), the gateway includes the string
‘annexb=no’ in the SDP of the relevant SIP messages. If
silence suppression is enabled or set to ‘Enable w/o
Adaptations’, ‘annexb=yes’ is included. An exception to this
logic is when the remote gateway is a Cisco device
(IsCiscoSCEMode).
Both GSM-FR and MS-GSM coders use Payload Type = 3.
Using SDP, it isn’t possible to differentiate between the two.
Therefore, it is highly recommended not to select both coders
simultaneously.
For example:
CoderName = g711Alaw64k,20,,,0
CoderName = g711Ulaw64k,40
CoderName = g7231,90,1,,1
CoderName = g726,$$,2,,0
AMRPayloadType
Obsolete parameter, use CoderName instead.
AMRSendRate
Obsolete parameter, use CoderName instead.
EVRCRate
Obsolete parameter, use CoderName instead.
EVRCPayloadType
Obsolete parameter, use CoderName instead.
TransparentPayloadType
Obsolete parameter, use CoderName instead.
DSPVersionTemplateNumb
er
[DSP Version Template
Number]
Determines the number of the DSP load (doesn’t apply to the V6100). Each
load has a different coder list, a different channel capacity and different
supported features.
Available values are 0, 1, 2 and 3.
For detailed information on the supported coders and channel capacity, see
the Release Notes.
VBRCoderHeaderFormat
Defines the format of the RTP header for VBR coders.
0 = Payload only (no header, no TOC, no m-factor) (default).
1 = Supports RFC 2658 - 1 byte for interleaving header (always 0), TOC,
no m-factor.
2 = Payload including TOC only, allow m-factor.
3 = RFC 3358.
Summary of Contents for V6100
Page 28: ...28 V6100 and V7122 User Guide Reader s Notes...
Page 48: ...48 V6100 and V7122 User Guide Reader s Notes...
Page 72: ...72 V6100 and V7122 User Guide Reader s Notes...
Page 80: ...80 V6100 and V7122 User Guide Reader s Notes...
Page 152: ...152 V6100 and V7122 User Guide Reader s Notes...
Page 262: ...262 V6100 and V7122 User Guide Reader s Notes...
Page 284: ...284 V6100 and V7122 User Guide Reader s Notes...
Page 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process...
Page 324: ...324 V6100 and V7122 User Guide Reader s Notes...
Page 354: ...354 V6100 and V7122 User Guide Reader s Notes...
Page 374: ...374 V6100 and V7122 User Guide Reader s Notes...
Page 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes...
Page 392: ...392 V6100 and V7122 User Guide Reader s Notes...
Page 409: ...V6100 and V7122 User Guide 409 Reader s Notes...
Page 413: ...V6100 and V7122 User Guide 413 Reader s Notes...
Page 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes...
Page 431: ...V6100 and V7122 User Guide 431 Reader s Notes...
Page 447: ...V6100 and V7122 User Guide 447 Reader s Notes...
Page 483: ...V6100 and V7122 User Guide 483 Reader s Notes...