Asterisk 1.8 package
-
Rebooted again and everything started succesfully
This time I waited a little longer before logging into the webinterface.
Maybe the problem is related with logging into soon after a reboot (interfering with processes still starting in the background) -
matthijs,
After rebooting, pfSense normally needs a bit "patience/time" to autostart all services …
P.S : Agree ! doktornotor ;)
-
Package seems to be broken..
install on new 2.2.2 -> asterisk dont start
after apply Bastions dirty workaround ends up with -> no asterisk_enable in rc.conf after manual add-in in rc.conf -> pam_error
-
Update:
after make a new /etc/rc.asterisk an put asterisk_enable=YES into it … it works again
-
I just installed Asterisk on PfSense 2.2.2.
I ran into some of the problems mentioned in this thread.
These are my notes on solutions to the problems.1. Installation
Installation takes a long, long time (on my box, about 24.5 minutes AFTER download is complete).
You can't see what's going on in the web UI.
I recommend enabling ssh, logging in to ssh and issuing the following command at the ssh command prompt:pfSsh.php playback installpkg Asterisk
After a few minutes it will say 'Done' and the cursor will remain at the end of that line.
It isn't done: it's just done with the download.
Wait until it's really done – you'll know from the console output. Be patient.I'm not sure if this method installs the PfSense GUI stuff.
If, after this step, you don't have an Asterisk entry in the PfSense Status menu, go to
System->Packages and under Installed Packages->Asterisk click on the 'xml' button.2. Post-install fixes
First, do this stuff:
https://forum.pfsense.org/index.php?topic=47210.msg490067#msg490067
Next, to fix the Asterisk log warnings about res_snmp.so and libperl.so, do the following:
-
under Diagnostics->NanoBSD set Media Read/Write status to Read/Write
-
log in with ssh, start a shell and cd to /usr/pbi/asterisk-<arch>/local/lib
note: replace <arch>with i386 or amd64, depending on your system -
issue the following command at the ssh command prompt:
ln -s perl5/5.18/mach/CORE/libperl.so -
under Diagnostics->NanoBSD set Media Read/Write status to Read-Only
-
under Status->Asterisk->Log press 'Clear log'
-
under Status->Asterisk->Commands press 'Restart Asterisk'
-
under Status->Asterisk->Log check the log; there should be no WARNINGs
Hope this helps. I wanted to summarize everything in one place.</arch></arch>
-
-
Hi,
first thanks for the hard work everyone is putting into this, I migrated over to Pfsense several months ago and I've come to enjoy the flexibility available. Now after the Asterisk update a couple of months ago the module chan_sccp.so no longer works, I was relying on a pre-built deb package. Can someone please build the module to support the latest build of pfsense and asterisk.
Thanks in advance.
-
The package installation failed on pfsense 2.2.3 i386 :-\ help plz!!!
-
I Have the Asterisk Package Installed (0.3.1) on my pfSense system (2.2.2-RELEASE (amd64)) but there does not seem to be any of the modules installed. The config file suggests "/usr/local/lib/asterisk/modules" would be the place, but that directory does not exist.
This means things like musiconhold won't work.
Have I missed something out when installing this package?
Regards
Ben
-
I Have the Asterisk Package Installed (0.3.1) on my pfSense system (2.2.2-RELEASE (amd64)) but there does not seem to be any of the modules installed. The config file suggests "/usr/local/lib/asterisk/modules" would be the place, but that directory does not exist.
This means things like musiconhold won't work.
Have I missed something out when installing this package?
Regards
Ben
I have the same package version installed on the same pfSense version, but i386 instead of amd64.
Yes, according to asterisk.conf the modules directory is /usr/local/lib/asterisk/modules.
No, that directory doesn't exist on my system either.
But Asterisk works fine.
If no modules were being loaded Asterisk would be basically dead.
Are you speculating that something will not work if you attempt it, or have you actually observed that Asterisk does not work?For reference du -h /usr/pbi/asterisk-i386 reports 472MB. amd64 should be somewhat larger.
EDIT:
To see what modules are loaded issue the following command at the Asterisk CLI prompt:module show
-
The asterisk.conf references the chrooted paths. (For details on PBI junk, search this forum…)
-
If no modules were being loaded Asterisk would be basically dead.
Are you speculating that something will not work if you attempt it, or have you actually observed that Asterisk does not work?For reference du -h /usr/pbi/asterisk-i386 reports 472MB. amd64 should be somewhat larger.
EDIT:
To see what modules are loaded issue the following command at the Asterisk CLI prompt:module show
Your right, lots of modules are loaded. What does not work for me is the music on hold command. Thats when I started looking and found the modules directory missing.
-
Please help me to install Asterisk-GUI on PFsense. I'm a newbie on this. My Pfsense box version is:
2.2.1-RELEASE (amd64)
FreeBSD 10.1 -
Please help me to install Asterisk-GUI on PFsense. I'm a newbie on this. My Pfsense box version is:
2.2.1-RELEASE (amd64)
FreeBSD 10.1I assume you are referring to the old Asterisk GUI developed by Digium.
Before doing anything take a look at this page:https://wiki.asterisk.org/wiki/display/AST/Asterisk+GUI
There is no pfSense package for Asterisk GUI. Someone would have to make one, assuming it would be practical to run Asterisk GUI on pfSense (maybe not).
Alternately, Asterisk GUI doesn't need to run on the same machine that Asterisk runs on – it communicates with Asterisk via AMI. A more practical approach would be to build and run Asterisk GUI on a separate UNIX/Linux box, if you have one.
Note: I have never used Asterisk GUI. If you read the web page linked above you'll know as much about it as I do.
Personally, I just configured Asterisk manually. Now I know what goes on "under the hood."
-
Thanks Carlm for your advice.
-
Another one of many reasons to stick with 2.1.5
If you are serious about VoIP, 2.1.5 has working limiters, working asterisk (nice redundancy even if you do/should have another box or VM behind pfsense)
Strange, too , how hard it is to find old versions…..
:( >:( >:(
-
Strange, too , how hard it is to find old versions…..
Ok, so there isn't a big button on the download page saying 'old versions', but is it really that hard to look in the folder marked 'old' on the download mirror?
There are a few situations where you might want 2.1.5, but for most people 2.2.4 is better. -
I started out w/ v 0.3.1 of the Asterisk package.
Others have commented that this version is much larger than the previous version.
Anyone know what accounts for the size increase?
Anything to do with the gcc48 stuff? Is that stuff necessary?Whenever I have to reinstall Asterisk (e.g., restore a previous config) it takes about 25 minutes to untar the Asterisk .pbi. I'm running nanoBSD i386 with a SanDisk 8GB Class 4 microSD card. Was about the same with a Kingston Class 10 card. A much smaller .pbi would really help, unless there's a way to speed up the untar operation (permanent R/W on nanoBSD??).
Thanks!
-
Until pfSense 2.3 some packages will work better(and smaller) if you isntall via gui and then via console remove the pbi and install the freebsd package via pkg install
-
Until pfSense 2.3 some packages will work better(and smaller) if you isntall via gui and then via console remove the pbi and install the freebsd package via pkg install
Maybe I wasn't clear. My primary problem is the time required to reinstall Asterisk when, for instance, I restore a previous pfSense config. Of course, the time to untar the .pbi is proportional to the size of the .pbi, so any significant size reduction would be a significant help.
Your suggestion wouldn't help with the installation time: pfSense would still reinstall the .pbi when it determined it necessary to do so. (Unless you're talking about uninstalling the .pbi. But then I'd lose the Asterisk GUI.)
Also, the Asterisk package is unusual in that has that embedded gcc48 stuff and embedded Perl. The Perl is definitely necessary (res_snmp.so uses it, for one example). I'm not sure how I'd replace the untarred .pbi package with the FreeBSD package and its dependencies, even if it would help with the install time problem.
One more little gotcha: The FreeBSD 10.1 package is a slightly older Asterisk version: 1.8.31.1.
-
1/ No, you don't lose any GUI by removing PBI. (That is NOT the same thing like unstalling the package from GUI.)
2/ Install the latest package version (0.3.2).
