2.24
-
Having issues with 2.24. I have upgraded our PBX to Elastix 2.2 and had FOP2 2.2.4 loaded in via the add-ons, but just noticed I am getting a manager error no matter what I try. Verified it is set up properly.
I only noticed this as I upgraded another PBX from FOP2 2.23 to 2.24 yesterday to see if it fix issues with Chrome they were having, but in fact pretty much nothing worked after the upgrade, especially with the queues not showing members. I finally rolled back to 2.23 and everything immediately worked again.
Also curious that the add-on screen lists the version to download as 2.25, but 2.24 is what downloads. Just tried an uninstall and reinstall but no change in Elastix 2.2.
-
Hi,
Do not mix elastix rpm with .tar.gz versions, it will give you problems. They are different, even in version numbers. The elastix version will have problems with chrome for now, we still need to update the .rpm to include the chrome fix.
If you want to install the .rpm from elastix, it will work as is with no issues, if you later download 2.24 in tgz form and install that instead, you will have to do some things by hand, most importantly copying index.html to fop2.html. The upgrade will also break the integration with elastix phonebook and it will show you the regular fop2 phonebook instead.
Installting from addons in an upgraded elastix might give you problems if your /etc/elastix.conf file is not updated as in a standard 2.2 version (where the manager password is also located). The fix is quite easy anyways, you can edit /usr/local/fop2/fop2.cfg and set the manager secret by hand.
My advise right now would be to install 2.24 from tarball on elastix 2.2, not from the repos, if you want to fix google chrome. And also install fop2admin version 1.2.9.
FOP 2.24 from tarball and fop2admim 1.2.9 does not have any issues with queue buttons, chrome, etc. It is super important to clear the browser cache when upgrading, because if you load the .js client from 2.23 over a 2.24 server, you will experience issues like buttons not updating, strange footer with code, etc.
-
I failed to specify that the one with the Chrome issue is running on Druid and was installed via tar.
-
Hi,
The only thing that might go wrong with 2.24 using manual configuration files that worked before is the lack of context and extension in queue buttons, without them, the buttons will work partially. If you did not see the queued calls, it is because you are probably lacking extension or context in the button definition.
Everything else works as always,you should not have any other strange issues beyond that.
On the plus side, the queue button behaves correctly on multiple server setups now, mostly cluster servers where the configuration is replicated (before 2.24, or 2.23 , the state of inactive queues on the backup server was interfering with the real state of the active server).
Best regards,
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login