Messages

2506

QueueMetrics installation / Re: QM 1.4 and Trixbox 2.6.1

« on: May 30, 2008, 10:16:38 »

You need to install them manually - see the tutorial at http://queuemetrics.com/download/QM_TrixBox_210.pdf

2507

QueueMetrics installation / Re: QM 1.4 and Trixbox 2.6.1

« on: May 29, 2008, 11:11:47 »

That's good, thanks for letting us know the problems were solved!

2508

Running QueueMetrics / Re: Configuring Call Outcomes

« on: May 29, 2008, 10:52:52 »

1. that's the costs the analyzer module has to bear by keeping call records in an "hot area" for further updating - this slows down evertything else.
2. see #1
3. yes: if you use MySQL storage just enter a record with a timestamp that matches the beginning of the call
4. see #1 again

2509

QueueMetrics installation / Re: Main, Wrap, and Spill

« on: May 28, 2008, 11:01:40 »

QM is just a reporting packagage, so it knows nothing about how you set up your Asterisk box. It just allows for grouping together known sets of agents to make sense of reporting if you use queue penalities.

2510

QueueMetrics news / New FAQ page and new FAQ entries

« on: May 27, 2008, 15:30:32 »

We have put online a new FAQ page - the main advantage is that items are divided into topics, so it's easier to find just what you're looking for.

We also added four new FAQ entries:

- http://queuemetrics.com/faq.jsp#faq-046-protecting-queues
Explains how to use the QM security systems to make some queues private to some users.

- http://queuemetrics.com/faq.jsp#faq-045-n_agents
Explains how the "N Agents" field of the realtime page is computed.

- http://queuemetrics.com/faq.jsp#faq-044-backup
How to backup a QueueMetrics system.

- http://queuemetrics.com/faq.jsp#faq-043-configuring-vicidial
A short guide to configure ViciDial to work with QM.

2511

Running QueueMetrics / Re: wallboard page sizes

« on: May 27, 2008, 14:06:39 »

You can try making #titolo invisible as well. That should be it.

2512

Running QueueMetrics / Re: Call Reports Problem

« on: May 27, 2008, 10:34:45 »

No it's almost surely because your queue_log was rotated, so data that "used to be" there is not there anymore. See http://astrecipes.net/index.php?n=205 for a complete workaround.

2513

QueueMetrics installation / Re: Queues/Agents Questions

« on: May 27, 2008, 09:48:03 »

I think there is a basic misunderstanding here: QM is not a configuration editor for Asterisk, so calls will never take  a different path whatever you set in QM. 

The reason why QM has agent/queue associations is that such information cannot be inferred reliably from the basic queue_log when using agents.

About the icon versus a queue code, this is because in one case you have a "database" setting (this means: QM has no way to know on which queues this agent is working, as they are stored in Asterisk's DB); if an agent logs on to a specific queue, instead, the agent/queue association is shown.

Tip: use the rewriteLocalChannel option to have agents that look like Agent/264 and not local/264@from-internal

2514

General Asterisk configuration / Re: what do i need to begin running reports?

« on: May 26, 2008, 12:12:56 »

yes you should see lines appear in the queue_log when you make the call. Try posting here what you see when you send one call to an agent.
(Just one call, not the whole file )

2515

Running QueueMetrics / Re: wallboard page sizes

« on: May 24, 2008, 09:20:35 »

hmmm....  you should set the CSS element orologio to visibility: hidden or whatever that is in CSS. Do not change the HTML code because the page needs DHTML access to all of the elements.

2516

General Asterisk configuration / Re: what do i need to begin running reports?

« on: May 24, 2008, 09:13:20 »

If you run a call to that agent, do you see lines appended to your queue_log?

2517

Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup

« on: May 23, 2008, 12:01:33 »

We have developed a pure-diaplan solution that should work as a plug-in replacement for the queueDial.agi on 1.4 systems:

http://forum.queuemetrics.com/index.php?topic=261.0

Please test it and let us know how it goes.

2518

Outbound and QueueMetrics / EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution

« on: May 23, 2008, 11:56:52 »

We have been working for quite a while on a purely-dialplan solution to replace the queueDial.agi that seems to have problems with a number of 1.4 systems.

So we developed this script that targets Asterisk 1.4 and is a complete replacement of queueDial.agi:

Code: [Select]

[queuedial]
; using a global variable to pass values back from the answer-detect macro
; STATUS = U unanswered
;        = A answered
;
exten => _9XXX.,1,Set(MY_QUE=q-${EXTEN:1:3})
exten => _9XXX.,n,Set(MY_NUM=${EXTEN:4})
exten => _9XXX.,n,Set(MY_AGENT=Agent/${CALLERID(num)})
exten => _9XXX.,n,Set(MY_TECH=Zap/g0/)
exten => _9XXX.,n,NoOp,Ag: ${MY_AGENT} N: ${MY_NUM} Q: ${MY_QUE} T: ${MY_TECH}
exten => _9XXX.,n,MixMonitor(Q-${MY_QUE}-${UNIQUEID}.wav|b|)

exten => _9XXX.,n,Set(ST=${EPOCH})
exten => _9XXX.,n,Set(GM=QDIALV${MY_AGENT})
exten => _9XXX.,n,Set(GLOBAL(${GM})=U)
exten => _9XXX.,n,Set(GLOBAL(${GM}ans)=0)
exten => _9XXX.,n,System( echo "${ST}|${UNIQUEID}|${MY_QUE}|${MY_AGENT}|ENTERQUEUE|-|${MY_NUM}" >> /var/log/asterisk/queue_log )
exten => _9XXX.,n,Dial(${MY_TECH}${MY_NUM}||M(queuedial-answer^${UNIQUEID}^${GM}^${MY_QUE}^${MY_AGENT}^${ST}))

; Trapping call termination here
exten => h,1,NoOp( "Call exiting: status ${GLOBAL(${GM})} answered at: ${GLOBAL(${GM}ans)} DS: ${DIALSTATUS} HU: ${HANGUPCAUSE} "  )
exten => h,n,Goto(case-${GLOBAL(${GM})})
exten => h,n,Hangup()

; Call unanswered
exten => h,n(case-U),Set(WT=$[${EPOCH} - ${ST}])
exten => h,n,System( echo "${EPOCH}|${UNIQUEID}|${MY_QUE}|${MY_AGENT}|ABANDON|1|1|${WT}" >> /var/log/asterisk/queue_log )
exten => h,n,Hangup()

; call answered
exten => h,n(case-A),Set(WT=$[${GLOBAL(${GM}ans)} - ${ST}])
exten => h,n,Set(CT=$[${EPOCH} - ${GLOBAL(${GM}ans)}])
exten => h,n,System( echo "${EPOCH}|${UNIQUEID}|${MY_QUE}|${MY_AGENT}|COMPLETECALLER|${WT}|${CT}" >> /var/log/asterisk/queue_log )
exten => h,n,Hangup()

[macro-queuedial-answer]
; Expecting $ARG1: uniqueid of the caller channel
;           $ARG2: global variable to store the answer results
;           $ARG3: queue name
;           $ARG4: agent name
;           $ARG5: enterqueue
exten => s,1,NoOp("Macro: queuedial-answer UID:${ARG1} GR:${ARG2} Q:${ARG3} A:${ARG4} E:${ARG5}")
exten => s,n,Set(NOW=${EPOCH})
exten => s,n,Set(WD=$[${NOW} - ${ARG5}])
exten => s,n,System( echo "${NOW}|${ARG1}|${ARG3}|${ARG4}|CONNECT|${WD}" >> /var/log/asterisk/queue_log )
;exten => s,n,DumpChan()
exten => s,n,Set(GLOBAL(${ARG2})=A)
exten => s,n,Set(GLOBAL(${ARG2}ans)=${NOW})
exten => s,n,NoOp("Macro queuedial-answer terminating" )

Before telling everybody to use this, though, we would like our power-users to test this out and find any flaws that may be lingering

Known advantages over QueueDial.agi:
- Simpler setup and debugging
- No 'h' problems with calls that are not closed
- Correct tracking of answering time even for outbound (the calls stays unsnswered and then answered at the right time)
- Easier to add options (eg a timeout) to the actual DIAL commend executed

Known issues:
- The script does not distinguish whether it was the AGENT or the CALLED PARTY to hang up (anybody knows how?)
- It's for 1.4.x only
- It uses System() a number of times and not the QueueLog() app
- It uses global variables to pass values back from a different leg of the call

2519

Running QueueMetrics / Re: wallboard page sizes

« on: May 23, 2008, 11:38:51 »

At the moment column widths are in compiled-code, so they cannot be changed. Could you reduce the sreen resolution so thnat it appears larger?


 

2520

Running QueueMetrics / Re: wallboard page sizes

« on: May 23, 2008, 09:55:05 »

Can you show a screenshot of what is going on? Which browser are you running?