[Asterisk-bsd] Hello List :) New to Asterisk not new to FreeBSD

[Kim Culhan]

On 12/3/05, webmasterb <webmasterb at gmail.com> wrote:
>
> Hello fellow asteriskers (can i say that?)
>
> My name is Brian.  I'm looking to setup asterisk on a 1.1GB machine with
> 256MB of RAM Using an X100P wildcard (clone? i ordered the devices on EBay).
> When up and running I would like to use this machine with my Vonage VOIP
> connection. To support my young educational non-profit org -> shameless plug
> www.parkday.org.
>
> I have been reading about asterisk for about one month now. I have purchased
> the O'reilly Book "Asterisk: The Future of Telephony" and have read about
> half of it.
>
> First attempt at running asterisk on FreeBSD 6.0 RELEASE resulted in a core
> dump anytime I tried to run asterisk from the cmd line.  Poking around I
> read somewhere?? that asterisk is not quite ready for 6.0 RELEASE just yet.
> Upon reading this I went and re-installed the OS with version 5.4 RELEASE.

IMHO the best way to run asterisk with the zaptel card drivers is as follows:

1) Install FreeBSD 6.0-STABLE

2) Install the latest zaptel-bsd drivers, available via Subversion

3) Install the latest asterisk CVS HEAD available via CVS

Installing FreeBSD 6.0-STABLE is well documented..

If you have already installed asterisk from ports, the port will have installed
the dependencies required for this method, pwlib etc.

To install the latest zaptel-bsd drivers you need to first get the
source via Subversion:

Install subversion from ports, in devel/subversion

To get the latest zaptel-bsd source say:

svn co --username svn --password svn
https://svn.pbxpress.com:1443/repos/zaptel-bsd

The above is all on one line ..compensate for any line breaks.

Run 'make' then 'make install'

You need to make arrangements to load the kernel-loadable modules produced
from the source obtained above.

To do this at boot time, add to /boot/loader.conf:

zaptel.ko_load="YES"
qozap.ko_load="YES"
wcfxo.ko_load="YES"
wcfxs.ko_load="YES"
wct1xxp.ko_load="YES"
wct4xxp.ko_load="YES"
wcte11xp.ko_load="YES"

Next you could compile and install asterisk.

To get the latest source for asterisk CVS HEAD running the csh shell say:

setenv CVSROOT :pserver:anoncvs at cvs.digium.com:/usr/cvsroot
cvs login (it prompts for password, use: anoncvs)
cvs checkout zaptel libpri asterisk

The easiest way to get the asterisk build process to stop
complaining about your libpri being too old is to compile
the libpri source obtained via CVS in the above step.

To compile the libpri source you need to position a copy
of the top-level zaptel-bsd build tree (what is under 'trunk' obtained
via subversion
as described above) under a directory: zaptel on the same level as
the libpri directory. There are other methods, this is easiest..

asterisk source compilation requires the use of gnu make: gmake on bsd systems

gmake then gmake install libpri

asterisk may now be compiled and installed from the CVS source, just say
gmake then gmake install in the asterisk directory

The asterisk build process with CVS source from ~1400 UTC 10-4-05
builds and installs cleanly on FreeBSD 6.0-STABLE

If yours doesn't something is wrong, post to the list describing the problem.

You will probably want asterisk to startup on boot.

To do this you can use something like the following in /usr/local/etc/rc.d:

asterisk.sh

-

#!/bin/sh

# PROVIDE asterisk
# REQUIRE: NETWORKING SERVERS
# BEFORE: DAEMON
# KEYWORD: FreeBSD shutdown

#
# Add the following lines to /etc/rc.conf to enable asterisk:
#
# asterisk_enable="YES"
#

. /etc/rc.subr

name=asterisk
rcvar=`set_rcvar`

command=/usr/local/sbin/asterisk
pidfile=/var/run/asterisk.pid

asterisk_enable=${asterisk_enable:-"NO"}

/usr/local/bin/ztcfg

echo -n " zaptel"

load_rc_config $name

run_rc_command "$1"

-

Don't forget to add this to /etc/rc.conf:  asterisk_enable="YES"

The setup described above produces the most reliable asterisk-on-bsd
I've used so far -hope you find the same to be true.

BTW please excuse the insertion of HTML tags by the gmail editor, I can't
figure out how to turn that stuff off.

Also, it'll probably quote the preceeding threads in some weird way..
sorry about
that chief.

regards
-kim

--
w8hdkim at gmail.com