1
Running QueueMetrics / Re: Realtime page and ready agents
« on: October 25, 2011, 00:20:57 »
Nothing QM guys? ;-)
QueueMetrics professional call center suite for the Asterisk PBX
News:
Welcome to the new forum!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Running QueueMetrics / Re: Realtime page and ready agents
« on: October 12, 2011, 00:54:41 »
Hello,
I believe my queue_log entries are correct. Please follow these pictures.
This is clean queue_log - ready agents block shows 0 ready agents for all queues - this is correct
This is after agent login to one queue named Ceska (id 7000), but ready agents block shows 1 for all his defined queues - this is NOT CORRECT, should be only in queue Ceska
The entries after agent login:
| P001 | 1318372815 | MANAGER | 7000 | SIP/1999 | ADDMEMBER | | | | | | 8546066 | |
| P001 | 1318372815 | 1318372815.496Q | 7000 | Agent/998 | HOTDESK | SIP/1999 | | | | | 8546065 | |
Regards,
David Hajek
I believe my queue_log entries are correct. Please follow these pictures.
This is clean queue_log - ready agents block shows 0 ready agents for all queues - this is correct
This is after agent login to one queue named Ceska (id 7000), but ready agents block shows 1 for all his defined queues - this is NOT CORRECT, should be only in queue Ceska
The entries after agent login:
| P001 | 1318372815 | MANAGER | 7000 | SIP/1999 | ADDMEMBER | | | | | | 8546066 | |
| P001 | 1318372815 | 1318372815.496Q | 7000 | Agent/998 | HOTDESK | SIP/1999 | | | | | 8546065 | |
Regards,
David Hajek
3
Running QueueMetrics / Re: Realtime page and ready agents
« on: September 30, 2011, 12:17:27 »
Hello-
to summarize the problem: Ready agents value on realtime page are showing incorrect values when using with hotdesking and dynamic queues.
If you think our queue_log entries are not correct can you please give us the example of the correct queue_log entries. I will simulate it myself and see if it works.
Thanks
David
to summarize the problem: Ready agents value on realtime page are showing incorrect values when using with hotdesking and dynamic queues.
If you think our queue_log entries are not correct can you please give us the example of the correct queue_log entries. I will simulate it myself and see if it works.
Thanks
David
4
Running QueueMetrics / Re: Realtime page and ready agents
« on: September 29, 2011, 12:10:13 »
Hello,
this is not a solution for the problem. ADDMEMBER entries are generated by asterisk and it is a work for qloader to rewrite it accordingly. So when I'm looking into queue_log SQL table I can see that it is correctly rewritten:
See eg. this entry:
| P001 | 1317288427 | 1317288427.652Q | 8012 | Agent/534 | HOTDESK | SIP/1007 | | | | | 8231213 | |
| P001 | 1317288426 | MANAGER | 8012 | SIP/1007 | ADDMEMBER | |
Thank you
David Hajek
this is not a solution for the problem. ADDMEMBER entries are generated by asterisk and it is a work for qloader to rewrite it accordingly. So when I'm looking into queue_log SQL table I can see that it is correctly rewritten:
See eg. this entry:
| P001 | 1317288427 | 1317288427.652Q | 8012 | Agent/534 | HOTDESK | SIP/1007 | | | | | 8231213 | |
| P001 | 1317288426 | MANAGER | 8012 | SIP/1007 | ADDMEMBER | |
Thank you
David Hajek
5
Running QueueMetrics / Realtime page and ready agents
« on: September 27, 2011, 22:33:08 »
Hello,
we're using QM with dynamic agents with hotdesking and having issues on realtime page with ready agents values. We are generating proper HOTDESK and ADDMEMBER entries eg:
1317152725|1317152725.909Q|7000|Agent/998|HOTDESK|SIP/1999
1317152725|MANAGER|7000|Local/1999@qmqueue/n|ADDMEMBER|
Agent/998 is properly shown on realtime page on the bottom (agent's section) as logged in on extension 1999 and in the queue 7000. This agent has many other queues defined but is not logged in to them. But ready agents values on realtime page will count +1 for each member queue for this agent - but we don't generate ADDMEMBER entries for the other queues.
This is rather misleading when trying to find out how many agents are really available for each queue.
I believe this might be just a configuration bug, be we we're not able to find out any reference in manual to this problem.
Thank you
David
we're using QM with dynamic agents with hotdesking and having issues on realtime page with ready agents values. We are generating proper HOTDESK and ADDMEMBER entries eg:
1317152725|1317152725.909Q|7000|Agent/998|HOTDESK|SIP/1999
1317152725|MANAGER|7000|Local/1999@qmqueue/n|ADDMEMBER|
Agent/998 is properly shown on realtime page on the bottom (agent's section) as logged in on extension 1999 and in the queue 7000. This agent has many other queues defined but is not logged in to them. But ready agents values on realtime page will count +1 for each member queue for this agent - but we don't generate ADDMEMBER entries for the other queues.
This is rather misleading when trying to find out how many agents are really available for each queue.
I believe this might be just a configuration bug, be we we're not able to find out any reference in manual to this problem.
Thank you
David
6
Scripting QueueMetrics / Re: Changes in XML/RPC after upgrade from 1.6 to 1.7
« on: April 13, 2011, 10:14:42 »
What do you ask for? ;-)
David
David
7
Scripting QueueMetrics / Changes in XML/RPC after upgrade from 1.6 to 1.7
« on: April 12, 2011, 13:14:09 »
Hello-
we found there is a change in date format and its meaning when using DetailsDO.AgentPauses XML/RPC call. Version 1.6.X returns mm:ss format which specifies the length of pause, the new 1.7.X returns dd/mm hh:mm:ss formas which means time of pause being activated.
Is there a way how to change it back to 1.6.X format?
Regards
David Hajek
we found there is a change in date format and its meaning when using DetailsDO.AgentPauses XML/RPC call. Version 1.6.X returns mm:ss format which specifies the length of pause, the new 1.7.X returns dd/mm hh:mm:ss formas which means time of pause being activated.
Is there a way how to change it back to 1.6.X format?
Regards
David Hajek
8
Running QueueMetrics / Re: OnHold status and RT panel
« on: March 21, 2011, 14:31:40 »
It is not reported by Asterisk, but I can imagine using device state (hints) to filling up queuelog with necessary entries.....
9
Running QueueMetrics / OnHold status and RT panel
« on: March 14, 2011, 14:14:15 »
Hello,
is there some way to "monitor" onHold extension status in RT panel? Would be nice if we could use some dedicated verb for it. Our customer wants to measure "how long the customer has been onHold" - and have some report for it.
Thanks for ideas.
Regards,
David Hajek
is there some way to "monitor" onHold extension status in RT panel? Would be nice if we could use some dedicated verb for it. Our customer wants to measure "how long the customer has been onHold" - and have some report for it.
Thanks for ideas.
Regards,
David Hajek
10
Running QueueMetrics / Color of graphs in QM
« on: October 25, 2010, 13:11:45 »
Hello,
I have some weird problem with choosen color for generated graphs - they're grey or white and its hard to see on some monitors. Can I change the color by some config property? I was not able to find it in manual.
Thank you
I have some weird problem with choosen color for generated graphs - they're grey or white and its hard to see on some monitors. Can I change the color by some config property? I was not able to find it in manual.
Thank you
11
Scripting QueueMetrics / XML-RPC and DNIS filter
« on: August 17, 2010, 09:55:53 »
Hello,
it is possible to use DNIS filter in XML-RPC queueries? It is possible to use DNS filter in Custom reports in QM, but we need to use same filter in XML-RPC calls.
Thank you,
David
it is possible to use DNIS filter in XML-RPC queueries? It is possible to use DNS filter in Custom reports in QM, but we need to use same filter in XML-RPC calls.
Thank you,
David
Pages: [1]