Hi,

A possible solution would be to use the originatechannel setting (toggle advanced fields on the buttons section in the FOP2 Manager). You can use the Local pseudo channel there, so instead of dialing the device, it will dial an extension@context in your dialplan. Something like

Local/1234@from-internal

In the originate channel field will make any call origination or redirect to go through the dialplan, instead of using just a device.

I am not sure if it will work in the case of PJSIP with multiple AORS, but it might worth a try.

Best regards,

Hello,

Here is a direct download link if it does not appear on the plugins page in FOP2 Manager:

http://download.fop2.com/plugins/queuehintfpbx-1.0.1.tgz

Best regards,

Hi,

It is fixed already, thing is that the created context won't be recreated if you just upgrade FOP2 via usual means, they need to be regenerated

/usr/local/fop2/generate_override_contexts.pl -w

Best regards,

PD: I am both lazy and incompetent. :)

The latest FOP2 version has the getinfo option:

/usr/local/fop2/fop2_server --getinfo

Best regards,

Hi,

If users do not have the callhistory permission, it won't show up anywhere.

Best regards,

Version 1.0.1 of the plugin was released including the fix.

Best regards,

Hi,

Please update FOP2 to the latest version (released two days ago), it should fix the issue.

If you want to do it manually, edit the file /var/www/html/fop2/admin/system.php and look for the string

"amportal.conf"

and replace it with

"xxxxamportal.conf"

That should fix the issue also (quick and dirty). It is best to update to latest with this command:

wget -O - http://download.fop2.com/upgrade_fop2.sh | bash

Best regards,

If you create a new entry in the phonebook and try to dial that entry, do you have that problem also ?

Hi,

Did you upgrade from previous version? It seems you have a mixed up version between fop2_server and fop2.js client files. A dial command from the client/browser will show like this:

<msg data="34|dial|90123456789!TVJCQUM=|41c2f73d1642b78450f650459a281db9" />

Try to clear up your browser cache.

Best regards,

I am also confused as it is not clear to me where did you notice that ABANDONED call. The base FOP2 does not report statistics, you have two plugins that can show stats, and they behave differently as they source the data from different places.. the queue stats plugin shows the stats reported by Asterisk queue application (you can contrast that data with the command asterisk -rx "queue show"). And the full wallboard, that uses Asternic CCStats PRO repots.

They are different sources, and in this case ABANDON has a different meaning.

Asterisk Queue application will count any call that enters a queue and is not connected to an agent as an ABANDON.

In the other hand, Asternic Call Center Stats uses the asterisk queue_log file for its source data, and discerns between ABANDON event in that log (a caller enters a queue and hangs up before being connected to an agent), and Unanswered calls, those are calls that enter the queue, that are NOT connected to an agent, but diverted to somewhere else due to either pressing a key, a timeout, or the queue become empty.

Your last question does not make sense to me: Why a call is calculated as abandonded before it was answered? Because an ABANDON is exactly that, a call that was not answered by an agent (but entered the queue). So either if you use asterisk queue application abandon stats, or the queue_log stats, an ABANDON will always be recorded if a call is not connected to an agent (thus answered).

Now, if you can be more clear about the exact numbers you saw, the full line in the report, and perhaps contrast that with the line in /var/log/asterisk/queue_log, then I can give you a more specific answer.