INFO: Enabling a fax device trace log
This Zetafax technical note applies to:
All fax devices (modems, Gammafax, Brooktrout and CAPI devices) can be configured to produce their own details log files called "trace logs". These are intended to help technical support staff from Equisys and other companies to resolve any device-related problems which may occur.
This document gives instructions for enabling the trace log for a device when asked to do so by a technical support engineer - this produces a log file which can then be sent to the engineer for analysis.
To enable trace logging for a given device, edit the file zfax\SYSTEM\Z-DB\SETUP.INI (where 'zfax' is the name of the share where the Zetafax files are installed). Locate the settings section for that device (eg for device FCLASS-1 the section is headed "[FCLASS-1]"), then add the following line to the end of that section:
Save the file, then restart the Zetafax server. The trace log file will be stored in folder zfax\SERVER\Z‑ DB as devicename.LOG (e.g. FCLASS1.LOG)
Because of the amount of information in the log it is helpful to keep it specific to the problem which is occuring - for example, if the problem occurs sending to a specific fax number, then after enabling the trace log you should restart the server, send a fax to that fax number, then stop the fax server again.
The logs relate to the current run of the server only - they are deleted each time the Zetafax server is restarted. However they can become very large, and there is an overhead in producing them, so they should be switched off again (by deleting the line from SETUP.INI) once they are no longer required.
Finally, the following alternative settings are supported only by certain devices:
records all messages from the device from startup, plus extra info
only records messages during bad fax calls (FCLASS device only)
For additional information on modem troubleshooting, please see the following Zetafax technical note:
ZTN1065-INFO: Enabling detailed logging within Zetafax
Last reviewed: 21 October 2005 (GC/EB)
Date Published: 6 January 2000 (GC/GW)