Messages

1

Running QueueMetrics / Tracking Transfers Out of Queues

« on: March 21, 2014, 19:16:46 »

My apologies if this is in the wrong group - I also searched the forum, but could not quite find what I was looking for:

We have an "Operator Queue", and from that queue operators will transfer out to specific extensions. In QueueMetrics, as soon as the call is transferred out of the queue, the tracking stops. I presume this is because QM tracks queues, and after the direct transfer, we are no longer processing through a queue. The only solution we've thought of is to make each agent their own inbound queue, and then have the operator transfer to that queue. Is there another way we can still transfer to direct extensions and have QM track it? We only have 4 users in this group, so making 4 more queues isn't a big a deal, but this could quickly become unsustainable if the team grows.

Thanks for any thoughts or suggestions!

2

Running QueueMetrics / Possible to Remove Live Monitoring from User?

« on: October 02, 2013, 16:39:55 »

Hello -

Is it possible to restrict a user from seeing the Live Monitoring section? My organization requested a user account be made for a client to view call stats, but they want me to restrict them from seeing Live Monitoring. Is this currently possible?

3

Running QueueMetrics / Re: Agent Status Cannot be Determined

« on: October 02, 2013, 16:37:52 »

Firewall configuration seems to be ok, but I did not setup all of the policies, so that could be. For now, everything is running smoothly. Thanks for your feedback!

4

Running QueueMetrics / Re: Agent Status Cannot be Determined

« on: September 17, 2013, 20:16:32 »

Yes to both questions. No changes were made to the system, other than changing the IP of the QM machine. Since this issue first occurred, we have changed the machine's IP back to what it was, and have adjusted our fireboxes policy to route incoming traffic to this machine, so we are successfully serving QM on a public domain, and all agent statuses are reporting correctly. I would still be interested to know why this occurred - the only thing I changed was the machine's IP. Are there settings in qloaderd specific to machine addresses?

5

Running QueueMetrics / Agent Status Cannot be Determined

« on: September 12, 2013, 16:38:31 »

I know this question has been asked many times before, but I believe I've found myself in a unique - or n00b - scenario..

QM and Asterisk are on different servers. I use freePBX as the GUI for asterisk. Everything was working great. I changed the IP of the QM server in order to host it on a public domain. I mounted my recordings folder back to asterisk, and everything seemed fine. However, all of my users were getting "Status cannot be determined". I checked the freePBX queue reports from Asterisk, and I can see all agents in their correct queues. They can even make and receive calls. So my assumption is the info is being written via the AMI correctly, but QM is not reading the queue log correctly.. so I have changed the IP back to what it was, (and re-mounted to Asterisk) and everything is back working correctly.

Is there a setting or config I missed after changing the servers IP? Or is there maybe a log I can review that might give clues? I rebooted QM and Asterisk both, and like I said, QM appeared to be sending the correct commands and Asterisk received them... but there must've been something wrong with the queue_log data....

Thanks for all your help!

6

General Asterisk configuration / Saving Asterisk Recordings to QM Server

« on: June 26, 2013, 17:20:26 »

Hello -

    I have seen other posts related to this topic, but the threads have all been inactive for quite some time. What I am looking to do is have our Asterisk recordings saved to the same server as QM. I recently took over control of our network, and the previous admin had this setup correctly, but do to a recent crash, the recordings were changed to save on the Asterisk server. Now that we have QM up and running again, I would like to store the recordings on the QM server. I am a relative novice with Asterisk - and Linux - so a step-by-step walk-through (or link to one) would be much appreciated. Currently the calls are saved in the directory /var/spool/asterisk/monitor and are separated by year, month, and day. If you think this would be more appropriate for an Asterisk forum, I would be glad to post there.

Thank you!!

7

Running QueueMetrics / Re: QM not in /init.d/ or services

« on: June 25, 2013, 21:12:42 »

Again, my apologies for the delay and thank you so much for the replies! I ended up removing everything and installing via yum. All is well now!

8

Running QueueMetrics / Re: QM not in /init.d/ or services

« on: June 20, 2013, 21:31:04 »

Thank you for your reply, my apologies I did not see it! I installed using the .tar rather than yum. Our QM server crashed recently, and we did not have a proper backup (I know, I know - I am the new guy, shame on the old guy). I am now having to build a new QM server, and to avoid any issues with the Asterisk server, I used the tar to install the same version of QM that was on the crashed server (12.2.4)

9

Running QueueMetrics / QM not in /init.d/ or services

« on: June 11, 2013, 20:08:07 »

Hello all! Short-time troll, first-time poster here. To start, my apologies if this is in the wrong section. I have searched many times and have not been able to locate an answer anywhere, but if this has already been answered elsewhere, please let me know and I will gladly follow it!

I've recently installed QM and its dependencies (Java, Tomcat, mySQL, java connector) and can successfully access the site. My current issue is that QM does not appear in /init.d, and thus I don't know how to stop/start/restart it. "service queuemetrics stop" returns the same "no such file" notice. Did I screw something up during install? Is it possible to just locate the script and place it in init.d? I searched the QM files and was only able to locate a restart.sh script.

I should also add that I am a relative novice to Linux (currently running Cent), but can certainly follow directions and post screenshots/logs!