Hi, again. I've spent a week trying to get asterisk to work on FreeBSD unix, with some success. Everything works until I plug the box into the TELCO line and then the line goes off-hook and stays that way. So I bit the bullet and decided to install the application on a fresh linux install. Not to start an OS war, here, but linux is ... difficult ... for an old unix hand to get his mind around. It's a completely different landscape! And why is it that /etc/modules.conf in one release is /etc/modprobe.conf in another? Is this beast not based on standards? But I digress. I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did. At least with unix I was able to get a dial tone! Not so much with this flavor of linux. Each time I run "modprobe wcfxs" I get the following errors in /var/log/messages: Jan 5 17:57:59 asterisk wait_for_sysfs[2782]: either wait_for_sysfs (udev 039)needs an update to handle the device '/class/zaptel/zap1' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> Jan 5 17:57:59 asterisk wait_for_sysfs[2784]: either wait_for_sysfs (udev 039)needs an update to handle the device '/class/zaptel/zap2' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> Jan 5 17:57:59 asterisk wait_for_sysfs[2786]: either wait_for_sysfs (udev 039)needs an update to handle the device '/class/zaptel/zap3' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> Jan 5 17:57:59 asterisk wait_for_sysfs[2788]: either wait_for_sysfs (udev 039)needs an update to handle the device '/class/zaptel/zap4' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> I'm not so interested in notifying these guys at lists.sourceforge.net, since I'm only interested in running asterisk. Once I commit to actually using linux I might participate in their forum, but not yet :) So ... the question: What flavor of linux does asterisk actually run on "Out the box?" I'm not scared to compile asterisk, but I'm not at all interested in recompiling a linux kernel. Of course if that is the only way, then I guess I'll just bite another bullet. Hell! I want this PBX to work so bad that I can almost taste it! Please advise. lane
Lane wrote:> Hi, again. > > I've spent a week trying to get asterisk to work on FreeBSD unix, with some > success. Everything works until I plug the box into the TELCO line and then > the line goes off-hook and stays that way. > > So I bit the bullet and decided to install the application on a fresh linux > install. Not to start an OS war, here, but linux is ... difficult ... for an > old unix hand to get his mind around. It's a completely different landscape! > And why is it that /etc/modules.conf in one release is /etc/modprobe.conf in > another? Is this beast not based on standards?I think you mean conf.modules vs modules.conf, which are there for backwards compatibility. Yes, I concur they should stick with one or the other to not confuse newbies, but tell that to all the linux maintainers :)> > But I digress. > > I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did.There's your first problem :) Try Gentoo or Slackware.> > At least with unix I was able to get a dial tone! Not so much with this > flavor of linux. Each time I run "modprobe wcfxs" I get the following errors > in /var/log/messages:Did you read the docs, check the mailing lists and the wiki for information on kernel 2.6? you will have to issue 'make linux26' for that to work. Also, since the cvs release as of Nov 9th, it's now modprobe wctdm, not wcfxs> So ... the question: What flavor of linux does asterisk actually run on "Out > the box?"Many of them, but you will have to do some reading first. Or try one of the Asterisk Live cd's, or customized ISO installers.> > I'm not scared to compile asterisk, but I'm not at all interested in > recompiling a linux kernel.You are going to have to get your hands dirty if you wish to accomplish anything productive. Or, hire a consultant. Matt -- Matt Gibson VOIP Administrator NJ Tech Solutions 1.314.480.4550 ex. 6400 1.877.999.4678 ex. 6400
A good alternative would be to try a free rebuild of RedHat Enterprise Linux, for example www.taolinux.org. Just use the 32 bit version, the 64 bit version (if you would have the cpu) gives me trouble compiling the kernel modules. With 32 bit Tao it runs almost out of the box and works like a charm. You get the (community) support, the updates, just not the RHEL bill :) Fedora is way too experimental for any system you would want to be stable IMHO. Choosing any free RedHat EL rebuild is a safe, conservative and widely supported choice and easy to install (lots of docs) Cheers! On Wed, 5 Jan 2005, Lane wrote:> Hi, again. > > I've spent a week trying to get asterisk to work on FreeBSD unix, with some > success. Everything works until I plug the box into the TELCO line and then > the line goes off-hook and stays that way. > > So I bit the bullet and decided to install the application on a fresh linux > install. Not to start an OS war, here, but linux is ... difficult ... for an > old unix hand to get his mind around. It's a completely different landscape! > And why is it that /etc/modules.conf in one release is /etc/modprobe.conf in > another? Is this beast not based on standards? > > But I digress. > > I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did. > > At least with unix I was able to get a dial tone! Not so much with this > flavor of linux. Each time I run "modprobe wcfxs" I get the following errors > in /var/log/messages: > > Jan 5 17:57:59 asterisk wait_for_sysfs[2782]: either wait_for_sysfs (udev > 039)needs an update to handle the device '/class/zaptel/zap1' properly (no > device symlink) or the sysfs-support of your device's driver needs to be > fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> > Jan 5 17:57:59 asterisk wait_for_sysfs[2784]: either wait_for_sysfs (udev > 039)needs an update to handle the device '/class/zaptel/zap2' properly (no > device symlink) or the sysfs-support of your device's driver needs to be > fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> > Jan 5 17:57:59 asterisk wait_for_sysfs[2786]: either wait_for_sysfs (udev > 039)needs an update to handle the device '/class/zaptel/zap3' properly (no > device symlink) or the sysfs-support of your device's driver needs to be > fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> > Jan 5 17:57:59 asterisk wait_for_sysfs[2788]: either wait_for_sysfs (udev > 039)needs an update to handle the device '/class/zaptel/zap4' properly (no > device symlink) or the sysfs-support of your device's driver needs to be > fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> > > I'm not so interested in notifying these guys at lists.sourceforge.net, since > I'm only interested in running asterisk. Once I commit to actually using > linux I might participate in their forum, but not yet :) > > So ... the question: What flavor of linux does asterisk actually run on "Out > the box?" > > I'm not scared to compile asterisk, but I'm not at all interested in > recompiling a linux kernel. > > Of course if that is the only way, then I guess I'll just bite another bullet. > Hell! I want this PBX to work so bad that I can almost taste it! > > Please advise. > > lane > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
On Wed, 2005-01-05 at 18:14 -0600, Lane wrote:> Hi, again. > > I've spent a week trying to get asterisk to work on FreeBSD unix, with some > success. Everything works until I plug the box into the TELCO line and then > the line goes off-hook and stays that way. > > So I bit the bullet and decided to install the application on a fresh linux > install. Not to start an OS war, here, but linux is ... difficult ... for an > old unix hand to get his mind around. It's a completely different landscape! > And why is it that /etc/modules.conf in one release is /etc/modprobe.conf in > another? Is this beast not based on standards? > > But I digress. > > I chose FC3 (FePersonally, I've never had a problem with Debian. Use the testing version (as opposed to unstable or stable). I suspect this should work quite painlessly. PS, In my experience, RH is quite 'loose' with the 'standards' while debian tends to be quite strict. Also, regardless of which distro you choose, it will be quite different to FreeBSD, I walked into a job with a bunch of FreeBSD servers having only experience on Linux, and, while it is different, unusual, and seemingly stupid at times how things are done, eventually you will see the good sides as well. <off topic rambling> There is something about "make world" that I just really liked.... However, I never did like the lack of information in /proc on FreeBSD, nor the lack of lots of 'standard (on linux)' tools that are so helpful. So, overall, there are some things better done in linux, and some better in FreeBSD, but since we can't live on both sides of the fence, you gotta take the good with the bad... </off topic rambline> Regards, Adam
>I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did. > >I setup an asterisk server on FC3 without any problems using with some help from the wiki. http://www.voip-info.org/wiki-Asterisk+Fedora+Core+3 It doesn't require a kernel compile, just a few conf file changes and a different make command when building the zaptel drivers, because of the 2.6 kernel udev system>I'm not so interested in notifying these guys at lists.sourceforge.net, since >I'm only interested in running asterisk. Once I commit to actually using >linux I might participate in their forum, but not yet :) > >So ... the question: What flavor of linux does asterisk actually run on "Out >the box?" > >I'm not scared to compile asterisk, but I'm not at all interested in >recompiling a linux kernel. > >
Lane wrote:> Hi, again. > > I've spent a week trying to get asterisk to work on FreeBSD unix, with some > success. Everything works until I plug the box into the TELCO line and then > the line goes off-hook and stays that way.I wasn't able to get the zaptel stuff working under 5.3, but that has more to do with me running the amd64 port, but I do understand it works. I think the FreeBSD port is a little behind the Linux stuff.> So I bit the bullet and decided to install the application on a fresh linux > install. Not to start an OS war, here, but linux is ... difficult ... for an > old unix hand to get his mind around. It's a completely different landscape!I've been a BSD guy for years and I had not really been interested in learning Linux, but everyone seems to want to see that on your resume. I finally got the opportunity to start working with RedHat 7.3 in production about a year ago (not for * mind you). I also used Red Hat Enterprise and played a little with Fedora. All I can tell you is it will be easier if you _embrace_ Linux and learn it. I find things much easier to resolve now that I understand how things are wired under the hood. I'm still a BSD guy, but as someone else pointed out there are pros and cons to both.> But I digress. > > I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did.Well I must say that the Core 3 release is much closer to production stable than any of the previous releases, I'm pretty impressed with how well the OS is put together in comparison to RHES (which sort of comes from Fedora anyway). I've gotten everything to work so far, but it did take some reading and really had more to do with learning * than Fedora.> At least with unix I was able to get a dial tone! Not so much with this > flavor of linux. Each time I run "modprobe wcfxs" I get the following errors > in /var/log/messages:The problem seems that you may not have updated your system, this is a udev issue that's fixed in an update. If you're not familiar with up2date and this is a test system, you might want to install a full system and use Gnome (like windows) or KDE so you can get exposure to the system. You also need to modify the init.d script to load the modules with the correct *mod* commands (like you said, all Linuxes are a little different). Here's a good pointer page for FC3, I wish I saw it before I figured it out myself... http://voip-info.org/tiki-index.php?page=Asterisk%20Fedora%20Core%203#comments> I'm not so interested in notifying these guys at lists.sourceforge.net, since > I'm only interested in running asterisk.They already know and fixed it : http://lwn.net/Articles/111858/?format=printable> So ... the question: What flavor of linux does asterisk actually run on "Out > the box?"None. As a BSD guy you should know nothing just runs out of the box ;-) Although ports does a good job.> I'm not scared to compile asterisk, but I'm not at all interested in > recompiling a linux kernel.Not needed, you just need to download the SRPM (that matches the updated kernel, at this time is kernel-2.6.9-1.724_FC3) install it (rpm -ivh kernel-2.6.9-1.724_FC3.src.rpm) and follow the instructions on the wiki page above. All you're doing is the equivalent of "make depend" to update/create a header file.> Of course if that is the only way, then I guess I'll just bite another bullet.Keep an open mind, that's all I can say. At this point I like the RedHat based Linux distro. Others are also good, some more suited to desktop or server, but I believe that RedHat is one of the leading distros in terms of community/commercial support, much the same way FreeBSD is over Net/Open BSD.> Hell! I want this PBX to work so bad that I can almost taste it!Been there, I've got dialtone now and have both TDM400P FXO/FXS ports working. Chris