FOP2 small bugs

[nicolas]

FOP2 does not have any of those bugs, they seem to be related to configuration or perhaps having Asterisk 13 with a version of FOP2 that was not fully tested with that newer Asterisk version. If that is the case, upgrade FOP2 to 2.31.00 as it will work better with queues and conferences in Asterisk 13. The version of FreePBX is not relevant, Asterisk is the important thing here.

Best regards,

[Damir]

Thanks. But we've checked out configuration many times and it makes us sure that it was done correct. We've done that looking at your guide, and everything is ok except that things( Have we try to upgrade recently to newest version of FOP2?

[nicolas]

Are you using Asterisk 13? You never told.

[Damir]

Asterisk 1.8.32.1 built by ............... on a x86_64 running Linux
That's our version.

[Damir]

And it does not reload FOP2 from admin. Only by fop2 service restarting(((

[nicolas]

Sorry, I missed the Asterisk version. In queue config in freepbx set eventmemberstatus=yes if you want the member icon in queue button to show correct state always, but I advise against it, as it will put too much load to asterisk manager and fop2 if you have a bunch of queues/members.

Conference members will show fine, not sure if you might have a limit because of the free/lite version, you should not have any issues with it.

You can contact me via live help and grant access to your server so I can review it, as I say, there are no bugs on queue member status or conference members in FOP2, they are not small but quite big from your description, something that is NOT showing is a a big bug in my opinion.

[Damir]

Thanks! What about it does not reload FOP2 from FOP2 admin? It works only by "fop2 service" restarting(((

[Damir]

Guys, how we can contact to you via upper mentioned 'live help'?

[Damir]

We've noticed that while trying to Reload FOP2 from FOP2 Manager there is some warning in Asterisk CLI:
[2016-05-12 10:36:48] NOTICE[29016]: manager.c:2480 authenticate: 127.0.0.1 failed to authenticate as '...................'

[nicolas]

The FOP2 Manager takes manager user and secret from FreePBX configuration files, and use those to connect to AMI to perform certain commands, like the Reload event. If you see that error it means that the config parser is not able to retrieve the user or password fully, or something similar to that. You might want to upgrade the FOP2 Manager as it has some fixes on the config parser (allowing some extra characters in passwords).