SIP User's Manual
5
.
MediaPack
Configuration Tools
Version 2.4
159
June 2008
interface sip
interface isdn
gateway sip
5.4
MediaPack Configuration File
As an alternative to configuring the VoIP gateway using the Web interface (described in
Section '
797H823H
Embedded Web Server
' on page
798H824H
53
) or the CLI (refer to Section '
799H825H
Embedded
Command Line Interface
' on page
800H826H
56
), you can configure the MediaPack by loading the
configuration
file containing customer-configured parameters.
The
configuration
file is loaded to the MediaPack using the Web interface or the CLI using
a standard TFTP server (refer to Section
827H
6.4 on page
802H828H
119).
The
configuration
file is stored in the MediaPack's non-volatile memory after the file is
loaded. When a parameter is missing from the
configuration
file, a default value is assigned
to that parameter. Therefore, to restore the default configuration parameters, load an
empty configuration file to the MediaPack.
Notes:
•
Some of the MediaPack parameters are only configurable through the
configuration file or the CLI (and not through the Web interface).
•
The configuration file can only be used to change the startup
configuration. Therefore, after loading this file to the MediaPack (via
CLI or Web), the MediaPack must be reset for the changes to take
affect.
5.4.1 Configuration
File
Structure
The structure of the configuration file is similar to the structure of the CLI. For example,
specific parameters must be entered in context of their operation mode, and the
Configuration Modes that aren’t updated on-the-fly must be terminated with a ‘no
shutdown’ command (refer to Section '
803H829H
Shutdown / No Shutdown
' on page
804H830H
60
).
The following general rules apply to the structure of the configuration file:
Lines beginning with a number ‘#’ sign (as the first character) are ignored.
A carriage return must be the final character of each line.
The
configuration
file must end with one or more carriage returns.
5.4.2 Modifying
a
Configuration File
¾
To modify the configuration file:
1.
Save the
configuration
file on the gateway to a folder on your PC using the CLI or
embedded Web server (refer to Section
831H
6.4 on page
802H832H
119) or alternatively use the
default Configuration file supplied with the Software package.
2.
Open the file (the file is opened in Notepad or a Customer-defined text file editor) and
modify the
configuration
file parameters according to your requirements; save and
close the file.
3.
Load the modified
configuration
file to the gateway using CLI or the Embedded Web
Server (refer to Section
833H
6.4 on page
802H834H
119).
