Manual

Support for QSIG Over BRI and Q.931 Over BRI Backhaul
Provisioning Tasks
13
Cisco MGC Software Release 9.5(2)
If you decide to configure PRI and BRI signaling backhaul on the same media gateway, we recommend
that you use a single link between the media gateway and the Cisco MGC. If you do not remove a link
from your PRI signaling backhaul provisioning, and one of those links should fail and be restored, you
will need to set the service state of the related MGCP signaling service to OOS, and then set it to IS to
restore both links to full functioning.
To add Cisco media gateway external nodes to your provisioning data, perform the following steps:
Step 1 Start a provisioning session as described in the “Starting a Provisioning Session” section on page 9.
Step 2 Enter the following command to add a Cisco BRI voice gateway external node:
mml>prov-add:extnode:name="name", desc="description", type=”as”, isdnsigtype=”na”
Where:
• name—The name you want to give to the external node. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
• description—An assigned name. It can be as many as 128 alphanumeric characters in length.
• as—The MML name for the type of Cisco BRI voice gateway. The valid values are as follows:
– C1751
– C1760
– C2600
– C2610XM
– C2611XM
– C2620XM
– C2621XM
– C2650XM
– C2651XM
– C2691
– C3640
– C3640A
– C3660
– C3725
– C3745
For example, to add a Cisco BRI voice gateway external node named va-3640-01, enter the following
command:
mml>prov-add:extnode:name="va-3640-01", desc="BRI 3640", type="C3640", isdnsigtype=”na”
Step 3 Repeat Step 2 for each Cisco BRI voice gateway external node you want to add to your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating Your Provisioning Changes” section on page 10.
Otherwise, proceed to the “Adding MGCP Signaling Services” section on page 14.