Troubleshooting guide

6-131
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
– OG_BUSY_BOTH_BLOC—Outgoing is busy, blocked both remotely and locally
– IDLE—The circuit is idle, available for use
– IDLE_LOC_BLOC—Idle, blocked locally
– IDLE_REM_BLOC—Idle, blocked locally
– IDLE_BOTH_BLOC—Idle, blocked both locally and remotely
Resolving Local and Remote CIC State Mismatch
When the local and remote states for CICs do not match and the problem lies with the local CIC states,
you can attempt to resolve the mismatch using an MML command, if your CICs are using ANSI SS7
signaling. To resolve a CIC state mismatch, log in to the active Cisco PGW 2200 Softswitch, start an
MML session, and enter the
query-cic: sig_srv :cic= number [,rng= range ],rslv command.
Where:
• sig_srv—MML name for the signaling service that is associated with the affected CICs.
• number—Number of the first CIC in the range of affected CICs.
• range—Number such that number+range is the number of the last CIC in the range of affected CICs.
The system attempts to resolve state mismatches for all CICs between number and number+range.
Note Use the rslv option only if the system is using ANSI SS7 signaling. If the system uses ITU SS7 signaling
and you enter this command, the system ignores the rslv option and performs a regular query-cic
operation.
Note Configure the Cisco PGW 2200 Softswitch software to issue individual or group supervision messages
for point codes that are associated with an ISUP signaling service. ISUP signaling services issue group
supervision messages by default. Configure an ISUP signaling service to issue individual supervision
messages, you cannot use the range option with this command. Resolve CIC state mismatches only one
CIC number at a time for point codes that are associated with an ISUP signaling service configured to
issue individual supervision messages.
If the command fails in its attempt to resolve the local and remote CIC state mismatch, collect system
data according to the instructions in the “Collecting System Data for Cisco TAC” section on page 6-93
and 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.
Performing CIC Validation Tests
When performing initial turn-up of circuits or in troubleshooting certain problems with your bearer
channels, perform a circuit validation test to verify that the properties defined in the Cisco PGW 2200
Softswitch for the affected bearer channels match the associated properties that are defined in the far-end
exchange.
Note Perform CIC validation tests only on CICs associated with ANSI SS7-based DPCs.