- App_rpt-users - lists.keekles.org

wishes
by Bryan D. Boyle 25 Dec '11

25 Dec '11

a very Merry Christmas and sincere best wishes for a happy and healthy 2012. and for duuuude...for all you've done, and continue to do.. my personal thanks and appreciation! -- Bryan Sent from my iPhone please forgive misspellings...

1 0

Re: [App_rpt-users] CTCSS Drop Out Time
by Jim W7RY 25 Dec '11

25 Dec '11

Well perhaps we can get a suggestion from one of the Gurus on how to do it. We'll standby and wait for an answer... Thanks all! 73 Jim W7RY From: Lu Vencl Sent: Saturday, December 24, 2011 8:39 PM To: 'Jim W7RY' Cc: 'John Boteler' Subject: RE: [App_rpt-users] CTCSS Drop Out Time I think that is correct, but I there is more to the effort that needs to happen and that is the part I don't understand.. You have to install it some way. From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim W7RY Sent: Saturday, December 24, 2011 11:34 PM To: Ken; 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] CTCSS Drop Out Time It seems to be here: /usr/src/astsrc/asterisk/channels/xpmr And the line is: #define TOC_NOTONE_TIME 900 // ms I changed it from 600 to 900. Did not change a thing... Did I change the right thing? From: Ken Sent: Saturday, December 24, 2011 6:01 PM To: 'Jim Duuuude' ; w7ry(a)centurytel.net ; 'app_rpt mailing list' Subject: RE: [App_rpt-users] CTCSS Drop Out Time Notone AKA chicken burst gives you carrier with no tone at the end. But some radios are too slow in closing the CTCSS and still make noise. There was a posting on here a while back that pointed the time delay in: /usr/src/asterisk/asterisk/channels/xpmr/xpmr.h The default is 600 ms. Some radios might be slower than this. You could change (increase) it, then make / make install and restart asterisk. My Alinco DR-?35 series seem to want to give you a small squelch tail no matter what you do, however. 73 Ken From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Saturday, December 24, 2011 6:17 PM To: w7ry(a)centurytel.net; app_rpt mailing list Subject: Re: [App_rpt-users] CTCSS Drop Out Time try txtoctype = notone in usbradio.conf JIM WB6NIL -------------------------------------------------------------------------------- From: w7ry(a)centurytel.net To: app_rpt-users(a)ohnosec.org Date: Sat, 24 Dec 2011 13:55:51 -0800 Subject: [App_rpt-users] CTCSS Drop Out Time Anyone know if there is an adjustment of the time the transmitter stays keyed, and the PL tone drops out and where that setting is? With my rigs, I still here the squelch crash after the repeater drops out. I would like to cut the PL off a little sooner or delay the transmitter a little longer. BTW, I'm all up and running with the repeater function and the node! Thanks to all that helped me get past the learning curve! Thanks! Merry Christmas 73 Jim W7RY _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4700 - Release Date: 12/24/11 No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4701 - Release Date: 12/24/11

1 0

Repeater and one remote Node
by Fran 24 Dec '11

24 Dec '11

Hello, I have my server setup and my base station (Repeater Node) setup...... My server is connected directly to repeater. Now I want to connect a remote simplex node useing the RTCM, I have read the info on the RTCM and it looks pretty easy however Im just a bit confused on what files I need to change on the server side...Any help woud be appreciated, yes I have the help files but would be nice to have it from someone who has already had the experience. Thanks

2 1

Beagle Board-xM + LOX OS and power consumption
by Ron Morell 24 Dec '11

24 Dec '11

Trying to catch up on the threads of information and now trying to understand the Beagle Board and LOX. So reading along, I find this board is using an ARM DM3730CBP 1GHz processor in the current versions. I find that Pickle Linux is supplying an Asterisk+app_rpt ISO image meant to be written to a 4Gbyte mini SD Card, and that GMK Engineering is selling a LOX board with adapter cables to connect it to the Beagle Board-xM and that this device will connect up to 2 radios. Reading on, there is the RTCM device that is capable of replacing an Asterisk+app_rpt computer at a radio site, but these devices need to connect to a "Hub" Asterisk+app_rpt to be addressable through the AllStar Link Network. Recently WB6NIL has added firmware updates to manage these RTCM devices as a simple repeater controller in the event they lose connection with the "Hub" Asterisk+app_rpt switch controller. So my questions so far are: how much power in watts does the Beagle Board-xM with LOX use on average? how much power in watts does the RTCM use on average? Has anyone compiled a Debian OS with Asterisk+app_rpt for use on the Beagle Board-xM, or is Pickle Linux the only currently available OS solution? Is the current Beagle Board-xM the recommended computer to use, or is another version better supported? Do the Beagle Board users need to have a JTAG device to debug and interface with the system and upgrade uBoot? If so, which JTAG device is recommended? OK, enough with the questions. Given that the RTCM seems to be an attractive solution and the Beagle Boards are supporting up to 2 radios per device with a very elegant solution, I would like to learn as much as I can about these devices and their intended as well as extended uses. I'm not at all competent with the discussion on simulcasting repeaters and nodes, but from what I've read that is not really the scope of these devices, or is there something about simulcast that I've missed in the threads here? 73 and Merry Christmas, Ron - KA7U

2 1

FW: Allstar RTCM (Radio Thin Client Module) is nowavailable
by Marshall Oldham 24 Dec '11

24 Dec '11

Jim, WOW, that was a quick feature update and new firmware addition. Man you work fast. Thanks for this great functional feature to the RTCM. An early Christmas gift! <GRIN> 73 Marshall - ke6pcv _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Friday, December 23, 2011 8:34 PM To: Marshall Oldham; conny(a)tangandjonsson.com Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable I've been really busy (and productive) today. The new version (0.60) of the RTCM/Voter board firmware now supports the following: Notification via CW of host connection failure (with the option of repeating it periodically if still failed, along with option of repeating it after receiver un-key). Notification via CW of host connection restoral after failure. "Offline" repeat mode, where it becomes a "dumb" repeater if host connection is lost. Includes settable hang time. The "Notification via CW of host connection failure" feature also can serve as a CW identifier in this mode (and was designed to do so). The CW speed, CW strings (content of messages), and some other stuff is user-settable from a menu. Speaking of menus, the "big humongous" main menu is now split in to 3 nice, smaller ones. The 2 sub-menus are IP (networking) parameters, and "Offline Mode" parameters. The only thing it does *NOT* do is generate CTCSS tone when transmitting. I doubt it ever will, since we are pretty much out of code space in the processor. This would require the use of floating point trig functions to calculate generation constants (or from a table), neither of which we have room for. The 0.60 version will be available on SVN at 2115 PST tonight. JIM WB6NIL _____ From: ke6pcv(a)cal-net.org To: telesistant(a)hotmail.com; conny(a)tangandjonsson.com CC: app_rpt-users(a)ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Thu, 22 Dec 2011 13:42:57 -0800 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@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

3 2

RTCM + LOX/Beagle Board Setup
by Fredric Moses 24 Dec '11

24 Dec '11

Hello all new to the list and app_rpt with asterisk in general. My question is if the beagle board/LOX combo is powerful enough to also be the radio server for the RTCM's. My first 2 LOX/Beagleboard combo's should up a few days ago.. Just sat down and hooked up my first radio to it about 24 hours ago and it's really slick how it's just working to the point that I am thinking of replacing the arcom rc210 I have on my UHF machine after i keep working and testing this more.. I want to not only run the RTCM's from the beagle board that will be located at the main site but have the 2 radio ports on the LOX's be used as remote bases to the RTCM. As from what I am reading about the RTCM's they need a app_rpt server to show up as a radio port for ID's n Such.. My current UHF Site1 is a motorola purc 5000 with a UHF link radio towards a friends site. If the RTCM/Beagleboard combo's work I will be installing a second purc about 10 miles away on another mountain ridge site so will want the voted RX audio as well as the simulcast to work out the "remote" link ports on the LOX. A third site is planned to the west about 18 miles away but won't come up till the microwave path is installed direct to it.. This RTCM came out at just the right time as i have a stack of 900mhz maxtracs and a spectra tac voter that i was about it install for remote RX's. -- Fredric Moses - W8FSM - WQOG498 fred(a)moses.bz

2 1

Allstarlink/ubuntu
by KB7RSI 23 Dec '11

23 Dec '11

Does anyone have the scripts that K1LNK wrote a little over a year ago that they could send me or direct me to? His domain seems to be down and I also assume that his email which is to his old domain is down also. If not, has anyone successfully gotten this to work on Ubuntu with minimum issues? Thanks all Harold Kb7rsi Las Vegas From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Little Denver Sent: Friday, December 23, 2011 4:20 PM To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] setting up a new node with a maxtrac Looking to build an allstar node with for my dad. The OS is installing now, my URI with internal eeprom has been delivered and I am soldering the connections to my Maxtrac. I would like to set this up for Simplex with tones, Can i get a guide of standard settings for the web configuration, specifically for the radio configuration section? we have been messing around with getting an HT to work with no success and basically have changed all the setting in there. Just want to make sure we start off with everything as a standard or best pratice for this new radio configuration. -- Thanks & 73, Denver Little KF5EFG

2 2

Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable
by Jim Duuuude 23 Dec '11

23 Dec '11

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 documentationcorrectly 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 GuibordMicro-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

3 4

setting up a new node with a maxtrac
by Little Denver 23 Dec '11

23 Dec '11

Looking to build an allstar node with for my dad. The OS is installing now, my URI with internal eeprom has been delivered and I am soldering the connections to my Maxtrac. I would like to set this up for Simplex with tones, Can i get a guide of standard settings for the web configuration, specifically for the radio configuration section? we have been messing around with getting an HT to work with no success and basically have changed all the setting in there. Just want to make sure we start off with everything as a standard or best pratice for this new radio configuration. -- Thanks & 73, Denver Little KF5EFG

1 0

Re: [App_rpt-users] No registration for peer 'ka7u' (from 96.254.195.117)
by Ron Morell 23 Dec '11

23 Dec '11

David, Thanks for the reply. The mystery has been solved. My friend W4BGH and I experimented a while back with Zoiper soft phones and IAX connections. I had since changed some of the iax.conf settings, but that Zoiper soft phone was trying to maintain a connection. That has been fixed. So the learning curve continues! You are right on target with the problem. 73, Ron Morell KA7U On 12/23/2011 10:19 AM, David KE6UPI wrote: > Well looking up the IP address its from Verizon FIOS. Could it be from > anther IAXagent? Are you in the city of Valrico?? > > > > General IP Information > > IP: 96.254.195.117 > Decimal: 1627308917 > Hostname: pool-96-254-195-117.tampfl.fios.verizon.net > <http://pool-96-254-195-117.tampfl.fios.verizon.net> > ISP: Verizon Internet Services > Organization: Verizon Internet Services > Services: None detected > Type: Broadband <http://whatismyipaddress.com/broadband> > Assignment: Static IP <http://whatismyipaddress.com/dynamic-static> > > > Geolocation Information > > Country: United States us flag > State/Region: Florida > City: Valrico > Latitude: 27.9158 > Longitude: -82.229 > Area Code: 813 > Postal Code: 33596 > > > > David > > > On Fri, Dec 23, 2011 at 8:36 AM, Ron Morell <ron(a)morell.us > <mailto:ron@morell.us>> wrote: > > I have a mystery connection attempt going on. I don't know if it is > bouncing back because of a connection attempt from my node or if it is > from another device trying to call into the node. It looks like this: > > test*CLI> > [Dec 23 09:08:37] NOTICE[29328]: chan_iax2.c:6839 register_verify: No > registration for peer 'ka7u' (from 96.254.195.117) > > Tried to figure out where it comes from, but end up with Verizon, > which > covers a lot. I have my cell phone turned off, just in case > IaxAgent on > my phone was running in the background and was somehow trying to call > in. So that device is out of the loop. Just for knowing IaxAgent on > the cell phone is using this IP currently: 174.253.181.123, and > calls in > just fine. > > [root@test asterisk]# traceroute 96.254.195.117 > traceroute to 96.254.195.117 (96.254.195.117), 30 hops max, 40 > byte packets > 1 192.168.0.1 (192.168.0.1) 0.737 ms 1.175 ms 1.400 ms > 2 boid-dsl-gw03-195.boid.qwest.net > <http://boid-dsl-gw03-195.boid.qwest.net> (184.99.64.195) 53.113 > ms 53.921 > ms 54.598 ms > 3 184-99-65-17.boid.qwest.net > <http://184-99-65-17.boid.qwest.net> (184.99.65.17) 55.379 ms > 56.067 ms > 57.184 ms > 4 sjp-brdr-03.inet.qwest.net <http://sjp-brdr-03.inet.qwest.net> > (67.14.34.10) 90.062 ms 90.844 ms > 92.233 ms > 5 63.146.27.230 (63.146.27.230) 92.767 ms 97.868 ms 98.521 ms > 6 0.ge-2-1-0.SJC01-BB-RTR2.verizon-gni.net > <http://0.ge-2-1-0.SJC01-BB-RTR2.verizon-gni.net> (152.63.2.62) > 84.364 ms > 79.095 ms 80.897 ms > 7 130.81.199.29 (130.81.199.29) 139.337 ms 140.607 ms 141.284 ms > 8 * * * > 9 * * * > > So if I have a setting somewhere that is calling out and trying to > register ka7u it should show up in my /etc/asterisk/*.conf files, > I think. > [root@test asterisk]# grep -R "ka7u" * > extensions.conf:;exten => 3001,1,Dial(IAX2/ka7u) > [root@test asterisk]# > > The above is the only instance of 'ka7u' in those files and it is > commented out while I'm trouble shooting this. I've checked > through the > iax.conf files of the friend nodes I work with and commented out > all the > ka7u references in the iax.conf files on those and still the > connection > attempts continue. > > Any ideas of what this is all about? > Ron KA7U > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >

1 0