Hi,

Login credentials are not related to symlinks at all, they are just credentials. FOP2 manages its own tables for login in, if you add extensions after fop2admin was installed, those extensions are not added to fop2, you must add them by hand.

Heh, sorry - should have trimmed the quote - I mean the 32-bit version worked great - I wasn't having issues with the credentials.

No problem!.. back to symlinks then. Version 2.27 should not require any symlinks on centos,debian or ubuntu. I am trying to include all needed libraries on the package to avoid these conflicts.

Best regards,

Odd. I can't remember the exact error that I was getting, but it was similar to what other people were seeing before they ran the symlink on their systems. I was using the most up-to-date version of the FreePBX distro, so I wonder if maybe some of their tinkering caused the symlink to be necessary afterall? Unfortunately the system is now in production otherwise I'd try it again from scratch. It was an anomaly for me to use 32-bit in the first place...

Hi,

Login credentials are not related to symlinks at all, they are just credentials. FOP2 manages its own tables for login in, if you add extensions after fop2admin was installed, those extensions are not added to fop2, you must add them by hand.

Heh, sorry - should have trimmed the quote - I mean the 32-bit version worked great - I wasn't having issues with the credentials.

32 bit version: http://download.fop2.com/fop2-2.27-centos-i386.tgz

If you are prompted for login every time, then there is no problems at all with running the server, but just bad credentials being entered. (incorrect extension/password).

Best regards,

Thanks for this one, Nicolás - it worked. I did still have to create the symlink before it would start properly, though - should that be the case?

Hey Pezzz - try going to the Other -> FOP2 Users menu in FPBX, then enter in the secret for that extension manually.
I think it's because you added the extension after installing FOP2 that it's not picking up the data for the extension. It may even be the case that the extension isn't listed - if so, add it!
As far as I've seen FOP2 doesn't pick these up automatically if they're added after-FOP2 was installed.

http://download.fop2.com/fop2-2.27-centos-x86_64.tgz

Best regards,

That worked like a charm on a freshly installed CentOS 6.2 64-bit FreePBX install that I just put together. Any chance we could get access to a 32-bit version? *sheepish grin*

I ran into this a couple of weeks ago as well. Unfortunately the symlink fix does not work with the FreePBX distro on 64-bit. When you run the command it breaks all communications between FreePBX's GUI and Asterisk. Very bad. Not sure if there might be another workaround available?

No, I don't even have the GUI open most of the time.

I'm wondering if it might be a problem with using the latest version of the FOP2 manager from this website versus FreePBX's repo version?

Finally caught it happening just now. It doesn't just get stuck at a white screen - it actually shows the FOP2 panel every 10 seconds exactly (watched it against a clock) for just a moment (maybe a quarter of a second).

Just confirmed with the staff here - IE is seeing the same thing as well.

I think almost everyone is using Firefox - whatever the most recent version is (16/17?).
The service does not appear to stop, however when I restart ("service fop2 restart") it that seems to fix the issue for a while.

I'll try watching for it in Chrome to see if it happens there too.