...
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.
...
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.
...
NFS Server Status |
|