Messages

196

Running QueueMetrics / Re: inbound queue member problem

« on: September 03, 2014, 11:35:13 »

That depends on your inbound trunk's settings.

Usually extensions like 300* are used to log in queues (in systems like FreePBX or Elastix); you need to remove that *

Mirko

197

Running QueueMetrics / Re: inbound queue member problem

« on: September 03, 2014, 10:53:46 »

Not sure I understand the problem, could you please rephrase?

198

Running QueueMetrics / Re: Need to synchronize QM agents/users with third-side database

« on: September 03, 2014, 10:49:24 »

Hi,

QueueMetrics' Json API (QM 14.06+) has the possibility to add / remove agents, queues, users and so on in QM.
You can use that to integrate with your system.

http://manuals.loway.ch/QM_JSON_manual-chunked/

Best Regards
Mirko

199

Scripting QueueMetrics / Re: RealtimeDO.RTRiassunto Not returning Num Agents and Ready Agents in 14.06.2

« on: September 02, 2014, 18:17:38 »

Thanks.

How do you log your agents to start work? Are they static? Because in that case is right that QueueMetrics 14.06 does not show them as logged in the queues; it was wrong in the old version.

If you log your agents (from the agent's page) with Join Q/Leave Q you'll see exactly what agent is working on a given queue; try enabling hotdesking: http://manuals.loway.ch/QM_UserManual-chunked/ch24.html#_enabling_hotdesking_in_the_agent_page  (24.16)

Mirko

200

Scripting QueueMetrics / Re: RealtimeDO.RTRiassunto Not returning Num Agents and Ready Agents in 14.06.2

« on: September 02, 2014, 18:00:16 »

Well, something could have been changed, 1.6 is really old; could you please post four screenshots all taken in the same moment:

1)xml-rpc browser for 1.6
2)xml-rpc browser for 14.06
3)realtime page in queuemetrics from 1.6
4)realtime page in queuemetrics from 14.06

(disable all filters from realtime page)

Thanks
Mirko

201

Scripting QueueMetrics / Re: RealtimeDO.RTRiassunto Not returning Num Agents and Ready Agents in 14.06.2

« on: September 02, 2014, 17:09:41 »

Hello Barry,

could you verify if using the same configuration.properties for both the machine they still have a different behaviour?
Are they looking to the same Asterisk?

Kind Regards
Mirko

202

Running QueueMetrics / Re: calls being processed dont works

« on: September 02, 2014, 15:48:59 »

Hi,

for inbound calls you should follow this tutorial: http://manuals.loway.ch/QM_Trixbox-chunked/ch03.html

Kind Regards
Mirko

203

Running QueueMetrics / Re: Multiple Agents Join Queues on Single Extension

« on: September 01, 2014, 11:23:51 »

Hello,

Before I continue, I should mention that we are not using the new agent page. We are using the live_agent.jsp page because this prevents agents from adding or removing queues on the fly when they are assigned specific queues.

This was fixed and will be available in the next release (realtime.dynamicLoginQueues=assigned will only show assigned queues and will prevent the agent from logging in/out from single queues).

As for the main issue, we think this could be implemented (I created and entry in our bug tracker: #2457), but we don't have a schedule for this, surely won't be present in the next release. If you need it urgently you could think about a customization.

Kind Regards
Mirko

204

Problems / MOVED: calls being processed dont works

« on: September 01, 2014, 10:52:23 »

This topic has been moved to Running QueueMetrics.

http://forum.queuemetrics.com/index.php?topic=1880.0

205

Running QueueMetrics / Re: calls being processed dont works

« on: September 01, 2014, 10:50:53 »

Hi,

when you did the test (inbound) you called the extension directly or the queue?
Outbound won't work since outbound calls needs some additional configuration.

What you could do is to post here what Asterisk writes in queue_log.
Open a shell on your asterisk machine and send this command: tail -f /var/log/asterisk/queue_log  (it will show you new lines in queue_log as soon as they're written by Asterisk). Keep it opened.

Now, do the following:

1) Log in an agent on a queue
2) Make a call on that queue, make it ring two or three times
3) Answer, wait for some secods, the hang up the call
4) Log off
5) send us the output

Mirko

206

Running QueueMetrics / Re: Reporting on number dialed to reach queue

« on: September 01, 2014, 09:57:55 »

Solved on support portal:

In order to track this kind of information you need to setup the DNIS tracking on your dialplan: http://manuals.loway.ch/QM_UserManual-chunked/ch24.html#_tracking_dnis_and_ivr_information

Mirko

207

Scripting QueueMetrics / Re: method QM.stats Params description

« on: September 01, 2014, 09:28:57 »

Solved on support portal

208

Running QueueMetrics / Re: Multiple Agents Join Queues on Single Extension

« on: August 22, 2014, 11:41:31 »

Hi,

in many cases this is the desired behaviour since many times agents forget to log off after their working session.

A solution for this problem could be to implement a script in the logon dialplan that checks if the extension is already used by an agent in that given moment (you can use QueueMetrics' API to get this information),

Mirko

209

Running QueueMetrics / Re: Outcome after 30 minutes

« on: August 13, 2014, 10:21:32 »

Hi,

we solved that bug, now the 30 minutes start from the end of the call; update to the latest version (14.06), there's also other interesting stuff such as:

- a nice GUI facelift
- a new JSON API
- the new Agent's Page (you can enable it adding the NEWAGENTPAGE security key to your users)

I suggest the clean tomcat's cache and also your browsers' cache after the update!

Kind Regards
Mirko

210

Running QueueMetrics / Re: New Icon Agent Page

« on: August 06, 2014, 12:24:41 »

This enquiry was solved on our support portal.

The new agent page is automatically enabled on all the new installation. If you update from a previous version you want find there because our updates doesn't change anything in your configuration (this is by design).

If you want to enable the new agent's page add the NEWAGENTPAGE key to your user's or directly to the AGENTS user class.