Fop2 on Centos 6 64-bit

nicolas

Hi,

Please read the last question in the FAQ for a solution:

http://www.fop2.com/documentation-faq.php

Best regards,

gspence

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?

nicolas

Hmm, I do not want to contradict anyone. But what you describe does not make sense. Communications between FreePBX GUI and Asterisk is done via AMI, libcrypto is not being used at all for that. Perhaps you changed the asterisk AMI password without modifying the freepbx config files? The symlink works without breaking anything, but you have to do the correct symlink. FOP2 version 2.27 does not have that issue, you can try that version out, altough is currently in beta

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

Best regards,

gspence

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

pezzz

[quote]
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[/quote]

Would very much like a 32 bit version as well.
My problem is a little different in that when i do a reload, there is no operator.cfg file and i get a continuous login loop on the web interface for fop2

nicolas

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,

pezzz

Hi Nicolas,
I tried again on a fresh install of FreePBX Distro 2.210.62-5 and I get the same thing.
I have setup 3 extensions, all with voicemail access numbering 2000,2001,2002 and passwords 123789 (not real extensions or passwords listed) and each time i try to login to fop2 i get the login box come back.
Interstingly when using the chrome extension i currently have scrolling around the icon Invalid Credentials.
I have double checked and triple checked .. even made then 1234 for each and all to no avail.
When i put into the CLI service fop2 restart, i get the below come up.

[root@localhost ~]# service fop2 restart
Shutting down Flash Operator Panel 2:                      [  OK  ]
grep: /var/www/html/panel/op_server.cfg: No such file or directory
Starting Flash Operator Panel 2:                           [  OK  ]
[root@localhost ~]#

I downloaded FOP2 through the FreePBX repos via yum install fop2-fpbx

Any Help would be much appreciated.
Pezzz

nicolas

Hi,

If you configure by hand, you MUST remove the last #exec line that will generate a new set of users with probably different passwords.

#exec is not commented, is a command, and whatever is output by that script will override anything you wrote above that config file.

If you are prompted for user/password again, then you are entering bad credentials. It is not related to versions, platform, nothing. it is just plain bad credentials.

Best regards,

pezzz

Hi Nicolas,
I have done nothing by hand.
My install procedure is as follows:
Installed freepbx distro as noted above
Ran yum install fop2-fpbx
Installed module
Created extension with voicemail enabled
Extension number 2000
Extension Password abc123test
Voicemail Password 123789

When I go to http://IP.of.freepbx.server/fop2 I get login prompt.
I use username of 2000
Password of 123789

Says attempt 1 then reopens the login box again.
I test same thing on my centos 5.8 based freepbx here and works flawlessly.

Any idea?
Pezzz

gspence

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.

gspence

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?

nicolas

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.

gspence

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.

nicolas

[quote]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.[/quote]

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,

gspence

[quote][quote]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.[/quote]

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,[/quote]

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...

pezzz

Sorry guys.. for some reason i was not notified there was a reply and i just thought i would check in.....
The server is not available for me to test right now (test server running on laptop loaned to customer) but i will check that.
The extensions were in fact created after FOP2 was installed so that is probably it.
Is there no way for FOP2 to query extension lists say each time it loads? Then as an admin after adding abunch of extensions (new department started for example with 15 users) you would only have to open FOP2 once and login once rather than go and add users in individually.
Does this make sense?

I guess this has been bought up before but not sure so thought i would suggest.

Will let you know if adding users manually makes it all work
Thanks again.

nicolas

Actually, having NO users added into fop2 when a new extension is created was done on purpose. Not everyone wants to open fop2 to every extension on their companies.

pezzz

Fair enough .. i can see how that would be useful for large companies. And i guess that really only the receptionist and a few key people need to see what is going on.

By the way, i added the users manually and all worked a treat.
Thanks again for a great panel.

sd9204

I have Asterisk 11.2.1 on Centos 6.4, i installed the centos 64 bit version and it works fine, however now my asterisk gui is acting funny. i can get to my gui via the ipaddress in a web browser, clicking on the admin icon brings up the password prompt as normal. after entering the password it takes me to the status screen, but its arranged differently now, more so in a text format and not the dashlet format as before. the menu dropdowns are still at the top as before, they drop down fine, but when i select any menu option out of any of the drop downs, im taken to the main page with the admin icon, user console, operator console and support icons. clicking on the admin icon prompts a password again. now, asterisk seems to be working fine, and i can ssh into it no problem. i think i broke the gui somehow. suggestions?

nicolas

FOP2 does not touch any of your GUI configuration files at all and in any way. Whatever you did to break the GUI is probably not related to FOP2 itself.

One thing you might want to check is that your admin manager password was not changed in /etc/asterisk/manager.conf. If you change that password, and forget to change it also on your GUI configuration files (like /etc/amportal.conf or similar), then things will work quite badly.

Best regards,

FOP2 Community Forum

Fop2 on Centos 6 64-bit