Since upgrading from 2.29.00 to 2.31.01 my window sizes do not remain the same size after logging out and logging back in to the panel. I see there is now a "Lock" button. It is hard to tell what is being locked. Sometimes there is a large blank area below the last extension button on the screen which can be removed by collapse and reopen. Or by manually adjusting the size from the corner resize icon. But nothing stays the same after closing and reopening. Always I am having to readjust the screens. Especially the extension screen that have the most buttons. Moving screens around will produce a large area below it that is not filled and remains white in color unless you manually move the window or uncheck the locked button and collapse and open. Am I missing something? What can I do to lock my layout the way I want it?
gene778
Posts
-
Window size tutorial and layout -
Update from 2.29 to 2.31 failedAnd the new version does work much better in showing the extension numbers during an internal calls and correct callerid information in general. Thanks for the update.
-
Update from 2.29 to 2.31 failedThat simple fix did work. I will work on getting the "proper" fix in place. Thank you!
-
Update from 2.29 to 2.31 failedHere is installation command line echo:
eirasterisk:/home# cd /home/fop2
eirasterisk:/home/fop2# make install
Reactivation failed! (EXPIRED)You must purchase the annual maintenance fee in order to upgrade your
version ( https://www.fop2.com/buy.php ).Enter your license upgrade code: y4*********
Reactivation Successful
Thanks! Do not forget to restart fop2 to activate the license.
eirasterisk:/home/fop2# make install
Reactivation Successful/bin/sh: 40: [: asterisk: unexpected operator
/bin/sh: 43: [: asterisk: unexpected operator
New configuration file /usr/local/fop2/fop2.cfg.new installed. Original fop2.cfg preserved.
New configuration file /var/www/html/fop2/config.new.php installed. Original config.php preserved.
New configuration file /var/www/html/fop2/admin/config.new.php installed. Original config.php preserved.
update-rc.d: using dependency based boot sequencing
Done!
eirasterisk:/home/fop2# service fop2 restart
Restarting Flash Operator Panel 2: fop2. -
Update from 2.29 to 2.31 failedAfter updating my license for another year, I tried to update my fop2 from 2.29.00 to 2.31.
I have debian 64 bit with asterisk 13.
Everything was working fine with the old system but the new install says:Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.22 (Debian) Server at eirasterisk.zapto.org Port 80I have two ethernet cards on this system, one for internal network and one to connect to the internet.
What more information do you need to troubleshoot this problem?
Thank you,
A Happy FOP2 user,
Gene in Virginia, USA -
FOP2 with Debian Jessie?Do you foresee any problems with FOP2 and Debian Jessie? I don't understand all the changes, but I understand it is considerable and includes a controversial move to the systemd system and service manager. Please advise.
Thank you,
Gene in VA.Currently running Asterisk 13 on Debian Wheezy. Freepbx 12.0.74 and FOP2 2.29.00
-
Action Buttons not showingIn my case, I forgot to put in what the permissions were! Once I put in "all" for permissions, the action buttions showed up. I thought I better post the solution! Even, as simple as it is.
Thank you for your work! -
Action Buttons not showingOnly the conference button is showing after upgrading from fop2 29 beta to fop2.29.00
Freepbx distro, Freepbx 12.
Asterisk 12 originally, then 13, now 11. I am running Asterisk 11 because of the problems with freepbx and pjsip configuration.As you will see in the picture what happens. I rebooted and the same shows up.
According to my buttons config it is set to show all buttons for this user.Any idea?
If you need more info I can get it to you per your instructions.
Gene in Virginia. -
Conference talkers not shown correctlyI sent you an email, there was one conference in this debug file that shows the problem.
custom-conf9520 it had four participants. While one person was talking, all the icons were "lit up" showing that all were talking at the same time, even the ones who were muted. -
Conference talkers not shown correctlyFor the benefit of others who need to do a debug:
I created directory /var/log/fop2
Then:
changed the /etc/default/fop2 to :OPTIONS="-d -p $PIDFILE -X 1 --logdir /var/log/fop2 --audit /var/log/fop2/audit.log"
I see the capture is working and will forward you info from a conference.The debug file is 8000kb, I keep getting an error message after uploading that the file is empty.
How do I get it to you? -
Conference talkers not shown correctlyAnother picture of what is not working. The extension dialing into the conference should be showing "656" as the number that was called to access the conference, not "dstring" or "out". This worked prefectly with Asterisk 11 and FOP2 2.27. That is why I am seeing a problem. The difference between the two is very noticeable.
And you can see the numbers are out of order in the conference.
Gene -
Conference talkers not shown correctlyAsterisk 13 Debian FOP2 2.29 See attached file, in a conference call using MeetMe, the status of the listener is not shown correctly. Even if a person is muted (*1) the icon shows they are talking. The buttons seem to work but is very confusing of who is doing the talking when several icons are showing "talker".
If you need more info, let me know and will provide.
-
FOP2 Asterisk 13 upgrade not showing correct information in conference or trunkUPDATE--on Debian. I did finally get the 2.28 to work and it looks great! After several restarts, log offs and log back in, it finally worked right. For some reason version 2.27 was still in a cache or memory, and it finally cleared out and when the proper log in screen came up, I knew something had changed. I put in my credentials and everything worked as it is supposed to! I will try the 2.29 after you put it up publically.
I did not do a restart of operating system or a restart of asterisk, just several restarts of fop2 and several log off, log in, log off, log in to the panel and finally it worked.
Thank you,
Gene -
FOP2 Asterisk 13 upgrade not showing correct information in conference or trunkI have the 2.29 working on the Centos 64 bit Freepbx distro but not on the Debian 64 bit.
I downloaded the 2.29 debian, installed it, uninstalled the old FOP2Admin, did a service fop2 restart, just to make sure it was loaded correctly, but when I try to access the panel I get what appears to be the old login screen and putting in the user name and password does nothing.
The server test shows valid license and connection to manager OK.
But I was not able to get the screen to load. The new version of FOP2 has the login screen in the middle
of the screen, 2.27 has the login at the top of the screen. The login continues to be at the top of the screen as if 2.27 is still installed.So I install 2.28 debian over the top of the 2.29 debian and that is working except it has the same problems as 2.27 not showing the correct information in the conference or trunk area of the screen.
If you need more info from me, I am at my computer for most of the day.
Thank you,
Gene -
FOP2 Asterisk 13 upgrade not showing correct information in conference or trunkIt is on a Debian 64 bit installation. Freepbx 2.11
Will the dev 2.29 work with asterisk 11 if I have to go back to using Asterisk 11?What is the license requirement for the dev version?
I am currently licensed to have 2.27 with activation code dating back to May 20, 2013.Please forward the Debian tgz if I need to go ahead with installation.
-
FOP2 Asterisk 13 upgrade not showing correct information in conference or trunkFOP2 2.7 not showing correct information after upgrade from Asterisk 11 to Asterisk 13.
After putting Asterisk 13 in place, and restarting FOP2, I received the FOP2 Connection Manager error.
I read the posts and downloaded the most recent version of 2.7 and replaced the fop2_server binary.Then the FOP2 would load and open correctly. But the information being displayed was not correct
as you will see in the picture.Let me know if you need more info to troubleshoot.
This system is not a Freepbx distro and want to keep Freepbx 2.11.42 and FOP2 2.27 with Asterisk 13 if possible.
Thank you for your work and help.I recently purchased another license and installed FOP2 on freepbx distro 6 updated to Asterisk 13 with freepbx 12 and all is well on that system.
Gene in Virginia, USA -
Freepbx distro Asterisk 12 Freepbx 12 installation errorI must have been confusing it with the FOP2Admin module that I installed via the Freepbx module.
Thanks for the help.Gene
PS: Thank God for Kristina Kirchner and the fight Argentina is waging against the "vulture funds"!
Your President is a blessing to your country, its people and the world community. America needs
such a President! -
Freepbx distro Asterisk 12 Freepbx 12 installation errorNic,
Last night I set up a computer with Asterisk 12 and Freepbx 12 the 64 Bit distro from Freepbx.When I try to install FOP2 on this distro from Freepbx I get the following error message after uploading the
module.The following error(s) occurred processing the uploaded file:
Missing module.xml in /var/www/html/admin/modules/_cache/fop2-2.28-centos-x86_64.tgzI get the same error message with version 2.27.
Can you point me in the right direction?
Thanks,
Gene in Virginia -
Buttons DisappearAll is going well today after the change you suggested.
I have done many mod reloads today for many reasons and no problem with the FOP2 panel.
Thank you NicolasGene in Virginia, USA
-
Buttons DisappearDone and restarted FOP2. Will let you know tomorrow how things go.
Gene