Call Tracing

Owned by Kelli Higdon
Last updated: Apr 12, 2024 by Nathaniel Halbrooks
6 min read

 

 

For troubleshooting purposes, the IMG 2020 supports logging calls over a specific period of time. The IMG 2020 can be configured to log all call events from the IMG 2020 into one or multiple files for viewing. The Call Trace logging feature can be configured to log all calls on a per-call basis for a minimum of 1 minute to a maximum of 71520 minutes (1192 hours or approximately 49 days). After the pre-determined amount of time has elapsed, the IMG 2020 will stop logging the call events. The Call Tracing log entries can either be sent to an NFS Server or to a Trace Server. The GUI page will adapt itself depending upon which type of server is to be used.  

Web GUI Page

Dialogic > IMG 2020 > New Call Tracing

Or

 

Maximum Objects

One Call Tracing object can be created per IMG 2020.

Related Topics and Dependencies

The Call Tracing can either send its log entries to either an NFS Server or a Trace Server.

If an NFS Server is to be used, then an NFS Server object must be created and connected to an NFS Server before being able to configure the Call Tracing functionality. After the NFS Server object has been created, the Server can be selected in the drop down list of the Server field of the Call Tracing object. Refer to the NFS Server and Configure NFS Share topics for more information on configuring NFS. The Server field name will automatically change to NFS Server when choosing an NFS server from the drop down list.

If a Trace Server is to be used, then a Trace Server object must be created and be able to connect to an external Trace Server. After a Trace Server object has been created, the Trace Server can be selected in the drop down list of the Server field. The Server field name will automatically change to Trace Server when choosing a Trace Server from the drop down list.

Within a Call Trace, a Timestamp is generated displaying the exact time of each call event. For the timestamp to be accurate, an NTP (Network Time Protocol) server must be configured to send the time to the IMG 2020. If the NTP Service is not configured, the time will default to Jan 1970. Refer to the Configure SNTP for more information on configuring/starting the NTP service.

Call Trace - Setup and Configuration

Call Trace - Log File Overview

Trace Server - Setup and Configuration

Trace Servers

Trace Server

NFS Servers

NFS Server

Field Descriptions

Call Tracing

The Call Tracing functionality can be either enabled or disabled. Select from drop down list whether Call Tracing is to be Enabled or Disabled.

Start (Default)- Starts the Call Trace logging functionality. Call Tracing Gel starts running and is being logged to either an NFS mounted directory or to a Trace Server depending upon the type of server chosen in the Server field below.

Stop- Stop the Call Trace logging functionality. Logging of Call Traces will stop. Call Tracing Gel is stopped.

Start - Until Stopped - Starts Call Tracing indefinitely, until stopped from the WebUI. This is a way to override the 49 days limit described below.

Trace Time (Default 60 Minutes)

The Trace Time field gives the user the ability to configure how long an occurrence of a call trace event will log for. The range of time is from 1 - 71520 minutes (1192 hours or approximately 49 days). To enter a time, click in the Minutes field and enter a time in minutes. If a value is entered that falls outside of the Call Tracing Period range the Minutes box will be displayed with a red outline indicating the number is outside its limits and a Maximum value box will appear informing you that the value is out of range. If this is ignored, the field will automatically set the time at the maximum which is 71520 minutes.

Roll-over Interval (Default = 0 Minutes = Disabled)

This property only applies if the Server is an NFS Server. If the Server is a Trace Server, then this property is not visible. Call Trace log files can get very large and difficult to handle. To ease in the management of the call tracing log files, a Roll-over provision was added to enable a user to configure how long the log file will capture data before creating a new log file. The default value is 0 which indicates the Roll-Over feature is disabled. The Roll-over field is configured in one minute intervals and has a range from 0-120 minutes. If a value is entered that falls outside of the Roll Over Interval Period range, the Minutes box will be displayed with a red outline indicating the number is outside its limits and a Maximum value box will appear informing you that the value is out of range. If this is ignored, the field will automatically set the time at the maximum which is 120 minutes. The Roll Over files will be logged into the directory specified in the Mount Directory field described below.

If Roll-Over Interval is enabled (set to something other than 0) and the Roll-Over Interval value is changed, the Roll-over timer is restarted. This allows a user the ability to disable or extend the timer as needed.

Mount Directory (NFS Server)

If the Server is an NFS Server then the Mount Directory property is available. If the Server is a Trace Server then this property is invisible. Enter the directory that the call trace log files will be saved to. The directory should be prefaced with a forward slash ( / ). The mount directory has to be configured on the NFS Server prior to sending log files to that directory. Refer to the screen capture below.

 

Enable NFSV3

Disable (Default) - NFSV2 is enabled by default.

Enable- We can enable NFSV3 for Call Tracing. Refer to the screen capture above.

Available in version 2.3.1 and above.

Disable NFSV2 on EMS CentOS 7.3 Server

CentOS 7.3 supports NFSV2, NFSV3 and NFSV4, EMS enables NFS2 by default by modifying the NFS configure file to support Call tracing On EMS CentOS 7.3 VM.

Here are the steps to disable NFSV2 on EMS CentOS 7.3 VM:

  • Go to the /etc/sysconfig

  • Comment out the settings below in the configuration file /etc/sysconfig/nfs

#RPCNFSDARGS="-V 2" #RPCMOUNTDOPTS="-V 2" #mountd_nfs_v2="yes"

 

  • Restart the NFS service using the command: service nfs restart

Call Tracing Flags

By default, all call tracing flags are enabled. To limit the call trace information, we can set the desired call tracing flags we wish to monitor.

Server

The Server property contains all of the available external NFS servers and the external Trace Servers. Select from the drop down list the NFS Server or Trace Server that will be used. If a Trace Server is selected then the Roll-Over Interval and the Mount Directory properties will be invisible. The name of the Server will change to NFS Server or Trace Server depending upon the selected Server type.

Monitoring Fields

Server Status

The Server Status field displays whether the IMG 2020 can communicate with the selected Server, which can be either an NFS Server or a Trace Server. If Available is displayed, the IMG 2020 is communicating. If Unavailable is displayed, there is an issue and the IMG 2020 can not communicate with the NFS Server. Some issues could be the following:

Is the NFS Server object configured in the Web GUI and on the IMG 2020.

Is the actual NFS Server configured with a mount directory for Call Tracing.

Some type of cabling/network issue

Is the Trace Server up and running.

Is the Trace Server IP address and port configured correctly.

Call Tracing Time Remaining

The amount of time remaining in the current trace period. Once the time has fallen to zero, a Timer Expired message will be displayed. 

Buttons

Reset Call Tracing

The Reset Call Tracing button will start a new call trace. If the Reset Call Tracing button is clicked while a call trace log session is already running, the call trace that was running would be restarted at the time interval expressed in the Call Tracing field above.

 

Return to Documentation Home I Return to Sangoma Support