Member
Last active 12 years ago
Hi,
is there a need to reinstall fop2 with "make" after asterisk version change 1.4 --> 1.8?
Thanks
Andrej
Hi,
we're having lots of queues for variety of partners with very few calls.
Is it possible to configure one button that would indicate (react to) calls for multiple queues? Idea is to preserve space, we just want to see if there are any calls waiting / ringing for any of small call volume queues.
Any chance of configuring that with FreePbx module?
We're using
Thanks and best regards
Andrej
Many thanks, that worked like a charm! :-)
Have a good day,
Andrej
Hi,
I've double checked the ownership of /var/lib/php/sessions and owner was already asterisk:asterisk.
According to use of tail -f /var/log/httpd/error_log while clicking on play or download icons produces no error messages.
I'm using Centos 5.7 x64, Freepbx and compiled asterisk. Asterisk and apache are running under asterisk user. I'm getting same result with Chrome and IE.
Other apps relying on php sessions are working OK.
I understand that working environment has nothing to do with excelent product of yours, but would appreciate any further hints.
Thanks
Andrej
Hi Nicolas,
is there a reason why this post is ignored?
BR
Andrej
Hello,
I have a problem with using recordings interface on FOP 2.24. I can see recorded calls in FOP2's interface. They are also physically present in /var/spool/asterisk/fop2/date.
I've found some information about the "no way" message and memcached, but I haven't found any settings in /etc/php.d.
Also, is there a way of showing recorded calls in ARI (Freepbx call monitor) interface?
Thank you,
Andrej
Can someone please point me to the fop 2.24 download location? It seems there's only 2.23 in download section.
Thanks a lot.
Exactly same behaviour / error in our case (FOP 2.23 vs Chrome 16.x).
Problem was solved by correcting the dialplan (adding sanity checks for login attempts) - Users were able to login with blank extensions (it happened sometimes by mistake). When they corrected their error and logged in properly, it caused strange results.
Bottom line: all solved. Thanks for taking time & looking into it, Nicolas. Keep up the good work.