1906
Running QueueMetrics / Re: feature request: adding default terminal for agents
« on: July 01, 2009, 23:16:07 »
I agree - we track this as bug #762.
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.
1907
Running QueueMetrics / Re: Agents on multiple queues have wrong realtime status
« on: July 01, 2009, 23:14:12 »
R>una report for queues A and B, so yo get the statuses correct.
1908
Improving QueueMetrics / Re: Forgot Password option
« on: June 30, 2009, 14:52:49 »
yes I think this would work.
If you don't mind, I would add this to the user-contribuited scripts for QM.
If you don't mind, I would add this to the user-contribuited scripts for QM.
1909
General Asterisk configuration / Re: Pause reasons "-"
« on: June 30, 2009, 14:51:34 »
Hello I think this is a bug - the "-" should mean "no pause code", while in the reports the hyphen should mean "pauses without a pause code".
I would likel to see a piece of your queue_log that reproduces the problem - plese send it to our techical support, cite bug #761.
I would likel to see a piece of your queue_log that reproduces the problem - plese send it to our techical support, cite bug #761.
1910
Outbound and QueueMetrics / Too few rings for outbound
« on: June 26, 2009, 17:28:41 »
A number of users complain that the dial-out macros do incorrect logging if the callee answers too late.
It would be better to make the dial time way longer in the default extensions_queuemetrics.conf file that ships with QM; so that where it currently says:
you change that to
This should solve the issue at hand.
It would be better to make the dial time way longer in the default extensions_queuemetrics.conf file that ships with QM; so that where it currently says:
Code: [Select]
exten => s,n,Dial(${QDIALER_CHANNEL},30,.... you change that to
Code: [Select]
exten => s,n,Dial(${QDIALER_CHANNEL},300,.... This should solve the issue at hand.
1911
Outbound and QueueMetrics / Re: EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution
« on: June 26, 2009, 17:25:23 »
You would better do a trace ands see steèp-by-step what it does.
1912
Outbound and QueueMetrics / Re: chosing outbound queue numbers
« on: June 26, 2009, 17:24:21 »
Well it's not a good idea, because you don't control the same parameters.
Eg. on an inbound call, the wait time is something you strive to optimize.
On an outbound call, you have no control.... callees pick up when they please.
So if you run a report for both, the meaning of the wait time will be hard to understand.
I suggest that you create different queues for the tracking, and then if you really want you rcreate an aggregate queue that joins together inbound and outbound traffic.
Eg. on an inbound call, the wait time is something you strive to optimize.
On an outbound call, you have no control.... callees pick up when they please.
So if you run a report for both, the meaning of the wait time will be hard to understand.
I suggest that you create different queues for the tracking, and then if you really want you rcreate an aggregate queue that joins together inbound and outbound traffic.
1913
QueueMetrics installation / Re: Switching from flatfile to Mysql
« on: June 26, 2009, 17:21:39 »
Is it working?
1914
Improving QueueMetrics / Re: Forgot Password option
« on: June 25, 2009, 12:02:08 »
If a number of people are interested, we could add this in.
1915
Improving QueueMetrics / Re: Email Alerts
« on: June 25, 2009, 12:01:23 »
It could be an idea to have some alarms trigger an email as well.
1916
Running QueueMetrics / Re: lag upon retrieving call details // verbose logging
« on: June 24, 2009, 17:53:04 »
I tell you what it is: you have too many audio recordings, and QM wil scan all them.
You should use a PM like LocalFilesByDay to reduce searching - see here: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s17.html#_pms_to_match_recorded_calls
You should use a PM like LocalFilesByDay to reduce searching - see here: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s17.html#_pms_to_match_recorded_calls
1917
Running QueueMetrics / Re: Agent Queue Log in
« on: June 24, 2009, 17:51:25 »
Hello Vidura,
you have basically two scenarios:
- if you use Agent/xxx channels, they can be sitting anywhere and they will be reported with their logins
- if you use Local/xxx channels or SIP/xxx channels, they wiull be shown as Agent/xxx, but the "xxx" is the extension tehy were sitting at.
you have basically two scenarios:
- if you use Agent/xxx channels, they can be sitting anywhere and they will be reported with their logins
- if you use Local/xxx channels or SIP/xxx channels, they wiull be shown as Agent/xxx, but the "xxx" is the extension tehy were sitting at.
1918
Running QueueMetrics / Re: Signal Problem
« on: June 24, 2009, 17:50:49 »
if you use the Agent's page, you could associate a URL like xmpp:mysupervisor@myfirm so that you click on a button, a Jabber client is launched and it connects to mysupervisor@myfirm.
A good client to use is Spark from Jive Software (I think itì's free).
A good client to use is Spark from Jive Software (I think itì's free).
1919
QueueMetrics installation / Re: "The extension to monitor must be defined" error with live call monitor
« on: June 24, 2009, 17:48:14 »
We'll be working on this since next week.
1920
QueueMetrics installation / Re: agents can't login via the agent page.
« on: June 24, 2009, 17:47:22 »
If the dialplan on the top post was executed, you should have the AddQueuememeber() command run and add the agent to the queue. You gent no errors? are you sure the AMI user has all permissions?