User guide

Provisioning the iMG/RG Provisioning Strategy
669
AlliedView NMS Administration Guide
Before VoIP can work, the following must have already been done, or voice service will not work:
1. Profiles have been filled out correctly to support voice service. In particular, in the Voice profile for the RG, the voice
domain name must be filled out, and the voice VLAN that is filled in for the RG General profile has already been created.
Also, the route to the Genband must be filled out in the RG General Profile if the Genband is on a separate subnet.
2. The Genband (G6, G2) has been provisioned to support voice (Line Profile, Interface Group, CRV)
3. The GenBand has the routing information for the RG; moreover, the routing table in the GenBand must use the BBI
interface.
4. On the Triple Play form, the Genband (G6, G2) information for the GenBand (in Step 2) has been filled in for the
customer.
5. There is Dynamic DNS (DDNS) between the DHCP server(s) and the DNS server (usually one is reserved only for
voice). This is needed since the DNS tables, which correlate the RG’s voice IP interface address with the domain name,
are updated dynamically.
Note: The Genband/RG configuration can be statically configured, but this is very difficult to maintain administratively since the IP
addresses must be tracked/changed manually.
FIGURE 7-10 Voice Service Configuration
When all of the prerequisite steps have been performed and the RG is plugged in, the following occurs: