Messages

1

Running QueueMetrics / Re: Auto generate/email reports failing

« on: January 12, 2010, 20:16:38 »

On Gentoo, I'm using  net-misc/wget-1.11.3 USE="ssl -debug -ipv6* -nls* -socks5 -static".

2

Running QueueMetrics / Re: Auto generate/email reports failing

« on: December 29, 2009, 20:43:34 »

I tried it again, removed the -p switch. That seems to have fixed it.

New code:

Code: [Select]

wget -nH -k -K -l 1 -O report.html "$QM_SERVER/$QM_WEBAPP/qm_rep.do?user=$QM_USER&pass=$QM_PASS&queues=$QM_QUEUE&period=$QM_PERIOD"

3

Realtime Live / Re: Robot AJAX Realtime Login

« on: December 28, 2009, 19:02:07 »

Thanks for the update Marco! I look forward to seeing 1.5.6 released.

4

Running QueueMetrics / Auto generate/email reports failing

« on: December 28, 2009, 18:53:21 »

Using the instructions in the FAQ:  http://queuemetrics.com/faq.jsp#faq-063-printing_pdf

I am getting an error with this script regarding the wget command:

Code: [Select]

Cannot specify both -k and -O if multiple URLs are given, or in combination with -p or -r. See the manual for details.
Any ideas on how to make this work? BTW, I'm using Gentoo and have htmldoc and nail emerged.

5

Running QueueMetrics / Re: Old data still showing in reports

« on: December 14, 2009, 15:19:53 »

Upon second check, you are correct. There was a leftover line the queue_log that threw off the agent data. I removed it from the queue_log and the corresponding SQL table. All is fixed. Thanks! 

6

Running QueueMetrics / Old data still showing in reports

« on: December 11, 2009, 19:42:06 »

Before going live with my QM install, I cleared the the file /var/log/asterisk/queue_log and the queue_log table in MySQL. However, when I run reports, specifically on Agent Availabilty, I see old data included 100+ hours of login time when the 'live' operation hasn't even been up that long. How can I truncate the data to show only the relevant data since going live?

7

Realtime Live / Re: Robot AJAX Realtime Login

« on: December 11, 2009, 19:40:02 »

There are four realtime options now:

Start realtime monitoring
Start realtime monitoring (AJAX)
Start wallboard
Start wallboard (AJAX)

Running http://server:8080/queuemetrics/qm_wab.do?user=robot&pass=xxx&reloads=1&queues=00-All will show Realtime Monitoring using the robot login. What would the URLs be to access Realtime Monitoring (AJAX) and Wallboard (AJAX) using the robot login? Thanks!

8

Realtime Live / Re: Robot AJAX Realtime Login

« on: December 08, 2009, 20:19:40 »

The blocks? When I navigate to that page, there is no AJAX involved. How can I utilize the new features with the robot login?

9

Realtime Live / Robot AJAX Realtime Login

« on: December 03, 2009, 16:53:22 »

I know you can use http://server:8080/queuemetrics/qm_wab.do?user=robot&pass=xxx&reloads=1&queues=00-All for the 'old' realtime page. What would the URL be for the new AJAX realtime page?

10

Outbound and QueueMetrics / Re: Using IVR code to track outgoing

« on: December 01, 2009, 17:19:35 »

Perfect!! Thanks for the assistance! 

11

Outbound and QueueMetrics / Re: Using IVR code to track outgoing

« on: December 01, 2009, 16:39:09 »

There is no Goto in start:

Code: [Select]

exten => s,1,NoOp,Outbound call -> A:${QDIALER_AGENT} N:${QDIALER_NUMBER} Q:${QDIALER_QUEUE} Ch:${QDIALER_CHANNEL}
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},IVR|${IVR})
exten => s,n,Dial(${QDIALER_CHANNEL},30,gM(queuedial-answer^${UNIQUEID}^${GM}^${QDIALER_QUEUE}^${QDIALER_AGENT}^${ST}))
exten => s,n,Set(CAUSECOMPLETE=${IF($["${DIALSTATUS}" = "ANSWER"]?C)})


12

Outbound and QueueMetrics / Re: Using IVR code to track outgoing

« on: December 01, 2009, 14:50:03 »

Because all of my incoming calls have an IVR tag. If the outgoing calls do not, they are confusingly marked in QM as Untracked.

13

Outbound and QueueMetrics / Using IVR code to track outgoing

« on: November 19, 2009, 16:04:32 »

I have successfully setup IVR tracking for inbound calls:

Code: [Select]

QueueLog(incoming-q,${UNIQUEID},NONE,INFO,IVR|${IVR})
And I'm using the default qm-queuedial context for outbound calls. How can I insert an IVR code 'outgoing' for all outbound calls?

Here's what I tried (it shows Untracked in the IVR detail in QM):

Code: [Select]

exten => s,n,Macro(queuelog,${ST},${UNIQUEID},${QDIALER_QUEUE},${QDIALER_AGENT},CALLOUTBOUND,-,${QDIALER_NUMBER},IVR|${IVR})


-- Executing [s@qm-queuedial:7] Macro("SIP/NOC1-f6819b48", "queuelog|1258642605|1258642605.151|outgoing-q|413|CALLOUTBOUND|-|4077828790|IVR|Outgoing") in new stack
-- Executing [s@macro-queuelog:1] QueueLog("SIP/NOC1-f6819b48", "outgoing-q|1258642605.151|413|CALLOUTBOUND|-|4077828790|IVR") in new stack

It cuts off the actual IVR selection in the QueueLog command. How shall I restructure this?

14

Running QueueMetrics / Re: Handled By displays different name in QM

« on: November 12, 2009, 14:37:07 »

That did it...thanks!! 

15

Running QueueMetrics / Re: Handled By displays different name in QM

« on: November 11, 2009, 18:18:00 »

Well, why is Asterisk logging the user name instead of the agent number? Here is my Agent Login:

Code: [Select]

exten => _4XXX,1,Answer
exten => _4XXX,n,Set(CALLBACKNUM=${CALLERID(num)})
exten => _4XXX,n,Set(AGENTCODE=${EXTEN:1})
exten => _4XXX,n,NoOp( "QM: Logging on Agent/${AGENTCODE} to extension ${CALLBACKNUM}@from-internal" )
exten => _4XXX,n,AgentCallbackLogin(${AGENTCODE}||${CALLBACKNUM}@from-internal)
exten => _4XXX,n,Hangup

nocvoip*CLI> agent show
413          (Chris Ryan) available at '6025150990@from-internal' (musiconhold is 'default')