TeleFlow Logging
From TeleFlow
| Line 1: | Line 1: | ||
| - | + | This topic is intended to explain how TeleFlow Server (and TeleFlow Simulator) logging works, how to configure it to suit your needs, and how to read and take advantage of the logs. | |
| + | |||
===When TeleFlow Server Logs=== | ===When TeleFlow Server Logs=== | ||
| + | |||
| + | Typically, TeleFlow Server is configured such that it logs all application errors that occur while the TeleFlow Server service is running. @@@ options / how to @@@ | ||
===Where TeleFlow Server Logs To=== | ===Where TeleFlow Server Logs To=== | ||
| + | |||
| + | You can check where your TeleFlow Server is logging by looking at the setting in TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config). Logs are written to the "Log Directory". (NOTE: The directory path must exist for TeleFlow to write to it.) | ||
===Collecting Logs for Support=== | ===Collecting Logs for Support=== | ||
| + | If you are attempting to collect and provide logs of a specific issue(s) in order to get support/help solving a problem, here are some tips on the best/most effective methods of providing both enough of the logs to solve the problem with the minimum amount of unnecessary information: | ||
| + | |||
| + | ====For Problems That Result in Application Errors (Resulting in dropped calls)==== | ||
| + | ====For Problems @@@==== | ||
| Line 16: | Line 25: | ||
In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config): | In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config): | ||
| - | * Ensure "Telephony Hardware" matches the hardware you are running. | ||
* Set "Active Application List File" to the Default.tal file verified/modified in TeleFlow LineList. | * Set "Active Application List File" to the Default.tal file verified/modified in TeleFlow LineList. | ||
* Make sure "Log Directory" is a valid directory path. | * Make sure "Log Directory" is a valid directory path. | ||
Revision as of 00:26, 1 September 2009
This topic is intended to explain how TeleFlow Server (and TeleFlow Simulator) logging works, how to configure it to suit your needs, and how to read and take advantage of the logs.
Contents |
When TeleFlow Server Logs
Typically, TeleFlow Server is configured such that it logs all application errors that occur while the TeleFlow Server service is running. @@@ options / how to @@@
Where TeleFlow Server Logs To
You can check where your TeleFlow Server is logging by looking at the setting in TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config). Logs are written to the "Log Directory". (NOTE: The directory path must exist for TeleFlow to write to it.)
Collecting Logs for Support
If you are attempting to collect and provide logs of a specific issue(s) in order to get support/help solving a problem, here are some tips on the best/most effective methods of providing both enough of the logs to solve the problem with the minimum amount of unnecessary information:
For Problems That Result in Application Errors (Resulting in dropped calls)
For Problems @@@
In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config):
- Set "Active Application List File" to the Default.tal file verified/modified in TeleFlow LineList.
- Make sure "Log Directory" is a valid directory path.
- Check "Unlimited Log File Size".
- Set "Log Lines" to 2000.
- Check "Start TeleFlow Service Automatically".
Before restarting the computer, ensure the following:
- The log directory for TeleFlow is empty (clear any files in it).
- The services for the telephony hardware will start automatically with Windows.
Once the steps above are complete, restart the computer. After logging in:
- Wait a couple minutes before proceeding with the remaining steps.
- Verify that board services have started.
- Run TeleFlow Monitor to see if your applications are running with green lights, or if they have stopped with errors (red lights).
If the system has started with green lights, call the phone number to reach the system to see if it answers.
If it starts with red lights, review the logs. The logs should have only a single attempt to start the application and wait for an incoming call. This means the log will show the minimum amount of output with whatever error(s) are preventing the system from running normally.
