Messages

31

General Asterisk configuration / Re: Hotdesking with member penalties

« on: January 10, 2011, 14:39:07 »

Hello Cursor.

This is, effectively, a bug. It's filled as 1233 in our bug tracker and it will be solved for next QM release.
Thank you and regards.

Marco.

32

MySQL storage and Qloaderd/Uniloader / Re: database maintenance

« on: January 10, 2011, 12:40:35 »

Hi,

No. We don't provide any external tool able to archive old database logs.
What I can suggest is to move and/or drop the queue_log and qa_data tables through any sort of MySQL administration tool.
The qa_data contains information related to QA activities so it could be empty if you don't use this feature.

Thank you and regards,
Marco.

33

MySQL storage and Qloaderd/Uniloader / Re: QueueMetrics bug that has something to do with a Connector/J auto-created union

« on: January 10, 2011, 12:33:48 »

Hi Alex.

Thank you for the valuable information provided.
I can confirm that we fixed the problem with QueueMetrics and that will be present since next QueueMetrics 1.7 version.
I've tested the next coming QueueMetrics 1.7. with MySQL 5.5.8 and seems working fine.

Thank you again.
Marco.

34

MySQL storage and Qloaderd/Uniloader / Re: QueueMetrics bug that has something to do with a Connector/J auto-created union

« on: January 04, 2011, 17:47:42 »

Hi Alex.

Thanks for opening this thread and to the information you provided. I was able to replicate the problem with a debug machine and, effectively, there are some queries that are not working with the latest MySQL server (5.5..
I've opened a bug in our bug tracker and it will be fixed as soon as possible.

In the meantime I suggest you, if possible, to use an old SQL server engine. We tested with 5.1.41 and all seems working fine.

Marco.

35

MySQL storage and Qloaderd/Uniloader / Re: QueueMetrics bug that has something to do with a Connector/J auto-created union

« on: January 03, 2011, 12:47:48 »

Hi Alex.

I'm trying to replicate here the problem installing MySQL 5.5.8 on a Windows debug machine.
Just one question to better understand your environment: did you installed QueueMetrics 1.6.3 from scratch or it was an upgrade of a previous QM version?

Thank you and regards,

Marco.

36

Outbound and QueueMetrics / Re: Can't get Outbound working with Asterisk 1.4

« on: January 03, 2011, 12:32:56 »

Hi

Are you using trixbox/freebpx? I think yes reading the reported logs.
This probably could helps you: http://www.queuemetrics.com/manuals/QM_Trixbox-chunked/ar01s03.html

The main idea is to generate an outbound route that forward the outbound call to the queuedial context defined in the extension_queuemetrics.conf
You need to customize it a little bit following what is explained in the document provided at the link above.

Let me know if this could helps.

Regards,
Marco.

37

Running QueueMetrics / Re: ERR:Could not download dialplan. You may have to set grant 'config'

« on: January 03, 2011, 12:15:27 »

Hello,

Do you have the config key in the manager.conf file?
In order to be able to run AMI tester properly, the user that access to asterisk through AMI should have the grant "config" enabled.
You can do that modifying the file manager.conf in the asterisk configuration folder then restart asterisk.
Assuming "admin" is the username used by QueueMetrics to access asterisk through AMI you should have something like:

;
; Asterisk Call Management support
;
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

[admin]
secret = yourpasswordhere
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,user,config,originate
write = system,call,log,verbose,command,agent,user,config,originate

Thanks.
Marco.

38

Running QueueMetrics / Re: Agent not getting added to the selected queue

« on: January 03, 2011, 12:06:15 »

Hi,

We need more details to understand the problem.
When are you saying "my selection is not saved into the queue setup" are you telling that checkboxes associated to agents in the queue member list are not saved as expected?
What browser are you using?
Did you tryed to flush the browser cache?

Thanks.

39

Running QueueMetrics / Re: Vicidial y Queuemetrics.

« on: January 03, 2011, 11:15:19 »

Hi.

I'm just reading your first post and I've found something strange:

cluster.servers=pixies|mudhoney

cluster.mudhoney.manager=tcp:usuario:clave@10.0.50.14
#cluster.mudhoney.queuelog=sql:VIC
cluster.mudhoney.queuelog=sql:PO1
cluster.mudhoney.monitored_calls=z:/qm_streamcall/server_mudhoney
cluster.mudhoney.callfilesdir=/media/mudhoney/monitor
cluster.mudhoney.audioRpcServer=
cluster.mudhoney.agentSecurityKey=

What I'm reading is that the cluster.mudhoney.queuelog key is set to sql:PO1 ... where O is an O not a zero...
Could be that the problem?

Thanks,
Marco.

40

General Asterisk configuration / Re: Hotdesking with member penalties

« on: January 03, 2011, 11:00:40 »

Hi,

This feature populates two new channel variables ${QM_AGENT_PRIOLBL} and ${QM_AGENT_PRIONUM} when AddQueueMember is called by extensions 25 and 35 in the queuemetrics context.

QM_AGENT_PRIOLBL is set to "U" when the queue is not assigned to the agent, "M" when the queue is a normal working queue for the agent (Main), "W" when the agent is set as Wrap for the queue, "S" when the agent is set as Spill for the queue.

QM_AGENT_PRIONUM is set to 0 when the queue is not assigned to the agent or the queue is a normal working queue for the agent; 1 when the agent is set as Wrap for the queue, 2 when the agent is set as Spill for the queue.

Please take a look at the updating.txt and to the extensions_queuemetrics.conf provided example.

Thanks.

41

QueueMetrics installation / Re: Upgraded to QM 1.6.3.0

« on: January 03, 2011, 10:30:40 »

Hello Tony.

Sometime happens that tomcat does not understand that jsp pages were changed and lets the cache not synchonized with the new code.
I dont know if this is the case but I suggest you to start with a clean fresh cache following this FAQ:

http://www.queuemetrics.com/faq.jsp#faq-076-error_after_upgrade

then post back here the result.

Thank you and regards.

42

QueueMetrics news / Re: QueueMetrics 1.6.3 released

« on: January 03, 2011, 10:18:36 »

Hi Bruce.

Here are some notes about your reply:

Despite the notes from the news letter, it create a new folder and didn't copy my license info. I had to reinstall my license code but don't know what else mgith have been broken in config.properties file or hoping it has copied my configs like promised in the news-letter.

This is a feature that will work starting from this release, meaning that you need to configure manually the license code when upgrading from 1.6.2 to 1.6.3 but this will be the last time. The next upgrade to 1.6.4 or more will be automatically performed.

#1202 - Agent MUST set a pause reason    - Agent can still chose "-" as the reason and "-" still appears as the reason code in the list of pause codes. This was discussed to be removed on the forum which prompted this ticket to be created.

The new behavior is not enabled by default but should be enabled by means of a new configuration key in the configuration.properties file (as by the updating.txt file).

Please add:
default.pausecoderequired = true
to your configuration file then restart QueueMetrics

***Another serious problem is that pressing on "Quick Activity Reports > Last 90 Days" tells me that I have more agents that my license allows which is not correct. I have 16 agents made and our license is for 20 agents. Furthermore, pressing on Last 7 Days and Last 30 Days works. So, it seems like a bug for Last 90 Days only.

This is something strange because we did change anything in the license rules. The problem normally arises if you have more than 20 agents (or agents changed code) in the long period. Could you, please, check this?
What I mean is that if the agent "John Doe" changed their asterisk code from Agent/101 to Agent/301, and the report you're calculating contains the two codes, he will be counted twice for the purposes of licence agents calculation.

43

General Asterisk configuration / Re: Queuemetrics and Asterisk 1.8

« on: December 15, 2010, 12:15:44 »

We spent some days around asterisk 1.8.1 and, at the end, we found a set of workarounds that let us able to have it working with QueueMetrics, at least in the environment we set up. Please note that we tested the environment using dynamic agents with hotdesking enabled, as described in the document you can find at the link http://www.queuemetrics.com/download/QM_Trixbox_40.pdf

We started from a fresh TrixBox 2.8.0.4 install then we replaced asterisk with the latest 1.8.1, compiling it from sources.

The first problem found seems related to a bug present in asterisk (since the 1.8.0 version) that prevents the full queue activity log until a reload command is issued from the CLI. To fix this problem we had to change the code in the logger.c file found in the main subfolder present in the asterisk sources, near the line 396, in order to have something similar to what is listed below:

        if (qlog)
                fclose(qlog);

        {
                char tmp[4096];
                snprintf(tmp, sizeof(tmp), "%s/%s", ast_config_AST_LOG_DIR, queue_log_name);
                qlog = fopen(tmp, "a");
        }

Then we had to rebuild asterisk and to reinstall it.

The next step is to change the extensions_queuemetrics.conf in order to fix a problem related to the pipe separator that is now deprecated in asterisk 1.8.
To have this, we replaced the macro-queuelog at the end of the file with the code:

exten => s,1,Set(ADDINFO=${ARG6}|${ARG7}|${ARG8})
exten => s,n,QueueLog(${ARG3},${ARG2},${ARG4},${ARG5},${ADDINFO})

This should solve the login-logout procedures from the agent panel.

We then changed the line

exten => 11,7,ChanSpy(${QM_AGENT_EXT)

to

exten => 11,7,ChanSpy(${QM_AGENT_LOGEXT})

in the extensions_queuemetrics.conf file to enable chan spy for dynamic agents with hotdesking.

We restarted QM and agents were able to log-in/log-out pause/unpause through the QueueMetrics agent page.

44

MySQL storage and Qloaderd/Uniloader / Re: Manually dump old log files into qloader database

« on: September 10, 2010, 11:10:13 »

Hi,
What you did is correct.
Morehover, we provided a script that you can use for inserting timestamps in an already present queue log.
The script is called queuePartialUpdater.pl and you can use it in this way:

queuePartialUpdater.pl /my/queue_log/file partition_name /my/queue_log/logfile

The script takes the /my/queue_log/file as input and merge the events found with the information stored in the database for the specified partition.
You have to customize it a little bit, before to run it for the first time, in order to better adapt to your database configuration.

Thank you and regards,
Marco Signorini.

45

Running QueueMetrics / Re: Agent is unable to mark himself away from the queue

« on: September 10, 2010, 11:00:04 »

Wow. That's interesting!

Yes. I've to ask to send us the catalina.out log file. Could you, please, follow the instructions you can find here: http://astrecipes.net/index.php?n=251

Send us to info(at)queuemetrics(dot)com

We will update as soon we will find the causes.

Thank you and regards.
Marco Signorini.