Generating a debug log from uaCSTA server for SIP phones

This article helps you to enable the so-called debug logging in uaCSTA server for SIP phones and to provide the corresponding log files for analysis.

Log files can only be examined if meaningful anchor points are available. Therefore, always provide the following additional information:

• • When did the behavior occur (timestamp with date and time, at least to the minute)?
  • Which internal phones (MAC address/ line) were involved?
  • Which external participants were involved?
  • Sequence of the workflow that led to the error

For meaningful processing, all available log files (preferably the full packed .\Program Files\estos\uaCSTA Server\logs directory) should always be provided.

Procedure

uaCSTA server for SIP phones management

Open uaSCTA server for SIP phones administration

In the uaCSTA configuration, switch to the Info about section and set the following settings:

Example screenshot: uaCSTA Server for SIP phones – diagnostics

Note about the amount of data

Since the amount of data can grow rapidly, it is also recommended to check Delete log files daily, unless it is mandatory to log over several days.

If the server log is already activated and has been running for some time, please delete the old logs in the specified log files path first.

Providing the log files

Click the "Deploy" button and all the necessary log files will be deployed to the desktop as a ZIP file.

Further information

Creating a debug log in the ECSTA middleware