Troubleshooting guide

6-182
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Platform Troubleshooting
Step 2 If your system is provisioned to control Voice over IP (VoIP) calls that do not originate or terminate on
SS7 or PRI (such as SIP-to-SIP or SIP-to-EISUP/H.323 calls), you must synchronize the system state
data before continuing. To synchronize the system state data, proceed to Step 3.
If your system is provisioned to control VoIP calls for which at least one call leg is SS7 or PRI, proceed
to Step 4.
Step 3 To synchronize the system state data, you must restart the Cisco PGW 2200 Softswitch software on the
standby Cisco PGW 2200 Softswitch. To restart the Cisco PGW 2200 Softswitch software, stop the
software, as described in the “Shutting Down the Cisco PGW 2200 Softswitch Software Manually”
section on page 2-4 and then start the software, as described in the “Starting the Cisco PGW 2200
Softswitch Software” section on page 2-2.
Step 4 Verify that the path to the affected peer is out-of-service, according to the instructions in the “Verifying
the Status of all Signaling Services” section on page 3-9.
If the destination is in-service, or there is no destination that is associated with the peer, proceed to
Step 5.
If the destination associated with the peer is out-of-service, restore the destination to service, as
described in the “SS7 Destination is Out of Service” section on page 6-102.
Note If the out-of-service destination is an IP destination, perform the procedure that is described in
“Media Gateway IP Destination or Link Out-of-Service” section on page 6-151.
If restoring the destination to service resolves the problem, this procedure is complete. Otherwise,
proceed to Step 5.
Step 5 Trace the route to the peer by entering the traceroute ip_addr UNIX command on the active Cisco
PGW 2200 Softswitch:
Where:
ip_addr—IP address of the affected peer.
The system responds with a listing of the peers that are passed through on route to the identified peer.
If the system response indicates that the identified peer was reached with no problems, proceed to Step 7.
If the system response indicates that the identified peer is unreachable, proceed to Step 6.
Step 6 Log in to the peer identified in Step 4 and verify that the Ethernet interfaces for this peer are working
correctly. See the documentation for the peer for more information.
If the Ethernet interfaces are working properly, proceed to Step 7.
If the Ethernet interfaces are not working properly, replace the element that is not working properly. See
the documentation of the peer for more information. If replacing the element resolves the problem, the
procedure is complete. Otherwise, proceed to Step 7.
Step 7 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.