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.


Messages - QueueMetrics

Pages: 1 ... 21 22 [23] 24 25 ... 202
331
This issue was fixed in upcoming version 13.x.
If you'd like to test it please contact us for a beta.

332
This is weird. I'll open up a bug for this.
Bug #1839

333
Not at the moment, as the profile in itself knows nothing about the extension the agent is supposed to work at.

334
In cluster mode, the agent's page should display a selector so they can choose where to log in to.

335
You can use a validation so that agents can only enter numbers that match a specific regexp. See e.g. realtime.agentRegexp in http://queuemetrics.com/manuals/QM_UserManual-chunked/apd.html

336
If you run a call center, serving clients in a timely way is often very complex, as it requires having enough people available to handle traffic spikes. The number of callers that disconnect because they have been waiting too long in a queue is then an important driver of the quality of your work, and these frustrated callers are the focus of much attention and scheduling/planning efforts in all call centers. This is because in a traditional setting doing inbound calling you basically had no other way of servicing the client but waiting for the person to call in.

With an Asterisk-based PBX and using digital lines, this scenario changes a bit, as:

* Your average caller has an associated caller-id that often matches a physical phone in their proximity
* Telephone traffic is very cheap compared to the cost of agent time for call handling
* You have ample means of programming the PBX to suit your exact needs

So it is now a conceivable scenario to improve the services you are offering by adding an automated call-back option, so that you search the logs of lost calls and you actively schedule recalls on them in order to get back to people who hung up in frustration.

See http://blog.wombatdialer.com/post/41774590472/autorecall

337
The config looks correct.
Are you sure that your agents are choosing the right server when logging in?

338
Running QueueMetrics / Re: Agents not getting proper penalty on queue
« on: January 28, 2013, 12:40:48 »
Qm will not do this automatically, but with the variables passed to the dialplan there is one that you can use to set a penalty if you need it.

339
Did you configure the AMI connection to the remote server? are you using a cluster?

340
Hi Luiz,
when you send a command do you see anything happening in Asterisk?

341
One thing you could do is to try changing the connector/j QM uses to a version pre 5.xx as this should not support the query timeout.

342
I went ahead and ran an AMI test and this was the information it returned:

    AMI URL: tcp:queuemetrics:javadude@172.20.0.11:5038
ERR   Originate failed. You may miss 'originate' privilege on Asterisk 1.6+ or you do not have extension 10@queuemetrics
    Not found: 37@queuemetrics
OK   Asterisk dialog was OK
    AMI Dialog took 9905 ms

I guess you did not include the extensions_queuemetrics dialplan?

343
Running QueueMetrics / Re: Call detail not opening in Firefox...
« on: January 21, 2013, 09:41:41 »
You sure you don't simply have a pop-up blocker enabled? we did not test in on a Mac, but I do not expect such big differences in the same product - same version.
Also, try opening the developer tools and see if you get a Javascript error somewhere.

344
We have started an open project to be used as a helper to query XML-RPC services on QueueMetrics.

This acts as a working example of a PHP library and a viewer that makes it easy to see what is returned on a certain call with a given set of parameters.

Feel free to fork and modify!

https://github.com/Loway/QueueMetricsXmlRpcBrowser



345
See Using the DbTest Diagnostic Tools on page 175 of the User Manual

Pages: 1 ... 21 22 [23] 24 25 ... 202