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 - matts

Pages: [1]
1
@coolname that doesn't do what I need unless I'm missing something.

@Marcos I'm not sure what your referring to by "atomic item", do you have link a manual on it?  I know can the DNIS table to a report but I need to add the Info as column of an existing report or create a new one with the info.  We need to be able to see which calls came from which DNIS. Not just how many to each DID.

2
Running QueueMetrics / Adding a column to an exsisting report
« on: July 18, 2011, 22:55:12 »
Can a column be added to an existing report? We want to add DNIS info to the existing Queue details report that shows on the Answer Detail tab, so that it can exported as a single report.

3
Running QueueMetrics / Re: Assigning a user multiple Keys
« on: June 03, 2011, 18:44:44 »
That's how I have it setup.

We have queue's A, B, C, & D each with the respective key A, B, C, & D
So Agent1 will be configured with Keys A & C but only sees data for queue A and nothing for queue C.

Is there a certain syntax they should be entered with? Coma separated etc?

I plan on upgrading to 1.7.1 over the weekend and will see if it still behaves the same.

4
Running QueueMetrics / Assigning a user multiple Keys
« on: May 24, 2011, 22:55:06 »
We have some agents that need to be able to see real time data for multiple queues.  When I add multiple Keys to a single agent only one key takes effect.  Is there a way to assign multiple keys to each agent? 

5
Here are screen shots for one of the queue's the biggest issue is when watching the "All Queues" group as it doubles the length of the the screen.  And selecting Agents = Members filters out the "Calls Being Processed" which makes it useless for the managers to be able to monitor call times.

I also noticed today that the same duplicate entries show up on the Payroll Report page.

Agents All:


Agents Members:


6
QueueMetrics installation / Re: Unable to report based on agent
« on: April 13, 2011, 19:05:54 »
Here's a chunk of the log for agent/7008 logging into Q160, pausing, unpausing, and logging out

Code: [Select]
1302712733|1302712733.21445|160|Local/7008@from-queue/n|ADDMEMBER|
1302712756|NONE|NONE|Local/7008@from-queue/n|PAUSEALL|
1302712756|NONE|160|Matthew S|PAUSE|
1302712756|1302712756.21447|NONE|Agent/7008|PAUSEREASON|22
1302712771|NONE|NONE|Local/7008@from-queue/n|UNPAUSEALL|
1302712771|NONE|160|Matthew S|UNPAUSE|
1302712782|1302712782.21454|160|Local/7008@from-queue/n|REMOVEMEMBER|

7
When on the real time page it shows duplicate info for the "Agents currently logged in" at the top of the list it shows just the Agent Description for those currently logged in and at the bottom of the list it shows agent/description for all the assigned agents logged in or not.  Setting the second agent field at the top to "Members" filters out the bottom group of agents, but it also filters out the "Calls being processed" but only for some calls, some will show whether it's set to "members" or "all" all the agents are assigned to the queues or queue groups that I'm looking at.

8
QueueMetrics installation / Re: Unable to report based on agent
« on: April 11, 2011, 18:49:00 »
I don't see that option in my 'configuration.properties' but I have "default.rewriteLocalChannels=true"

9
QueueMetrics installation / Re: Unable to report based on agent
« on: April 08, 2011, 20:07:43 »
I'm selecting the agents from the drop down menu.  The agents are setup as agent/xxxx in QM, and that looks like what the report is looking for and that's what it shows in the report for all agents.

Now to make QM work with our server and all the queue priority patches our developer wrote for asterisk we have to log the agents into the queues as local/xxxx.
exten => 35,4,AddQueueMember(${QUEUENAME},Local/${AGENTCODE}@from-queue/n,${DB(QPENALTY/${QUEUENAME}/agents/${AGENTCODE})},,${DB(AMPUSER/${AGENTCODE}/cidname)},HINT:${AGENTCODE}@ext-local)

I just tried setting one of the agents as Local/xxxx in QM but now he doesn't show up at all in any report.  I'm guessing the report is hard set to look for Agent/xxxx? Or am I missing something?

10
QueueMetrics installation / Unable to report based on agent
« on: April 07, 2011, 22:23:52 »
When I run a custom report for an agent it comes back with 0 calls.  But if I run it for all queues or a queue group it will show calls for that agent.

Any ideas? We're running 1.7

11
Realtime Live / Groups not showing on Realtime Ajax screen
« on: February 22, 2011, 21:27:53 »
The agents groups filter isn't showing on the "realtime monitoring (AJAX)" page on our server, the drop down just shows "-".  It works on the regular realtime monitoring page, also if you set it on the regular page the settings are effective on the ajax page but the groups drop down still just shows "-".

Also if I set the Location filter all the Queues and "Calls being processed" disappear is there a way to change that behavior?

12
QueueMetrics installation / queue_log rotation question
« on: January 31, 2011, 23:37:04 »
I'm in the process of installing a QueueMetrics trial and have run into an issue with queue_log rotation.

Background info:
Running a Pbxact server (FreePBX based on CentOS 5.4) with asterisk 1.4.32
QueueMetrics installed a separate server (CentOS 5.4)
qloaderd is installed on the asterisk server pushing all the data to the MySQL server on the QueueMetrics server.

Your install docs suggest disabling log rotation for the /var/log/asterisk directory which is out of the question on our server.

I found one forum post that suggests simply restarting the qloaderd daemon will work to keep data flowing; http://forum.queuemetrics.com/index.php?topic=137.0

My thought is to adjust the logrotate script as below to restart the daemon after the file is rotated.  Will that work and would there be any drawbacks using this method?

Code: [Select]
/var/log/asterisk/queue_log {
daily
missingok
rotate 30
notifempty
sharedscripts
create 0640 asterisk asterisk
postrotate
        /etc/rc.d/init.d/qloaderd restart > /dev/null 2> /dev/null
endscript
}

Pages: [1]