Messages

61

General Asterisk configuration / Re: aleph and trix servers? What are those?

« on: September 06, 2010, 10:15:05 »

Hi,
Aleph and Trix server are a placeholder in the configuration.properties file.
QueueMetrics could be used to monitor a cluster of asterisk PBXs and, in the configuration example, there are two servers named aleph and trix.
If you are not running this modality you could forget these configuration keys.

More details are reported in the QueueMetrics user manual you download or read online at http://www.queuemetrics.com/manual_list.jsp

Thank you and regards,
Marco Signorini.

62

General Asterisk configuration / Re: Agent status cannot be determined - What is causing this?

« on: September 06, 2010, 09:37:50 »

Hi.
I think this is related to other problems you have posted and I'm sure you'll have it working as soon you will be able to have agents pushbutton working.

Other possible situations where this could happen are related to the timespan configuration used by QueueMetrics to evaluate past events.
If your agents are not logged in/out for a period longer than what is specified in the configuration key realtime.startHour and/or this value is not compatible with the agent shift working period.
Please see a brief explanation in the QueueMetrics FAQ you can find at http://queuemetrics.com/faq.jsp#faq-020-midnight-rt

Thank you and regards,
Marco Signorini.

63

General Asterisk configuration / Re: Neither of agent portal controls such as Logon,Logoff,Add,Remove,or Pause work!

« on: September 06, 2010, 09:28:13 »

Hi,

Did you included the extensions_queuemetrics.conf file in your local Asterisk dialplan?
Did you changed the main QueueMetrics configuration.properties file in order to let it able to communicate with Asterisk through AMI?
What type of error and/or CLI output do you have when pressing a pushbutton on the QueueMetrics realtime agent page?

You can have more information on how to have QueueMetrics working with TrixBox and FreePBX in this tutorial: http://www.queuemetrics.com/manuals/QM_Trixbox-chunked

Thank you and regads,
Marco Signorini.

64

General Asterisk configuration / Re: What is realtime.agent_button_4=Local/104 ? I don't have that extension

« on: September 06, 2010, 09:22:42 »

Hi,

This set of configuration keys controls a feature you cand find in the realtime agent page.
As you can see in this picture: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s08.html#_real_time_agent_rsquo_s_page_customizable_buttons is possible to have a maximum of 4 customizable buttons present on the realtime agent page. Each button could be individually enabled/disabled and could trigger different actions like, for example, open a specific URL or start a call to a specific extension.
Customizations should be made changing the realtime.agent_button_X.yyyyyy related keys.

In the example provided, pressing the button 4 will start a new call originating from the extension 104 in the from-internal context, directed to the ext-queue example. Obviously this is an example to show how to configure a particular button, and should be changed for your system (where I suppose neither the extension 104 neither the ext-queue is present).

realtime.agent_button_4.channel=Local/104@from-internal
realtime.agent_button_4.ext=200@ext-queue

To have more detail on that you can read the QueueMetrics user manual online at the link reported above. More details on the configuration key values should be found on the Appendix D of the same document.
Each time you change the configuration file, don't forget to issue a "/etc/init.d/queuemetrics restart" root shell command.


Regards,
Marco Signorini.

65

QueueMetrics installation / Re: What to do after install? Real-time doesn't show agents status

« on: September 06, 2010, 09:06:22 »

Hi,

The $rewriteToAgent variable in the qloader.pl script is something different on what are your needs and is responsible to rewrite agent information to MySQL database. If you modify something related to this script, you need to restart their related daemon through a "service qloaderd restart" shell command.

Setting "default.rewriteLocalChannels=true" in configuration.properties should be enought to solve your issue: this option affects how QueueMetrics analyzes MySQL stored data.
Normally, after executing any key settings modifications in the configuration.properties file, you need to issue a shell "service queuemetrics restart" command to make them effective. Dont' forget to log-off and log-on again on QueueMetrics.

Regards,
Marco.

66

Running QueueMetrics / Re: Queuemetrics says agents are logged out but they are not...

« on: April 19, 2010, 11:48:32 »

Hi,
In my test setup I can confirm QueueMetrics is working fine if you set:

default.ignoreQueueStarts=true
default.useRawAgentSessions=true

Then issue a QueueMetrics restart.
Tell me if you have problems after these configuration modifications.

67

Running QueueMetrics / Re: Queuemetrics says agents are logged out but they are not...

« on: March 02, 2010, 16:16:25 »

Hello.

I've replicated the problem. I've inserted a bug in our internal bug tracker. You can refer it to #1002 for any other information.

Thank you and regards,
Marco Signorini.

68

Improving QueueMetrics / Re: Deletes agents remain in Queue Detail screen

« on: February 25, 2010, 16:48:57 »

Hello.

The problem was already reported and it's fixed. It will be public on next coming 1.6.0 QueueMetrics release.

If an agent is removed and there are queues containing it, now the queues are marked in red in the queue list configuration page. The invalid agents are then marked in red when the queue is edited.
The user should edit the agents associated to the red-marked queue then save it again in order to solve the problem.

69

Outbound and QueueMetrics / Re: Popping a URL with Outgoing Call

« on: February 01, 2010, 15:41:19 »

Hi,
I've fixed the bug and it will be released starting from QueueMetrics 1.6.0beta1.

You can fix the problem by yourself without waiting for next coming release. The problem is effectively present in the extensions_queuemetrics.conf.

If you look at the [qm-queuedial] context, the row:

Code: [Select]

exten => s,n,Macro(queuelog,${ST},${UNIQUEID},${QDIALER_QUEUE},${QDIALER_AGENT},CALLOUTBOUND,-,${QDIALER_NUMBER})

you can note that there is a "-" between CALLOUTBOUND and ${QDIALER_NUMBER}. You have to remove it in order to obtain what's reported below:

Code: [Select]

exten => s,n,Macro(queuelog,${ST},${UNIQUEID},${QDIALER_QUEUE},${QDIALER_AGENT},CALLOUTBOUND,,${QDIALER_NUMBER})

Followed by an Asterisk dialplan reload it should fixes the problem.

Thank you and regards.
Marco Signorini.

70

Outbound and QueueMetrics / Re: Popping a URL with Outgoing Call

« on: February 01, 2010, 14:53:55 »

Hi.
Thank you for the detailed explanation.

I've replicated the problem in my debug version and I've issued an internal bug feedback (Bug 968).
It will be fixed in the next coming QueueMetrics 1.6.0beta1 version we will deliver in few weeks.

Thank you and regards,
Marco Signorini.

71

Realtime Live / Re: Robot AJAX Realtime Login

« on: December 18, 2009, 12:30:43 »

Hi.
We added two new verbs:

- qm_wab_ajax.do
- qm_rt_ajax.do

They have to be called with the same parameters required by the not-ajax enabled versions and they will provide you the new Realtime and Wallboard ajax based pages.

The fix will be included on next coming QueueMetrics 1.5.6 release.

Thank you and regards
Marco Signorini.

72

Problems / Re: Custom report error with time range

« on: October 30, 2009, 10:48:01 »

Having not received any answer I suppose that the suggested interpretation is the correct one.
Actually QueueMetrics is not able to perform such type of reports.
We will plan to have it on a future release.

Thanks.
Marco Signorini.

73

Outbound and QueueMetrics / Re: Outbound alias and queues

« on: September 03, 2009, 11:41:34 »

Hi,
I don't see any problem but... could you, please, better explain what do you want to do?

74

Running QueueMetrics / Re: [major bug] unicode issues

« on: September 03, 2009, 11:10:45 »

The bug is fixed since the version 1.5.4.
To have it working, please be sure to set the key:

default.charsetEncoding=UTF8

in the configuration.properties file.

Remember to restart the queuemetrics service and to log-off and log-on again to QM session.

75

Running QueueMetrics / Re: loading agents.conf in utf8

« on: September 03, 2009, 11:09:50 »

The bug is fixed since the version 1.5.4.
To have it working, please be sure to set the key:

default.charsetEncoding=UTF8

in the configuration.properties file.

Remember to restart the queuemetrics service and to log-off and log-on again to QM session.