[App_rpt] Asterisk segfaults after installation

I've been trying to install Asterisk on a CentOS 4.4 box for a while, but not with much luck. I got Asterisk compiled and the software installed. After a couple of issues finding the right kernel-devel package for my kernel, all seemed to install fine. I also installed chan_rtpdir (v 0.2 so far, though now I will need 0.5). However, when I try and start Asterisk, I get a segfault if there is anything at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon as I uncomment any line, then Asterisk dies with a segfault on the second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first pass and then dies on the second pass. For the record, I recompiled chan_rtpdir on my system to avoid library/compiler issues, which I did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an existing Asterisk box? I'm running no RF hardware on Asterisk at this stage. All paths to RF are via the rtpDir link. Eventually, I might add a remote base directly to Asterisk, or move the RF hardware to Asterisk.

73 de VK3JED
http://vkradio.com

Does it leave a core dump around? Anything useful come from an analysis of that? If you aren't sure about how to handle that, you must compile with debug symbols turned on as a start, and then use gdb or other tools. A quick google on "linux core file analysis" should give you something useful. If you can track down where it is dying it surely will help figure out why.

  Steve

···

On Jul 27, 2008, at 2:05 AM, Tony Langdon, VK3JED wrote:

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

Tony,

I suppose the segfault could be backtraced and the results posted here
along with the versions of app_rpt, asterisk, libpri and zaptel but I'd
like to suggest a possible alternate course of action.

Getting the right versions of all of this software, building it from
source, and getting it all to work together without subtle problems can
be a labor of love.

I hear you about not wanting to re-install a whole system from scratch.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

Steve
WA6ZFT

Tony Langdon, VK3JED wrote:

···

I've been trying to install Asterisk on a CentOS 4.4 box for a while,
but not with much luck. I got Asterisk compiled and the software
installed. After a couple of issues finding the right kernel-devel
package for my kernel, all seemed to install fine. I also installed
chan_rtpdir (v 0.2 so far, though now I will need 0.5). However,
when I try and start Asterisk, I get a segfault if there is anything
at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I
was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first
pass and then dies on the second pass. For the record, I recompiled
chan_rtpdir on my system to avoid library/compiler issues, which I
did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an
existing Asterisk box? I'm running no RF hardware on Asterisk at
this stage. All paths to RF are via the rtpDir link. Eventually, I
might add a remote base directly to Asterisk, or move the RF hardware
to Asterisk.

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Tony,

Here's some additional information to go along with my previous message.

1. After compiling and installing files.tar.gz, use the initial config
files in the /usr/src/configs and ./usr/src/configs/usbradio directory
to /etc/asterisk then
move file zaptel.conf to /etc.

2. files.tar.gz currenly comes with chan_rptdir version 0.2. After you
have resolved the segfaulting issue, you'll need update the source file
to version 0.5.

Steve
WA6ZFT

Tony Langdon, VK3JED wrote:

···

I've been trying to install Asterisk on a CentOS 4.4 box for a while,
but not with much luck. I got Asterisk compiled and the software
installed. After a couple of issues finding the right kernel-devel
package for my kernel, all seemed to install fine. I also installed
chan_rtpdir (v 0.2 so far, though now I will need 0.5). However,
when I try and start Asterisk, I get a segfault if there is anything
at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I
was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first
pass and then dies on the second pass. For the record, I recompiled
chan_rtpdir on my system to avoid library/compiler issues, which I
did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an
existing Asterisk box? I'm running no RF hardware on Asterisk at
this stage. All paths to RF are via the rtpDir link. Eventually, I
might add a remote base directly to Asterisk, or move the RF hardware
to Asterisk.

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Why not just use Jim Dixon's SVN branch on Digium's servers? I would
think that would be the cleanest, easiest, and most up to date code.

svn checkout http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4

Thanks,
Steve Totaro

···

On Sun, Jul 27, 2008 at 11:34 AM, Stephen Rodgers <hwstar@rodgers.sdcoxmail.com> wrote:

Tony,

Here's some additional information to go along with my previous message.

1. After compiling and installing files.tar.gz, use the initial config
files in the /usr/src/configs and ./usr/src/configs/usbradio directory
to /etc/asterisk then
move file zaptel.conf to /etc.

2. files.tar.gz currenly comes with chan_rptdir version 0.2. After you
have resolved the segfaulting issue, you'll need update the source file
to version 0.5.

Steve
WA6ZFT

Tony Langdon, VK3JED wrote:

I've been trying to install Asterisk on a CentOS 4.4 box for a while,
but not with much luck. I got Asterisk compiled and the software
installed. After a couple of issues finding the right kernel-devel
package for my kernel, all seemed to install fine. I also installed
chan_rtpdir (v 0.2 so far, though now I will need 0.5). However,
when I try and start Asterisk, I get a segfault if there is anything
at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I
was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first
pass and then dies on the second pass. For the record, I recompiled
chan_rtpdir on my system to avoid library/compiler issues, which I
did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an
existing Asterisk box? I'm running no RF hardware on Asterisk at
this stage. All paths to RF are via the rtpDir link. Eventually, I
might add a remote base directly to Asterisk, or move the RF hardware
to Asterisk.

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Sorry to reply to my own post but why is there such pushback from the
"app_rpt" community from installing manually?

Everyone pushes EVB or ACID, why?

Any 3rd party ISO distro takes away from security and flexibility. I
can tell you that EVB can be rooted VERY easily if it is not
firewalled properly or services and settings changed.

Who knows what other code is in that ISO?

So again, I pose the question, "Why are manual installs discouraged?"

Just an example, I asked this very same question months ago and got an
offlist reply from Steve Henke, he called me and we talked for quite a
while, great guy, but in the end, his final answer was "Find an old
machine and install EVB ISO then run the scripts."

Is it because HAM people are assumed to be dumb? Couldn't a shell
script be written to pull down known versions of zaptel/dahdi, libpri,
and Jim's branch, and install?

If you are just using the box for USB/URI use, do you need
zaptel/dahdi? I seriously doubt you need libpri (lol).

I look forward to a logic answer as to why EVB and ACID are being
basically forced, and why nobody writes a simple howto or script to
get Asterisk, libpri, Zaptel/DAHDI from Digium's servers and build
from source.

Thanks,
Steve Totaro

···

On Sun, Jul 27, 2008 at 12:11 PM, Steve Totaro <stotaro@totarotechnologies.com> wrote:

Why not just use Jim Dixon's SVN branch on Digium's servers? I would
think that would be the cleanest, easiest, and most up to date code.

svn checkout http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4

Thanks,
Steve Totaro

On Sun, Jul 27, 2008 at 11:34 AM, Stephen Rodgers > <hwstar@rodgers.sdcoxmail.com> wrote:

Tony,

Here's some additional information to go along with my previous message.

1. After compiling and installing files.tar.gz, use the initial config
files in the /usr/src/configs and ./usr/src/configs/usbradio directory
to /etc/asterisk then
move file zaptel.conf to /etc.

2. files.tar.gz currenly comes with chan_rptdir version 0.2. After you
have resolved the segfaulting issue, you'll need update the source file
to version 0.5.

Steve
WA6ZFT

Tony Langdon, VK3JED wrote:

I've been trying to install Asterisk on a CentOS 4.4 box for a while,
but not with much luck. I got Asterisk compiled and the software
installed. After a couple of issues finding the right kernel-devel
package for my kernel, all seemed to install fine. I also installed
chan_rtpdir (v 0.2 so far, though now I will need 0.5). However,
when I try and start Asterisk, I get a segfault if there is anything
at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I
was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first
pass and then dies on the second pass. For the record, I recompiled
chan_rtpdir on my system to avoid library/compiler issues, which I
did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an
existing Asterisk box? I'm running no RF hardware on Asterisk at
this stage. All paths to RF are via the rtpDir link. Eventually, I
might add a remote base directly to Asterisk, or move the RF hardware
to Asterisk.

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Posted here because someone without a threaded email client wanted to
start a flame war with a bunch of off-topic emotional comments.

HOWTO:
1. Install your favorite flavor of Linux and configure it your way,
optimize your way, secure your way.
2. Install prerequisites for Asterisk
3. Go into /usr/src directory on your linux box
# cd /usr/src
4. b) Download the latest SVN stable release of libpri and zaptel and
Jim's branch
# svn checkout http://svn.digium.com/svn/libpri/branches/1.4 libpri-1.4
# svn checkout http://svn.digium.com/svn/zaptel/branches/1.4 zaptel-1.4
# svn checkout http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4/
asterisk_usbradio
5. cd into each of the above directories and read any READMEs or
similar all caps files.
6. cd into libpri-1.4
# make clean
# make && make install
7. cd into zaptel-1.4
# make clean
# make && make install
8. cd into asterisks_usbradio
# make clean
# ./configure
# "make menuselect" and make the selections you want.
# make && make install
9. Edit required files
10. Start Asterisk on the console with core dump on and a bit of verbose
# asterisk -vvvvvvvvvvvgc

Someone please test this as I have, and post to the websites pushing
EVB or ACID.

Thanks,
Steve Totaro

···

On Sun, Jul 27, 2008 at 1:44 PM, Steve Totaro <stotaro@totarotechnologies.com> wrote:

Sorry to reply to my own post but why is there such pushback from the
"app_rpt" community from installing manually?

Everyone pushes EVB or ACID, why?

Any 3rd party ISO distro takes away from security and flexibility. I
can tell you that EVB can be rooted VERY easily if it is not
firewalled properly or services and settings changed.

Who knows what other code is in that ISO?

So again, I pose the question, "Why are manual installs discouraged?"

Just an example, I asked this very same question months ago and got an
offlist reply from Steve Henke, he called me and we talked for quite a
while, great guy, but in the end, his final answer was "Find an old
machine and install EVB ISO then run the scripts."

Is it because HAM people are assumed to be dumb? Couldn't a shell
script be written to pull down known versions of zaptel/dahdi, libpri,
and Jim's branch, and install?

If you are just using the box for USB/URI use, do you need
zaptel/dahdi? I seriously doubt you need libpri (lol).

I look forward to a logic answer as to why EVB and ACID are being
basically forced, and why nobody writes a simple howto or script to
get Asterisk, libpri, Zaptel/DAHDI from Digium's servers and build
from source.

Thanks,
Steve Totaro

On Sun, Jul 27, 2008 at 12:11 PM, Steve Totaro > <stotaro@totarotechnologies.com> wrote:

Why not just use Jim Dixon's SVN branch on Digium's servers? I would
think that would be the cleanest, easiest, and most up to date code.

svn checkout http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4

Thanks,
Steve Totaro

On Sun, Jul 27, 2008 at 11:34 AM, Stephen Rodgers >> <hwstar@rodgers.sdcoxmail.com> wrote:

Tony,

Here's some additional information to go along with my previous message.

1. After compiling and installing files.tar.gz, use the initial config
files in the /usr/src/configs and ./usr/src/configs/usbradio directory
to /etc/asterisk then
move file zaptel.conf to /etc.

2. files.tar.gz currenly comes with chan_rptdir version 0.2. After you
have resolved the segfaulting issue, you'll need update the source file
to version 0.5.

Steve
WA6ZFT

Tony Langdon, VK3JED wrote:

I've been trying to install Asterisk on a CentOS 4.4 box for a while,
but not with much luck. I got Asterisk compiled and the software
installed. After a couple of issues finding the right kernel-devel
package for my kernel, all seemed to install fine. I also installed
chan_rtpdir (v 0.2 so far, though now I will need 0.5). However,
when I try and start Asterisk, I get a segfault if there is anything
at all in rpt.conf.

While the idea of using a distribution like ACID or EVB is nice, I
was forced to use a pre-existing system, so reformatting isn't an option.

If I use the sample rpt.conf, Asterisk loads fine. However, as soon
as I uncomment any line, then Asterisk dies with a segfault on the
second pass of reading my rpt.conf.

On my system, it reads and identifies the rtpDir link on the first
pass and then dies on the second pass. For the record, I recompiled
chan_rtpdir on my system to avoid library/compiler issues, which I
did have also.

Anyone have any ideas?

Alternatively, are there some sample configs that can be used on an
existing Asterisk box? I'm running no RF hardware on Asterisk at
this stage. All paths to RF are via the rtpDir link. Eventually, I
might add a remote base directly to Asterisk, or move the RF hardware
to Asterisk.

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Well, running asterisk -g will leave a core dump around when it segfaults, just have to work out how to analyse it. Running gdb on Asterisk itself provided no useful clues, as the traceback gets clobbered just before the segfault. I suspect the core dump is the only hope of continuing further down this path of investigation.

73 de VK3JED
http://vkradio.com

···

At 12:14 AM 7/28/2008, you wrote:

On Jul 27, 2008, at 2:05 AM, Tony Langdon, VK3JED wrote:
> If I use the sample rpt.conf, Asterisk loads fine. However, as soon
> as I uncomment any line, then Asterisk dies with a segfault on the
> second pass of reading my rpt.conf.

  Does it leave a core dump around? Anything useful come from an
analysis of that? If you aren't sure about how to handle that, you
must compile with debug symbols turned on as a start, and then use gdb
or other tools. A quick google on "linux core file analysis" should
give you something useful. If you can track down where it is dying it
surely will help figure out why.

I hear you about not wanting to re-install a whole system from scratch.

That's because the system is used for other purposes.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

I was originally looking for a package that would install Asterisk and some suitable sample configs on an existing system, sort of like ACID or EVB without the base Linux system, but in any case, I'm open to this route. I did use the current Asterisk, Zaptel and libpri from the Asterisk site for my system.

Will consider it as a good option to try in any case.

73 de VK3JED
http://vkradio.com

···

At 01:03 AM 7/28/2008, you wrote:

http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4/ is
up to date total Asterisk install. chan_rptdir is .5.

Thanks,
Steve Totaro

···

On Sun, Jul 27, 2008 at 4:53 PM, Tony Langdon, VK3JED <vk3jed@vkradio.com> wrote:

At 01:03 AM 7/28/2008, you wrote:

I hear you about not wanting to re-install a whole system from scratch.

That's because the system is used for other purposes.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

I was originally looking for a package that would install Asterisk
and some suitable sample configs on an existing system, sort of like
ACID or EVB without the base Linux system, but in any case, I'm open
to this route. I did use the current Asterisk, Zaptel and libpri
from the Asterisk site for my system.

Will consider it as a good option to try in any case.

73 de VK3JED
http://vkradio.com

I am doing a fresh install on FC8 with the instructions I posted
above, will post results, my guess is "make samples" after making and
installing chan_usbradio-1.4 (Asterisk 1.4 with additional code and
channel driver) will populate /etc/asterisk/ with chan_usbradio-1.4
specific samples.

Thanks,
Steve T

···

On Sun, Jul 27, 2008 at 5:49 PM, Steve Totaro <stotaro@totarotechnologies.com> wrote:

On Sun, Jul 27, 2008 at 4:53 PM, Tony Langdon, VK3JED > <vk3jed@vkradio.com> wrote:

At 01:03 AM 7/28/2008, you wrote:

I hear you about not wanting to re-install a whole system from scratch.

That's because the system is used for other purposes.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

I was originally looking for a package that would install Asterisk
and some suitable sample configs on an existing system, sort of like
ACID or EVB without the base Linux system, but in any case, I'm open
to this route. I did use the current Asterisk, Zaptel and libpri
from the Asterisk site for my system.

Will consider it as a good option to try in any case.

73 de VK3JED
http://vkradio.com

http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4/ is
up to date total Asterisk install. chan_rptdir is .5.

Thanks,
Steve Totaro

Yeah, it does http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4/configs

···

On Sun, Jul 27, 2008 at 5:56 PM, Steve Totaro <stotaro@totarotechnologies.com> wrote:

On Sun, Jul 27, 2008 at 5:49 PM, Steve Totaro > <stotaro@totarotechnologies.com> wrote:

On Sun, Jul 27, 2008 at 4:53 PM, Tony Langdon, VK3JED >> <vk3jed@vkradio.com> wrote:

At 01:03 AM 7/28/2008, you wrote:

I hear you about not wanting to re-install a whole system from scratch.

That's because the system is used for other purposes.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

I was originally looking for a package that would install Asterisk
and some suitable sample configs on an existing system, sort of like
ACID or EVB without the base Linux system, but in any case, I'm open
to this route. I did use the current Asterisk, Zaptel and libpri
from the Asterisk site for my system.

Will consider it as a good option to try in any case.

73 de VK3JED
http://vkradio.com

http://svn.digium.com/svn/asterisk/team/jdixon/chan_usbradio-1.4/ is
up to date total Asterisk install. chan_rptdir is .5.

Thanks,
Steve Totaro

I am doing a fresh install on FC8 with the instructions I posted
above, will post results, my guess is "make samples" after making and
installing chan_usbradio-1.4 (Asterisk 1.4 with additional code and
channel driver) will populate /etc/asterisk/ with chan_usbradio-1.4
specific samples.

Thanks,
Steve T

You might find that http://dl.allstarlink.org/installcd/phase2.sh
does almost EXACTLY what you are looking for. Id get rid of the stuff from
echo “Getting setup scripts…”
and beyond because the filesystem format may be different on your OS or OS version (it installs
stuff into files/directories specific to Centos/Fedora).

When I have a second or two, which wont be for a while unfortunately, I was going to post a copy
of the script edited exactly in that manner (or maybe a change to the existing one with an optional
command argument that exits at that point).

···

Date: Mon, 28 Jul 2008 06:53:53 +1000
To: app_rpt@lists.illiana.net
From: vk3jed@vkradio.com
Subject: Re: [App_rpt] Asterisk segfaults after installation

At 01:03 AM 7/28/2008, you wrote:

I hear you about not wanting to re-install a whole system from scratch.

That’s because the system is used for other purposes.

A possible solution for your problem is to use a set of source files
which is known to work together very well. Why not try downloading the
files.tar.gz source file tarball from
http://dl.allstarlink.org/installcd and unpack it in
/usr/src? After unpacking, run ./configure, make and make install in
the zaptel, libpri, and asterisk directories.

I was originally looking for a package that would install Asterisk
and some suitable sample configs on an existing system, sort of like
ACID or EVB without the base Linux system, but in any case, I’m open
to this route. I did use the current Asterisk, Zaptel and libpri
from the Asterisk site for my system.

Will consider it as a good option to try in any case.

73 de VK3JED
http://vkradio.com


App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

Is there a good "getting started" for this step? :slight_smile:

73 de VK3JED
http://vkradio.com

···

At 06:32 AM 7/28/2008, you wrote:

9. Edit required files

You might find that http://dl.allstarlink.org/installcd/phase2.sh
does almost EXACTLY what you are looking for. Id get rid of the stuff from
echo "Getting setup scripts..."
and beyond because the filesystem format may be different on your OS or OS version (it installs
stuff into files/directories specific to Centos/Fedora).

OK, I would be interested in trying this. I have no issue with reinstalling Asterisk from scratch (it's busted anyway LOL). I'm using a CentOS box, so should be able to make this work. :slight_smile:

When I have a second or two, which wont be for a while unfortunately, I was going to post a copy
of the script edited exactly in that manner (or maybe a change to the existing one with an optional
command argument that exits at that point).

It would be perfect. When you do get it going, I'm happy to beta test it.

73 de VK3JED
http://vkradio.com

···

At 09:30 AM 7/28/2008, you wrote:

OK, keep us posted how you go. I actually want a no radio sample at this stage, though eventually, I will go with a USB interface (probably when I get a new Asterisk box).

73 de VK3JED
http://vkradio.com

···

At 07:56 AM 7/28/2008, you wrote:

I am doing a fresh install on FC8 with the instructions I posted
above, will post results, my guess is "make samples" after making and
installing chan_usbradio-1.4 (Asterisk 1.4 with additional code and
channel driver) will populate /etc/asterisk/ with chan_usbradio-1.4
specific samples.

Hi Tony,

I'm interested in your results, too. I had trouble with asterisk version
1.4.20 & 1.4.20.1 that I downloaded and compiled, including the latest
app_rpt, etc., from the xeletec SVN....My problem was that when I tried to
connect 2 channels, asterisk would hang requiring a kill -9 of the
asterisk process to recover....See my messages from earlier this month for
more info...Moving to the 1.4.19 version included in files.tar.gz resolved
this.

I, too, have seen some segfaults with the 1.4.19 asterisk version....But,
I attributed this to a corrupted rpt.conf config--due to my experimenting
with this file....Once I fixed the config, all was okay.

I don't really want to get into the politics of whether to include code in
the asterisk trunk, but, I will make a comment....I've used linux for 17
years now, and I maintain several commercial code libraries for use with
various open-source tools--like PHP and Apache....I can say from
experience that keeping up with a rapidy evolving/moving target--like many
of the open source projects are--can be VERY tedious. In fact, it can be a
full time job in itself! ....So, I have some tolerence about the positions
voiced in earlier threads about not trying the latest & greatest.

Just my $0.02

73, David KB4FXC

···

On Mon, 28 Jul 2008, Tony Langdon, VK3JED wrote:

At 07:56 AM 7/28/2008, you wrote:

>I am doing a fresh install on FC8 with the instructions I posted
>above, will post results, my guess is "make samples" after making and
>installing chan_usbradio-1.4 (Asterisk 1.4 with additional code and
>channel driver) will populate /etc/asterisk/ with chan_usbradio-1.4
>specific samples.

OK, keep us posted how you go. I actually want a no radio sample at
this stage, though eventually, I will go with a USB interface
(probably when I get a new Asterisk box).

73 de VK3JED
http://vkradio.com

_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt

the new version of chan_rtpdir which supports the irlp and echolink bridge softwares
is now available on both the xelatec and digium/asterisk/team/jdixon SVN respistories.

there were only very minor changes and the 0.5 actually will work fine if you dont want to
upgrade immediately.

···