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
9
Cisco MGC Software Release 9.5(2)
• Adding QSIG/Q.931 Over BRI Backhaul Connections, page 12
• Modifying QSIG/Q.931 Over BRI Backhaul Components, page 20
• Deleting QSIG/Q.931 Over BRI Backhaul Components, page 26
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate
the changes you have made.
• Starting a Provisioning Session, page 9
• Saving and Activating Your Provisioning Changes, page 10
• Ending a Provisioning Session Without Activating Your Changes, page 10
• Retrieving Provisioning Data, page 10
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You might need to start a provisioning session as part of your system operations. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
• curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
–
new—A new default session configuration; no existing source configuration is available.
–
active—Selects the active configuration as the source for configuration changes.
Note If you do not know the name of your current configuration session, you can use the procedure in
the “Retrieving Data on the Current Provisioning Session” section on page 11.
• mod_ver—A new configuration version name that contains your provisioning changes.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you
would enter the following command:
prov-sta::srcver=”ver1”,dstver=”ver2”
Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML
commands to add, modify, and delete components on your system. This document describes how to
provision this feature. For more information on provisioning other components on your Cisco MGC,
refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes,
as described in the “Saving and Activating Your Provisioning Changes” section on page 10 or ending
your provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating Your Changes” section on page 10.










