|
Depending on how the TeleFlow Application was developed, there may or may not be some statistics collected. Most of the new application template applications provided with TeleFlow have the "Logger" flowchart built-in, and they are automatically set to create a log entry for calls answered, and when a caller hangs up.
These logs are CSV files, and the "fields" in them are described in the Logger flowchart. This means that you can import them into a database table(s) and create any reports on them you wish.
If your application wasn't developed to log events, then it won't have any call statistics. (If it was, the .log files will be in a "stats" directory(usually) in the same directory as the .TAP file resides(usually)) The Logger flowchart can be added to your application in the TAP screen. In the steps toolbox, switch to the templates tab, click "Logger", and drop it into the TAP screen flowchart space to add it. Then, add Run Flowchart steps to run Logger to log codes you wish to track in the appropriate places. See the example applications packaged with TeleFlow Designer for examples of how this is done.
The "Health" of the system, and dropped calls, can be monitored with TeleFlow Monitor: if all the lights are green, then likely, no calls were dropped. Checking the TeleFlow log directory - set in TeleFlow Config - for *.log files can also indicate problems. If no errors are logged, there likely have been no dropped calls. (This does assume that your TeleFlow Application exits when a Fatal Error is triggered. Most of the sample applications packaged with TeleFlow Designer properly exit when a Fatal Error occurs.)
|
