[op25-dev] Re: Repeater Build attempts

Doug Bade kd8b at thebades.net
Tue Mar 5 14:34:03 UTC 2013


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 at yahoogroups.com [mailto:op25-dev at yahoogroups.com] On Behalf
Of n4dav
Sent: Tuesday, March 05, 2013 8:10 AM
To: op25-dev at 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 at yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug
Bade" 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 at yahoogroups.com <mailto:op25-dev%40yahoogroups.com>
[mailto:op25-dev at yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On
Behalf
> Of ikj1234i
> Sent: Monday, March 04, 2013 10:35 AM
> To: op25-dev at 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
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....
>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20130305/ed62f980/attachment.html>


More information about the op25-dev mailing list