Hi Gavin,

I already replied on the other post, the Invalid Session is an Elastix error, not a fop2 error. Remove the index.php, upgrading the Elastix rpm from the fop2 tarball will cause other inconsitsencies as the Elastix rpm version is deeply integrated into Elastix itself (the phonebook is the one from elastix, not the one included in fop2, it requires an open session with elastix and it auto login the fop2 based on elastix credentials, etc..).

But the fix is quite easy, remove the index.php file so the native index.html from fop2 takes over. Regarding Firefox 11, you still need to disable websockets if you connect via https, and when using elastix that is the case. So be sure to set disableWebSocket=true in presence.js

Best regards,

Hi Guys
I'm getting a similar issue here.

I can log into FOP2 fine - using Firefox11.
However a collegue using Chome, cannot.
He types:
xxx.xxx.xxx.xxx/fop2
and the page automatically redirects to
https://xxx.xxx.xxx.xxx/fop2/
And shows him "Invalid Session" in the page.

Here's the thing though. Mind is a fresh new install of Elastix 2.3.0-6 and I installed FOP2 from the addons page. Then Revoked my old registration code from my old Trixbox, and registered it on the new Elastix box.

So in theory, there's no upgrading been going on at all.

Help.....

Cliff.

The invalid session is an error from ELASTIX, that *REQUIRES* you to be logged into Elastix in order to open up FOP2. If you can bypass that, you will have to go manually to

https://your.server/fop2/fop2.html

Best regards,