FOP2 Community Forum

After looking at the problem a bit more, we've seen that the delay happens when there's more of 2 "free" agents in a queue. And it seems exponential: more free agents, more time it will take to show the ringing status of the extensions (even if we hang up the call, the call will appear and then disappear).

Don't know if it's relevant, but looking at the fop2 log, when the call enters the queue, we can see the RINGING (output with a few greps to only show relevant data):

127.0.0.1 <- Device: Queue:127
127.0.0.1 <- State: RINGING

127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Device: SIP/350
127.0.0.1 <- State: RINGING

127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Device: SIP/351
127.0.0.1 <- State: RINGING

127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Device: SIP/352
127.0.0.1 <- State: RINGING
....

But until we see the ChannelStateDesc: Ringing, the buttons do not appear as ringing. Don't really know if it could be a clue.

I forgot to mention Eventfilters in manager.conf didn't seem to make any difference

On a system with Asterisk 13.9.1, FreePBX 12 and FOP2 2.30.02, we have a problem whith incoming calls to queues. When a call enters a queue, the small icons of the agents of the queue start moving indicating the extensions are ringing, but the extension buttons do not turn orange for 10 seconds or more (seems some sort of delay).
All the agents of the queues are dynamic. We have 12 queues with 8-12 dynamic agents in each queue, and 44 extensions in the panel.
We have tried FOP2 2.31.00 and 2.31.01, with the same results (but had to revert to 2.30.02 because some bug made some calls appear empty in the queues boxes and would not disappear).

Can it be caused by too many AMI events? Is there something we can do?

Yes, I've tried iceweasel 17.0.6 on Debian and chrome and explorer on windows with the same results

Hi, I'm trying to install the latest version of fop2 on an elastix 1.6.2-27. Everything went smooth following the docs, but when I try to login the fop2 web it fails. I keep getting the:

Connecting to server, attempt number : 1

And eventually I see at the bottom of the page:

FOP2 - Version 2.26 - Lite Version - Limited to 15 extensions . Buy it now for unlimited extensions. If you already have a code enter it here

Which is a little unexpected, as I've registered succesfully the full white label version, via /usr/local/fop2/fop2_server --register (and fop2_server --test confirms it, see below)

Fop1 is running on port 4444 and fop2 on 4445:

tcp        0      0 0.0.0.0:4444                0.0.0.0:*                   LISTEN      3593/perl           
tcp        0      0 0.0.0.0:4445                0.0.0.0:*                   LISTEN      7271/fop2_server 

fop2 is running:

pgrep fop2
7271

There are no iptables rules, no selinux and I can telnet the server from localhost.

fop2_server --test says everything is ok:

/usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - White Label Version.
Flash Operator Panel 2 - White Label License (7)
Connection to manager OK!

The extensions at the freepbx don't use voicemail, so I've created a few using the fop2 freepbx add-on, and they show up when executing by hand autoconfig-users-freepbx.sh:

.....
user=101:101:all:All Trunks,All Conferences,All Queues,All Extensions,All Buttons
user=315::all:All Buttons
user=500:1234:all:All Trunks,All Conferences,All Queues,All Extensions,All Buttons
buttonfile=autobuttons.cfg

And the script is not commented out at the end of the fop2.cfg file:

.....
; This line is NOT commented, it executes 
; the autoconfig configuration for FreePBX
#exec autoconfig-users-freepbx.sh

When I try to login on the fop2 web, I see some traffic on the lo interface to port 4445, and the responses it gives back:

[root@xxx fop2]# ngrep -W byline -p -q -d lo '*' tcp and port 4445
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip) and ( tcp and port 4445 )
match: *

T 127.0.0.1:37383 -> 127.0.0.1:4445 [AP]
<msg data="GENERAL|contexto|1" />.

T 127.0.0.1:4445 -> 127.0.0.1:37383 [AP]
{ "btn": "0", "cmd": "key", "data": "XXXXXXX", "slot": "" }.

T 127.0.0.1:4445 -> 127.0.0.1:37383 [AP]
{ "btn": "0@GENERAL", "cmd": "version", "data": "2.26!xxx!7", "slot": "" }.

T 127.0.0.1:37383 -> 127.0.0.1:4445 [AP]
<msg data="GENERAL|checkauth|500|XXXXXXXXX" />.

T 127.0.0.1:4445 -> 127.0.0.1:37383 [AP]
ok

Am I missing something?

Thanks,