User guide

Provisioning Strategy Naming Convention for Customer IDs (Triple Play Form)
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
7-24
When all of the prerequisite steps have been performed and the RG is plugged in, the following occurs:
1. The AlliedView NMS puts together the FQDN for the RG voice interface (i.e. rgvoip-<MAC addr.>.domain) and the port
of the iMAP (as <ip addr of connected iMAP>_slot.port). The AlliedView NMS also adds the line entries that were filled
out in the Triple-Play form.
2. The AlliedView NMS configures each voice line that has been set up for the RG (creates the voice VLAN, creates the voice
IP interface, enables DHCP)
3. The RG sends a DHCP discover to the DHCP server. After an exchange of DHCP messages, the DHCP server has the MAC
address (sent by the RG) and the IP address (assigned by the DHCP server) associated.
4. The DHCP updates the DNS server to include the DNS entry between the RG’s voice IP interface (the rgvoip string) and
actual IP address.
5. The MGCP protocol is run between the GenBand and the RG, and the result is dial tone.
7.2.7 Naming Convention for Customer IDs (Triple Play Form)
Customer IDs have the following attributes:
• Up to 31 characters in length
• Must be unique so they can identify each customer
• Cannot have wild cards (*)
• Cannot contain the word “error” or “Error”.
• Cannot contain a question mark (?), backslashes (\), double quote (“) or single quote (‘)
• # is allowed
The naming system for customers is entirely up to the administrator, but should reflect one or more of these:
• Specific attributes that identify a customer
• Service mix
• Common attributes when customers form a logical group
Some example IDs could have the format:
• firstname_lastname_phonenumber
• name_servicemix
• name_grouplabel
Note: This is where a unique prefix (x.) or suffix (_test) would create an easy way to group employees that will
participate in ongoing tests but are spread out in many AIs around the network
Note: When providing voice service using the G6 (or G2)product, the G6 will drop any characters in the Customer
ID after the 20th character. As a result, any customer ID in which the first 20 characters are the same will
not be seen as different by the G6. Although customer IDs longer than 20 can be datafilled there will be the
following consequences for the provisioned voice lines if the first twenty characters of the Customer IDs are
the same:
- In the Voice Configuration tab of Triple Play Service Management Window, there will be an MGC tab for each voice
line that has the identical 20 first characters.
- On the Deprovision Ports Form, multiple voice lines would appear if their associated Customer IDs have the same first
twenty characters, and so the administrator would have to know through other attributes the actual voice line(s) to
delete.