Troubleshooting guide

6-162
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
The call trace stops for one of the following four reasons.
• Call trace is stopped because the MCL is reached.
MGC-02 - Media Gateway Controller 2008-04-28 10:25:36.782 EDT
M RTRV
“../var/trace/eisup-0428_eisup-pgw2_20080427223536.btr: MCL reached.
"
;
• Call trace is stopped automatically and the desired call trace is collected.
MGC-02 - Media Gateway Controller 2008-04-30 14:39:19.042 CST
M RTRV
"../var/trace/_ss7svc1_20080430143908.btr: automatically stopped.
"
;
• Call trace is stopped manually.
MGC-02 - Media Gateway Controller 2008-04-30 14:39:59.849 CST
M RTRV
"../var/trace/_ss7svc1_20080430143951.btr: manually stopped.
"
;
• Call trace is stopped because the trace period is over.
MGC-02 - Media Gateway Controller 2008-04-30 14:43:59.982 CST
M RTRV
"../var/trace/_ss7svc1_20080430144354.btr: trace period expired.
"
;
Viewing the Call Trace
The MML command sta-sc-trc produces binary trace (.btr) files, which you cannot view with a text
editor. The main part of the filename is set up in the sta-sc-trc command, as explained in the “Starting
A Call Trace” section on page 6-156, and the Cisco PGW 2200 Softswitch adds the extension .btr to
these files. The .btr files can contain tracings from many calls all mixed together. Each tracing record in
the file has a specific record type and records information of the type that relates to that record. Each
record has a unique call ID that associates it with a specific call and is a recording of the external events
to which the MDL call model was exposed while the recording was made. Each tracing record is not a
recording of the actual MDL.
Use the trace viewer to view and navigate through call trace outputs. For more information on using the
trace viewer, see the “Using the Trace Viewer” section on page 3-134.
Also view the call trace output data using the get_trc.sh UNIX script. Get_trc.sh uses the Conversion
Analyzer and SimPrint utilities in combination to give a single common interface to all the trace tools.
Get_trc.sh uses the UNIX less utility for displaying file output (it is assumed that less is available on
the system). For more information on the less utility, enter the man less UNIX command.
You can start the script by entering the
get_trc.sh filename UNIX command.
Where:
filename—Name of the call trace output data file (.btr) that you want to view.