The IMG supports Call Tracing, which allows you to view various pieces of information on a per call basis. The ClientView GUI will allow up to 4320 minutes (72 hours) of Call Tracing. Call tracing uses NFS to write the files to the host. A Call Trace log includes information such as:
Call Leg Information
Call ID Information
Call Duration
RTCP Stats
Codec Information
Routing Information
The Call Trace is saved to a log file in the following directory in the GCEMS server:
/opt/dialogic/common/calltracing (Software 10.5.1+)
/opt/cantata/common/calltracing (Software 10.3.3 to 10.5.0)
Naming Convention:
Call Trace log files have the following naming convention:
syslog_<ChassisSerialNumber>_<YYMMDD>_.log
If call tracing is not writing to the file, verify that the NFS server is running and verify the NFS mount status.
Call Trace Format Examples:
The following is an example of a call trace segment:
18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7)
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 below for all Call Components on IMG
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 |
H.323 | ITU standard Call Control Channel Setup over VoIP |
H.225 | Member of H.323 Protocols |
H.245 | Control Channel Protocol Used in H.323 |
RAS | Registration, Admission, Status |
Segment 3:
(01:0003:00):
| Example: | Range |
Node ID | 01 | 0-31 |
Call ID | 0003 | 0-99999 |
Call Leg Direction | 00 | 00=Inbound / 01=Outbound |
Segment 4:
Description of event:
RCVD IAM (0x382b:0x813:7) = Received Initial Address Message