FreeSWITCH package for pfSense 1.2.1 and 2.0 released. PBX or Proxy
-
@mcrane:
pfSense FreeSWITCH package version 0.8.1 is now available.
yayyyy!
0.8.0 went BOOM!!!Update:
Actually both my systems went boom on even the 0.8.1 update.. Won't start up due to line errors on freeswitch.incHere is some more info from the status page….
unable to connect to 68.XXX.XXX.XXX:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 Warning: fsockopen(): unable to connect to 192.168.0.3:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 no handleUpdate 2:
ok, I crashed my test machine by editing the backup and restoring (that's why it's a test machine).
Anyways, fresh install of pfsense 1.2.2
Freeswitch installs with the above errors.So I'd say it's temporarily broken.. Do not update!!
-
After update to FreeSWITCH 0.8.1:
Service Freeswitch does not start and nothing is written to the log.
-
@oln:
After update to FreeSWITCH 0.8.1:
Service Freeswitch does not start and nothing is written to the log.
I am having the same issues.
-
No issues here on 2.0 (other than the unrelated php xml bugs we're fighting in 2.0).
–Bill
-
-
I can confirm this behavior. When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC). Removing this file or creating it ahead of time with world-writable permissions had no effect.
I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface. So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).
-
I can confirm this behavior. When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC). Removing this file or creating it ahead of time with world-writable permissions had no effect.
I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface. So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).
Interesting just upgraded to latest nightly snapshot and still no freeswitch for me..
-
So I guess the common theme is
1. If you are running 1.2.1 or 1.2.2. DO NOT UPGRADE TO THE LATEST VERSION. Until we hear back from mcrane
2. If you are running 1.2.3 or 2.0 take your own risk if you want. It may/may not work.
3. If you upgraded already and it's crashed your freeswitch, then we are out of luck until mcrane comes up with something..wait…
-
The system I'm running is working fine on pfSense 1.2.3.
I'm currently on IRC at #pfsense-freeswitch. Those with problems please contact me there and I will help you get your systems working. As the problem is identified I will get it fixed in the package.
Mark
-
I updated my test 1.2.2 machine to 1.2.3 (today's build) and freeswitch was a no-go just like 1.2.2
I then updated to 2.0 and it looked like it was running (service was running) but I could not get to it from the web admin page. That does not say much to me, as when I rebooted I could not get to even the login page. I count that as a pfsense issue.
I then reinstalled a fresh copy of 1.2.3 (not upgrade as in 1st attempt). Still no go (even after reboot).
Service won't start…
So it's either that some 1.2.3 build let freeswitch work, while the new build does not. That or it's related to a specific hardware that it's working/not working.
I don't have too much of specialized hardware. Main pfsense is an AMD Sempron LE-1150, 1 VIA onboard NIC, 1 Intel PIC NIC.
Other test machine is an ATOM 330 with 2 realtek NICS (yah they suck, but it's a test machine)Maybe you can go back to older and freeswitch build until the 0.8 bugs are worked out?
-
Running 2.0-ALPHA-ALPHA built on Thu Jan 15 23:00:25 EST 2009 FreeBSD 7.1-RELEASE-p2 still here.
latest freeswitch package installed fine for me. Running now…
-
Mcrane is working on resurrecting an older version for us 1.2.2 guys- this is a known bug for FS and freebsd 7.0..
I'll be happy to test and confirm… ;D ;D
-
I have a work around until the bug is fixed for FreeSWITCH on FreeBSD 7.0 (pfSense 1.2.1 or 1.2.2)
Once you have the package installed go to Diagnostics -> Command -> PHP Execute then run the following commands. The following PHP code will download a FreeSWITCH build from Jan 2009 and replace the build that comes in the package. (please note this is not the entire install procedure so you must have the package already installed)
require_once("config.inc");
require_once("/usr/local/pkg/freeswitch.inc");
exec("cd /tmp/;fetch http://portableusbapps.com/packages/config/freeswitch/freeswitch.1.jan.2009.tgz");
exec("cp /tmp/freeswitch.1.jan.2009.tgz /tmp/freeswitch.tgz");
unlink_if_exists("/tmp/freeswitch.1.jan.2009.tgz");
freeswitch_php_install_command(); -
I'm running 1.2.3 from Feb 18th and I also couldn't get the new FS package working. Mcrane's php fix worked for my system; I'm back up now.
This issue brings up an interesting scenario that pfSense really needs some type of version control for packages, or at least a "roll back" feature (sorry to use a M$ term).
Thanks for fixing this Mcrane; I bet that was a lot of work.
-
Thank you, the workaround works for me
Bye
-
working like a charm on 1.2.2 now to get this thing configured.. ???
-
mcrane, you mention 1.2.2 and 1.2.1. I seem to have this issue on my now 1.2.3 test machine also (others seem to also have this problem).
I also see an updated version available. Does that mean the updated version is for 1.2.3 / 2.0 and the workaround script is for the 1.2.1/1.2.2 versions?Ditto with the others. Tonight it's back to where I left off, that damm internal setting so my extensions can talk to each other…...
-
I am on 1.2.2, the script did not help. I am still facing with the same issue.
-
Freeswitch Version 0.8.3.1
1 Test Machine 1.2.3 Yesterday's build. Now up and running
1 Production machine 1.2.2 - No go as advertisedOn 1.2.2 used the supplied script…
Worked as advertised! Wohooo... back to playing!Now that I've tested 1.2.3 I'm even tempted to switch the production machine.....
-
Need Help:
For those that still need help catch me on #pfsense-freeswitch irc channel. New to IRC I recommend using chatzilla which is a simple Firefox add on then just search for the #pfsense-freeswitch channel and join it.Backup Package:
I am planning on building a pfSense backup package that will be designed to backup whatever package files are desired. It will be designed to create a single tgz backup file for any directories that are listed to backup. Such a backup package could be used to "roll back" a package.It would also be useful to back pfSense, FreeSWITCH, TFTP files, RRD graph data, logs, and any other future packages.
Trouble Shooting Tip:
If you are having problems starting FreeSWITCH then the following will help you see what is wrong.
1. Enable SSH on pfSense
2. Connect to the console or through SSH
3. cd /usr/local/freeswitch/bin
4. check to see if freeswitch is running with the following:
ps -waux | grep freeswitch
5. start FreeSWITCH from the console
./freeswitch
Watch for immediate errors an execution ending or red errors that indicate something has gone wrong.If you FreeSWITCH is running and you want to connect to monitor the console
1. cd /usr/local/freeswitch/bin
2. Replace the 192.168.1.1 with your LAN IP address.
./fs_cli -H 192.168.1.1
