Call Trace - Log File Overview
Call Tracing gives the IMG 2020 the ability to view various pieces of information on a per call basis. The Web GUI will allow up to 4320 minutes (72 hours) of Call Tracing. Call tracing uses NFS to write the files to an NFS Server. The call trace is logged into a file for viewing at a later date. A call trace log includes the following information:
 |
---|
Call Leg Information |
Call ID Information |
Codec Information |
Routing Information |
RTCP Stats |
Call Duration |
Â
The Call Trace is saved to a log file in the directory configured in the NFS Mount Directory field of the Call Tracing object. This directory is located in the NFS Server configured in the NFS Server field of the Call Tracing object.
Log File Naming Convention
The following is an example of a call trace: 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7). Each segment is described below:
Segment 1
18.56:20.045 = Time Stamp. NTP must be configured for the correct time to be displayed.
Segment 2
CALL(SS7) = Call Component. See table below which displays all Call Components on IMG 2020
Â
Internal Call Components
Call Component | Description |
---|---|
GCL | Routing/Translation |
L4 | Routing |
MEDIA | DSP Resources |
FACPFC | VoIP Resources |
Â
External Signaling ComponentsÂ
Call Component | Description |
---|---|
SS7 | Signaling System 7 |
ISDN | Integrated Services Digital Network |
SIP | Session Initiation Protocol |
RAS | Registration, Admission, Status |
Segment 3
(01:0003:00):
Example Value | Description | Range |
---|---|---|
01: | Node ID | 0-31 |
0003: | Call ID | 0-99999 |
00 | Call Leg Direction | 00=Inbound / 01=Outbound |
Segment 4
Description of event:
RCVD IAM (0x382b:0x813:7) = Received Initial Address Message
Â