QueueMetrics forum
QueueMetrics => MySQL storage and Qloaderd/Uniloader => Topic started by: blackgecko on June 21, 2012, 01:45:50
-
Im installing a test setup this is the scenario.
Slackware Linux running Asterisk 1.8.7.1
qloader 1.27 installed and running and uploading data correctly
Centos 5.6
Queuemetrics 12.5.1 installed via yum
modified configuration.properties
"default.queue_log_file=sql:P001"
"cluster.servers=testsrv|trix"
"cluster.testsrv.manager=tcp:queuemetrics:*****@172.XXX.XXX.XXX"
I can check Mysql Storage Information and i can see info uploaded
Partition Entries N. calls From: To: Days of data: Last heartbeat:
P001 1 0 2012-06-20 06:02 2012-06-20 06:02 0,0 days 2012-06-20 06:02
i can run the setup wizard and i get my queue config from asterisk, so i think manager conection is working
I log in as an agent and when i try to logon to the queue
it has a dropdown menu to select server wich is blank
agent´s code already with the agent code
and current extension where i put the extension im at.
but when i click the run button i get this error
QueueMetrics cannot send the command to the PBX.
so im stuck at this point.
Any help about this ?
-
After lots of research ive found that you need to configure the AMI parameter in configuration.properties
callfile.dir=tcp:queuemetrics:*****@172.XXX.XXX.XXX
now it is working i just had one problem with the time queuemetrics report
configuration.properties
#The default time zone offset. Valid values -24...24 hours
default.timeZoneOffset=0
qloader.pl
my $timezone_offset = -5 * 3600; # in seconds
cause whe are in mexico city.
session of agent from 06/21 - 11:00:58 06/21 - 11:03:00 is reported as 06/21 - 06:00:58 06/21 - 06:03:00
once i changed back to
qloader.pl
my $timezone_offset = 0 * 3600; # in seconds
everything is being reported as it should.
hope this is usefull to someone.
-
I am having this same issue here. I am running on CentOS 5.8 and QM version 12.10.1. We have PBXact installed on a separate server. The PBX has for the firmware, it is : 10.818.210.57-2 and the Service Pack is: 1.0.0.24.
I have updated the config file to point to the PBX server, and restart services, however I am still receiving this error message.
Any help or ideas will be greatly appreciated.
-
What is the error msg you are having?
Did you try the connection tester?
-
I have looked and have been unable to locate a connection tester.
For the error, when I log in as a test agent, I click on "Show inbound calls for agent xxxx". I then click on Join Q, and select the Q I wish to join. When I do that I get the error, "QueueMetrics cannot send the command to the PBX."
I also did some digging and noticed on my PBX server, it is trying to access the MySQL database on that server instead of the actual QueueMetrics server. The file I was using was /var/log/asterisk/qloaderd.log
-
See Using the DbTest Diagnostic Tools on page 175 of the User Manual
-
Ok, just an update, I have resolved the issue with qloader being able to talk to the MySQL database. What we are seeing now is that QM is seeing the queues on Asterisk and when calls come in. However, it is not seeing any agents being logged in through QM. I can have up real-time monitoring and see the queue there and the call on hold for that queue, and no agents available. I can log-in on another browser with the agent that I created and join that agent to the queue. Unfortunately QM does not add the agent to that queue, even though it said that the requested action was performed.
For the connection tester, it shows calls coming in, and the queues that they are going to, however it doesn't show any agents listed. This is the same data that I see when looking at the MySQL database.
-
I went ahead and ran an AMI test and this was the information it returned:
AMI URL: tcp:queuemetrics:javadude@172.20.0.11:5038
ERR Originate failed. You may miss 'originate' privilege on Asterisk 1.6+ or you do not have extension 10@queuemetrics
Not found: 37@queuemetrics
ERR callfile.agentremovemember_ht not found Local/37@queuemetrics/n / 10@queuemetrics
Not found: 35@queuemetrics
ERR callfile.agentaddmember_ht not found Local/35@queuemetrics/n / 10@queuemetrics
Skipping check for $EM@from-internal
Not found: 11@queuemetrics
ERR callfile.monitoring not found Local/$EM@from-internal/n / 11@queuemetrics
Skipping check for $EM@from-internal
Not found: 28@queuemetrics
ERR callfile.customdial not found Local/$EM@from-internal/n / 28@queuemetrics
Not found: 33@queuemetrics
ERR callfile.agentunpause_ht not found Local/33@queuemetrics/n / 10@queuemetrics
Skipping check for $EM@from-internal
Not found: 14@queuemetrics
ERR callfile.outmonitoring not found Local/$EM@from-internal/n / 14@queuemetrics
Not found: 23@queuemetrics
ERR callfile.agentunpause not found Local/23@queuemetrics/n / 10@queuemetrics
Not found: 32@queuemetrics
ERR callfile.agentpause_ht not found Local/32@queuemetrics/n / 10@queuemetrics
Not found: 12@queuemetrics
ERR callfile.calloutcome not found Local/12@queuemetrics/n / 10@queuemetrics
Not found: 25@queuemetrics
ERR callfile.agentaddmember not found Local/25@queuemetrics/n / 10@queuemetrics
Not found: 27@queuemetrics
ERR callfile.agentremovemember not found Local/27@queuemetrics/n / 10@queuemetrics
Not found: 22@queuemetrics
ERR callfile.agentpause not found Local/22@queuemetrics/n / 10@queuemetrics
Not found: 10@queuemetrics
ERR callfile.transfercall not found Local/10@queuemetrics/n / 31@queuemetrics
OK Asterisk dialog was OK
AMI Dialog took 9905 ms
-
Here is the information from the DB connection tester:
01/16 - 12:19:20 1358360360 NONE NONE NONE HEARTBEAT
01/16 - 12:04:19 1358359459 NONE NONE NONE HEARTBEAT
01/16 - 11:40:42 1358358042 NONE NONE NONE HEARTBEAT
01/16 - 10:48:26 1358354906 1358354903.9 999 NONE ABANDON 1 1 3
01/16 - 10:48:23 1358354903 1358354903.9 999 NONE DID 254299****
01/16 - 10:48:23 1358354903 1358354903.9 999 NONE ENTERQUEUE 254227**** 1
01/16 - 10:28:02 1358353682 1358353665.8 999 NONE ABANDON 1 1 17
01/16 - 10:27:45 1358353665 1358353665.8 999 NONE DID 254299****
01/16 - 10:27:45 1358353665 1358353665.8 999 NONE ENTERQUEUE 254227**** 1
01/16 - 10:23:02 1358353382 1358353350.7 999 NONE ABANDON 1 1 32
01/16 - 10:22:30 1358353350 1358353350.7 999 NONE DID 254299****
01/16 - 10:22:30 1358353350 1358353350.7 999 NONE ENTERQUEUE 254227**** 1
01/16 - 10:21:49 1358353309 1358353286.6 999 NONE ABANDON 1 1 22
01/16 - 10:21:27 1358353287 1358353286.6 999 NONE DID 254299****
01/16 - 10:21:27 1358353287 1358353286.6 999 NONE ENTERQUEUE 254227**** 1
01/16 - 09:48:28 1358351308 1358351184.5 999 NONE ABANDON 1 1 124
01/16 - 09:46:24 1358351184 1358351184.5 999 NONE DID 254299****
01/16 - 09:46:24 1358351184 1358351184.5 999 NONE ENTERQUEUE 512284**** 1
01/16 - 09:46:19 1358351179 NONE NONE NONE CONFIGRELOAD
01/16 - 09:45:46 1358351146 NONE NONE NONE CONFIGRELOAD
01/16 - 09:45:05 1358351105 NONE NONE NONE CONFIGRELOAD
01/16 - 09:44:56 1358351096 NONE NONE NONE CONFIGRELOAD
01/16 - 09:43:57 1358351037 NONE NONE NONE QUEUESTART
01/16 - 09:43:57 1358351037 NONE NONE NONE CONFIGRELOAD
01/16 - 08:03:37 1358345017 NONE NONE NONE CONFIGRELOAD
01/16 - 04:02:13 1358330533 NONE NONE NONE QUEUESTART
01/16 - 04:02:13 1358330533 NONE NONE NONE CONFIGRELOAD
-
I went ahead and ran an AMI test and this was the information it returned:
AMI URL: tcp:queuemetrics:javadude@172.20.0.11:5038
ERR Originate failed. You may miss 'originate' privilege on Asterisk 1.6+ or you do not have extension 10@queuemetrics
Not found: 37@queuemetrics
OK Asterisk dialog was OK
AMI Dialog took 9905 ms
I guess you did not include the extensions_queuemetrics dialplan?
-
I am having an issue similar here. I got everything configured, I imported the extensions_queuemetrics.conf to the remote server, I pass all test but I cant still login the agent on the remote server. I did notice that I do not have a callfile.dir configured for my remote server, only for the local server.
-
Hi Luiz,
when you send a command do you see anything happening in Asterisk?
-
I see the command running on the local server where asterisk and quemetrics are installed, but it never gets to the remote server where the agent is trying to login. Here is my setup, server test1 has elastix and queuemetrics installed with queue 600, remote server, test2, has qloader installed and it is reporting back to the test1 server, has queue 800 an ext 1000, agent is trying to login to queue 800 sitting at ext 1000, agent is logging in to queuemetrics on test1 server.
-
Did you configure the AMI connection to the remote server? are you using a cluster?
-
Yes, I can connect to the AMI on the remote server and I am using a cluster. I've pasted the cluster part of my configuration.properties.
# This is the default queue log file.
default.queue_log_file=sql:cluster:*
# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API
cluster.servers=test2|test1
cluster.test2.manager=tcp:admin:mysuperpassword@192.168.2.208
cluster.test2.queuelog=sql:P002
cluster.test2.monitored_calls=/var/spool/asterisk/monitor/
cluster.test2.callfile.dir=
cluster.test2.audioRpcServer=
cluster.test2.agentSecurityKey=
cluster.test1.manager=tcp:admin:mysuperpassword@127.0.0.1
cluster.test1.queuelog=sql:P001
cluster.test1.monitored_calls=/var/spool/asterisk/monitor/
cluster.test1.callfile.dir=
cluster.test1.audioRpcServer=
cluster.test1.agentSecurityKey=
-
The config looks correct.
Are you sure that your agents are choosing the right server when logging in?
-
When the agent goes to login, they have no option to choose the server. It only give the agent the option for their agent number, extension number and the queue they are logging in to.
-
In cluster mode, the agent's page should display a selector so they can choose where to log in to.
-
Would you be able to send me a working configuration.properties file? I dont see anywhere on my agent's page where they can select the server.
Thank you
-
Update: I am able to login to the remote server only if i add the tcp AMI connection setting to the following line.
#callFile spool dir, set to blank for no call files at all or use TCP AMI connection
callfile.dir=
This is not the line under the cluster section. If I leave this line empty I get an error message on queuemetrics and I can't find a way to add both server AMI configuration.
-
This is weird. I'll open up a bug for this.
Bug #1839
-
Thank you, Do you have a bug tracker page? So I can track the progress in this case. This feature is extremely important for us, and my demo license is about to expire.
-
Hi Luiz,
we don't verify your issue.
With the following settings:
# This is the default queue log file.
default.queue_log_file=cluster:*
#callFile spool dir, set to blank for no call files at all or use TCP AMI connection
callfile.dir=tcp:admin:amp111@127.0.0.1
# Cluster to poll for RT data
# list of pipe-separated members of the cluster
# if callfilesdir = "", the commands will be sent through the manager API
cluster.servers=aleph|trix
cluster.aleph.manager=tcp:admin:amp111@127.0.0.1
cluster.aleph.queuelog=sql:P001
cluster.aleph.monitored_calls=
cluster.aleph.callfilesdir=
cluster.aleph.audioRpcServer=
cluster.aleph.agentSecurityKey=
cluster.trix.manager=tcp:admin:amp111@127.0.0.1
cluster.trix.queuelog=sql:P002
cluster.trix.monitored_calls=z:/qm_streamcall/server_trix
cluster.trix.callfilesdir=
cluster.trix.audioRpcServer=
cluster.trix.agentSecurityKey=
I get the drop-down server selection. What matters here is the "cluster:*" that tells the agent page to ask for a selector.
We are marking bug #1839 as "not verified" for now, pending further input.
-
Thank you, Do you have a bug tracker page? So I can track the progress in this case. This feature is extremely important for us, and my demo license is about to expire.
Please ask for a renewal to our support line. We want you to be happy with the product.
-
Solved.
Thank you I was able to get it to work. Under this line default.queue_log_file=cluster:*, I had wrong information there, I had default.queue_log_file=sql:cluster:*
-
That was a hard find :)