The loca files are not relevant. The troubleshooter tells you to check 3 things:
1) that fop2 server is running
pgrep fop2
it must return a pid number.
2) that is binding to port 4445 and that port 4445 is not filtered or blocked in a firewall
netstat -lnp | grep fop2
to verify port binding, you cannot check network firewalls on the same machine, you can check if you have iptables firewall rules with the command
iptables -vnL
If you see a bunch of rules, be sure you have one allowing tcp port 4445
3) that the flash player is installed and not blocked on your browser. Try with another browser, disable flashblock/adblock, etc.
You did not provide any feedback on what you tried or did, so I cannot help you further. I am almost copying verbatim the troubleshooter guide, please TRY EACH and tell us what are your results.
I have the same issue, but I just noticed using internet explorer on the same machine works while firefox does not anymore.
I am pretty certain firefox just did an update firefox version is 11.0 on Windose 7, I made sure all add-ons are up to date, disabled every one of the add-ons and still see the same issue.
So I am led to believe this is a browser specific issue rather than FOP2 issue.
Now for my little plug! I love FOP2, as a home user with a lot of extensions I can see what is going on, whom is using and doing what.. This is a great addition to my home VOIP solution..
Perhaps adobe flash was not updated with the recent Firefox update? Flash installation is independant from browser to browser, be sure to check that out.
I am not running Firefox 11 so I cannot tell you for sure, another option would be that Firefox 11 is using some kind of problematic websocket implementation, in that case you can edit /var/www/html/fop2/js/presence.js and set disableWebsockets to true.
We also have seen our (previously working) FOP2 installation completely borked by FF 11. Updating to most recent Adobe Flash 11 does not fix the problem. Users can log in with Chrome (version unknown) or IE 8/9, or FF 10 or earlier, but not FF 11. We are currently running FOP 2.24, I haven't tried 2.25 yet.
Also, almost all of my machines are W7 (mostly Pro), and I also have a Win XP machine that has the same problem. Unknown as to whether or not Vista works.
Ok, I have the opportunity to try Firefox 11, and in fact is a websocket implementation issue. For now, you must disable websockets in fop2 presence.js file to make it work with Firefox 11.
I have already fixed the issue in my fop2 trunk version, so the next Fop2 release will work with websockets in Firefox 11.
Websockets is a moving target, specification changes every week/month, browsers are implementing different versions all the time. If you want to stay current with the latest browser, for now it would be wiser to disable websockets on fop2. If you want to have the latest versiones of everthing, you shuld expect this kind of issues with every browser version release, until the websockets specifications stabilizes and the dust settles a bit.
The file is cached on browsers, so a change will not take effect until you hard refresh the file or clear the cache. Try shift-reload or ctrl-reload on the fop2 page, or load the file by hand
Hey, I do have another question. I have 4 trunks within freePBX. FOP2 is only showing 2 of them, all 4 are configured and in use.
1 trunk is for international - FlowRoute (showing)
2 trunks are for Local Long distance - Sipstation (only 1 showing)
1 trunk is a rollover for international - VoipVoip (not showing)
Any thoughts on this? FreePBX shows them all there and running, I can use them, just not showing up in FOP2 up until a couple of days ago. Only thing happened is a few updates on freePBX side.
Interesting, I found if I have a Queue working, it knocks the trunks off the list. Is there a maximum display setting that is stopping them from showing? it would seem the more info there is on the right side, the less trunks get shown.
Same problem immediately after upgrading to 11.0 Firefox.
Solution was:
Change disablewebsocket to true
restart fop2 ( "service fop2 restart" from your # prompt on linux asterisk box )
****and you must reload the fop2 via the "shift reload" in your Firefox browser as
described by Nicolas in these posts. Otherwise you get the same problem.
The stored fop2 code in the cache will not load.
I've cleared cache and restarted the server and continued the same problem in firefox11 ....
only when it is disabled the webSocket in presence.js file that works in firefox11.
Running in the command line does not mean that the running server is that version, you can have a previous version running, download the new version and upgrade (and by not restarting the service, keep the old version running).
I am not saying that this is the case, but could be. And as I said before, it works for me and for several other users using Firefox 11. I am sorry if it does not work for you.
Not working here, every time I try a shift-> reload I get the login prompt again and even http://your.server/fop2/js/presence.js show the change it does not display anything.
one interesting part is that the versions 2.11 works fine. Ill assume that does not support web socket...
I have also try to clear the cache.
is there an update I can download?
Comments
http://support.asternic.biz/index.php?/ ... tep/View/4
Inside the /usr/local/fop2 folder contains below files
-rw-r--r-- 1 root root 36 Mar 9 09:47 autobuttons.cfg
-rwxr-x--x 1 root root 8669 Mar 9 09:47 autoconfig-buttons-freepbx.sh
-rwxr-x--x 1 root root 3097 Mar 9 09:47 autoconfig-users-freepbx.sh
-rw-r--r-- 1 root root 1126 Mar 9 09:47 buttons.cfg.sample
-rw-r--r-- 1 root root 123 Mar 9 09:47 extensions_override_freepbx.conf
-rw-r--r-- 1 root root 3001 Mar 9 09:47 FOP2Callbacks.pm
-rw-r--r-- 1 root root 6477 Mar 14 08:59 fop2.cfg
-rw-r--r-- 1 root root 129 Mar 9 10:12 fop2.lic
-rwxr-x--x 1 root root 8435030 Mar 9 09:47 fop2_server
-rw-r--r-- 1 root root 7168 Mar 9 10:11 fop2settings.db
-rwxr-x--x 1 root root 8219 Mar 9 09:47 generate_override_contexts.pl
-rw-r--r-- 1 root root 11817 Mar 9 10:10 NEWFOPoHd8Bz
-rwxr-xr-x 1 root root 6934 Mar 9 09:47 recording_fop2.pl
-rwxr-xr-x 1 root root 6271 Mar 9 09:47 tovoicemail.pl
This file NEWFOPoHd8Bz is generate from FreePBX FOP2 admin.
1) that fop2 server is running
pgrep fop2
it must return a pid number.
2) that is binding to port 4445 and that port 4445 is not filtered or blocked in a firewall
netstat -lnp | grep fop2
to verify port binding, you cannot check network firewalls on the same machine, you can check if you have iptables firewall rules with the command
iptables -vnL
If you see a bunch of rules, be sure you have one allowing tcp port 4445
3) that the flash player is installed and not blocked on your browser. Try with another browser, disable flashblock/adblock, etc.
You did not provide any feedback on what you tried or did, so I cannot help you further. I am almost copying verbatim the troubleshooter guide, please TRY EACH and tell us what are your results.
I am pretty certain firefox just did an update
So I am led to believe this is a browser specific issue rather than FOP2 issue.
Now for my little plug! I love FOP2, as a home user with a lot of extensions I can see what is going on, whom is using and doing what.. This is a great addition to my home VOIP solution..
Perhaps adobe flash was not updated with the recent Firefox update? Flash installation is independant from browser to browser, be sure to check that out.
I am not running Firefox 11 so I cannot tell you for sure, another option would be that Firefox 11 is using some kind of problematic websocket implementation, in that case you can edit /var/www/html/fop2/js/presence.js and set disableWebsockets to true.
Best regards,
Also, almost all of my machines are W7 (mostly Pro), and I also have a Win XP machine that has the same problem. Unknown as to whether or not Vista works.
I have already fixed the issue in my fop2 trunk version, so the next Fop2 release will work with websockets in Firefox 11.
Websockets is a moving target, specification changes every week/month, browsers are implementing different versions all the time. If you want to stay current with the latest browser, for now it would be wiser to disable websockets on fop2. If you want to have the latest versiones of everthing, you shuld expect this kind of issues with every browser version release, until the websockets specifications stabilizes and the dust settles a bit.
http://your.server/fop2/js/presence.js
Read it, do you see the change? No? Try shift-reload.. do you see it? Yes, then log back into fop2 with shift-reload.
Screenies..
Edit:
http://img690.imageshack.us/img690/8701/websockets.png
And I thought I would show my integration of the link in freepbx
http://img31.imageshack.us/img31/5460/fop22.png
Thank you, that worked out great... working like it was before.
I used to like Firefox, but it seems to be getting worse with every release anymore! maybe it is just me?
As an every day browser I personally like Google Chrome better.
But both browsers are riding the websocket rollercoaster now, so you might expect issues with fop2 or any other websocket enabled server.
Hey, I do have another question. I have 4 trunks within freePBX. FOP2 is only showing 2 of them, all 4 are configured and in use.
1 trunk is for international - FlowRoute (showing)
2 trunks are for Local Long distance - Sipstation (only 1 showing)
1 trunk is a rollover for international - VoipVoip (not showing)
Any thoughts on this? FreePBX shows them all there and running, I can use them, just not showing up in FOP2 up until a couple of days ago. Only thing happened is a few updates on freePBX side.
Solution was:
Change disablewebsocket to true
restart fop2 ( "service fop2 restart" from your # prompt on linux asterisk box )
****and you must reload the fop2 via the "shift reload" in your Firefox browser as
described by Nicolas in these posts. Otherwise you get the same problem.
The stored fop2 code in the cache will not load.
Thank you Nicolas.
Gene
about:config
and set:
network.websocket.enabled = false
Anyways, I will release FOP 2.26 probably at the end of this week that will fix websockets for firefox 11.
I update to version 2.26 now and had the same problem in firefox 11.
Only disabling websocket it worked.
FOP 2.26 It works fine in Firefox 11. Perhaps you forgot to restart the fop2 server.
only when it is disabled the webSocket in presence.js file that works in firefox11.
Are you on 2.26?
All I can say: it works for me using Firefox 11. It should work for you.
fop2_server version 2.26
I am not saying that this is the case, but could be. And as I said before, it works for me and for several other users using Firefox 11. I am sorry if it does not work for you.
Best regards,
one interesting part is that the versions 2.11 works fine. Ill assume that does not support web socket...
I have also try to clear the cache.
is there an update I can download?