Manual
Table Of Contents
- Support for QSIG Over BRI and Q.931 Over BRI Backhaul
- Feature Overview
- Supported Platforms
- Supported Standards, MIBs, and RFCs
- Prerequisites for Using This Feature
- Configuration Tasks
- Provisioning Tasks
- Monitoring and Maintaining the Feature
- Configuration Examples
- Provisioning Examples
- Command Reference
- Reference Information
- Obtaining Documentation
- Documentation Feedback
- Obtaining Technical Assistance
- Obtaining Additional Publications and Information
- Glossary
Support for QSIG Over BRI and Q.931 Over BRI Backhaul
Provisioning Tasks
6
Cisco MGC Software Release 9.5(2)
Collecting External Node Data
Note If your network supports both PRI and BRI backhaul signaling, we recommend that you maintain the
PRI and BRI interfaces on different media gateways. PRI singling backhaul configurations typically use
redundant links between the Cisco MGC and the media gateway, and BRI signaling backhaul
configurations use a single link between the Cisco MGC and the media gateway.
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 for both. 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 service.
The external node component type represents another node with which the MGC communicates. You
must be ready to enter the following data about the node:
• MML name
• Component description
• The type of the external node
• ISDN signaling type
You can define the parameters for your external nodes in Table 9 in the “Provisioning Worksheets”
section on page 51.
Collecting MGCP Path Data
The MGCP component type represents a MGCP signaling service to a particular Cisco voice gateway.
Refer to the “Restrictions” section on page 2 for more information on the Cisco media gateways that can
be used to setup this feature. You must be ready to enter the following data:
• MML name
• Component description
• MML name of the associated external node
You can define the parameters for your MGCP signaling services in Table 10 in the “Provisioning
Worksheets” section on page 51.
Collecting MGCP Path Property Data
This component type represents properties for an existing MGCP signaling service. All of the MGCP
signaling service properties have default values. You must be ready to enter data for the properties you
are going to modify. For information on all of the MGCP signaling service properties, refer to the Cisco
Media Gateway Controller Software Release 9 Provisioning Guide.
You can define the new values for the trunk group properties in Table 11 in the “Provisioning
Worksheets” section on page 51.