FAQs

uniloader-freeswitch is generating no data

To test that the system is working, you can either send a call to a mod_callcenter queue, or you can change the status of an agent from the FusionPBX GUI. When either of these things happen, Freeswitch will generate events that will trigger the writing on your aggregate queue_log file.

If this does not happen, it might mean that:

  • Uniloader cannot connect to Freeswitch - you can esily exclude this by checking access - see Check ESL access

  • Freeswitch is generating no events

  • Freeswitch is generating events with a format that is not supported

To verify the which is which of the last two, we can connect with and do the same interaction Uniloader does (note: we assume the default address, port and auth token - change as needed):

nc -v 127.0.0.1 8021

When you have a reply, you type:

auth ClueCon

And then:

events json custom callcenter::info

At this points, events are printed. If you log an agent on or off and you receive nothing, than events are not generated.

To close the connection, press Ctrl + D.

If the command nc is not available, netcat is available with apt-get install netcat on Debian and yum install netcat on CentOS.

My tenant is receiving no data

(tbd)

Agents cannot log on or off

First, log on to the QueueMetrics Live instance, then click on Home Page → Settings Bar → Diagnostics → AMI Commands.

You should see a list of actions performed recently (or pending), and their own state.

  • A state of wait means that the action was not yet picked up by Uniloader; a few seconds are OK, but if it stays there for longer, it may mean that service uniloader-splitter is not running, or there is a network issue, or maybe you did not set actions: True in the Ansible script.

  • A state of ok means that the action was performed successfuly, i.e. the PBX handled it without raising errors.

  • A state of ko means that the action was not performed: that is, the PBX was unreachable, access credentials were wrong or agent/queue ids were incorrect. Check PBX access using Uniloader.

The time shown in "Sent" is how long the command waited/has been waiting in the queue, while "Proc" is how long it took for the PBX to process it.