User guide

Provisioning the iMG/RG Creating RG Profiles with Field Descriptions
698
AlliedView NMS Administration Guide
TABLE 7-16 Create RG Voice Port Profile Form
Attribute Value
Profile Name A descriptive name that should match the service/function provided
The prefix of profile name could include the string that identifies the Access Island as
well as the service potential, such as:
SPSI-AI01-UpTo4Line
Note: The user would give this name to the profile because it would have four
voice lines filled in; if the user had one voice line provisioned and needed
to provision an additional voice line, the same profile could be used.
Profile Scoping When used in conjunction with the Triple-Play form, controls the profiles available
after selecting the device.port, or controls the device.port available after selecting the
Profile.
VOIP Type The protocol/server configuration to provide VOIP service:
MGCP
SIP
Note: The only options are MGCP or SIP; specific types for each are selected in
the Advanced VOIP Attributes panel.
Include Voice VLAN in Profile The value entered here depends on the network model:
False - The Access Island model is used, and the Voice VLAN Id field is blank.
True - The Open Access model is used, and the Voice VLAN Id field is activated.
iMG/RG Voice VLAN Id The VLAN that supports voice service.
If the ‘Include Voice VLAN in Profile’ is set to True, this field is activated.
Use DHCP to obtain WAN IP
Address
Use DHCP to obtain the network side address for the RG. This is the default, since
this makes administration easier
iMG/RG Domain The critical component of provisioning voice, this is used in the following ways:
- the domain that is added to the fully qualified domain name for the voice subnet.
Refer to 7.2.6.4.
- When using MGCP and not using a GenBand device, this can have the VoIP
endpoint. The value specified must start with a @. Note that this value must match
the endpoint provisioned in the other MGCP device in the configuration.
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.
This value can also be changed on the iMG/RG->Voice Service tab of the service
management form. Refer to 7.9.7
MGC or Proxy Server Proxy Server for MGCP or SIP
SIP Location Server Activated when SIP is chosen as the Voip Type