Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

To configure  call tracing on the IMG 2020, first an NFS Server with mountpoint must be configured. Once the NFS Server is configured, the Call Tracing object within the Web GUI must be configured. The Call Tracing object configures the IMG 2020 where to go to send the log files created. The Call Tracing function allows a user to log up to 4320 minutes (72 hours) of Call Processing logs. The call traces created can be used to troubleshoot call issues such as call failures etc. There are two steps to configuring the Call Tracing functionality. First, NFS must be configured to capture the call trace and send it to the appropriate directory on the server. Second the Call Tracing object in the Web GUI must be configured for each IMG 2020 that the call trace will be taken from.

Configure NFS Mount

The procedure below was executed on Red Hat Linux Enterprise 5. The screen captures and procedure may vary if different versions of Red Hat are going to be used.

If NFS Server being configured is on an operating system other than Red Hat Enterprise Linux, it is up to the administrator to know the processes and procedures needed to configure their own NFS Server.

  • Open the NFS Server Configuration pane by going to System > Administration > Server Settings > NFS

  • This will open the NFS Server Configuration screen. Select Add from the toolbar and an Add NFS Share dialog box will appear. Add the following information to the dialog box:

NFS Setup

  • In the Directory field, enter the mountpoint. In this example, the mountpoint is /home/dialogic/shares.

  • In the Host(s) field ether enter the ip address of the NFS Server or enter a wildcard symbol * indicating any IP address.

  • Check the Read/Write Radio button.

  • In the General Options tab select check the  Sync write operations on requestbox.

  • In the User Access tab check theTreat all clients users as anonymous usersbox.

  • Check both theSpecify local users ID as anonymous usersandSpecify local group ID for anonymous usersboxes. The User ID and Group ID were both given an ID of 500.

  • Select OK and the share will get configured.

  • Once the NFS Share is configured, restart the NFS Service. Open a terminal window and resatrt the NFS Service. The commands below will restart the service and configure it to restart whenever the server is rebooted.

#/sbin/service nfs start      (Start the nfs service)
#/sbin/service nfs status     (Verify whether nfs is running)
#/sbin/chkconfig nfs on       (Configure nfs service to restart after a reboot of BDN EMS server)
#/sbin/chkconfig nfs --list   (Verify that runlevels 3,4 and 5 are all on.)
 
Example:  nfs                0:off     1:off     2:on     3:on     4:on     5:on     6:off

  • Once call tracing is configured on NFS and the NFS service has been re-started, the configuration of Call Tracing on the IMG 2020 can be started. The next section below describes this. 

Configure NFS Server

The procedure below describes the steps needed to configure the IMG 2020 to connect to the NFS Server created and to start writing the log files to the directory configured above.

  • Right click on the Dialogic object and select New External Network Elements. The External Network Elements object is a container or parent object and no configuration is needed here. Refer to the External Network Elements topic for more information on this object.

  • Right click on the External Network Elements object and select New NFS Servers. The NFS Servers object is a container object also and no configuration is needed here. Refer to the NFS Servers topic for more information on this object.

  • Right click on the NFS Servers object and select New NFS Server. Enter a Name to identify this server and enter the IP address of the server running NFS.

  • Right click on the IMG 2020 physical node object and select New Call Tracing. The Call Tracing field is set to Enabled by default. Below is screen capture of the Call Tracing object with the information filled in for this example.

Call Tracing Properties

  • Trace Time- Configure the number of minutes the trace will log for.

  • Roll Over- If a log file created at a set interval of time, configure that interval in the Roll Over field.

  • Mount Directory- Enter the path to the directory that the log files will be written to. Be sure to include the mount point path in the path name entered. In this example the mount point is /home/dialogic/shares and the directory is calltracing. This was all configured in the Configure NFS Mount section above.

  • NFS Server- Select from drop down menu the server that the log files will be written to. All the NFS Servers configured on the IMG 2020 will be in this list.

  • Once all fields have been populated, click on the Reset Call Tracing button and the Call Tracing will begin. Verify this by navigating to the calltracing directory and verify the log files are being generated.

Additional Information

  • The Log File being generated in example above will roll-over and create a new file every 5 minutes. Below is screen capture of the calltracing directory after the Call Tracing feature has been running for 60 minutes.

  • The NFS Server Status field will display the various states described below.

NFS Server Status

  • Available - The IMG 2020 can communicate with the server running NFS. This is usually displayed if the call tracing id Disabled but the NFS Server is configured and communicating with the IMG 2020.

  • Error Writing to System Log File - Cannot write to log file. Possible NFS problem or network cabling issue. (This error will only occur when the IMG 2020 tries to write to the NFS server at the interval configured and could not.

  • Timer Expired - The Call Tracing Session has completed. The field will have a value of 0 displayed.

Related Topics

 Call Tracing

Call Trace - Log File Overview

  • No labels

Return to Documentation Home I Return to Sangoma Support