Thank you, so far everything looks good. The interface shows version 2.28, and after copying over the autoconfigs, I now see the supervised transfer button, and all looks as it should.

Thank you, I will opt for the upgrade. There are new features I think will be useful and we only purchased the license a few weeks ago.

In the install documentation, it states to "upgrade" an existing install, to simply install over the old version...Is this still the case, when using the elastix-specific RPM install? Or do you reccommend uninstalling the RPM and doing a fresh install from source?

This thread is a continuation from a discussion started in a different thread. I thought it would be best to start it on its own.
The problem is that after upgrading to Elastix 2.5, I get database "parking lot" errors. (original thread)

I thought after the most recent uninstall / reinstall of FOP2 from the elastix addons fixed the problem, but it has returned.

If I make a config change to the pbx, I get errors when trying to "apply" changes, if I uninstall FOP2 then the pbx will apply changes without error.

The suggestion was to upgrade FOP2 via tarball rather than use the market provided RPM version....which sounds good since that version is outdated...but my question then is, Will I have any liscense issues doing that? or will the new install recognize the current liscensing? Also, I am a bit of a noob, so can you walk me through the recommended process of installing from Tarball?

I had a similar problem the other night. I upgraded to Elastix 2.5 (from 2.4 release 8) and that broke FOP2... More importantly, any changes I made in the PBX would throw errors when I tried to "apply" them.

That is the reason I registered for this forum. While waiting for my registration to be approved, I uninstalled FOP2 from the Elastix addons and that seemed to fix the PBX issues.

I then rebooted and installed FOP2 again, and FOP2 worked, but the PBX would still throw an error about selecting parked calls from the database whenever I attempted to apply changes...so i uninstalled FOP2 again until I could reach support about the issue.

Anyway, as of this morning, In preparing to document the issue for support, I re-installed FOP2 again (and it seems there was a repository update this time) in which the installation seems successful. FOP2 is running, and PBX changes are applying without errors.