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
30
Cisco MGC Software Release 9.5(2)
Step 5 If there are no other components that you need to delete, end your provisioning session as described in
the “Saving and Activating Your Provisioning Changes” section on page 10.
Deleting MGCP Signaling Services
To delete MGCP signaling services from your provisioning data, perform the following steps:
Step 1 Set the service state of the MGCP signaling service to OOS, as described in the “Setting the Service State
of a Signaling Service” section on page 32.
Step 2 If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 9.
Step 3 Delete the bearer channels associated with this signaling service using the following MML command:
mml>prov-dlt:nailedtrnk:dstsrv=”sig_svc”, “all”
Where sig_svc is the MML name of this signaling service.
Step 4 Enter the following command to delete a MGCP signaling service:
mml>prov-dlt:mgcppath:name="name"
Where name is the MML name of the MGCP signaling service to be deleted.
For example, to delete a MGCP signaling service named mgcpsvc1, you enter the following command:
mml>prov-dlt:MGCPPATH:NAME="mgcpsvc1"
Step 5 If there are no other components that you need to delete, end your provisioning session as described in
the “Saving and Activating Your Provisioning Changes” section on page 10.
Troubleshooting Provisioning Data
The following sections contain troubleshooting procedures related to provisioning:
• Alarm Troubleshooting Procedures, page 30
• Signaling Channel Troubleshooting Procedures, page 31
• Rebooting Software to Modify Configuration Parameters, page 34
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Alarm Troubleshooting Procedures
Any alarms that are associated with signaling services can be issued as a result of errors related to this
feature. For information on troubleshooting those alarms, refer to the Cisco Media Gateway Controller
Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
The following alarm is added for this feature.