User guide

Provisioning the iMG/RG Provisioning Strategy
666
AlliedView NMS Administration Guide
7.2.6.3 Character Usage Rules
• Character allowed are letters, numbers, single dashes (-), and periods (.).
• Do not use a double dash, such as when you need a placeholder. Instead, use a string such as -X-.
• Do not use spaces, underscores, colons, or other special characters.
7.2.6.4 Dynamic DNS Naming for Voice Subnets
For voice service, there must be a Dynamic DNS entry for all RGs in the voice subnet. Moreover, each entry must have a
specific structured name (Fully Qualified Domain Name, or FQDN) so that all related components can communicate with
each other and be aware when changes are made. The format of the FQDN is as follows:
rgvoip-<MAC address>.domain
This is part of the DHCP discovery process, and its success depends on the components that make up voice service being
configured and pre-provisioned correctly. This is explained in detail in 7.2.6.6
7.2.6.5 Detailed steps for DHCP Discovery
Refer to Figure 7-8 for the first four steps for DHCP discovery.
TABLE 7-6 Reference for Remote ID
Description 4
character
name for
the
serving
area
2 character
name for the
state the
serving area
is located in.
Access Island
that this
device
belongs in,
separated by
a dash.
1
1. Use one dash on each side to help in reading the string. this part of the string. Do not use double dashes or spaces in the
string.
Characters used to identify the device and any attributes
that are significant.
Example
Values
SPSI NA -AI00-
-AI01-
-AIT- (test)
MAP1x7