Recent Posts

Pages: [1] 2 3 ... 10
1
Loway team will present the new contact center management software lineup at the Asterisk Community Conference Africa 2018, where they will guide attendees through the new features of the call-center solutions portfolio and introduce them to the QueueMetrics monitoring and reporting suite.
   
Loway's CEO and Founder, Lorenzo Emilitri, will deliver two technical speeches on March 14 and 15: "Asterisk and the Docker revolution" and "Call centers 101: QueueMetrics and WombatDialer".

The speeches will be in a dedicated room of the convention and will cover, respectively, what Docker containers are and how Asterisk can work in a containerized environment, and effective call center management best practices using QueueMetrics monitoring suite and WombatDialer predictive dialer.

Read more at

https://www.loway.ch/press-releases.jsp?uid=press-20180220-asterisk-africa&lid=U067
2
Running QueueMetrics / Re: license agreement every 5 minutes.
« Last post by emel_punk on February 17, 2018, 16:46:54 »
Does anybody have a clue? or should I contact support  by mail?... because this issue is really important and it's happening on my 3 servers connected to the cluster
3
QueueMetrics news / QueueMetrics monitoring suite for Asterisk Payroll tutorial
« Last post by Mausabot on February 14, 2018, 10:05:13 »
Are you looking for a way to easily track your Asterisk call center agents' session times, in order to produce accurate payroll records?
Are you having trouble figuring out how to differentiate between payable and non payable pauses for your workers?

If your answer is yes then discover how with the new QueueMetrics payroll tutorial:

https://www.queuemetrics.com/blog/2018/02/13/queuemetrics-payroll/?lid=U066
4
Problems / Re: JSON Report API missmatch V14 - V17
« Last post by mirkox on February 13, 2018, 14:27:17 »
Which kind of difference there are? Do you have a sample response from both version?

Anyway yes, it's possible that the table changed over time
5
Problems / Re: JSON Report API missmatch V14 - V17
« Last post by NereliZ on February 13, 2018, 12:44:03 »
Hi,

That did helped. I was going round and round via configs it was bit confusing as they all mainly for the panel and these to not mention API. Anyway big part of the problem solved. But it still return onqueue differently form older version. Just populate field with search query.

Thanks,
Nerijus Barauskas
6
Problems / Re: JSON Report API missmatch V14 - V17
« Last post by mirkox on February 13, 2018, 10:03:16 »
Hi NereliZ,

does setting the following in the configuration help?

realtime.members_only=true
realtime.all_subqueues=true
7
Problems / Re: JSON Report API missmatch V14 - V17
« Last post by NereliZ on February 12, 2018, 11:42:58 »
Hi, thanks for quick response.

1. API Call: curl -X GET -H "Content-Type: application/json" --user "username:password" "https://exmaple.com:443/queuemetrics/QmRealtime/jsonStatsApi.do?queues=x1|x2|x3&block=RealtimeDO.RTRiassunto"

2. API Call: curl -X GET -H "Content-Type: application/json" --user "username:password" "https://example.com:443/queuemetrics/QmRealtime/jsonStatsApi.do?queues=x1|x2|x3&block=RealtimeDO.RTAgentsLoggedIn"

These API calls in question. Sorry forgot to include in my question.
8
Problems / Re: JSON Report API missmatch V14 - V17
« Last post by mirkox on February 12, 2018, 11:36:19 »
Hi NereliZ,
please send us the call to the API so that we can test locally

Kind Regards
Mirko
9
Problems / JSON Report API missmatch V14 - V17
« Last post by NereliZ on February 12, 2018, 10:59:09 »
Hi,

We are using JSON Reprot API with our QueueMetrics. But after upgrade from version 14 to version 17 we spot some issues which is holding us to use version 14. The problem is the change with some API calls we used to use. In all the cases we send a Queues ids to get only information related to queues we are interested in.

1. In earlier version RTRiassunto was returning information about the all queues passed by queues parameter including queues with no active call. Now it looks like it returns only those with active calls.

2. RTAgentsLoggedIn behaves even worse. We have both version running in parallel to make sure we are ready to make the switch. But the RTAgentsLoggedIn returns different number of logged in agents. While the newer version includes some other agents from other queues and field on_queues populated with the search value, so where is no way to trace which agent belongs to which queue.

It looks more like it completely ignores queues parameter or use it in some kind of different way.
10
Running QueueMetrics / license agreement every 5 minutes.
« Last post by emel_punk on February 09, 2018, 18:06:56 »
EHLO

I have 3 QM servers on clusters. I had to update one of the servers because had some problem with hardware and after installed  and configured cluster every 5 minutes ask for "agree license". 
the updated server has  queuemetrics-17.06.4-419 while others 2 queuemetrics-15.10.6-20 and queuemetrics-14.06.2-822 could this be the problem?
Pages: [1] 2 3 ... 10