December 2011 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] App_rpt-users Digest, Vol 34, Issue 59
by Paul Nannery 22 Dec '11

22 Dec '11

Jim the simple repeat idea is good we just need to make sure it can id in that mode. On Dec 22, 2011 5:35 PM, <app_rpt-users-request(a)ohnosec.org> wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > Today's Topics: > > 1. Re: Allstar RTCM (Radio Thin Client Module) is nowavailable > (Marshall Oldham) > 2. Re: Allstar RTCM (Radio Thin Client Module) is nowavailable > (michaelcarey(a)internode.on.net) > > > ---------- Forwarded message ---------- > From: "Marshall Oldham" <ke6pcv(a)cal-net.org> > To: "'Jim Duuuude'" <telesistant(a)hotmail.com>, <conny(a)tangandjonsson.com> > Cc: 'app_rpt mailing list' <app_rpt-users(a)ohnosec.org> > Date: Thu, 22 Dec 2011 13:42:57 -0800 > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > ** > This would be a good function or to add in the future firmware! > > > ------------------------------ > *From:* Jim Duuuude [mailto:telesistant@hotmail.com] > *Sent:* Thursday, December 22, 2011 12:51 PM > *To:* conny(a)tangandjonsson.com > *Cc:* Marshall Oldham; app_rpt mailing list > *Subject:* RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > Not at the moment as the firmware currently stands. However, that's not > a bad idea. > It could simply act as a totally "dumb" controller and just repeat the > input back to > the output. > > JIM > > ------------------------------ > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > From: conny(a)tangandjonsson.com > Date: Thu, 22 Dec 2011 13:46:17 -0700 > CC: ke6pcv(a)cal-net.org; app_rpt-users(a)ohnosec.org > To: telesistant(a)hotmail.com > > If you use RTCM as "generic" radio interface on the hill and a linux box > at a remote location connected over an IP connection and you loose the > connection can the RTCM failover to be a minimal repeater controller on the > hill? > > 73 de N5HC > /Conny > > On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote: > > Yeah, that's the general idea. The location of the Linux server running > app_rpt/Asterisk can be > more or less anywhere within Internet connectivity of all of the receiver > and/or transmitter sites. > Of course, "Internet" can mean either some sort of public Internet > connection, or a privately-provided > Internet connection (low-cost microwave link(s), etc). > > The only limitation is that an RTCM/Voter module *must* be located on the > same LAN as the Linux > server, to at least provide a GPS-based timing reference. A system could > be set up with a server > located in some sort of datacenter "on the ground", and all the radios > could have an RTCM "on the > hill" with them, and as long as there is Internet connectivity of some > sort between each of them > and the server, the system will work nicely. That is providing that there > is an RTCM located at > the server location also (whether or not that particular RTCM has radio > hardware connected to it > or not). > > One minimal Linux server can easily support 1 or 2 dozen RTCM's (on 1 or 2 > allstar nodes), > and a larger server could easily support MANY dozens of them on dozens of > allstar nodes. > Of course, you REALLY dont want to put too many of them on a single > server, being a potential > single point of failure. For pretty much any practical purpose, the > reasonable limitation is > the point of failure/redundancy issue, not technical limitations. > > I'm not sure if you were clear on this, so I thought I would mention that > the RTCM is not just > usable as a GPS-timing-based Multi-Receiver Voting system and/or a > Simulcast Transmitter system. > It can also be used as a "generic" radio interface for a conventional > (non-GPS-based) either simplex > or full duplex (repeater) radio. The advantage of doing this would be to > not have the Linux > host "on the hill" with the radio (as mentioned above). In addition, the > RTCM allows for > portable/mobile operation with a mobile/portable Internet connection in > both the GPS-based > and non-GPS-based environments. > > JIM WB6NIL > > > ------------------------------ > From: ke6pcv(a)cal-net.org > To: app_rpt-users(a)ohnosec.org > Date: Wed, 21 Dec 2011 10:54:18 -0800 > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > I have been looking at the Allstar RTCM (Radio Thin Client Module) and it > really looks like a GREAT product and addition to the already cool Allstar > hardware. > > Among all the other cool features of the RTCM (Radio Thin Client Module) > like Transmitter Simulcasting and Receiver Voting, if I understand the > documentation > correctly you can use this very small Radio Thin Client Module at a remote > radio site to set up an Allstar repeater node if the site has internet > connection without a COMPUTER at the site? > > Then you can point the node on the hilltop back to a server on the ground > somewhere that is easy to get too? > > How many total sites can you use Radio Thin Client Modules on and point > back to a single server on the ground? > > If this is the case, All I can say is WOW, how cool! > > 73 > > Marshall > > > > > ------------------------------ > *From:* app_rpt-users-bounces(a)ohnosec.org [mailto: > app_rpt-users-bounces(a)ohnosec.org] *On Behalf Of *Mark Guibord > *Sent:* Sunday, December 18, 2011 11:03 AM > *To:* app_rpt-users(a)ohnosec.org > *Subject:* [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. > > > > For more information visit http://micro-node.com/thin-m1.html > > > > Regards, > > Mark Guibord > > Micro-Node International > > > > > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > ---------- Forwarded message ---------- > From: michaelcarey(a)internode.on.net > To: "Marshall Oldham" <ke6pcv(a)cal-net.org>, "Jim Duuuude" < > telesistant(a)hotmail.com>, conny(a)tangandjonsson.com > Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> > Date: Fri, 23 Dec 2011 09:05:37 +1030 > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > I agree! > > I was going to ask exactly the same question. Maybe this > loss-of-connectivity-failover function could be enhanced to include a > simple timed morse ID and dedicated repeater tail tone so you > know immediately that something is wrong. > > Michael. > VK5ZEA > > > ----- Original Message ----- > From: > "Marshall Oldham" <ke6pcv(a)cal-net.org> > > To: > "Jim Duuuude" <telesistant(a)hotmail.com>, <conny(a)tangandjonsson.com> > Cc: > "app_rpt mailing list" <app_rpt-users(a)ohnosec.org> > Sent: > Thu, 22 Dec 2011 13:42:57 -0800 > Subject: > Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable > > > This would be a good function or to add in the future firmware! > > > ------------------------------ > *From:* Jim Duuuude [mailto:telesistant@hotmail.com] > *Sent:* Thursday, December 22, 2011 12:51 PM > *To:* conny(a)tangandjonsson.com > *Cc:* Marshall Oldham; app_rpt mailing list > *Subject:* RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > Not at the moment as the firmware currently stands. However, that's not > a bad idea. > It could simply act as a totally "dumb" controller and just repeat the > input back to > the output. > > JIM > > ------------------------------ > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > From: conny(a)tangandjonsson.com > Date: Thu, 22 Dec 2011 13:46:17 -0700 > CC: ke6pcv(a)cal-net.org; app_rpt-users(a)ohnosec.org > To: telesistant(a)hotmail.com > > If you use RTCM as "generic" radio interface on the hill and a linux box > at a remote location connected over an IP connection and you loose the > connection can the RTCM failover to be a minimal repeater controller on the > hill? > > 73 de N5HC > /Conny > > On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote: > > Yeah, that's the general idea. The location of the Linux server running > app_rpt/Asterisk can be > more or less anywhere within Internet connectivity of all of the receiver > and/or transmitter sites. > Of course, "Internet" can mean either some sort of public Internet > connection, or a privately-provided > Internet connection (low-cost microwave link(s), etc). > > The only limitation is that an RTCM/Voter module *must* be located on the > same LAN as the Linux > server, to at least provide a GPS-based timing reference. A system could > be set up with a server > located in some sort of datacenter "on the ground", and all the radios > could have an RTCM "on the > hill" with them, and as long as there is Internet connectivity of some > sort between each of them > and the server, the system will work nicely. That is providing that there > is an RTCM located at > the server location also (whether or not that particular RTCM has radio > hardware connected to it > or not). > > One minimal Linux server can easily support 1 or 2 dozen RTCM's (on 1 or 2 > allstar nodes), > and a larger server could easily support MANY dozens of them on dozens of > allstar nodes. > Of course, you REALLY dont want to put too many of them on a single > server, being a potential > single point of failure. For pretty much any practical purpose, the > reasonable limitation is > the point of failure/redundancy issue, not technical limitations. > > I'm not sure if you were clear on this, so I thought I would mention that > the RTCM is not just > usable as a GPS-timing-based Multi-Receiver Voting system and/or a > Simulcast Transmitter system. > It can also be used as a "generic" radio interface for a conventional > (non-GPS-based) either simplex > or full duplex (repeater) radio. The advantage of doing this would be to > not have the Linux > host "on the hill" with the radio (as mentioned above). In addition, the > RTCM allows for > portable/mobile operation with a mobile/portable Internet connection in > both the GPS-based > and non-GPS-based environments. > > JIM WB6NIL > > > ------------------------------ > From: ke6pcv(a)cal-net.org > To: app_rpt-users(a)ohnosec.org > Date: Wed, 21 Dec 2011 10:54:18 -0800 > Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > I have been looking at the Allstar RTCM (Radio Thin Client Module) and it > really looks like a GREAT product and addition to the already cool Allstar > hardware. > > Among all the other cool features of the RTCM (Radio Thin Client Module) > like Transmitter Simulcasting and Receiver Voting, if I understand the > documentation > correctly you can use this very small Radio Thin Client Module at a remote > radio site to set up an Allstar repeater node if the site has internet > connection without a COMPUTER at the site? > > Then you can point the node on the hilltop back to a server on the ground > somewhere that is easy to get too? > > How many total sites can you use Radio Thin Client Modules on and point > back to a single server on the ground? > > If this is the case, All I can say is WOW, how cool! > > 73 > > Marshall > > > > > ------------------------------ > *From:* app_rpt-users-bounces(a)ohnosec.org [mailto: > app_rpt-users-bounces(a)ohnosec.org] *On Behalf Of *Mark Guibord > *Sent:* Sunday, December 18, 2011 11:03 AM > *To:* app_rpt-users(a)ohnosec.org > *Subject:* [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is > nowavailable > > Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. > > > > For more information visit http://micro-node.com/thin-m1.html > > > > Regards, > > Mark Guibord > > Micro-Node International > > > > > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >

1 0

Re: [App_rpt-users] urb0
by Monty 22 Dec '11

22 Dec '11

Was this ever resolved? I am getting the same error on my Intel D510 board running acid. I get it after it has been running awhile and I make change and do the astres.sh. Have to make a trip up to the site to hit the almighty reset button. Monty On Fri, Oct 22, 2010 at 8:36 AM, Jim Duuuude <telesistant(a)hotmail.com>wrote: > Well, that's what you get for naming your driver so close to > something that dumasses like me will confuse for it something else! :-) > > Honestly, in all the work ive done with USB under Linux, Ive never even > heard of the urb thing. The only thing Ive heard of in the realm is your > channel driver, and obviously that's what I thought it was. > > Does that mean that there is something in between the 'urb' and > the 'urd' called an 'urc' ???? :-) > > You know I always believe in 'go big or go home' and that includes > when I make a total fool of myself in front of the whole world. Oh well.. > > JIM WB6NIL > > > > > Date: Fri, 22 Oct 2010 11:28:51 -0400 > > Subject: Re: [App_rpt-users] urb0 > > From: w9sh(a)xelatec.com > > To: telesistant(a)hotmail.com > > CC: holldrl(a)gt.rr.com; app_rpt-users(a)qrvc.com > > > > > Duuuude, > > > > I think you mean that chan_urd is in the XIPAR distro. If he's using > > XIPAR then of course I'm glad to help. > > > > An "urb" message indicates a USB kernel/hardware problem. > > > > 73, > > Steve, W9SH > > > > > > > > You should probably address that question to Steve, W9SH, since the urb > > > channel driver is > > > uniquely part of his distribution. > > > > > > JIM WB6NIL > > > > > > From: holldrl(a)gt.rr.com > > > To: app_rpt-users(a)qrvc.com > > > Date: Fri, 22 Oct 2010 07:34:47 -0500 > > > Subject: [App_rpt-users] urb0 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On linux console keep getting " cannot submit > > > datapipe for urb0, error-22 internal error. What could be causing this? > > > Darril/WD5GJP > > > > > > _______________________________________________ > > > App_rpt-users mailing list > > > App_rpt-users(a)qrvc.com > > > http://qrvc.com/mailman/listinfo/app_rpt-users > > > _______________________________________________ > > > App_rpt-users mailing list > > > App_rpt-users(a)qrvc.com > > > http://qrvc.com/mailman/listinfo/app_rpt-users > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)qrvc.com > http://qrvc.com/mailman/listinfo/app_rpt-users > >

3 2

Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable
by Marshall Oldham 22 Dec '11

22 Dec '11

Pete, Thanks for the information on how you have been using the RTCM. It seems that there are many different applications that one can use these RTCM's for. They are kind of universal in nature. Enjoyed the photo of the portable traveling node. Just had one question about the Ubiquiti PicoStation set up as a bridge. Can you give/explain a little more information on it? I am interested in how this works to provide the internet for your setup. Thanks Marshall _____ From: Peter Elke [mailto:pete.elke@esquared.com] Sent: Thursday, December 22, 2011 12:44 AM To: Marshall Oldham; Jim Duuuude; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is "perma-link" nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS's 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater's output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don't have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it's dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff. Pete WI6H. From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Yeah, that's the general idea. The location of the Linux server running app_rpt/Asterisk can be more or less anywhere within Internet connectivity of all of the receiver and/or transmitter sites. Of course, "Internet" can mean either some sort of public Internet connection, or a privately-provided Internet connection (low-cost microwave link(s), etc). The only limitation is that an RTCM/Voter module *must* be located on the same LAN as the Linux server, to at least provide a GPS-based timing reference. A system could be set up with a server located in some sort of datacenter "on the ground", and all the radios could have an RTCM "on the hill" with them, and as long as there is Internet connectivity of some sort between each of them and the server, the system will work nicely. That is providing that there is an RTCM located at the server location also (whether or not that particular RTCM has radio hardware connected to it or not). One minimal Linux server can easily support 1 or 2 dozen RTCM's (on 1 or 2 allstar nodes), and a larger server could easily support MANY dozens of them on dozens of allstar nodes. Of course, you REALLY dont want to put too many of them on a single server, being a potential single point of failure. For pretty much any practical purpose, the reasonable limitation is the point of failure/redundancy issue, not technical limitations. I'm not sure if you were clear on this, so I thought I would mention that the RTCM is not just usable as a GPS-timing-based Multi-Receiver Voting system and/or a Simulcast Transmitter system. It can also be used as a "generic" radio interface for a conventional (non-GPS-based) either simplex or full duplex (repeater) radio. The advantage of doing this would be to not have the Linux host "on the hill" with the radio (as mentioned above). In addition, the RTCM allows for portable/mobile operation with a mobile/portable Internet connection in both the GPS-based and non-GPS-based environments. JIM WB6NIL _____ From: ke6pcv(a)cal-net.org To: app_rpt-users(a)ohnosec.org Date: Wed, 21 Dec 2011 10:54:18 -0800 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable I have been looking at the Allstar RTCM (Radio Thin Client Module) and it really looks like a GREAT product and addition to the already cool Allstar hardware. Among all the other cool features of the RTCM (Radio Thin Client Module) like Transmitter Simulcasting and Receiver Voting, if I understand the documentation correctly you can use this very small Radio Thin Client Module at a remote radio site to set up an Allstar repeater node if the site has internet connection without a COMPUTER at the site? Then you can point the node on the hilltop back to a server on the ground somewhere that is easy to get too? How many total sites can you use Radio Thin Client Modules on and point back to a single server on the ground? If this is the case, All I can say is WOW, how cool! 73 Marshall _____ From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. For more information visit http://micro-node.com/thin-m1.html Regards, Mark Guibord Micro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

3 4

Allstar RTCM (Radio Thin Client Module) is now available
by Mark Guibord 22 Dec '11

22 Dec '11

Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. For more information visit http://micro-node.com/thin-m1.html Regards, Mark Guibord Micro-Node International

10 24

Courtesy Tones
by Chris Perrine (KB2FAF) 22 Dec '11

22 Dec '11

Hi, Could someone give me an explanation of how all the courtesy tones interact? Specifically, linkunkeyct, nolocalinkct remotect etc... I have tried every combination I can think of and still can't get the beeps to do what I want and nothing stays consistent between and echolink connection or an Allstar connection or just a local connection. Currently when I connect to a local node I have set up I get a series of high pitched beeps and I have no idea where they are accounted for in rpt.conf. None of the ct's in the telemetry stanza would account for that. Are there possibly parameters other than nolocalinkct remotect linkunkeyct and unlinkedct that I am unaware of? Thanks! Chris KB2FAF

3 2

ALLSTAR RTCM ?
by Fran 22 Dec '11

22 Dec '11

Hello, Great product I jsut have one question, this unit is all self contained and in itself is a small footprint computer with internet access. My question is can this unit be used as the ALLSTAR Server connected directly to a repeater, or do I first need to have a ALLSTAR Server running connected to my repeater and the RTCM as the remote node?

2 1

Re: [App_rpt-users] Asterisk Install Help!
by Jim W7RY 21 Dec '11

21 Dec '11

Ron.. See the below message when I enter the command asterisk -rvv And yes, my DMK URI is plugged in and it's green LED is lit. From: Ron Morell Sent: Tuesday, December 20, 2011 8:19 PM To: w7ry(a)centurytel.net Subject: Re: [App_rpt-users] Asterisk Install Help! Jim, It sounds like you have a ways to go with this project! First thing is to login, now that you have the prompt. So where it asks you to login, type "root" and then your password. That should get you to the prompt on the terminal session. This software all runs from a terminal, there is not a GUI to reduce the learning curve. So you will be at the command prompt for all the work. Are you currently a Linux user? What you are installing with the ACID install is a Linux distribution called CENTOS ver. 5.7 and the Asterisk PBX plus the app_rpt repeater control program. Asterisk+app_rpt is both a server and an application. You should approach it as a server that you will be configuring to control your repeater or node radio. You do have a built in applicaton which you can access by typing "asterisk -rv" from the command prompt in the terminal. You will then be presented with a prompt that looks like this. [root@test asterisk]# asterisk -rvv Asterisk , Copyright (C) 1999 - 2008 Digium, Inc. and others. Created by Mark Spencer <markster(a)digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?) Thanks Ron 73 Jim W7RY Connected to Asterisk currently running on test (pid = 2572) Verbosity is at least 3 test*CLI> This will not work out unless you have the USB FOB connected. The GMK URI is a good choice. If it is connected, you will be able to configure the node. Hope this helps you to move forward. Write if I can be of further assistance, or if I completely miss understood the question, rephrase it and I'll try again. Hi Hi Ron Morell KA7U Oh... One more thing... Do you have to have a server and a node? The web site is a bit un-clear on this. I just want to have a node that will connect to other nodes and the WIN System Allstar reflector. Thanks! 73 Jim W7RY From: Jim W7RY Sent: Tuesday, December 20, 2011 7:08 PM To: App_rpt-users at ohnosec.org Subject: [App_rpt-users] Asterisk Install Help! Group.. I'm having some issues getting a new node set up and have some questions. Not sure if this is the right forum or not. I successfully loaded the OS twice.. I apparently mistyped my password when the install asked me for it. After I put it in in-correctly, the screen went to a login prompt... now I cant figure out how to re-start the install without starting from square 1. I've searched the internet and found little information on the actual node install. Can anyone point me to some? Thanks! 73 Jim W7RY -- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4693 - Release Date: 12/20/11

1 0

Asterisk Install Help!
by Jim W7RY 21 Dec '11

21 Dec '11

Group.. I'm having some issues getting a new node set up and have some questions. Not sure if this is the right forum or not. I successfully loaded the OS twice.. I apparently mistyped my password when the install asked me for it. After I put it in in-correctly, the screen went to a login prompt... now I cant figure out how to re-start the install without starting from square 1. I've searched the internet and found little information on the actual node install. Can anyone point me to some? Thanks! 73 Jim W7RY

1 1

call into an Asterisk+app_rpt node with a cell phone??
by Ron Morell 19 Dec '11

19 Dec '11

My node 28174 is linking to other nodes FB and iaxRPT makes it easy to facilitate the linking process. Now I want to be able to call in from my Android cell phone and use that for an interface with the Asterisk cli: . I've installed IaxAgent on my Android phone. I followed along with the instructions found in the acid-sysadmin.pdf for calling in for "dial up access" that goes like this in iax.conf [my-ip-phone] type=user context=radio-control auth=md5 secret=mypassword host=dyanamic disallow=all allow=gsm allow=g726aal2 transfer=no and goes like this in extensions.conf [radio-control] exten=>28174,1,Answer() exten=>28174,n,Playback(rpt/node) exten=>28174,n,Playback(digits/2) exten=>28174,n,Playback(digits/8) exten=>28174,n,Playback(digits/1) exten=>28174,n,Playback(digits/7) exten=>28174,n,Playback(digits/4) exten=>28174,n,Rpt(28174|P) Then from the reload all looks fine. test*CLI> iax2 reload [Dec 13 21:56:24] NOTICE[16896]: chan_iax2.c:11489 set_config: Ignoring bindaddr on reload == Loaded firmware 'iaxy.bin' -- Registered IAX2 to '67.215.233.178', who sees us as 174.27.6.80:4569 with no messages waiting test*CLI> But when I try to call in using the IaxAgent application on the Android Cell Phone I get this: test*CLI> [Dec 13 21:58:06] NOTICE[16870]: chan_iax2.c:6839 register_verify: No registration for peer 'my-ip-phone' (from 174.253.162.48) [Dec 13 21:58:06] NOTICE[16864]: chan_iax2.c:6839 register_verify: No registration for peer 'my-ip-phone' (from 174.253.162.48) test*CLI> I've tried "registering" with a line like this in iax.conf: register=my-ip-phone:password@OK.no-ip.org But that doesn't change the outcome. So any ideas on how to set a "registration" for 'my-ip-phone' calling in from Verizon using a cell phone? Ron Morell KA7U --

10 13

Re: [App_rpt-users] [PATCH] Zaptel modified for newer kernels & IOCTL issues.
by James Le Cuirot 18 Dec '11

18 Dec '11

Hello all, I'm not a radio user but I've been helping Ken out and I made the necessary changes to get Zaptel working with Linux 3.1.0. I know it is customary to send patches directly to the list so here it is. Ken didn't mention that I did not fix all the drivers. I was primarily just trying to get wctdm working. If you blank out the SUBDIR_MODULES variable in the Makefile then the build will complete, albeit with some drivers missing. No specialist knowledge is needed to complete this task as I merely applied the same changes that have already been applied to DAHDI. Both the name change and the other numerous modifications since then mean that existing patches cannot simply be applied. This brings me to a controversial point. As I won't be staying here long, I won't mince my words. Why on earth are you still dragging your heels with Zaptel? All the work that went into making this patch had already been done before by somebody else. This made the effort feel pointless, hence why I wasn't compelled to finish the job. There have no doubt been countless other feature additions and bug fixes to DAHDI that you are missing out on. Jim complains that DAHDI has stupid bugs that he had to fix in his Zaptel fork. I'm new here so I don't know if he's ever mentioned exactly what these bugs are. Why not fix them in DAHDI? If upstream doesn't agree, you can still continue to apply these patches against future versions. You can't cling to the past forever in the hope that things won't break because they inevitably do. Jim also stated that DAHDI would not work for radio setups. Is this really true? I gather that if you don't have a telephony card, only the ztdummy module is required for timing. I've seen the code for ztdummy and dahdi_dummy. It's relatively short. Do the aforementioned bugs apply to this code? Would they really be that hard to fix? I wish I had the radio hardware just so I could try it for myself. As for Asterisk, I don't know whether Jim insists on this old version because later versions don't support Zaptel or because he also has other issues with it. If it's the latter then I agree with the sentiment but not the solution. You only have to look as far as the publicly posted rationale for FreeSWITCH to learn that Asterisk has some fundamental flaws. This was written by someone who invested an awful lot of time and code in Asterisk but ultimately decided that a clean break was the only way to go. If Asterisk is so bad, why have you stuck with it and how does clinging to an older version help? One would hope that it has at least gone some way to address the flaws in more recent versions. I have just begun developing a new VoIP product and will be evaluating Yate in favour of Asterisk very soon. I don't know much about it yet but I like what I've seen so far. Maybe you should also consider the alternatives? Zaptel wasn't the only thing I had to modify for Linux 3.1.0. chan_usbradio itself was also broken. I need to go into some detail about that so I'll save it for another post. Regards, James

2 2