Troubleshooting guide

6-156
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Tracing
Performing a Call Trace
After eliminating all physical connections, signal links, bearer channels, and destinations as the cause
of a problem, the call engine running on the Cisco PGW 2200 Softswitch might be part of a problem.
Performing a call trace while making a call can derive details about what takes place inside the call
engine and might indicate where a breakdown is occurring.
The following sections describe call tracing:
• Starting A Call Trace, page 6-156
• Starting A Call Trace (on Release 9.7(3) Patch 8), page 6-158
• Stopping A Call Trace, page 6-161
• Retrieving Names of Open Call Trace Files, page 6-161
• Viewing the Call Trace, page 6-162
• Deleting Call Trace Files, page 6-163
• Understanding the Call Trace, page 6-163
Starting A Call Trace
To start a call trace, perform the following steps:
Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the appropriate
command.
You can enter this command in any one of five different formats:
• sta-sc-trc:sig_path:[log=”filenameprefix”][,prd=n], confirm
• sta-sc-trc:sig_path:span=x[,rng=y][,log=”filenameprefix”][,prd=n]
• sta-sc-trc:sig_path:span=x[[,tc=z],rng=y][,log=”filenameprefix”][,prd=n]
• sta-sc-trc:trkgrp:[log=”filenameprefix”][,prd=n], confirm
• sta-sc-trc:trkgrp:trk=w[,rng=y][,log=”filenameprefix”][,prd=n]
Where:
• sig_path—Logical signaling destination, such as an SS7 point code, an FAS path, an IP FAS path,
or a DPNSS path,
• trkgrp—Logical trunk group that is associated with the call that you want to trace.
• filenameprefix—Trace files are created and written to a file that the system names differently
according to how you enter the command. (The system generates a log message for each trace
started. The sta-sc-trc command creates the filenames that are contained in the log messages.) If
you specify the log= parameter, the value of this parameter is prefixed to the filename.
If you do not specify the log= parameter, the system adds default filenameprefix values for each
sta-sc-trc command, as shown in the following examples:
– The command sta-sc-trc:sig_path:confirm generates the following filename:
sig_path_yyyymmddhhmmss.btr
– The command sta-sc-trc:trkgrp:confirm generates the following filename:
trkgrp_sig_path_yyyymmddhhmmss.btr