AudioCodes MP-1FXO Bedienungsanleitung PDF herunterladen (Seite 210)

MediaPack

SIP User's Manual 210 Document #: LTRT-65408

6.3 The ini File Structure

The ini file can contain any number of parameters. The parameters are divided into groups

by their functionality. The general form of the ini file is shown in Figure 6-1 below.

Figure 6-1: ini File Structure

[Sub Section Name]

Parameter_Name = Parameter_Value

; REMARK

[Sub Section Name]

6.3.1 The ini File Structure Rules

 The ini file name mustn’t include hyphens or spaces, use underscore instead.

 Lines beginning with a semi-colon ‘;’ (as the first character) are ignored.

 A Carriage Return must be the final character of each line.

 The number of spaces before and after ‘=’ is not relevant.

 If there is a syntax error in the parameter name, the value is ignored.

 Syntax errors in the parameter value field can cause unexpected errors (because

parameters may be set to the wrong values).

 Sub-section names are optional.

 String parameters, representing file names, for example CallProgressTonesFileName,

must be placed between two inverted commas (‘…’).

 The parameter name is NOT case-sensitive; the parameter value is not case-sensitive

except for coder names.

 The ini file should be ended with one or more carriage returns.

6.3.2 The ini File Example

Figure 6-2 shows an example of an ini file for the VoIP gateway.

Figure 6-2: SIP ini File Example

[Channel Params]

DJBufMinDelay = 75

RTPRedundancyDepth = 1

DefaultNumber = 101

MaxDigits = 3

CoderName = g7231,90

; Phone of each endpoint

EnableSyslog = 0

[Files]

CallProgressTonesFilename = 'CPUSA.dat'

FXSLoopCharacteristicsFileName = 'coeff.dat'

SaveConfiguration = 1

1 2 ... 205 206 207 208 209 210 211 212 213 214 215 ... 389 390

Keine Kommentare

AudioCodes MP-1FXO Bedienungsanleitung Seite 210