Specifications

Chapter 3 - Basic Configuration Administration Manual (SIP/MGCP Version)
AT-VP504E FXS 29
<mibAttributeName> = "<mibAttributeValue>"
Example of a Configuration File
interfaceUseDhcp="1"
interfaceStaticPrimDnsIp="192.168.0.10"
interfaceStaticSecDnsIp="192.168.0.10"
interfaceStaticDefaultRouterIp="192.168.0.10"
interfaceStaticSubnetMaskIp="255.255.255.0"
apaManagerEnable="1"
apaManagerUseDhcp="1"
apaManagerStaticPrimHost="192.168.0.10"
apaManagerStaticPrimTrapPort="162"
tftpFileName="vp500.bin"
tftpEmergencyFileName="vp500_emergency.bin"
tftpUseDhcp="1"
tftpServerStaticHost="192.168.0.10"
tftpServerStaticPort="69"
tftpServerStaticEmergencyHost="192.168.0.10"
tftpServerStaticEmergencyPort="69"
Management Information Base – MIB
Sending information as a MIB via SNMP means that individual
variables could be changed without sending the whole MIB. You could
use a dual system where a configuration file is sent for initial
configuration and a MIB is used to implement minor changes.
The AT-VP504E FXS has three configurable MIBs: the Provisioning
MIB, SIP MIB and MGCP MIB. All variables in these MIBs have been
configured by default upon start up. However, if you need to modify
some of these variables (for instance, variables related to the country
in which you are), use a MIB browser.
Provisioning
Sequence
You can change the configuration at will after the initial provisioning
and the provisioning system can refresh the AT-VP504E FXS
configuration. The provisioning system consists of the Unit Manager
and a DHCP server. The Unit Manager includes a provisioning client,
provisioning server, and SNMP proxy server.
Restart Handler
The Provisioning Server provides a restart handler, which will
synchronize the provisioned data in the AT-VP504E FXS in the event
it goes off line and is rebooted again.