4 Mar
2013
4 Mar
'13
2:45 p.m.
Well it looks like in order to build this I am going to need a little more
input from anyone who has succeeded. Every attempt with every OS I have
tried has failed at some point due to lack of direct support for some
modules and or failures to compile to outright incompatibility.
Ubuntu 12.0.4 LTS got me the closest however when attempting to compile
Zaptel, the compile fails with errors which googling them results in
commentary that the Kernel is too new so I will need an older Kernel in
Debian or Ubuntu. How old??? Good question. as all the notes in Allstar's
build indicate CentOS 5.x is supported, nothing newer.. that does not help
me much in the debian world.
I tried several versions of CentOS 5.x , and all result in various modules
being of incorrect versions available or would not compile. I tried CentOS
6.x and got closer but failed to compile Zaptel for the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical that
have been used that I have yet to find a version that will build.
So unless someone wants to give some specifics in versions of OS that are
currently running asterisk as well as op25 as well as GNURadio, I have been
thus far unable to find a combination that supports all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that process
eludes me and my limited research to get it running as well as patience.
I would say with the current state of the docs, at best
Linux experts seem to be the only group of builders that are going to be
able to step through the minefield of a build. I am not criticizing the
docs, I understand they are written to be generic in many ways, but the
build requirements are far from generic in OS/Kernel requirements to get it
running.
While I am maybe a power user of Linux, I am not a
developer. so I may be above my knowledge base attempting the build. I own
and operate a dozen or so linux box's in my life including VMWare
virtualization on CentOS at work. I thought the instructions looked do-able
for my skillset.
I do not mean to criticize as much as suggest a little more
documentation on OS baseline starting points are in order.. As Debian and
Ubuntu seem to build best, that maybe tell us what version is in use so we
can get Zaptel to compile??? If that part fails, the rest is moot. Without
Asterisk running the repeater part is dead.
Doug
KD8B
4 Mar
4 Mar
4:34 p.m.
OK, don't know what we could be doing different in a radical enough way to blast
through this - other than to work patiently on the issues, one at a time until there is
progress. I'm very glad to see that you haven't just given up. We probably would
not be successful to attempt to put out a "binary" release of anything either,
for the same basic reasons you've already listed.
I run asterisk on a centos-5 system and run gnu radio on various versions if ubuntu 10 and
11. It may simplify things to separate the two packages and there is certainly no need to
shoehorn everything into a single machine/OS version. The asterisk component is designed
to communicate with the gnu radio components via UDP whether they're running in the
same machine or not. In general the repeater stuff tries to follow this rule, mostly
successfully.
I tried several versions of CentOS 5.x , and all
result in various modules
being of incorrect versions available or would not compile. I
which modules ?
tried CentOS
6.x and got closer but failed to compile Zaptel for
the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical that
which modules ?
have been used that I have yet to find a version that
will build.
So unless someone wants to give some specifics in versions of OS that are
currently running asterisk as well as op25 as well as GNURadio, I have been
thus far unable to find a combination that supports all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that process
As previously mentioned, it might be easier to start with the CLI version. I don't
know if the app_rpt stuff even uses the GUI. There may be no benefit to having a GUI, not
sure.
that maybe tell us what version is in use so we
can get Zaptel to compile??? If that part fails, the rest is moot. Without
Asterisk running the repeater part is dead.
Yeah asterisk is a beast but it really shouldn't be THAT hard to compile. Zaptel is
necessary due to the "dummy" zap channel support that's used internally. In
addition this list isn't necessarily the right forum for problems compiling asterisk
and/or app_rpt - but the problems might be trivial, so it wouldn't hurt to at least
post a few more details here....
5:21 p.m.
I will try to build on CentOS 6.x tonight which in theory I got the farthest
and it has a kernel that should be asterisk friendly as well as GNURadio
friendly. I will detail the build as far as it gets and what errors I am
unable to resolve myself. I have about 30-40 hours into the project of
trying to build in various forms. I am sorry I did not keep notes on each
failure. I have located some notes on getting zaptel to compile in a base
CentOS system, maybe I can get past that hurdle long enough to get to
asterisk and then GNU radio.
I will provide more concise details when I can get at least something
running that IS a step forward. So far that has not happened.
I can easily get the asterisk part running by using allstar or Xipar.. but
in both cases it is not a GNURadio friendly environment. So I am forced to
build a GNURadio friendly environment and try to get asterisk running. if I
want them on one box and that has been problematical.
Doug
KD8B
From: op25-dev(a)yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf
Of ikj1234i
Sent: Monday, March 04, 2013 10:35 AM
To: op25-dev(a)yahoogroups.com
Subject: [op25-dev] Re: Repeater Build attempts
OK, don't know what we could be doing different in a radical enough way to
blast through this - other than to work patiently on the issues, one at a
time until there is progress. I'm very glad to see that you haven't just
given up. We probably would not be successful to attempt to put out a
"binary" release of anything either, for the same basic reasons you've
already listed.
I run asterisk on a centos-5 system and run gnu radio on various versions if
ubuntu 10 and 11. It may simplify things to separate the two packages and
there is certainly no need to shoehorn everything into a single machine/OS
version. The asterisk component is designed to communicate with the gnu
radio components via UDP whether they're running in the same machine or not.
In general the repeater stuff tries to follow this rule, mostly
successfully.
I tried several versions of CentOS 5.x , and all
result in various modules
being of incorrect versions available or would not compile. I
which modules ?
tried CentOS
6.x and got closer but failed to compile Zaptel for
the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical
that
which modules ?
have been used that I have yet to find a version that
will build.
So unless someone wants to give some specifics in versions of OS that are
currently running asterisk as well as op25 as well as GNURadio, I have
been
thus far unable to find a combination that supports
all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that
process
As previously mentioned, it might be easier to start with the CLI version. I
don't know if the app_rpt stuff even uses the GUI. There may be no benefit
to having a GUI, not sure.
that maybe tell us what version is in use so we
can get Zaptel to compile??? If that part fails, the rest is moot. Without
Asterisk running the repeater part is dead.
Yeah asterisk is a beast but it really shouldn't be THAT hard to compile.
Zaptel is necessary due to the "dummy" zap channel support that's used
internally. In addition this list isn't necessarily the right forum for
problems compiling asterisk and/or app_rpt - but the problems might be
trivial, so it wouldn't hurt to at least post a few more details here....
5 Mar
5 Mar
2:09 p.m.
I have gotten a GUI running on both XIPAR and ACID, pretty easily by running yum
groupinstall X-windows and groupinstall gnome-desktop-environment. (Syntax may be a little
off there). That gives you a gui to work with. FWIW, Of the two, I like ACID better and
that seems to be the more popular. As far as getting GNR Radio and everything else built
-- well, you found as I did, thats a different story.
--- In op25-dev(a)yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
I will try to build on CentOS 6.x tonight which in theory I got the farthest
and it has a kernel that should be asterisk friendly as well as GNURadio
friendly. I will detail the build as far as it gets and what errors I am
unable to resolve myself. I have about 30-40 hours into the project of
trying to build in various forms. I am sorry I did not keep notes on each
failure. I have located some notes on getting zaptel to compile in a base
CentOS system, maybe I can get past that hurdle long enough to get to
asterisk and then GNU radio.
I will provide more concise details when I can get at least something
running that IS a step forward. So far that has not happened.
I can easily get the asterisk part running by using allstar or Xipar.. but
in both cases it is not a GNURadio friendly environment. So I am forced to
build a GNURadio friendly environment and try to get asterisk running. if I
want them on one box and that has been problematical.
Doug
KD8B
From: op25-dev(a)yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf
Of ikj1234i
Sent: Monday, March 04, 2013 10:35 AM
To: op25-dev(a)yahoogroups.com
Subject: [op25-dev] Re: Repeater Build attempts
OK, don't know what we could be doing different in a radical enough way to
blast through this - other than to work patiently on the issues, one at a
time until there is progress. I'm very glad to see that you haven't just
given up. We probably would not be successful to attempt to put out a
"binary" release of anything either, for the same basic reasons you've
already listed.
I run asterisk on a centos-5 system and run gnu radio on various versions if
ubuntu 10 and 11. It may simplify things to separate the two packages and
there is certainly no need to shoehorn everything into a single machine/OS
version. The asterisk component is designed to communicate with the gnu
radio components via UDP whether they're running in the same machine or not.
In general the repeater stuff tries to follow this rule, mostly
successfully.
I tried several versions of CentOS 5.x , and all
result in various modules
being of incorrect versions available or would not compile. I
which modules ?
tried CentOS
6.x and got closer but failed to compile Zaptel
for the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical
that
which modules ?
have been used that I have yet to find a version
that will build.
So unless someone wants to give some specifics in versions of OS that are
currently running asterisk as well as op25 as well as GNURadio, I have
been
thus far unable to find a combination that
supports all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that
process
As previously mentioned, it might be easier to start with the CLI version. I
don't know if the app_rpt stuff even uses the GUI. There may be no benefit
to having a GUI, not sure.
that maybe tell us what version is in use so we
can get Zaptel to compile??? If that part fails, the rest is moot. Without
Asterisk running the repeater part is dead.
Yeah asterisk is a beast but it really shouldn't be THAT hard to compile.
Zaptel is necessary due to the "dummy" zap channel support that's used
internally. In addition this list isn't necessarily the right forum for
problems compiling asterisk and/or app_rpt - but the problems might be
trivial, so it wouldn't hurt to at least post a few more details here....
2:20 p.m.
It took several hours of google assistance and stepping through pre-req h*ll
but I *think* I have all I need for GNURadio as well as Op25 as well as
Asterisk loaded into CentOS 6.3
But did not try to compile anything yet as I ran out of waking hours. Zaptel
will be first stop tonight..I found RPM's for just about all the
prerequisites although names are different in RH vs Debian branches.
It may be easier to just work with Debian at the correct Kernel versions. (
older) . for less hassle on pre-req names. I am not sure how Zaptel etc will
build there considering the allstar branch is RH centric.
Doug
KD8B
From: op25-dev(a)yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf
Of n4dav
Sent: Tuesday, March 05, 2013 8:10 AM
To: op25-dev(a)yahoogroups.com
Subject: [op25-dev] Re: Repeater Build attempts
I have gotten a GUI running on both XIPAR and ACID, pretty easily by running
yum groupinstall X-windows and groupinstall gnome-desktop-environment.
(Syntax may be a little off there). That gives you a gui to work with. FWIW,
Of the two, I like ACID better and that seems to be the more popular. As far
as getting GNR Radio and everything else built -- well, you found as I did,
thats a different story.
--- In op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug
Bade" wrote:
are
I
I will try to build on CentOS 6.x tonight which in theory I got the
farthest
and it has a kernel that should be asterisk friendly
as well as GNURadio
friendly. I will detail the build as far as it gets and what errors I am
unable to resolve myself. I have about 30-40 hours into the project of
trying to build in various forms. I am sorry I did not keep notes on each
failure. I have located some notes on getting zaptel to compile in a base
CentOS system, maybe I can get past that hurdle long enough to get to
asterisk and then GNU radio.
I will provide more concise details when I can get at least something
running that IS a step forward. So far that has not happened.
I can easily get the asterisk part running by using allstar or Xipar.. but
in both cases it is not a GNURadio friendly environment. So I am forced to
build a GNURadio friendly environment and try to get asterisk running. if
I
want them on one box and that has been problematical.
Doug
KD8B
From: op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com>
[mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On
Behalf
Of ikj1234i
Sent: Monday, March 04, 2013 10:35 AM
To: op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com>
Subject: [op25-dev] Re: Repeater Build attempts
OK, don't know what we could be doing different in a radical enough way to
blast through this - other than to work patiently on the issues, one at a
time until there is progress. I'm very glad to see that you haven't just
given up. We probably would not be successful to attempt to put out a
"binary" release of anything either, for the same basic reasons you've
already listed.
I run asterisk on a centos-5 system and run gnu radio on various versions
if
ubuntu 10 and 11. It may simplify things to separate
the two packages and
there is certainly no need to shoehorn everything into a single machine/OS
version. The asterisk component is designed to communicate with the gnu
radio components via UDP whether they're running in the same machine or
not.
In general the repeater stuff tries to follow this
rule, mostly
successfully.
> I tried several versions of CentOS 5.x , and all result in various
modules
being of
incorrect versions available or would not compile. I
which modules ?
tried CentOS
6.x and got closer but failed to compile Zaptel
for the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical
that
which modules ?
> have been used that I have yet to find a version that will build.
>
> So unless someone wants to give some specifics in versions of OS that currently
running asterisk as well as op25 as well as GNURadio, I have
been
thus far unable to find a combination that
supports all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that
process
As previously mentioned, it might be easier to start with the CLI version. don't know if the app_rpt stuff even uses the GUI.
There may be no benefit
to having a GUI, not sure.
> that maybe tell us what version is in use so we
> can get Zaptel to compile??? If that part fails, the rest is moot.
Without
Asterisk
running the repeater part is dead.
Yeah asterisk is a beast but it really shouldn't be THAT hard to compile.
Zaptel is necessary due to the "dummy" zap channel support that's used
internally. In addition this list isn't necessarily the right forum for
problems compiling asterisk and/or app_rpt - but the problems might be
trivial, so it wouldn't hurt to at least post a few more details here....
3:34 p.m.
You did better than I did on getting GUI running on allstar an xipar. It
sounds like we do not necessarily need a lot of ACID, but the core parts of
app_rpt. I use ACID distro on a couple sites and am familiar with it more so
than Xipar also. What I did see from Xipar is it may be easier to shoehorn
in what we need for P25 as it does not load a lot of site related stuff that
comes from the servers. as you can just do a simple 1 rptr build.. and then
go edit as needed. networking to servers not required..
I guess I could build a new site on Allstar that is just one repeater too.
I have a friend who is indicating some knowledge of how to
get Zaptel to compile on newer kernels.. I am going to do some inquiry on
that J
If I can get past that the rest should be buildable..
Doug
From: op25-dev(a)yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf
Of n4dav
Sent: Tuesday, March 05, 2013 8:10 AM
To: op25-dev(a)yahoogroups.com
Subject: [op25-dev] Re: Repeater Build attempts
I have gotten a GUI running on both XIPAR and ACID, pretty easily by running
yum groupinstall X-windows and groupinstall gnome-desktop-environment.
(Syntax may be a little off there). That gives you a gui to work with. FWIW,
Of the two, I like ACID better and that seems to be the more popular. As far
as getting GNR Radio and everything else built -- well, you found as I did,
thats a different story.
--- In op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug
Bade" wrote:
are
I
I will try to build on CentOS 6.x tonight which in theory I got the
farthest
and it has a kernel that should be asterisk friendly
as well as GNURadio
friendly. I will detail the build as far as it gets and what errors I am
unable to resolve myself. I have about 30-40 hours into the project of
trying to build in various forms. I am sorry I did not keep notes on each
failure. I have located some notes on getting zaptel to compile in a base
CentOS system, maybe I can get past that hurdle long enough to get to
asterisk and then GNU radio.
I will provide more concise details when I can get at least something
running that IS a step forward. So far that has not happened.
I can easily get the asterisk part running by using allstar or Xipar.. but
in both cases it is not a GNURadio friendly environment. So I am forced to
build a GNURadio friendly environment and try to get asterisk running. if
I
want them on one box and that has been problematical.
Doug
KD8B
From: op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com>
[mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On
Behalf
Of ikj1234i
Sent: Monday, March 04, 2013 10:35 AM
To: op25-dev(a)yahoogroups.com <mailto:op25-dev%40yahoogroups.com>
Subject: [op25-dev] Re: Repeater Build attempts
OK, don't know what we could be doing different in a radical enough way to
blast through this - other than to work patiently on the issues, one at a
time until there is progress. I'm very glad to see that you haven't just
given up. We probably would not be successful to attempt to put out a
"binary" release of anything either, for the same basic reasons you've
already listed.
I run asterisk on a centos-5 system and run gnu radio on various versions
if
ubuntu 10 and 11. It may simplify things to separate
the two packages and
there is certainly no need to shoehorn everything into a single machine/OS
version. The asterisk component is designed to communicate with the gnu
radio components via UDP whether they're running in the same machine or
not.
In general the repeater stuff tries to follow this
rule, mostly
successfully.
> I tried several versions of CentOS 5.x , and all result in various
modules
being of
incorrect versions available or would not compile. I
which modules ?
tried CentOS
6.x and got closer but failed to compile Zaptel
for the reasons stated
above.
So if the intent is to allow us to build over a wide array
of OS's I can say that Isn't going happen. The modules are so critical
that
which modules ?
> have been used that I have yet to find a version that will build.
>
> So unless someone wants to give some specifics in versions of OS that currently
running asterisk as well as op25 as well as GNURadio, I have
been
thus far unable to find a combination that
supports all of them.
I tried starting with Allstar and with XiPar and neither has
support for GUI nor was I able to get a GUI to run, apparently that
process
As previously mentioned, it might be easier to start with the CLI version. don't know if the app_rpt stuff even uses the GUI.
There may be no benefit
to having a GUI, not sure.
> that maybe tell us what version is in use so we
> can get Zaptel to compile??? If that part fails, the rest is moot.
Without
Asterisk
running the repeater part is dead.
Yeah asterisk is a beast but it really shouldn't be THAT hard to compile.
Zaptel is necessary due to the "dummy" zap channel support that's used
internally. In addition this list isn't necessarily the right forum for
problems compiling asterisk and/or app_rpt - but the problems might be
trivial, so it wouldn't hurt to at least post a few more details here....
4080
days inactive
4081
days old
5 comments
3 participants
participants (3)
-
Doug Bade -
ikj1234i -
n4dav