Troubleshooting guide

6-153
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Resolving Bearer Channel Connection Problems
Step 3 Verify that the signaling channels are in-service, as described in the “Verifying the Status of all Signaling
Services” section on page 3-9.
If any of the signaling channels are out-of-service, attempt to return them to service by using the
appropriate procedures. Otherwise, proceed to Step 4.
Step 4 Run a call trace as described in the “Performing a Call Trace” section on page 6-156.
Step 5 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information
about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request”
section on page xviii.
3.1 kHz (ISDN Category 3) Calls are Failing
If 3.1-kHz calls (also known as ISDN Category 3 calls) are failing, perform the following steps:
Note The following procedure is valid only if the Cisco PGW 2200 Softswitch is using the BTNUP protocol.
Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting
System Data for Cisco TAC” section on page 6-93.
Step 2 If your system is configured for the BTNUP protocol, proceed to Step 3. Otherwise, proceed to Step 7.
Step 3 Verify the setting for the defaultBC property on the trunk group that is associated with the failed calls
by entering the
prov-rtrv:trnkgrpprop:name=" trnkgrpname " MML command at the active Cisco PGW
2200 Softswitch.
Where:
trnkgrpname—MML name of the trunk group that is associated with the failed calls.
The system returns a response listing the values of all of the properties for the specified trunk group. The
defaultBC property should be set to 3_1_KHZ to ensure proper processing of 3.1 kHz calls. If the
defaultBC property is set to 3_1_KHZ, proceed to Step 7. Otherwise, proceed to Step 4.
Note Setting the defaultBC property changes the identifying information for incoming 3.1 kHz (ISDN
Category 3) calls to match the settings for speech (ISDN category 2) calls. This change allows
far-end switches to process 3.1-kHz calls, which are rejected ordinarily.
Step 4 Start a provisioning session as described in the “Starting a Provisioning Session” section on page 3-64.
Step 5 Modify the appropriate signaling service settings by issuing the
prov-ed:trnkgrpprop:name=” trnkgrpname ”,defaultBC=”3_1_KHZ” command:
Where:
trnkgrpname—MML name for the affected trunk group.
Step 6 Save and activate the new configuration as described in the “Saving and Activating your Provisioning
Changes” section on page 3-65.
If your system now completes 3.1-kHz calls, the procedure is complete. Otherwise, proceed to Step 7.