Recent Posts

Pages: [1] 2 3 ... 10
Why do you need Music-on-Hold tracking?

Because this is an important proxy of the quality of your service.
Time on-hold is a symptom of issues in daily handling calls.

QueueMetrics software provides detailed metrics about time on hold using its next-generation data loader: Uniloader.
Uniloader replaced the classic qloader upload tool and includes some new features like Music on Hold tracking.

Read the full tutorial
QueueMetrics news / WombatDialer Certification Training Program announced
« Last post by Mausabot on March 28, 2017, 10:55:06 »
Learn the essentials of WombatDialer predictive dialer for Asterisk PBX with Loway's new training courses.
Certification is included and the course is available in English or Spanish language.

Our training is designed to guide you through creation of unlimited calling number campaigns with focus on practical knowledge for fully automated telecasting, reverse IVRs and classic, agent-based, outbound campaigns.
Lots of helpful information and examples are included, together with references to online resources, including socials and video channels, for additional information and further learning.

Some of the topics covered include:

- WombatDialer full features overview
- Administrative functionalities
- Operational functionalities
- Reporting functionalities
- API functionalities
And much more.

For detailed information follow the link below:
QueueMetrics news / New WombatDialer Webinar Series Announced
« Last post by Mausabot on March 23, 2017, 14:55:34 »
Loway is glad to launch a new webinar series dedicated to its predictive dialer for Asterisk PBX: the WombatDialer.

Learn about Loway's predictive dialer software:

 - How does it work?
 - Which are its main features?
 - Common and less common applications
 - See it in action
 - Benefits for your call-center.

Reserve your Webinar seat now and check Loway's website to see upcoming webinars.

Registrations at

Press Release:
Open QueueMetrics Add-Ons / Re: Project moved to GitHub
« Last post by Hansahoney on March 16, 2017, 09:41:25 »

I was very impressed to read the information is good knowledge. It is very important if we have read the knowledge content.
QueueMetrics Soporte en Espaņol / Re: Mensaje de bienvenida
« Last post by Hansahoney on March 16, 2017, 09:41:15 »

This is very good content for me today. Because this is the most useful content I have come across today.
Loway celebrates the Release Anniversary of QueueMetrics-Live with a limited time promotion.
Each new customer buying a subscription of QueueMetrics-Live receives one month bonus with 30 day money back guaranteed, plus a free installation and initial configuration of the system.

QueueMetrics installation / Re: Issues with Time?
« Last post by mirkox on February 10, 2017, 08:59:12 »
Hi mnettel,
please open /usr/local/qloader/

and search: "my $timezone_offset"

By default it looks like,

my $timezone_offset  = 0 * 3600;  # in seconds

and normally Perl takes the correct time from system:

Do you have a different value?
If not probably you need to set the correct offset (8*3600 or -8*3600)

Remember to stop the qloaderd service, TRUCATE the queue_log table on the database; if your log is rotated use queuePartialUpdater to reload everything (if you have just one queue_log file that's not needed; then restart the qloaderd service


QueueMetrics installation / Re: Issues with Time?
« Last post by mnettel on February 09, 2017, 20:06:14 »
Thanks for the reply. Checking the time via mysql shows our correct time. I should also be clear that the row count is incrementing as expected. It looks like the qloader has been working correctly as expected, but the heartbeat times are still off. Epoch timestamps in the table are correct as well. I'm not sure where to troubleshoot
QueueMetrics installation / Re: Issues with Time?
« Last post by mirkox on February 09, 2017, 11:13:42 »
Hi mnettel,

probably what happens is the following:

- qloader loads new data from queue_log into the database only if the last record in the db has a timestamp < than the one of the new data
- every 15 minutes qloader writes an 'heartbeat' record using the mysql function NOW() to determine the timestamp, if the time is some hour beyond then qloader won't load any new data from queue_log

You can turn off the heartbeat from the qloader settings but what I'd do is to verify and in case fix the mysql time:

After that stop qloader; go to /usr/local/qloader; use queuePartialUpdater to reload the queue_log file(s); restart qloader

QueueMetrics installation / Re: Issues with Time?
« Last post by mnettel on February 08, 2017, 20:43:47 »
Another interesting thing- While the date is usually the correct date, the hour in the Mysql informatino page stays on 02:xx. So if it's 11:30AM the time will show 02:30. If it's 10:45PM, the time will show 02:45
Pages: [1] 2 3 ... 10