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

Pages: [1] 2
1
Running QueueMetrics / Weekly call answer percent?
« on: January 09, 2014, 21:49:04 »
Is there a way to get a graph of the percent of answered/unanswered calls per time unit (preferrably weekly)? I can put it in a custom time range and get the percent answered/unanswered for that whole range, and I can keep selecting different ranges, but only one at a time. Since that exists though I wonder if it means there is also a built-in way to look at averages broken out by week or month within a longer range, and I just can't find it.

2
QueueMetrics installation / Upgrade to 13.12 - Espresso failure notice
« on: December 19, 2013, 18:02:28 »
Getting "Warning: The Espresso installation failed!" on login screen after upgrading to 13.12. However I can log in fine, it still shows calls and is importing new calls, says 13.12.1 on License Page. Restarted server and error message persists. Not familiar with Espresso, what should I look for to see if anything is actually broken vs. the error message just displaying and everything being OK?

(FreePBX 2.11.0.11, filling out a ticket, just wondering if there's a quick way to see if something is truly broken or not.)

3
What do you have in extensions_queuemetrics.conf?

Code: [Select]
exten => _XXX.,n,Set(QDIALER_AGENT=Agent/${CALLERID(num)})
exten => _XXX.,n,Set(QDIALER_CHANNEL=SIP/myprovider/+1${QDIALER_NUMBER})

We're on FreePBX 2.11, which may be similar to yours, and I had to update ${CALLERID(num)} to ${FROMEXTEN} because asterisk was replacing the CALLERID variable with our outgoing phone number before the queuedial stuff was being called. As for the channel, you probably just need to add it between SIP and the number in the QDIALER_CHANNEL line. If you don't know what that is, you might it as Trunk Name under your Trunk in FreePBX.

4
That did not work, we don't have agents logged into QM while they are making calls... the queue logs from asterisk just get imported into QM. However, after looking at the 'full' asterisk logs I got it to work using ${FROMEXTEN} .... it looks like CALLERID gets set with the Agent extension but then gets set again with the business number for the outbound call before the queuedial lines try to reference it. Not sure if this is something new in this version or if we configured something different/incorrectly, but I saw that the FROMEXTEN variable was also getting set with the agent number, so I tried that and got it to store correctly.

5
Hello we have upgraded Asterisk to 11.3.0 and I'm having a minor issue with outbound calls... They are being imported into queuemetrics correctly but the agent field, instead of storing as "Agent/123" previously (where 123 was the employee's extension), they are all storing as "Agent/636xxxxxxx" where (xxxxxxx is our business phone number). Do we need to change what the QDIALER_AGENT is set to in [queuedial]?

Code: [Select]
exten => _XXX.,1,Set(QDIALER_QUEUE=q-340)
exten => _XXX.,n,Set(QDIALER_NUMBER=${EXTEN:1})
exten => _XXX.,n,Set(QDIALER_AGENT=Agent/${CALLERID(num)})
exten => _XXX.,n,Set(QDIALER_CHANNEL=SIP/VP-SIPSJC/+1${QDIALER_NUMBER})
exten => _XXX.,n,Set(QueueName=${QDIALER_QUEUE})
exten => _XXX.,n,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV,b,)
exten => _XXX.,n,Goto(qm-queuedial,s,1)

[qm-queuedial]
; We use a global variable to pass values back from the answer-detect macro.
; STATUS = U unanswered
;        = A answered    (plus CAUSECOMPLETE=C when callee hung up)
; The 'g' dial parameter must be used in order to track callee disconnecting.
; Note that we'll be using the 'h' hook in any case to do the logging when channels go down.
; We set the CDR(accountcode) for live monitoring by QM.
;
exten => s,1,NoOp()
exten => s,n,Set(CDR(accountcode)=QDIALAGI)
exten => s,n,Set(ST=${EPOCH})
exten => s,n,Set(GM=QDV-${QDIALER_AGENT})
exten => s,n,Set(GLOBAL(${GM})=U)
exten => s,n,Set(GLOBAL(${GM}ans)=0)
exten => s,n,Macro(queuelog,${ST},${UNIQUEID},${QDIALER_QUEUE},${QDIALER_AGENT},CALLOUTBOUND,,${QDIALER_NUMBER})
exten => s,n,Set(CALLERID(all)=<636xxxxxxx>)
exten => s,n,Dial(${QDIALER_CHANNEL},300,gM(queuedial-answer^${UNIQUEID}^${GM}^${QDIALER_QUEUE}^${QDIALER_AGENT}^${ST}))
exten => s,n,Set(CAUSECOMPLETE=${IF($["${DIALSTATUS}" = "ANSWER"]?C)})

6
Nevermind. User discovered that by selecting "Default" for Agent Group under Call filtering criteria (nothing was selected on the previous attempt), report showed up as expected. Not sure if a default changed with the update or if something just changed on user's screen, but it appears to be working as expected.

7
Updated to 13.04.1 last week. User trying to run custom report, getting this error after changing Call start date and Call end date (ex. 2013-02-05 and 2013-02-08) but changing/selecting nothing else:

"Alert: Error: Multiple selection criteria lead to no agent being selectable"

Is there something we need to be selecting here?

Thanks.

8
Well nevermind, seems like it kicked back on when the weekly log rotation kicked in. We've been having some other issues with this server and I don't have time to dig into it right now to figure out if it's related to QM or something else... but maybe that can be a clue if anyone else has a similar experience.

9
QM has been running great for awhile now with little maintenance, looks like we are on 12.5.1 right now. Today employees noticed there was no call data for yesterday or today. I looked and the last heartbeat was from a couple days ago... looks like the server may have barfed then. Anyway, the queue_log was still updating properly but qloaderd.log was not. I manually imported the data from the last couple days into QM with qloader.pl, but where do I need to look to get it going again? Already tried "service queuemetrics restart".

10
QueueMetrics installation / What's new for 12.02?
« on: March 21, 2012, 14:56:13 »
What's new with 12.02? yum update wants to upgrade us to 12.2.4-313 but I can't find a changelog and the latest news on the website is for 12.01.

11
Running QueueMetrics / Bug in editing Items?
« on: May 26, 2011, 20:44:20 »
Hello, may have discovered a bug when going to QA Forms > Edit Items. If an item is in use the Engagement Code field is disabled. The bug is that if you try to "Create New" item after viewing an item in use, the Engagement Code is still disabled for the new item, which means you cannot create the item. This issue is resolved by going back and viewing an item that is not in use, where the Engagement Code field is not disabled. Then when you "Create New" the Engagement Code field is no longer disabled. (Bug found on Firefox 3.x)

If you can replicate this error please at least fix it so that on "Create New" the field is not disabled no matter what you previously viewed. Ideally you could also update it so that it is always possible to change the Engagement Code, even if the item is already in forms. (Today we had a user that was setting up new items, putting them in forms, and then decided to rename one but had to take it back out of the form first)

Thanks.

12
QueueMetrics news / Re: QueueMetrics 1.7.0 released
« on: March 21, 2011, 15:13:24 »
Just upgraded from 1.6.2 and while we haven't checked out the new features yet everything seems to be working perfectly. Had to re do the license as we didn't get around to upgrading to 1.6.3 but actually all of our other customizations carried over. Thanks team!

(One minor note... the English translation on the database update wizard may want to change the verb "terminated" in the phrase that the database update was "terminated successfully..." I realize this simply a language difference, probably similar to how Spanish uses terminar as a verb for completing something, but in English "terminated" implies something was stopped early due to a problem, and "finished" is better for implying that the task completed with no problems)

13
We had a grouped queue for reports on all of our inbound queues, but I wanted to make one that included our outbound also so we could quickly see look at certain totals (I realize that some of the stats don't make much sense with both types). So I basically just cloned our existing queue and added our outbound queue to the Queue(s) list separated by | .

Everything works as expected, however I was initially confused by the "Call Flow" line which has the default choices of "Inbound calls / Outbound calls / Undefined." In general I guess this is for the single queues but I was afraid it wouldn't work for my grouped queue which has both Inbound and Outbound calls. I left it on Inbound and my report still had stats from both types, so I'm guessing that it doesn't really matter for the grouped queue but I just wanted to make sure I'm using this correctly.

14
The tavern / Re: Welcome everyone
« on: February 18, 2011, 15:41:41 »
Welcome... Just wanted to say thanks for all the help I've gotten over the last few months  :D

15
General Asterisk configuration / Re: Migrating QM to new server
« on: February 18, 2011, 15:39:28 »
Thanks! I'll let you know if I need anything else..

Pages: [1] 2