136
QueueMetrics installation / Re: AMI Test Status
« on: March 04, 2015, 16:23:50 »
Are QueueMetrics and the PBX on the same machine?
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.
137
QueueMetrics installation / Re: AMI Test Status
« on: March 04, 2015, 16:12:23 »
Ok, you should check that extensions_custom.conf is included from extensions.conf (usually at the end).
After that you should reload asterisk
asterisk -rx "core reload"
Mirko
After that you should reload asterisk
asterisk -rx "core reload"
Mirko
138
QueueMetrics installation / Re: AMI Test Status
« on: March 04, 2015, 15:57:41 »
In general yes; if you're using something like Elastix or FreePBX, insert it under extensions_custom.conf, since extensions.conf could be replaced after a PBX update.
Mirko
Mirko
139
QueueMetrics installation / Re: AMI Test Status
« on: March 04, 2015, 15:34:21 »
Hi,
did you include the QueueMetrics dialplan in your PBX? (You'll find it under /usr/local/queuemetrics/qm-current/WEB-INF/mysql-utils/extensions-examples/extensions_queuemetrics_18.conf
Mirko
did you include the QueueMetrics dialplan in your PBX? (You'll find it under /usr/local/queuemetrics/qm-current/WEB-INF/mysql-utils/extensions-examples/extensions_queuemetrics_18.conf
Mirko
140
QueueMetrics installation / Re: AMI Test Status
« on: March 03, 2015, 15:20:53 »
Hello iCapof,
the correct credentials are in your Asterisk machine at /etc/asterisk/manager.conf.
To modify that on the queuemetrics side, open the configuration file ("Edit system configuration") and find the callfile.dir property.
Give a look to this tutorial: https://github.com/Loway/QueueMetricsHowTos/blob/master/QueueMetricsInstall.md
Mirko
the correct credentials are in your Asterisk machine at /etc/asterisk/manager.conf.
To modify that on the queuemetrics side, open the configuration file ("Edit system configuration") and find the callfile.dir property.
Give a look to this tutorial: https://github.com/Loway/QueueMetricsHowTos/blob/master/QueueMetricsInstall.md
Mirko
141
Running QueueMetrics / Re: QM 15.02 bug fix questions
« on: March 03, 2015, 11:57:51 »
Hi Mike,
the bug tracker is not accessible outside our offices, usually we give those number as a reference for those who advised about the bug.
#2438 QueueMetrics permits duplicated fields: the configuration editor (Edit agents / queues / etc) did permit to create identical elements. Now this was corrected.
#2378 Call monitor from realtime is not enabled: there was a bug with the permissions needed to live monitor calls that has been fixed.
Kind Regards
Mirko
the bug tracker is not accessible outside our offices, usually we give those number as a reference for those who advised about the bug.
#2438 QueueMetrics permits duplicated fields: the configuration editor (Edit agents / queues / etc) did permit to create identical elements. Now this was corrected.
#2378 Call monitor from realtime is not enabled: there was a bug with the permissions needed to live monitor calls that has been fixed.
Kind Regards
Mirko
142
Running QueueMetrics / Re: cannot logon agent to queue
« on: February 26, 2015, 11:15:15 »
Yes, it looks like. Did you defined your queues in QueueMetrics?
Define the queues and run the realtime page on all the queues. You should start seeing the ongoing calls.
Mirko
Define the queues and run the realtime page on all the queues. You should start seeing the ongoing calls.
Mirko
143
Running QueueMetrics / Re: cannot logon agent to queue
« on: February 26, 2015, 11:10:44 »
I don't think that's queue_log, looks more like qloader.log 
144
Running QueueMetrics / Re: cannot logon agent to queue
« on: February 26, 2015, 11:06:26 »
You just get HEARTBEAT events?
Are you sure that asterisk is writing in /var/log/asterisk/queue_log?
Are you sure that asterisk is writing in /var/log/asterisk/queue_log?
145
Running QueueMetrics / Re: cannot logon agent to queue
« on: February 26, 2015, 09:35:03 »
Hello gustavoy,
is QueueMetrics reading correctly from queue_log, or better:
- is qloader running and writing on the db
- is queuemetrics set to read from the database?
I'd also check if the AMI connection is working.
Give a look here for more info:
https://github.com/Loway/QueueMetricsHowTos/blob/master/QueueMetricsInstall.md
Mirko
is QueueMetrics reading correctly from queue_log, or better:
- is qloader running and writing on the db
- is queuemetrics set to read from the database?
I'd also check if the AMI connection is working.
Give a look here for more info:
https://github.com/Loway/QueueMetricsHowTos/blob/master/QueueMetricsInstall.md
Mirko
146
QueueMetrics installation / Re: Asterisk 13.2.0 and QueueMetrics
« on: February 19, 2015, 09:26:59 »
Hi iCapof,
actually the current version of QueueMetrics it's not compatible (new AMI version), it will be supported in the next release of QueueMetrics, 15.02, released next week.
Kind Regards
Mirko
actually the current version of QueueMetrics it's not compatible (new AMI version), it will be supported in the next release of QueueMetrics, 15.02, released next week.
Kind Regards
Mirko
147
Running QueueMetrics / Re: Cluster and call recordings.
« on: January 28, 2015, 09:40:37 »
Hi Tom,
you should specify also the audioRpcServer field.
cluster.server1.audioRpcServer=
cluster.server2.audioRpcServer=
Probably the same you haave in default.audioRpcServer, otherwise give a look here for details: http://manuals.loway.ch/QM_UserManual-chunked/ch22.html
The one for you should be it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay; also if the recordings are divided by day you can set year, month, day variables in the path in order to make the search way faster, especially with remote mounts:
example:
cluster.server1.monitored_calls=/mnt/server1/%YY/%MM/%DD
%YY → the 4-digit year when the call was made
%MM → the 2-digit month when the call was made
%DD → the 2-digit day of month when the call was made
%SE → in a clustered environment, the server name (all lower case)
%QU → the queue name (all lower case)
you should specify also the audioRpcServer field.
cluster.server1.audioRpcServer=
cluster.server2.audioRpcServer=
Probably the same you haave in default.audioRpcServer, otherwise give a look here for details: http://manuals.loway.ch/QM_UserManual-chunked/ch22.html
The one for you should be it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay; also if the recordings are divided by day you can set year, month, day variables in the path in order to make the search way faster, especially with remote mounts:
example:
cluster.server1.monitored_calls=/mnt/server1/%YY/%MM/%DD
%YY → the 4-digit year when the call was made
%MM → the 2-digit month when the call was made
%DD → the 2-digit day of month when the call was made
%SE → in a clustered environment, the server name (all lower case)
%QU → the queue name (all lower case)
148
Running QueueMetrics / Re: Icon Agent Page Not Working
« on: January 27, 2015, 11:03:53 »
Hi, the softphone is still a beta feature (not every browser supports WebRTC), you can find here setup tutorials and compatibility: https://github.com/Loway/QueueMetricsHowTos
Mirko
Mirko
149
General Asterisk configuration / Re: Display all rows in reports
« on: January 26, 2015, 18:10:00 »
Hi zmohammad,
you should go to "Edit Reports", and replace the two reports (Answered details and Unanswered details) with their non-paged alternatives (replace OD03 with OD01 and UD02 with UD01).
Kind Regards
Mirko
you should go to "Edit Reports", and replace the two reports (Answered details and Unanswered details) with their non-paged alternatives (replace OD03 with OD01 and UD02 with UD01).
Kind Regards
Mirko
150
Scripting QueueMetrics / Re: JSON DetailsDO.CallsOK
« on: January 26, 2015, 09:27:00 »
Hi Stewart,
are you sure that when you run the report on QueueMetrics you don't have different filters set? Do try with a custom report.
Mirko
are you sure that when you run the report on QueueMetrics you don't have different filters set? Do try with a custom report.
Mirko