2176
QueueMetrics installation / Re: No Reports on "Unanswered Call"
« on: January 09, 2009, 09:57:06 »
Are you filtering by agent? can you post a screenshot?
QueueMetrics professional call center suite for the Asterisk PBX
News:
Welcome to the new forum!
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.
2177
QueueMetrics installation / Re: Multiple Sequential queues
« on: January 09, 2009, 09:55:38 »
Yes, this is in fact pretty easy to do.
Imagine that your queues are called q1, q2 .... to q5.
First you create a report-all queue in QM, with a composition of q1|q2|q3|q4|q5.
Then you run a report for it, enabling multi-stint mode.
This will give you a report as if all queues were a single one, with correct waiting time (from the start).
You can then drill down by turing off reports for multi-.stint mode and reporting on each stint separately (to see e.g. how many calls were answred in q3 and how many went through to q4).
Imagine that your queues are called q1, q2 .... to q5.
First you create a report-all queue in QM, with a composition of q1|q2|q3|q4|q5.
Then you run a report for it, enabling multi-stint mode.
This will give you a report as if all queues were a single one, with correct waiting time (from the start).
You can then drill down by turing off reports for multi-.stint mode and reporting on each stint separately (to see e.g. how many calls were answred in q3 and how many went through to q4).
2178
Outbound and QueueMetrics / Re: Outbound and Druid
« on: January 06, 2009, 18:16:43 »
I think you don't really need all that stuff.
I would intercept the:
exten=>_XXXXXXXXXX,n,Macro(ael-druid-trunkdial,SIP/ipcomms,${EXTEN},WTK,,,,,${EXTEN})
and change that to
You have to make sure that the original QM dialplan is included.
I would intercept the:
exten=>_XXXXXXXXXX,n,Macro(ael-druid-trunkdial,SIP/ipcomms,${EXTEN},WTK,,,,,${EXTEN})
and change that to
Code: [Select]
exten =>_XXXXXXXXXX,1,Set(QDIALER_QUEUE=q-999)
exten => _XXXXXXXXXX,n,Set(QDIALER_NUMBER=1${EXTEN})
exten => _XXXXXXXXXX.,n,Set(QDIALER_AGENT=Agent/${CALLERID(num)})
exten => _XXXXXXXXXX,n,Set(QDIALER_CHANNEL=SIP/trunk-name/${QDIALER_NUMBER})
exten => _XXXXXXXXXX,n,Set(QueueName=${QDIALER_QUEUE})
exten => _XXXXXXXXXX,n,MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV|b|)
exten => _XXXXXXXXXX,n,Goto(qm-queuedial,s,1)
You have to make sure that the original QM dialplan is included.
2179
Translations / It's never been easier to translate QueueMetrics!
« on: January 05, 2009, 16:28:56 »
We now have a new, easier way to translate our product. This will make it easier to complete translations and to check that they're actually working and how they look like in the final product (no more encoding problems!).
This is based on a web translation portal called PolyVox.
You can find the new documentation here: http://queuemetrics.com/download/QM_TranslatorManual_v200.pdf
If you want to correct an existing translation or create a completely new translation for QueueMetrics, please get in touch with us to have credentials issued to you.
This is based on a web translation portal called PolyVox.
You can find the new documentation here: http://queuemetrics.com/download/QM_TranslatorManual_v200.pdf
If you want to correct an existing translation or create a completely new translation for QueueMetrics, please get in touch with us to have credentials issued to you.
2180
QueueMetrics installation / "Statement GeneratedKeysNotRequested" error
« on: January 05, 2009, 09:54:27 »
If you installed QueueMetrics manually with a MySQL Connector/J version 5.x, you may have stumbled into the error:
The error appears when QM inserts a new row, e.g. by creating a new agent or a new queue.
This issue has been fixed for the next major release; if you are encountering it, just use a Connector/J version 3 for the moment.
http://dev.mysql.com/downloads/connector/j/3.0.html
Code: [Select]
Errore tecnico nella classe 'it.loway.app.queuemetrics.configurazione.cfg2.ptQueues'.
-- Inner Exception --
- Exception: it.loway.tpf.common.exceptions.TechException
- Stack trace:
- Problema update DB: java.sql.SQLException: !Statement.GeneratedKeysNotRequested!
The error appears when QM inserts a new row, e.g. by creating a new agent or a new queue.
This issue has been fixed for the next major release; if you are encountering it, just use a Connector/J version 3 for the moment.
http://dev.mysql.com/downloads/connector/j/3.0.html
2181
QueueMetrics installation / Re: Queuemetrics Migration to another machine
« on: January 05, 2009, 09:46:36 »
No that's in the QM database. If you have the queue configuration you should have the supervisor passwords as well - they live in the same database.
2182
Running QueueMetrics / Re: Information discrepancy between two reports...
« on: December 31, 2008, 11:51:30 »
It's two distinct pieces of information:
- the total number of calls taken is 176.
- the number of "attempts" seen in the log to ring the agent is lower. This means that the attempt logging is somewhat incomplete (attempts are not logged for every call). Anyway you care about attempts as much as they show "lost" attempts, so it's not a big problem. I think that version 1.5. should have a logic in the analyzer to assume an attempt event if it's not logged.
- the total number of calls taken is 176.
- the number of "attempts" seen in the log to ring the agent is lower. This means that the attempt logging is somewhat incomplete (attempts are not logged for every call). Anyway you care about attempts as much as they show "lost" attempts, so it's not a big problem. I think that version 1.5. should have a logic in the analyzer to assume an attempt event if it's not logged.
2183
Improving QueueMetrics / Re: Agent Login Data
« on: December 30, 2008, 18:08:44 »
So you basicvally would like a report per user session, that is, once per each login?
2184
QueueMetrics installation / Re: Queuemetrics Migration to another machine
« on: December 29, 2008, 21:00:48 »
About the licence, the same one will do. Not ethat you cannot run QM on two servers at the same time with the same licence.
You should backup:
- the queue_log file. Just create it twith the right perimissions before starting Asterisk on the new box
- the configuration.properties file and the web.xml file (so you have the licence)
- all the MySQL database
Nothing else is needed.
You should backup:
- the queue_log file. Just create it twith the right perimissions before starting Asterisk on the new box
- the configuration.properties file and the web.xml file (so you have the licence)
- all the MySQL database
Nothing else is needed.
2185
QueueMetrics installation / Re: yum Instalation 1.5.0 OK, but unable to access...
« on: December 29, 2008, 20:58:31 »
Thanks. We'll add it to the FAQ.
2186
Running QueueMetrics / Re: Logon/off and pause/unpause malfunction
« on: December 24, 2008, 11:35:47 »
I am not sure I understand what you mean with "prompting", can you post a screenshot?
2187
QueueMetrics installation / Re: yum Instalation 1.5.0 OK, but unable to access...
« on: December 24, 2008, 11:34:52 »
There must be something else attached to the default port 8080.
Try this
To see its actual line:
If you have some other program on port 8080, turn it off and restart QueueMetrics.
If there is nothing else on port 8080, try disabling iptables; if it's actually iptables, you should create a rule for QM.
Try this
Code: [Select]
[root@server ~]# lsof -i -P -n | grep 8080
java 2205 root 5u IPv6 5825 TCP *:8080 (LISTEN)
In this case we have a Java process whose PID is 2205.To see its actual line:
Code: [Select]
[root@server ~]# ps -fp 2205
UID PID PPID C STIME TTY TIME CMD
root 2205 1 0 Nov28 ? 00:26:35 /usr/local/queuemetrics/java/bin/java -Xms128M -Xmx128M -Djava.endorsed....If you have some other program on port 8080, turn it off and restart QueueMetrics.
If there is nothing else on port 8080, try disabling iptables; if it's actually iptables, you should create a rule for QM.
2188
Outbound and QueueMetrics / Re: outbound calls not working if logged in via QM
« on: December 23, 2008, 09:03:34 »
The problem seems to be here:
This does not seem to work when you logged in from QM, so that you get an empty Agent string (?).
You can use a workaround for this by changing the detection logic and not using Asterisk's built-ins, like for example here: http://queuemetrics.com/faq.jsp#faq-038-agent_tracking
I would really like to know how comes that the AGENTBYCALLERID variable is not set, or if it's the ${CALLERID(num)} that is failing...
Code: [Select]
exten => _XXX.,n,Set(QDIALER_AGENT=Agent/${AGENTBYCALLERID_${CALLERID(num)}})This does not seem to work when you logged in from QM, so that you get an empty Agent string (?).
You can use a workaround for this by changing the detection logic and not using Asterisk's built-ins, like for example here: http://queuemetrics.com/faq.jsp#faq-038-agent_tracking
I would really like to know how comes that the AGENTBYCALLERID variable is not set, or if it's the ${CALLERID(num)} that is failing...
2189
Running QueueMetrics / Re: Call routing on Queues
« on: December 22, 2008, 15:26:14 »
Setting options in QM has nothing to do with Asterisk call distribution, it'0s just used when displaying data. So this makes ense.
On the other side, I find it strange that call priorities don't work. They are pretty old in Asterisk, and they have always worked. What I'0 thinking of is that if you have a temporary problem with an agent's telephone (or the agent is busy on a different queue) then the first "stratum" is complete and Asterisk stries the second.
On the other side, I find it strange that call priorities don't work. They are pretty old in Asterisk, and they have always worked. What I'0 thinking of is that if you have a temporary problem with an agent's telephone (or the agent is busy on a different queue) then the first "stratum" is complete and Asterisk stries the second.
2190
QueueMetrics news / Winter break
« on: December 22, 2008, 09:39:30 »
The offices at Loway will be closed for the Winter break from 13.00 CEST of December 24, 2008 to January 2nd, 2009. Priority Support will be available by email.
Season's greeting to everyone!
Season's greeting to everyone!