
66
Configuration File Handling
Software Configuration Guide, Revision 1.03
mtu 1500
# interface WAN used for connection to access network
interface wan
ipaddress 172.19.32.30 255.255.255.0
mtu 1500
# interface used to access the PSTN telecom operator
interface pstn pstn-operator
routing dest-interface h323
bind port 1 0
# interface used to access the VoIP telecom provider
interface h323 voip-provider
routing dest-table rtab
remoteip 172.19.33.60
# H.323 gateway primarily used
gateway h323
codec g711alaw64k 10 20
codec g711ulaw64k 10 20
faststart
no ras
gatekeeper-discovery auto
bind interface lan router
use voip-profile default
no shutdown
port ethernet 0 0
medium auto
encapsulation ip
bind interface lan router
no shutdown
port ethernet 0 1
medium 10 half
encapsulation ip
bind interface wan router
no shutdown
Figure 9-1: Sample Configuration File
Each configuration file that is stored in the flash memory needs a unique name. The user has to
assign a file name to any user-specific configuration. SmartWare predefines some names for
configuration files. These are the file names used to represent the factory configuration, startup
configuration and running configuration, which are
factory-config
,
startup-config
and
running-config
.
Refer back to Chapter 1, “Terms and Definitions”, to learn more about configuration file types.
9.2 Factory Configuration
Inalp SmartNodes are delivered with a
factory
configuration
in the logical region
nvram:
of the
SmartNode that is used to initially parameterize the network and component settings of SmartWare
that are most useful when starting initially. Moreover, if a SmartWare is malfunctioning, resetting to
the initial state is possibleby reloading the factory configuration. The factory configuration consists
of:
•
Default settings for the IP networking subsystem,
•
Default settings for H.323 and ISoIP gateway subsystem, and
•
Default settings for the quality of service subsystem