The QueueMetrics Uniloader User Manual


Revision History
Revision 17.08 - covers Uniloader 0.4.02017/07/27L

Table of Contents

1. What is Uniloader?
1.1. What happens if….
2. Installation
2.1. Automated installation (RPM)
2.2. Manual installation
2.3. Running in production
2.4. Example: Uploading data to a local QueueMetrics system
2.5. Example: Uploading data to a QueueMetrics Live system
3. Concepts
3.1. Back-ends
4. Usage
4.1. Uploading data
4.2. Feedback actions: proxying AMI
4.3. Splitting a single queue_log file into multiple back-ends
5. Scenarios
5.1. One Asterisk instance, one local QueueMetrics instance
5.2. One Asterisk instance, one hosted QueueMetrics Live instance
5.3. Multiple Asterisk instances, one hosted QueueMetrics-Live instance
5.4. Multiple Asterisk instances, one QueueMetrics instance
5.5. One Asterisk instance, multiple QueueMetrics-Live instances
5.6. Multiple Asterisk instances, multiple QueueMetrics instances
6. Event tracking
6.1. Installing event tracking through RPM
6.2. Tracking Music-on-Hold
6.3. Tracking Parking lots as queues
6.4. Automatically Tracking Outbound Calls
6.5. Automatically tracking outbound queues in QueueMetrics
7. Diagnostics and tools
7.1. Diagnostics: AMI connection test
7.2. Diagnostics: Upload connection test
8. Custom PBX settings
8.1. Yeastar myPBX

List of Tables

6.1. Services installed in RPM