User with context in Phonebook
We have two kind of FOP2 users - without contexts and with contexts. And they have different time to access Phonebook interface in FOP2.
For users without contexts the phonebook opens almost instantly - about 1-2 sec, and the users with contexts have to wait for 40-50 seconds before interface will open. But if the user opened it first time, then closed and will open again there is no problem - it's opening without delay.
In mysql log i can see messages
Connect
INIT DB FOP2
Query Select keyword,parameter,value FROM fop2setup
Quit
and only after 5-6 these messages i see
Query DESC Visual Phonebook
Query Set Names UTF8 ... and so on. In this moment interface is coming up and the user can see records.
For user without contexts only one message
++++++++
Connect
INIT DB FOP2
Query Select keyword,parameter,value FROM fop2setup
++++++
appears.
If we try to open phonebook directly from phonebook.php - it opens well, without delay.
P.S. It doesn't matter how many records in BD, even empty BD opens so for "contexts" users.
Tested on several hosts with different versions of Linux, apache,mysql,php...
What does the request to "fop2setup" mean ? Do we have to create this table in fop2 DB and fill in with some info ?
Best regards,
Sergio.
For users without contexts the phonebook opens almost instantly - about 1-2 sec, and the users with contexts have to wait for 40-50 seconds before interface will open. But if the user opened it first time, then closed and will open again there is no problem - it's opening without delay.
In mysql log i can see messages
Connect
INIT DB FOP2
Query Select keyword,parameter,value FROM fop2setup
Quit
and only after 5-6 these messages i see
Query DESC Visual Phonebook
Query Set Names UTF8 ... and so on. In this moment interface is coming up and the user can see records.
For user without contexts only one message
++++++++
Connect
INIT DB FOP2
Query Select keyword,parameter,value FROM fop2setup
++++++
appears.
If we try to open phonebook directly from phonebook.php - it opens well, without delay.
P.S. It doesn't matter how many records in BD, even empty BD opens so for "contexts" users.
Tested on several hosts with different versions of Linux, apache,mysql,php...
What does the request to "fop2setup" mean ? Do we have to create this table in fop2 DB and fill in with some info ?
Best regards,
Sergio.
Comments
set_config($DBSETUP)
in config.php, and see if that helps... it is strange what you describe. Querying a non existant table should raise a warning, not make things that slow.
Best regards,
It was tested on Linux (x64) 11.1, 11.4 and 12.1 opensuse releases. Normal situation was only on 11.4 with apache 2.2.17 and mysql 5.1.63 with the same configuration of LAMP server components. And such problem has apeared only on last versions of 2.27 release.( 10 november and last ) I don't know the correct reason, maybe some php or apache bug with new java implementation...
P.S.Recording with script recording_fop2.pl didn't work for long time while i found out that it depends on perl-DBD-mysql driver which was not installed by default with perl package in suse. I didn't see this recommendation in oficial docs... is there a reason to add ?
Best regards,
Sergio.
FOP2 recording works perfectly without the postrecording script, you will find the recordings in the default recordings directory in Asterisk.
Adding a post recording script is an option, the scripts provided are working examples, but are disabled by default. It is up to the user decide what he wants to do *if* he wants to do anything. I will add to the comments sections that it requires the perl module (that comes installed in 95% of linux/asterisk installations).
About the slowness, if you can catch me in the live help we might be able to take a look at your actual implementation, perhaps we can get an idea on what is wrong.
Best regards,
On the current moment i solved my problem by migrating to Linux SuSe 11.4 and FOP works well with it. The last post just FYI and for some other SuSe based Linux users.
Best regards,
Sergio.