Topics

1

Running QueueMetrics / Custom Report not displaying calls when using a custom time range

« on: July 20, 2015, 03:06:05 »

When running a custom report, if we try to narrow down a search using a custom timeframe, it displays zero calls.

Example:
Agent logged in and took first call at 11:33. If I search from 11:30 - 16:30, it shows all calls from that time range.

If I change the start time from 11:30 to 11:31 to narrow down the search, it shows zero calls were taken, even though there are calls taken at 11:31, 11:34 and so on. It appears that the only way to search is by starting at a time before they took their first call, such as 11:30 or if I start at 00:00 it shows all calls.

Does anyone have any idea why we can't search for specific time ranges? Such as if I only wanted to see calls this agent took between 11:45 and 12:45?

Screenshots:
--------------

Search from 1130 - 1630
http://postimg.org/image/skyyjqqhh/

Results from 1130 - 1630
http://postimg.org/image/5k0c742ct/
(Shows all calls within the time range like you would expect)

Search from 1131 - 1630
http://postimg.org/image/o6b85i2t3/

Results from 1131 - 1630
http://postimg.org/image/resm8uxqn/
(Shows zero calls even though there are definitely calls within that time range)

2

General Asterisk configuration / Random second call on the line when agents are on the phone

« on: November 10, 2014, 15:31:07 »

At random, we are seeing agents get a second call while they are on the phone with a customer. The agents are on a call, look down and see that there is another call coming in. They ignore it and it rolls over to another agent after 12 seconds of not being answered.

Is there a way I can ensure that only 1 call gets sent to an agent at the time; change things so there is no possibility of a second call being sent to their extension from the queue?

Asterisk 11.7.0
Loway QueueMetrics - 14.03.3 - B: 4836 2014-04-03 13:24
O.S.: Linux - Ver: 2.6.32-220.13.1.el6.x86_64 - amd64
Endpoint: Yealink T46G

Full log shows:

Agent 1: Call IDs C-00074c7f and C-00074c82
[2014-11-01 16:04:02] VERBOSE[18895][C-00074c1c] file.c: -- Playing 'custom/XPB_Zip_2579.sl
in' (language 'en')
[2014-11-01 16:10:13] VERBOSE[8208][C-00074c7f] app_queue.c: -- Called SIP/1019
[2014-11-01 16:10:13] VERBOSE[8518][C-00074c82] app_queue.c: -- Called SIP/1019
[2014-11-01 16:10:13] VERBOSE[8208][C-00074c7f] app_queue.c: -- SIP/1019-000ccfe5 is ringing
[2014-11-01 16:10:13] VERBOSE[8518][C-00074c82] app_queue.c: -- SIP/1019-000ccfe6 is ringing
[2014-11-01 16:10:14] VERBOSE[8208][C-00074c7f] app_queue.c: -- SIP/1019-000ccfe5 answered SIP/XBET1-SIP-OUT-000ccfe1

Agent 2: Call IDs: C-00074ae8 and C-00074af5
[2014-11-01 15:57:13] VERBOSE[25617][C-00074ad3] file.c: -- Playing 'custom/XPB_Zip_2579.sl
in' (language 'en')
[2014-11-01 15:57:45] VERBOSE[27461][C-00074ae8] app_queue.c: -- Called SIP/1013
[2014-11-01 15:57:45] VERBOSE[28001][C-00074af5] app_queue.c: -- Called SIP/1013
[2014-11-01 15:57:45] VERBOSE[27461][C-00074ae8] app_queue.c: -- SIP/1013-000ccceb is ringing
[2014-11-01 15:57:45] VERBOSE[28001][C-00074af5] app_queue.c: -- SIP/1013-000cccec is ringing
[2014-11-01 15:57:46] VERBOSE[27461][C-00074ae8] app_queue.c: -- SIP/1013-000ccceb answered SIP/XBET2-SIP-OUT-0
00cccd3

3

General Asterisk configuration / Issue with Intra-company transfer (No link to call recording in Queuemetrics)

« on: September 15, 2014, 01:45:52 »

Hello,

I am trying to find a solution to an issue where a customer calls into our TFN, they dial 3 or 4 to go straight to our Touchtone / IVR system, then they transfer from Touchtone IVR back to any given queue. When the call is transferred out from the IVR to the queue, then there is no call recording available in Queuemetrics. Where there is normally a link to the .wav file listed next to "IVR Selection" in Queuemetrics call detail, looking at these calls there is no link to the recording. It seems that the file association is broken when they transfer from IVR -> queue.

For some reason it creates two call records. The wrong one gets associated with the call in QM.

An example:

CDR shows this one call as two call records: 1406921904.1213530 and 1406921904.1213531. The recording is linked to 531. When we go to look at the full log, full log has no record of 531.

[root@pbxha2 asterisk]# grep 1406921904 full
[2014-08-01 12:38:24] VERBOSE[31236][C-00073e22] pbx.c: -- Executing [s@macro-user-callerid:1] Set("Local/1142@from-queue-00031724;2", "TOUCH_MONITOR=1406921904.1213530") in new stack
[2014-08-01 12:40:28] VERBOSE[31236][C-00073e22] pbx.c: -- Executing [s@macro-user-callerid:1] Set("Local/1142@from-queue-00031724;2", "TOUCH_MONITOR=1406921904.1213530") in new stack
[2014-08-01 12:40:40] VERBOSE[31236][C-00073e22] pbx.c: -- Executing [s@macro-user-callerid:1] Set("Local/1142@from-queue-00031724;2", "TOUCH_MONITOR=1406921904.1213530") in new stack
[2014-08-01 12:40:40] VERBOSE[31236][C-00073e22] pbx.c: -- Executing [8004@ext-queues:35] QueueLog("Local/1142@from-queue-00031724;2", "8004,1406921904.1213530,NONE,DID,8774081999") in new stack

The only workaround we have found is to search for and get the call from CDR Reports in FreePBX admin. (This solution doesn't work well for our Supervisors). I need to fix things so that when a Supervisor pulls up a call detail in Queuemetrics, they can get to the file recording like normal instead of having to dig through CDR reports.

Queuemetrics info:
Software release:   Loway QueueMetrics - 14.03.3
B: 4836 2014-04-03 13:24
Operating System:   O.S.: Linux - Ver: 2.6.32-220.13.1.el6.x86_64 - amd64
Java Runtime:   Version: 1.6.0_22
Vendor: Sun Microsystems Inc.
Class Version: 50.0
Java Home: /usr/local/queuemetrics/jdk1.6.0_22/jre
System path:   /usr/local/queuemetrics/tomcat/webapps/queuemetrics/WEB-INF
Storage type:   SQL Storage (Partition: P001)
Loway TPF:   Version: TPF 229/P B:66
Language pack:   V:2014-03-31 10:20
System time:   Java Time: 2014-09-14 16:32:59
Java Time Zone: America/Los_Angeles
MySQL Time: 2014-09-14 16:32:59.0
MySQL Time is aligned with Java Time

FreePBX Admin:
PBX Firmware:   2.210.62-1
PBX Service Pack:   1.0.0.0