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.

Messages - mirkox

Pages: [1] 2 3 ... 14
Hi, in freepbx that's normally included from extensions_custom.conf (that file won't be rewritten with freepbx updates).

BTW you can verify that the dialplan is correctly included in Asterisk with:

asterisk -rx "dialplan show queuemetrics"

I'm sure you have it and that it is working because otherwise it's impossible for QM to perform actions on the PBX


Hi there;

actually we like to use SIP/ in order to keep everything compatible with all flavours of Asterisk (freePBX and so on); that may cause some incompatibility with built in login/logout/pause/unpause methods and other issues; basically better not mix up QM login methods with other one.
Anyway you can modify the QueueMetrics dialplan (usually /etc/asterisk/extensions_queuemetrics.conf) in order to log in the queues the kind of interface you prefer so you can make it compatible with your Asterisk implementation, (seach SIP/ in the document to see where it is used).

Remember to reload the dialplan after you save the file (asterisk -rx "dialplan reload")

Hi Jeff, the problem is both tomcat8 and java8, from the next release QM will be fully compatible with them.

General Asterisk configuration / Re: Queuemetrics and PJSIP
« on: May 30, 2017, 08:32:09 »
We will probably release a specific dialplan, although the switch is very easy:

search SIP/ and replace with PJSIP/

Hi Stephen, at the moment there's no detailed log about this but if you go into an editor, like the details of a queue, you can see which user did the last edit on that queue and the time of the edit

Running QueueMetrics / Re: Strange doubling after update
« on: April 21, 2017, 08:17:12 »
Honestly that's really weird because I tested the same version here and can't reproduce the problem; you can't disable it but you can use the default value for the background setting:

replace the with the correct url of your QueueMetrics

Running QueueMetrics / Re: Strange doubling after update
« on: April 20, 2017, 08:21:48 »
Hi there,

basicly QM has the possibility to integrate with a CRM and do other stuff by opening a URL in a iframe in the backgrorund of the page.

I see that your iframe is pointing to # so it's loading itself.

The property that could affect this are:

default.crmapp   (the page that opens automatically with each call, you can also pass some parameters of the call in the url; check if maybe it is defined twice)

realtime.agent_web2_url  (two custom urls)

realtime.agent_background_url  (the default background url)

Please check the above properties.

What's your version of QM btw?

Running QueueMetrics / Re: Strange doubling after update
« on: April 19, 2017, 08:03:13 »
The setting is fine; can you verify using the browser's inspector what page is loading the big iframe in the agent's page?

Also what's the exact version of your QM?

Running QueueMetrics / Re: Strange doubling after update
« on: April 18, 2017, 15:26:23 »
Please check into the configuration: how is set the default.crmapp property?

Realtime Live / Re: Select Queues
« on: April 18, 2017, 08:34:59 »
Hi, give a look at realtime.dynamicLoginQueues here:

Running QueueMetrics / Re: Strange doubling after update
« on: April 13, 2017, 07:53:37 »
Hi there,

this is the first time I hear about that; could you share a screenshot? Also do you get any errors in the browser's console?


Hi stephen,

the problem is that the log appears incorrect; what's the version of Asterisk you are using?

QueueMetrics installation / Re: Issues with Time?
« on: February 10, 2017, 08:59:12 »
Hi mnettel,
please open /usr/local/qloader/

and search: "my $timezone_offset"

By default it looks like,

my $timezone_offset  = 0 * 3600;  # in seconds

and normally Perl takes the correct time from system:

Do you have a different value?
If not probably you need to set the correct offset (8*3600 or -8*3600)

Remember to stop the qloaderd service, TRUCATE the queue_log table on the database; if your log is rotated use queuePartialUpdater to reload everything (if you have just one queue_log file that's not needed; then restart the qloaderd service


QueueMetrics installation / Re: Issues with Time?
« on: February 09, 2017, 11:13:42 »
Hi mnettel,

probably what happens is the following:

- qloader loads new data from queue_log into the database only if the last record in the db has a timestamp < than the one of the new data
- every 15 minutes qloader writes an 'heartbeat' record using the mysql function NOW() to determine the timestamp, if the time is some hour beyond then qloader won't load any new data from queue_log

You can turn off the heartbeat from the qloader settings but what I'd do is to verify and in case fix the mysql time:

After that stop qloader; go to /usr/local/qloader; use queuePartialUpdater to reload the queue_log file(s); restart qloader


Running WombatDialer / Re: Wombat and JRE issues
« on: December 13, 2016, 14:36:58 »
Hi terry,

thanks for your message, we'll look into it.
We know that Java 1.8 is not compatible at the moment; but it is supposed to work perfectly on Java 1.6 so this is quite strange.


Pages: [1] 2 3 ... 14