Importing call log files
To create call reports and system analysis reports (see Getting reports), you must make call log data available to the Management Station using one of these methods:
- Import call log data into Management Station database. This is the most common method.
- Use Log Collect to store data in a central location (without importing into the database).
To conserve disk space, Management Station doesn’t store the original call log data in its database. Instead, it extracts the data needed for reports (and data specified by the application to save) and automatically exports the original data (including any imported utterances) for you to archive. See Purging call log files and How Management Station exports log data.
In addition, Management Station ignores call log files greater than 30 MB. Whether you import the logs or use the Log Collect feature, Management Station ignores large files, continues with the import, and generates minor alarms at the network level.
Recommendations for reducing network traffic and improve system performance:
- Ensure at least 1 GB free disk space on the Management Station host before importing call logs. If the free disk space falls below this threshold, the import task halts and raises an alarm on Management Station. You can see Management Station alarms in the Alarms table at the Nuance Network scope. You’ll need to free up disk space before restarting the task.
- Schedule call log file imports at night when system use is low. You can do this on a daily basis.
- Optional. Import subsets of call logs for immediate use (for any needed time range), and then schedule a nightly task to retrieve all the remaining logs.
- Depending on your call volume, the size of your network, amount of data being imported, and so on, you can schedule call log imports more frequently. Ensure that the scheduled intervals do not overlap. For example, if you’re importing logs on an hourly basis, ensure that your busiest-hour transfers take less than one hour to complete so as not to end after the next scheduled import starts.
- For deployments with frequent import activity, you can configure a second network interface to handle call log activity (while the primary interface handle all other Management Station traffic). See Separating traffic to improve performance.
Related topics
Related topics