User guide

Provisioning the iMG/RG Provisioning Guidelines for Models
804
AlliedView NMS Administration Guide
When this change is made, or any change is made by the subscriber, the subscriber will need to save the configuration so
it can be redeployed if the iMG should reboot.
• Subscriber requests wireless parameters to be reset to default
If the subscriber has made changes to the wireless parameters, but the CPE needs to be reset to the default
configuration, the NMS administrator can go to the iMG/RG -> Wireless tab, and click on Reset Wireless Parameters.
This resets the wireless parameters and restarts the CPE, as shown in the warning message.
• CPE needs to be restored from the latest backup file
If there is a hardware replacement of the iMG, or there has been a maintenance recovery scenario, the iMG should be
restored to the latest backup file.
7.9.7 Changing VoIP Endpoint Syntax
As described in 7.4.5, for MGCP configurations that do not use GenBand, there is the option in the RG Voice profile to enter
the VoIP endpoint that will be used. On the service management form for the iMG (iMG/RG -> Voice Service) there is the
option of entering the endpoint syntax by selecting the Syntax checkbox and then filling in the iMG/RG Domain using the @
for the specific settings for the voice endpoint (@$IP, @$MAC, @$HOST, etc.). Refer to the following figure.
Note: The NMS supplies the “aaln/<telport number>”at the beginning of the string, and then the user continues the value with @.
Therefore, values form vendors that do not follow this format are not supported, such as “$MAC:aaln/0@[$IP]”. Modifying
the end-point syntax is an advanced setting and should not be used unless required by the MGCP server.
FIGURE 7-131 Setting VoIP Endpoint Syntax
7.9.8 Provisioning Custom VLANs
Although the RG General Profile is used to define VLANs for specific services, the iMG can support up to 14 VLANs. Each
port can be connected to any VLAN in in any combination of tagged, untagged bridged and routed configurations.