7 • Configuration file handling
# interface used to access the PSTN telecom operator
interface isdn telecom-operator
route call dest-interface h323
# interface used to access the VoIP telecom provider
interface h323 voip-provider
route call dest-table rtab
remoteip 172.19.33.60
bind gateway h323
# H.323 gateway primarily used
gateway h323
faststart
no ras
gatekeeper-discovery auto
bind interface lan router
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
Each configuration file 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 factory
configuration (factory-config), startup configuration (startup-config), and running configuration (running-
config) file names. Refer to appendix A,
tion file types.
Factory configuration
Patton SmartNodes are delivered with a factory configuration in the logical region nvram:. This factory configu-
ration initially parameterizes the most useful network and component settings of SmartWare. Moreover, in case
of SmartWare malfunction, resetting to the initial state means possibly reloading the factory configuration. The
factory configuration consists of:
•
Default settings for the IP networking subsystem
•
Default settings for H.323 and SIP gateway subsystem
•
Default settings for the quality of service subsystem
Once a user-specific configuration is created and stored as the startup configuration, the factory configuration
is no longer used, but still remains in the persistent memory. It is possible to switch back to the factory config-
84
Figure 19. Sample configuration file
"Terms and definitions"
SmartWare Software Configuration Guide
on page 517 to learn more about configura-
Factory configuration
Need help?
Do you have a question about the SmartNode Series and is the answer not in the manual?