From kb3ors at windstream.net Sat Jan 1 16:49:03 2011 From: kb3ors at windstream.net (KB3ORS - Brian) Date: Sat, 1 Jan 2011 11:49:03 -0500 Subject: [App_rpt-users] Fw: Weather Script Message-ID: ? ?Mark, Finally after a fresh install of all the files I have the get scripts running. When I try to play the scripts it acts like its running and goes back to the root prompt and nothing come out the speakers or transmitted over the air. Is there something I need to change in the play script to get it to play. I am using the W0ANM scripts. Brian KB3ORS 27321 -----Original Message----- From: Mark Phillips Sent: Friday, December 10, 2010 4:10 PM To: app_rpt mailing list Subject: Re: [App_rpt-users] Weather Script This is excellent but it doesn't speak to the requirement of a severe weather warning. Try this http://webpages.charter.net/w0anm/irlp/WxScripts.html and http://webpages.charter.net/w0anm/irlp/scripts/WxScripts-0.9.4.noarch.rpm You want the getWxAlert script. It calls out to NOAA and downloads an XML file formatted in the Govt's new alerting format. If you poll it every minute you'll get an update as soon as it's posted. We have it configured on our 220 repeater such that a severe event gets play instantly and then every 10 minutes for the first hour and then 20 mins for the second hour and then 30 mins thereafter until the event is canceled. The script can be modified to collect other info too. Amber Alerts are now using this XML format as are DHS and other Govt agencies. Mark On 12/10/2010 09:22 AM, David KE6UPI wrote: > I have used this script. Works well. > > > asterisk at home festival weather configuration > > MP3 Audio directly from NOAA! Updated URLs on 12-15-06 > > If you are in the San Diego NOAA Office area (and maybe others, check > your regional NOAA Office homepage from http://weather.gov/), you can > get an audio file of the current forecast for your zone and play it > directly. > > For the San Diego NOAA Office area, go to > http://newweb.wrh.noaa.gov/sgx/ and click on the Audio selection under > Forecasts. Get the URL of the audio file for your zone from the map. > > Create an announcement in wav format from: > http://www.research.att.com/~ttsweb/tts/demo.php > I like the UK-Audrey voice, but try some others too. > Make something like: > latest-forecast.wav "Please wait while I download the latest forecast" > select-weatherorvmc.wav > "Press 1 for voicemail press 2 for the latest weather forecast" > You will have to convert the wav files from 16000Hz to 8000Hz and maybe > speed them up a bit (135%) and reduce the volume (60%) before you use > them. Put them in /var/lib/asterisk/sounds named latest-forecast.wav and > select-weatherorvmc.wav > > Add something like this to your extensions.conf (maybe in the rans > section) to get the latest > forecast when you dial whatever extension (like 865) that you choose. > > My extensions.conf for audio weather: > > | > exten => 865,1,Answer > exten => 865,2,Playback(latest-forecast) > exten => > 865,3,System(/usr/bin/curl -shttp://www.wrh.noaa.gov/sgx/data/audio/LAXSAFC42.mp3 > > /tmp/LAXSAFC42.mp3) > > exten => 865,4,Wait(1) > exten => 865,5,MP3Player(/tmp/LAXSAFC42.mp3) > exten => 865,6,System(rm /tmp/LAXSAFC42.mp3 -f) > exten => 865,7,Hangup > | > > > > If you have trouble, make sure you have curl installed, change the path > above if necessary. find / -type f -name "curl" will find your curl > executable. I'm using MP3Player instead of Playback because I don't have > a sound card in the Asterisk box so mpg123 fails when it tries to use > /dev/dsp. I suppose there is a way to have a dummy dev, but I don't know > how. If you do use Playback instead of MP3Player, don't use the .mp3 > file extension in your extensions.conf. > > > http://www.voip-info.org/wiki/view/asterisk+at+home+festival+weather+configuration > > David > > > On Thu, Dec 9, 2010 at 8:27 PM, Dwaine Garden > wrote: > > I would be interested in that. > > Dwaine > > > "KB3ORS - Brian" > wrote: > > >I know there is weather scripts for irlp. But I am not having any > luck > >for allstar. I am wondering is there anyone who has one is willing > to > >help build one. What I am looking for just a weather alert script > for > >the severe alerts. I don?t want a full blown weather forcast. > > > >Any help appreciated > > > >KB3ORS ? Brian_______________________________________________ > >App_rpt-users mailing list > >App_rpt-users at qrvc.com > >http://qrvc.com/mailman/listinfo/app_rpt-users > > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at qrvc.com > http://qrvc.com/mailman/listinfo/app_rpt-users > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at qrvc.com > http://qrvc.com/mailman/listinfo/app_rpt-users -- /\/\ark Phillips _______________________________________________ App_rpt-users mailing list App_rpt-users at qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1170 / Virus Database: 426/3307 - Release Date: 12/10/10 From kb8pmy at kb8pmy.net Sat Jan 1 19:02:25 2011 From: kb8pmy at kb8pmy.net (Ryan Collier) Date: Sat, 1 Jan 2011 14:02:25 -0500 Subject: [App_rpt-users] Web Pages Message-ID: <1293908545735920900@kb8pmy.net> For anyone that needs it I have modified W0ANM scripts to work with thelinkbox. There might need to be a few things change but only takes a matter of a minute or two. Also, is there anything out there that will give me a basic overview of the asterisk node? Example who is connect, if t links are up, etc? Ryan KB8PMY? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Sun Jan 2 04:08:04 2011 From: ke2n at cs.com (Ken) Date: Sat, 1 Jan 2011 23:08:04 -0500 Subject: [App_rpt-users] iax / Asterisk & I should never be called Message-ID: <000001cbaa32$a8b39820$fa1ac860$@com> No replies on this one - yet Let me add one thing - if I try to connect to the node on port 4569 while the one on port 4568 is already connected, iaxRpt gives an error message about the node already being active and refuses to attempt the connection. So I am sort of concluding that iaxRpt cannot handle a case where there are two nodes on different ports at the same IP address. I am (slightly) surprised that the one that works is the higher-numbered node on the non-standard port, but given the messages that app_rpt is throwing off (below), it's clear that chan_iax.c and channel.c are working in some sort of goofball mode anyhow and I am just lucky that it fails in a way to yield a working connection (these are versions 266 and 267, incidentally). Has anyone else tried iaxRpt on an asterisk system with two nodes behind a common router? Ken From: Ken [mailto:ke2n at cs.com] Sent: Friday, December 31, 2010 12:09 PM To: 'app_rpt-users at ohnosec.org' Subject: iax / Asterisk & I should never be called Been scratching my head here for a week with iaxRpt. I have two nodes: I can connect to one of them (so iaxRpt is obviously working) but not the other App-rpt is trying to tell me something about the problem but I do not know what: atom2*CLI> -- Accepting AUTHENTICATED call from 69.243.53.147: > requested format = ulaw, > requested prefs = (), > actual format = ulaw, > host prefs = (ulaw|gsm), > priority = mine -- Executing [27021 at radio-gui:1] Rpt("IAX2/gui-126", "(27021|X)") in new stack [Dec 31 11:39:13] WARNING[1555]: app_rpt.c:20884 rpt_exec: Cannot find specified system node (27021 == Spawn extension (radio-gui, 27021, 1) exited non-zero on 'IAX2/gui-126' -- Hungup 'IAX2/gui-126' I have looked at iax.conf and extensions.conf and do not see any differences between the two nodes, other than the node numbers. I am connecting from behind the same router. The node that works is on port 4568 (on the internet side) and the one that does not work is on port 4569. The one that works can connect both on the local IP address and on the WAN address with the 4568 port number appended. I have tried making the iaxRpt "listener port 4567, "just for grins" - no effect. >>>>> Why can't app-rtp find it *own* node number when called by iaxRpt? Here is what it looks like when it works (the other node): -- Accepting AUTHENTICATED call from 69.243.53.147: > requested format = gsm, > requested prefs = (), > actual format = gsm, > host prefs = (gsm), > priority = mine -- Executing [27061 at radio-gui:1] Rpt("IAX2/gui-6459", "27061|X") in new stack [Dec 31 12:02:43] NOTICE[22711]: channel.c:2075 __ast_read: No/unknown event '0' on timer for 'IAX2/gui-6459'? [Dec 31 12:02:43] NOTICE[22711]: chan_iax2.c:4677 iax2_read: I should never be called! == Spawn extension (radio-gui, 27061, 1) exited KEEPALIVE on 'IAX2/gui-6459' -- From k8khw at att.net Sun Jan 2 20:13:51 2011 From: k8khw at att.net (k8khw at att.net) Date: Sun, 2 Jan 2011 15:13:51 -0500 Subject: [App_rpt-users] COP commands Message-ID: <07D488C38D0D41EA9FD816BBCD3F7DDB@joycet> Could someone direct me to where we can find a complete list of the cop commands. Were wanting to enable/disable RX audio on a URL if possible. We seem to be having a issue on the RF side of something getting into the reciever. Randy -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Jan 2 22:43:22 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 2 Jan 2011 14:43:22 -0800 Subject: [App_rpt-users] COP commands In-Reply-To: <07D488C38D0D41EA9FD816BBCD3F7DDB@joycet> References: <07D488C38D0D41EA9FD816BBCD3F7DDB@joycet> Message-ID: look in the first few lines of the source code for app_rpt.c JIM WB6NIL From: k8khw at att.net To: app_rpt-users at ohnosec.org Date: Sun, 2 Jan 2011 15:13:51 -0500 Subject: [App_rpt-users] COP commands Could someone direct me to where we can find a complete list of the cop commands. Were wanting to enable/disable RX audio on a URL if possible. We seem to be having a issue on the RF side of something getting into the reciever. Randy _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Mon Jan 3 02:34:02 2011 From: ke2n at cs.com (Ken) Date: Sun, 2 Jan 2011 21:34:02 -0500 Subject: [App_rpt-users] iax / Asterisk & I should never be called Message-ID: <002c01cbaaee$af94e420$0ebeac60$@com> Update The funny warning message comes from the fact that iaxRpt is not compatible with port address translation (PAT). I switched to the "bindport" method of changing the port number. But I still have the original problem: one node connects, the other does not. The connection that works looks like this: -- Executing [27061 at radio-gui:1] Rpt("IAX2/gui-5701", "27061|X") in new stack The one that does not work looks like this: -- Executing [27021 at radio-gui:1] Rpt("IAX2/gui-5264", "(27021|X)") in new stack == Parsing '/etc/asterisk/rpt.conf': Found == Parsing '/var/lib/asterisk/rpt_extnodes': Found [Jan 2 20:11:37] WARNING[24086]: app_rpt.c:20884 rpt_exec: Cannot find specified system node (27021 The obvious difference being the left parenthesis ahead of the node number. It seems that Asterisk is being asked to connect 27061 in one case and "(27021" in the other case. And Asterisk is complaining about a node whose number starts with a "(" I cannot figure out where the extra "(" is coming from.. Tnx Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Sat Jan 8 22:27:25 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Sat, 08 Jan 2011 14:27:25 -0800 Subject: [App_rpt-users] Two Servers Behind NAT Router? Message-ID: Is it possible to run two servers on one NATed network? I assume the second server one would be on some port other then 4569 but I don't see how to set that up. TIA. -- Tim :wq From buddy at brannan.name Tue Jan 11 01:05:24 2011 From: buddy at brannan.name (Buddy Brannan) Date: Mon, 10 Jan 2011 20:05:24 -0500 Subject: [App_rpt-users] A Bit of Irony Message-ID: Can we get allison to record the word "Repeater"? It strikes me as a little ironic that repeater control software doesn't know the word "repeater". (Besides, we could then make up repeater ID's that say repeater, without using Cepstral, if she said it.) -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY From kb2ear at kb2ear.net Tue Jan 11 01:59:09 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Mon, 10 Jan 2011 20:59:09 -0500 Subject: [App_rpt-users] A Bit of Irony In-Reply-To: References: Message-ID: <004301cbb133$22e320f0$68a962d0$@kb2ear.net> On a properly installed system the word repeater is located in /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater with localplay repeater -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan Sent: Monday, January 10, 2011 8:05 PM To: app_rpt mailing list Subject: [App_rpt-users] A Bit of Irony Can we get allison to record the word "Repeater"? It strikes me as a little ironic that repeater control software doesn't know the word "repeater". (Besides, we could then make up repeater ID's that say repeater, without using Cepstral, if she said it.) -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From telesistant at hotmail.com Tue Jan 11 02:08:13 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 10 Jan 2011 18:08:13 -0800 Subject: [App_rpt-users] A Bit of Irony In-Reply-To: <004301cbb133$22e320f0$68a962d0$@kb2ear.net> References: , <004301cbb133$22e320f0$68a962d0$@kb2ear.net> Message-ID: You know, irony can be so ironic.... :-) JIM WB6NIL > From: kb2ear at kb2ear.net > To: buddy at brannan.name > Date: Mon, 10 Jan 2011 20:59:09 -0500 > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] A Bit of Irony > > On a properly installed system the word repeater is located in > /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater > with localplay repeater > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan > Sent: Monday, January 10, 2011 8:05 PM > To: app_rpt mailing list > Subject: [App_rpt-users] A Bit of Irony > > Can we get allison to record the word "Repeater"? It strikes me as a little > ironic that repeater control software doesn't know the word "repeater". > (Besides, we could then make up repeater ID's that say repeater, without > using Cepstral, if she said it.) > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From buddy at brannan.name Tue Jan 11 02:52:58 2011 From: buddy at brannan.name (Buddy Brannan) Date: Mon, 10 Jan 2011 21:52:58 -0500 Subject: [App_rpt-users] A Bit of Irony In-Reply-To: <004301cbb133$22e320f0$68a962d0$@kb2ear.net> References: <004301cbb133$22e320f0$68a962d0$@kb2ear.net> Message-ID: <06AF6A1C-F9BC-43B4-87B5-0DC80A0FB1E1@brannan.name> Thanks Scott, I was looking in the wrong place (/var/lib/sounds/rpt). Think I looked in the root sounds directory before, but a long time ago. Now I have an ID that works a treat :) Now if I can just get this talkover ID followed by voice ID issue nailed down.... -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Jan 10, 2011, at 8:59 PM, Scott Weis wrote: > On a properly installed system the word repeater is located in > /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater > with localplay repeater > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan > Sent: Monday, January 10, 2011 8:05 PM > To: app_rpt mailing list > Subject: [App_rpt-users] A Bit of Irony > > Can we get allison to record the word "Repeater"? It strikes me as a little > ironic that repeater control software doesn't know the word "repeater". > (Besides, we could then make up repeater ID's that say repeater, without > using Cepstral, if she said it.) > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > From buddy at brannan.name Tue Jan 11 02:53:41 2011 From: buddy at brannan.name (Buddy Brannan) Date: Mon, 10 Jan 2011 21:53:41 -0500 Subject: [App_rpt-users] A Bit of Irony In-Reply-To: References: , <004301cbb133$22e320f0$68a962d0$@kb2ear.net> Message-ID: <611A6B6B-C4D9-4C53-8159-14DF2FB62A04@brannan.name> It can, especially when you're ironically wrong. Sorry 'bout that. I was looking in the wrong place. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Jan 10, 2011, at 9:08 PM, Jim Duuuude wrote: > You know, irony can be so ironic.... :-) > > JIM WB6NIL > > > From: kb2ear at kb2ear.net > > To: buddy at brannan.name > > Date: Mon, 10 Jan 2011 20:59:09 -0500 > > CC: app_rpt-users at ohnosec.org > > Subject: Re: [App_rpt-users] A Bit of Irony > > > > On a properly installed system the word repeater is located in > > /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater > > with localplay repeater > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan > > Sent: Monday, January 10, 2011 8:05 PM > > To: app_rpt mailing list > > Subject: [App_rpt-users] A Bit of Irony > > > > Can we get allison to record the word "Repeater"? It strikes me as a little > > ironic that repeater control software doesn't know the word "repeater". > > (Besides, we could then make up repeater ID's that say repeater, without > > using Cepstral, if she said it.) > > -- > > Buddy Brannan, KB5ELV - Erie, PA > > Phone: (814) 860-3194 or 888-75-BUDDY > > > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From kt9ac at ameritech.net Tue Jan 11 03:15:45 2011 From: kt9ac at ameritech.net (=?utf-8?B?VG9ueSBLVDlBQw==?=) Date: Mon, 10 Jan 2011 21:15:45 -0600 Subject: [App_rpt-users] =?utf-8?q?A_Bit_of_Irony?= Message-ID: <902101.69587.qm@smtp103.sbc.mail.re3.yahoo.com> Me too. Setting the wait ID timer to 4 seconds prevents the double id's, but 2 seconds still does it (both of mine are CW). ----- Reply message ----- From: "Buddy Brannan" Date: Mon, Jan 10, 2011 8:52 pm Subject: [App_rpt-users] A Bit of Irony To: "Scott Weis" Cc: Thanks Scott, I was looking in the wrong place (/var/lib/sounds/rpt). Think I looked in the root sounds directory before, but a long time ago. Now I have an ID that works a treat :) Now if I can just get this talkover ID followed by voice ID issue nailed down.... -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Jan 10, 2011, at 8:59 PM, Scott Weis wrote: > On a properly installed system the word repeater is located in > /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater > with localplay repeater > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan > Sent: Monday, January 10, 2011 8:05 PM > To: app_rpt mailing list > Subject: [App_rpt-users] A Bit of Irony > > Can we get allison to record the word "Repeater"? It strikes me as a little > ironic that repeater control software doesn't know the word "repeater". > (Besides, we could then make up repeater ID's that say repeater, without > using Cepstral, if she said it.) > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at michiganbroadband.com Tue Jan 11 03:45:04 2011 From: steve at michiganbroadband.com (Steve Gladden) Date: Mon, 10 Jan 2011 22:45:04 -0500 Subject: [App_rpt-users] A Bit of Irony In-Reply-To: References: , <004301cbb133$22e320f0$68a962d0$@kb2ear.net> Message-ID: <001201cbb141$eee95210$ccbbf630$@michiganbroadband.com> I personally am considering having Allison record the phrase "Repeat R". Just for old time's sake. You know you want it!! -SteveG From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jim Duuuude Sent: Monday, January 10, 2011 9:08 PM To: kb2ear at kb2ear.net; Buddy Brannan Cc: app_rpt mailing list Subject: Re: [App_rpt-users] A Bit of Irony You know, irony can be so ironic.... :-) JIM WB6NIL > From: kb2ear at kb2ear.net > To: buddy at brannan.name > Date: Mon, 10 Jan 2011 20:59:09 -0500 > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] A Bit of Irony > > On a properly installed system the word repeater is located in > /var/lib/asterisk/sounds/repeater.gsm and can be called from the repeater > with localplay repeater > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Buddy Brannan > Sent: Monday, January 10, 2011 8:05 PM > To: app_rpt mailing list > Subject: [App_rpt-users] A Bit of Irony > > Can we get allison to record the word "Repeater"? It strikes me as a little > ironic that repeater control software doesn't know the word "repeater". > (Besides, we could then make up repeater ID's that say repeater, without > using Cepstral, if she said it.) > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb2ear at kb2ear.net Tue Jan 11 04:11:52 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Mon, 10 Jan 2011 23:11:52 -0500 Subject: [App_rpt-users] URI ptt current sink Message-ID: <00e601cbb145$ad0d7070$07285150$@kb2ear.net> How much current can the PTT on a URI sink. I have a device that draws between 200- 250 ma at 5vdc and don't want to smoke it. Thanks, Scott From dkramer at dmkeng.com Tue Jan 11 06:35:22 2011 From: dkramer at dmkeng.com (David Kramer) Date: Mon, 10 Jan 2011 22:35:22 -0800 Subject: [App_rpt-users] URI ptt current sink In-Reply-To: <00e601cbb145$ad0d7070$07285150$@kb2ear.net> Message-ID: Hi Scott, The URI PTT open collector output will only sink about 50mA. You will need to boost the output for your application. See http://www.dmkeng.com/images/HIGH_CURRENT_PTT.pdf for a suggestion on how to do this. If you don't need 4 amps you can use a smaller MOSFET. Please contact me if you need any more info about this. David Kramer DMK Engineering Inc. 310-544-1222 -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Scott Weis Sent: Monday, January 10, 2011 8:12 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] URI ptt current sink How much current can the PTT on a URI sink. I have a device that draws between 200- 250 ma at 5vdc and don't want to smoke it. Thanks, Scott _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From n7pkt at picklejar.org Tue Jan 11 18:26:52 2011 From: n7pkt at picklejar.org (n7pkt at picklejar.org) Date: Tue, 11 Jan 2011 10:26:52 -0800 (PST) Subject: [App_rpt-users] Audio gateway issues?? Message-ID: Hi, I've been getting distorted and/or over driven audio from the Alaskan Reflector audio gateway (27299 and 27372). Is anyone else having problems with audio coming from the IRLP sides of these gateway nodes? I'm trying to eliminate causes on my end right now. I get pristine audio from an allstar to allstar connection and completely understandable (but lower quality) audio when I connect to the Alaskan Reflector via EchoLink. The only problem I seem to have is with audio coming from the IRLP side of the gateway nodes. 8-Dale From ckraly at gmail.com Tue Jan 11 18:40:57 2011 From: ckraly at gmail.com (Chuck Kraly) Date: Tue, 11 Jan 2011 12:40:57 -0600 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: Message-ID: I missed something. I thought we were asked to remove all IRLP connections from our nodes..... CHuck K0XM On Tue, Jan 11, 2011 at 12:26 PM, wrote: > Hi, > > I've been getting distorted and/or over driven audio from the Alaskan > Reflector audio gateway (27299 and 27372). Is anyone else having > problems with audio coming from the IRLP sides of these gateway nodes? > I'm trying to eliminate causes on my end right now. > > I get pristine audio from an allstar to allstar connection and > completely understandable (but lower quality) audio when I connect to > the Alaskan Reflector via EchoLink. The only problem I seem to have is > with audio coming from the IRLP side of the gateway nodes. > > 8-Dale > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Tue Jan 11 19:20:16 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 11 Jan 2011 11:20:16 -0800 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: , Message-ID: We have. It isnt on an app_rpt/allstar node. Its physically tied into an IRLP reflector at the source, which I guess is up to the discression of the reflector owner. From: ckraly at gmail.com Date: Tue, 11 Jan 2011 12:40:57 -0600 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Audio gateway issues?? I missed something. I thought we were asked to remove all IRLP connections from our nodes..... CHuck K0XM On Tue, Jan 11, 2011 at 12:26 PM, wrote: Hi, I've been getting distorted and/or over driven audio from the Alaskan Reflector audio gateway (27299 and 27372). Is anyone else having problems with audio coming from the IRLP sides of these gateway nodes? I'm trying to eliminate causes on my end right now. I get pristine audio from an allstar to allstar connection and completely understandable (but lower quality) audio when I connect to the Alaskan Reflector via EchoLink. The only problem I seem to have is with audio coming from the IRLP side of the gateway nodes. 8-Dale _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From vk3jed at vkradio.com Tue Jan 11 20:35:04 2011 From: vk3jed at vkradio.com (Tony Langdon, VK3JED) Date: Wed, 12 Jan 2011 07:35:04 +1100 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: Message-ID: <4d2cbf00.114ddf0a.6729.ffff8d1d@mx.google.com> At 06:20 AM 1/12/2011, Jim Duuuude wrote: >We have. It isnt on an app_rpt/allstar node. Its physically tied into an IRLP >reflector at the source, which I guess is up to the discression of >the reflector >owner. That's correct. Reflector owners do often tie a channel to other networks. I am planning on linking IRLP reflector 9559 to an AllStar hub, using chan_tlb and thelinkbox. Reflector interconnections are permitted (provided it's done by the owner, or with owner approval), because they are fixed and easily avoided by people who want to be IRLP snobs. ;) Half of my reflector channels already link to Echolink, and I want to add AllStar to that mix. 73 de VK3JED / VK3IRL http://vkradio.com From thorn at myactv.net Tue Jan 11 20:58:18 2011 From: thorn at myactv.net (Greg Thornwall) Date: Tue, 11 Jan 2011 15:58:18 -0500 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: <4d2cbf00.114ddf0a.6729.ffff8d1d@mx.google.com> References: <4d2cbf00.114ddf0a.6729.ffff8d1d@mx.google.com> Message-ID: <4D2CC46A.4090806@myactv.net> It (27299) has been working OK audio wise, sometimes it does goes out to lunch - you stop getting audio, I restart it and it's back to normal. It sounds fine via the web transceiver a little bit ago. Not sure what's going on. I wonder if the IRLP people changed something? Greg On 01/11/2011 03:35 PM, Tony Langdon, VK3JED wrote: > At 06:20 AM 1/12/2011, Jim Duuuude wrote: >> We have. It isnt on an app_rpt/allstar node. Its physically tied into >> an IRLP >> reflector at the source, which I guess is up to the discression of the >> reflector >> owner. > > That's correct. Reflector owners do often tie a channel to other > networks. I am planning on linking IRLP reflector 9559 to an AllStar > hub, using chan_tlb and thelinkbox. Reflector interconnections are > permitted (provided it's done by the owner, or with owner approval), > because they are fixed and easily avoided by people who want to be IRLP > snobs. ;) Half of my reflector channels already link to Echolink, and I > want to add AllStar to that mix. > > 73 de VK3JED / VK3IRL > http://vkradio.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From k6kya at hokeynet.net Tue Jan 11 21:28:23 2011 From: k6kya at hokeynet.net (Steve Passmore) Date: Tue, 11 Jan 2011 13:28:23 -0800 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: , Message-ID: <4D2CCB77.8050805@hokeynet.net> Dave Cameron of IRLP has stated that reflector channels can have crosslinks. They've had echolink conferences on the gsm channels for years. There are a few IRLP reflector channels that have crosslink allstar nodes that are stuck at ver 876 because of this. It would have been nice to just leave the IRLP stuff in the source but I guess there's no going back now. Steve On 1/11/2011 11:20, Jim Duuuude wrote: > We have. It isnt on an app_rpt/allstar node. Its physically tied into > an IRLP > reflector at the source, which I guess is up to the discression of the > reflector > owner. > > ------------------------------------------------------------------------ > From: ckraly at gmail.com > Date: Tue, 11 Jan 2011 12:40:57 -0600 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Audio gateway issues?? > > I missed something. I thought we were asked to remove all IRLP > connections from our nodes..... > > CHuck K0XM > > On Tue, Jan 11, 2011 at 12:26 PM, > wrote: > > Hi, > > I've been getting distorted and/or over driven audio from the > Alaskan > Reflector audio gateway (27299 and 27372). Is anyone else having > problems with audio coming from the IRLP sides of these gateway nodes? > I'm trying to eliminate causes on my end right now. > > I get pristine audio from an allstar to allstar connection and > completely understandable (but lower quality) audio when I connect to > the Alaskan Reflector via EchoLink. The only problem I seem to have is > with audio coming from the IRLP side of the gateway nodes. > > 8-Dale > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From k6kya at hokeynet.net Wed Jan 12 02:37:19 2011 From: k6kya at hokeynet.net (Steve Passmore) Date: Tue, 11 Jan 2011 18:37:19 -0800 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: <008601cbb1e3$e0a0fad0$a1e2f070$@org> References: , <4D2CCB77.8050805@hokeynet.net> <008601cbb1e3$e0a0fad0$a1e2f070$@org> Message-ID: <4D2D13DF.7070904@hokeynet.net> SVN Version 876 of the app_rpt source code. The last version that had IRLP support before it was removed from the code. I should have specified that crosslinks are only allowed by the reflector owner and they should be stated in the reflector's channel info. Steve On 1/11/2011 15:04, Kent Johnson wrote: > > What does ver 876 mean? > > *From:*app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] *On Behalf Of *Steve Passmore > *Sent:* Tuesday, January 11, 2011 1:28 PM > *To:* app_rpt-users at ohnosec.org > *Subject:* Re: [App_rpt-users] Audio gateway issues?? > > Dave Cameron of IRLP has stated that reflector channels can have > crosslinks. They've had echolink conferences on the gsm channels for > years. > > There are a few IRLP reflector channels that have crosslink allstar > nodes that are stuck at ver 876 because of this. It would have been > nice to just leave the IRLP stuff in the source but I guess there's no > going back now. > > Steve > > On 1/11/2011 11:20, Jim Duuuude wrote: > > We have. It isnt on an app_rpt/allstar node. Its physically tied into > an IRLP > reflector at the source, which I guess is up to the discression of the > reflector > owner. > > ------------------------------------------------------------------------ > > From: ckraly at gmail.com > Date: Tue, 11 Jan 2011 12:40:57 -0600 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Audio gateway issues?? > > I missed something. I thought we were asked to remove all IRLP > connections from our nodes..... > > CHuck K0XM > > On Tue, Jan 11, 2011 at 12:26 PM, > wrote: > > Hi, > > I've been getting distorted and/or over driven audio from the Alaskan > Reflector audio gateway (27299 and 27372). Is anyone else having > problems with audio coming from the IRLP sides of these gateway nodes? > I'm trying to eliminate causes on my end right now. > > I get pristine audio from an allstar to allstar connection and > completely understandable (but lower quality) audio when I connect to > the Alaskan Reflector via EchoLink. The only problem I seem to have is > with audio coming from the IRLP side of the gateway nodes. > > 8-Dale > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhammock.hur at gmail.com Wed Jan 12 05:32:21 2011 From: rhammock.hur at gmail.com (Randy Hammock) Date: Tue, 11 Jan 2011 21:32:21 -0800 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: <4D2D13DF.7070904@hokeynet.net> References: <4D2CCB77.8050805@hokeynet.net> <008601cbb1e3$e0a0fad0$a1e2f070$@org> <4D2D13DF.7070904@hokeynet.net> Message-ID: I have the audio and control lines from my IRLP node connected to a URI as one of the ports on my Asterisk Controlled (Allstar) repeater. I've had a discussion with Dave Cameron about this and he agrees with my "logic" where, when using Asterisk/Allstar to control a repeater, with IRLP connected to this repeater via a URI, it would be virtually impossible to tell the difference between this setup and and IRLP node connected to a sufficiently advanced, multi-port repeater controller on a large linked system, that also has remote bases and autopatches. Also, I put forward that few, if any, IRLP node operators who have their nodes connected to such extensive systems, have not implemented any sort of lockout controls such that when the IRLP node is in uses, remote bases, autopatches or even links still function "normally". Therefore, this whole business about IRLP on Allstar is a load BS. OK, so I'm back to a system that automatically accepts Daves diddling and allows me access to IRLP in pretty much the same way as any other repeater operator. My other analogy was to think of Allstar as one big, distributed, repeater controller. Why is it OK to connect IRLP to some repeater controllers but not others? Hmm. On Tue, Jan 11, 2011 at 6:37 PM, Steve Passmore wrote: > SVN Version 876 of the app_rpt source code.? The last version that had IRLP > support before it was removed from the code. > > I should have specified that crosslinks are only allowed by the reflector > owner and they should be stated in the reflector's channel info. > > Steve > > On 1/11/2011 15:04, Kent Johnson wrote: > > What does ver 876 mean? > > > > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Passmore > Sent: Tuesday, January 11, 2011 1:28 PM > > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Audio gateway issues?? > > > > Dave Cameron of IRLP has stated that reflector channels can have > crosslinks.? They've had echolink conferences on the gsm channels for > years. > > There are a few IRLP reflector channels that have crosslink allstar nodes > that are stuck at ver 876 because of this.? It would have been nice to just > leave the IRLP stuff in the source but I guess there's no going back now. > > Steve > > On 1/11/2011 11:20, Jim Duuuude wrote: > > We have. It isnt on an app_rpt/allstar node. Its physically tied into an > IRLP > reflector at the source, which I guess is up to the discression of the > reflector > owner. > > ________________________________ > > From: ckraly at gmail.com > Date: Tue, 11 Jan 2011 12:40:57 -0600 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Audio gateway issues?? > > I missed something. I thought we were asked to remove all IRLP connections > from our nodes..... > > CHuck K0XM > > On Tue, Jan 11, 2011 at 12:26 PM, wrote: > > ? Hi, > > ? I've been getting distorted and/or over driven audio from the Alaskan > Reflector audio gateway (27299 and 27372). Is anyone else having > problems with audio coming from the IRLP sides of these gateway nodes? > I'm trying to eliminate causes on my end right now. > > ? I get pristine audio from an allstar to allstar connection and > completely understandable (but lower quality) audio when I connect to > the Alaskan Reflector via EchoLink. The only problem I seem to have is > with audio coming from the IRLP side of the gateway nodes. > > ? 8-Dale > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -- Randy Hammock Phone: 818-925-4576 From ke2n at cs.com Thu Jan 13 01:45:05 2011 From: ke2n at cs.com (Ken) Date: Wed, 12 Jan 2011 20:45:05 -0500 Subject: [App_rpt-users] web transceiver? In-Reply-To: <000001cba90d$5f3a0ce0$1dae26a0$@com> References: <000001cba90d$5f3a0ce0$1dae26a0$@com> Message-ID: <002801cbb2c3$807c55b0$81750110$@com> Is the web transceiver broken? Or has Microsoft's latest update done something bad to my PC? When I start the web transceiver I do not get any nodes listed . (same with IE and Chrome) Ken From telesistant at hotmail.com Thu Jan 13 02:03:00 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Wed, 12 Jan 2011 18:03:00 -0800 Subject: [App_rpt-users] web transceiver? In-Reply-To: <002801cbb2c3$807c55b0$81750110$@com> References: <000001cba90d$5f3a0ce0$1dae26a0$@com>, <002801cbb2c3$807c55b0$81750110$@com> Message-ID: Well, it wasnt the webtransceiver that was the problem, merely an effect of the problem which should now be fixed. Thanks for letting me know. JIM WB6NIL > From: ke2n at cs.com > To: app_rpt-users at ohnosec.org > Date: Wed, 12 Jan 2011 20:45:05 -0500 > Subject: [App_rpt-users] web transceiver? > > Is the web transceiver broken? Or has Microsoft's latest update done > something bad to my PC? > > When I start the web transceiver I do not get any nodes listed . (same with > IE and Chrome) > > Ken > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Thu Jan 13 02:02:58 2011 From: ke2n at cs.com (Ken) Date: Wed, 12 Jan 2011 21:02:58 -0500 Subject: [App_rpt-users] web transceiver - now working again ... References: <000001cba90d$5f3a0ce0$1dae26a0$@com> Message-ID: <000001cbb2c6$000caad0$00260070$@com> Whatever the problem was ... it's now OK. Ken > -----Original Message----- > From: Ken [mailto:ke2n at cs.com] > Sent: Wednesday, January 12, 2011 8:45 PM > To: 'app_rpt-users at ohnosec.org' > Subject: web transceiver? > > Is the web transceiver broken? Or has Microsoft's latest update done > something bad to my PC? > > When I start the web transceiver I do not get any nodes listed . (same > with IE and Chrome) > > Ken From n7pkt at picklejar.org Thu Jan 13 19:00:59 2011 From: n7pkt at picklejar.org (n7pkt at picklejar.org) Date: Thu, 13 Jan 2011 11:00:59 -0800 (PST) Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: <4D2CC46A.4090806@myactv.net> References: <4d2cbf00.114ddf0a.6729.ffff8d1d@mx.google.com> <4D2CC46A.4090806@myactv.net> Message-ID: <440417c53e7eee5a1c9a0bbb54f9c6ea.squirrel@webmail.hybotics.com> > Not sure what's > going on. I wonder if the IRLP people changed something? It sounds like the audio level coming from the IRLP side is too high. Right now I am getting distorted audio listening to the Morning Net, but only from the IRLP side. 8-Dale From n7pkt at picklejar.org Fri Jan 14 20:40:43 2011 From: n7pkt at picklejar.org (n7pkt at picklejar.org) Date: Fri, 14 Jan 2011 12:40:43 -0800 (PST) Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: <4D2F4D08.5000809@myactv.net> References: <4d2cbf00.114ddf0a.6729.ffff8d1d@mx.google.com> <4D2CC46A.4090806@myactv.net> <440417c53e7eee5a1c9a0bbb54f9c6ea.squirrel@webmail.hybotics.com> <4D2F4D08.5000809@myactv.net> Message-ID: <32522da0884c63c4d1c187442155f67c.squirrel@webmail.hybotics.com> > > Sounds ok on the web tx. Must be something with allstar. I have my > allstar radio on dstar now, I can try to listen on it later. Well, I get perfect audio on regular AllStar to AllStar, such as from those who are also connected to your node using AllStar. I also get perfectly readable audio when I am connected to EchoLink. This **seems** to point to a problem somewhere between IRLP and AllStar, going from IRLP to AllStar. The problem is always with audio from the IRLP side. 8-Dale > On 01/13/2011 02:00 PM, n7pkt at picklejar.org wrote: >> >>> Not sure what's >>> going on. I wonder if the IRLP people changed something? >> >> It sounds like the audio level coming from the IRLP side is too high. >> Right now I am getting distorted audio listening to the Morning Net, but >> only from the IRLP side. >> >> 8-Dale >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> > From g4rky at yahoo.co.uk Fri Jan 14 21:27:29 2011 From: g4rky at yahoo.co.uk (Matt Beasant) Date: Fri, 14 Jan 2011 21:27:29 +0000 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: <4D2CCB77.8050805@hokeynet.net> <008601cbb1e3$e0a0fad0$a1e2f070$@org> <4D2D13DF.7070904@hokeynet.net> Message-ID: In case anyone is interested.... I have scripted a solution that is currently acceptable to Dave Cameron and Dave Gingrinch of IRLP fame, as an interim solution - this allows me to keep my allstar node functioning with IRLP while I try and devise a solution to keep my 2 IRLP nodes "alive", currently running within Allstar. Basically it uses the connect and disconnect scripts (that used to tweet the repeater status) to determine if an IRLP node is connecting. If it is an IRLP node, then the "No Incoming mode" is selected, stopping any crosslinking to Echolink or other Allstar nodes. This doesnt affect the existing Allstar connections in use to link my repeaters together, which is why its difficult for me to use traditional IRLP nodes. If an additional Allstar node or Echolink node connects, the script deletes the "enable" file from the IRLP/Local directory, thereby disabling the IRLP node and stopping any incoming or outgoing IRLP connections for the duration. Once the other node disconnects the "enable" file is restored, enabling the IRLP node once more. I've done this externally to the Allstar code as I dont know how to code it within the applcation but I am sure it would be possible to code a solution to keep the IRLP folk happy and with inherent flexibility within Allstar, it could be enabled and disabled as required. I can't emphasise enough how great it would be if we could have IRLP back as an integral part of Allstar - is it dead forever? I hope not. Matt G4RKY -------------- next part -------------- An HTML attachment was scrubbed... URL: From vk3jed at vkradio.com Fri Jan 14 22:16:19 2011 From: vk3jed at vkradio.com (Tony Langdon, VK3JED) Date: Sat, 15 Jan 2011 09:16:19 +1100 Subject: [App_rpt-users] Audio gateway issues?? In-Reply-To: References: <4D2CCB77.8050805@hokeynet.net> <008601cbb1e3$e0a0fad0$a1e2f070$@org> <4D2D13DF.7070904@hokeynet.net> Message-ID: <4d30cb3b.d37b0e0a.4164.65a0@mx.google.com> At 08:27 AM 1/15/2011, Matt Beasant wrote: >In case anyone is interested.... >I have scripted a solution that is currently acceptable to Dave >Cameron and Dave Gingrinch of IRLP fame, as an interim solution - >this allows me to keep my allstar node functioning with IRLP while I >try and devise a solution to keep my 2 IRLP nodes "alive", currently >running within Allstar. > >Basically it uses the connect and disconnect scripts (that used to >tweet the repeater status) to determine if an IRLP node is >connecting. If it is an IRLP node, then the "No Incoming mode" is >selected, stopping any crosslinking to Echolink or other Allstar >nodes. This doesnt affect the existing Allstar connections in use to >link my repeaters together, which is why its difficult for me to use >traditional IRLP nodes. This is pretty much how EchoIRLP does it, and something I remember suggesting way back. >If an additional Allstar node or Echolink node connects, the script >deletes the "enable" file from the IRLP/Local directory, thereby >disabling the IRLP node and stopping any incoming or outgoing IRLP >connections for the duration. Once the other node disconnects the >"enable" file is restored, enabling the IRLP node once more. A more "correct" way of doing it would be to flag your node as busy, which is achieved simply by putting your _own_ IRLP node number into $LOCAL/active. When other IRLP nodes attempt to connect, they see you as busy, and the status page will report you as "connected to Echolink", instead of "offline". This is the method EchoIRLP uses, which was worked out in consultation with Dave Cameron many years ago. >I've done this externally to the Allstar code as I dont know how to >code it within the applcation but I am sure it would be possible to >code a solution to keep the IRLP folk happy and with inherent >flexibility within Allstar, it could be enabled and disabled as required. > >I can't emphasise enough how great it would be if we could have IRLP >back as an integral part of Allstar - is it dead forever? I hope not. I think if the above is implemented, and run past Dave Cameron, you have every chance of getting AllStar back into the IRLP fold. This is all that was required in the first place. From what I understand, and asking questions of the Asterisk gurus, this is entirely feasible. I just never had an AllStar node working to develop it myself (and that can't happen until later this year at the earliest). I have the hardware (a couple of URIs, radios, etc) and the AllStar node number, but am in a somewhat temporary situation at the moment. 73 de VK3JED / VK3IRL http://vkradio.com From telesistant at hotmail.com Sat Jan 15 18:21:51 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 15 Jan 2011 10:21:51 -0800 Subject: [App_rpt-users] double ID fixed Message-ID: I think we fixed the double-ID problem. Whoever is having these problems, please download the latest copy of app_rpt.c from SVN. Thanks JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From g4rky at yahoo.co.uk Sat Jan 15 22:27:44 2011 From: g4rky at yahoo.co.uk (Matt Beasant) Date: Sat, 15 Jan 2011 22:27:44 +0000 Subject: [App_rpt-users] scripts to lockout other connections during an IRLP connection In-Reply-To: References: Message-ID: Hi After my earlier posting about the IRLP scripts, I had a number of emails asking for the scripts and a how to. Well here it is. First let me say that I know this is a nasty way to achieve this but its the only way I could come up with as I am not a programmer / coder and I am also crap at script writing! Next, there is bound to be a much better / neater / more correct way to achieve this but I am not the guy to do it - this is the limit of my scripting ability right now! Finally, this will not affect any pre existing connections - this is by design as I use Allstar to link my repeaters together and one of these repeaters has an Echolink and IRLP node on it. This node is where the scripts live. My linked repeaters are not affected by this setup, the Echolink and IRLP calls come and go as do the Allstar connections. Tony VK3JED has suggested that it would be better to mark the node as busy rather than disabled and I agree, so I'm going to work on this sometime soon. I made these scripts by modifying the twitter scripts that Randy Hammock gave me a while ago. First you need to modify your rpt.conf file to refer to the connect and disconnect scripts by adding these lines: connpgm=/etc/asterisk/connectprog.sh discpgm=/etc/asterisk/disconprog.sh in the node stanza. Then add these files to your /etc/asterisk directory: connectprog.sh disconprog.sh irlp_en.sh irlp_dis.sh It is VITAL that you edit these scripts to add your node number in the two locations stated in the script itself. The scripts can be downloaded from here: http://www.gb3fh.eclipse.co.uk/allstar/ Good luck! Oh and don't blame me if you break anything! 73 Matt G4RKY -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb2ear at kb2ear.net Sun Jan 16 18:28:59 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Sun, 16 Jan 2011 13:28:59 -0500 Subject: [App_rpt-users] Echolink announcements. Message-ID: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net> Has anyone else noticed that the eannmode= and echolinkdefault= no longer work? I have eannmode=0 and echolinkdefault=0 and still get echolink announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. Thanks & 73, Scott KB2EAR From buddy at brannan.name Sun Jan 16 19:23:04 2011 From: buddy at brannan.name (Buddy Brannan) Date: Sun, 16 Jan 2011 14:23:04 -0500 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net> References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net> Message-ID: On Jan 16, 2011, at 1:28 PM, Scott Weis wrote: > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. Yep, I've noticed this, too. Well, not the suppression of Echolink, because I never used that. However, W2DB turned me on to the solution, at least, to changing how Echolink nodes are announced (don't think you can suppress, though). Set up DTMF commands for cop 42 43 and 44. Then stick the appropriate one in your startup macro. > -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY > Thanks & 73, > Scott KB2EAR > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From kb4fxc at inttek.net Sun Jan 16 22:00:24 2011 From: kb4fxc at inttek.net (David McGough) Date: Sun, 16 Jan 2011 17:00:24 -0500 (EST) Subject: [App_rpt-users] Echolink announcements. In-Reply-To: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net> Message-ID: Hi everyone, I, too, noticed that echolink announcements went away after upgrading recently....After looking through the app_rpt.c code, I found a "new" variable that seems to need to be set, too. In the node stanza, try this: eannmode=2 tannmode=2 ...This worked for me....Anyone know what "tannmode" is being used for?? 73, David kb4fxc On Sun, 16 Jan 2011, Scott Weis wrote: > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > Thanks & 73, > Scott KB2EAR > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From telesistant at hotmail.com Mon Jan 17 00:36:39 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 16 Jan 2011 16:36:39 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, Message-ID: Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 17 00:37:56 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 16 Jan 2011 16:37:56 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, Message-ID: By the way, tannmode has nothing to do with echolink. Its for the TheLinkBox support. > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From kc2vrj at gmail.com Mon Jan 17 03:59:23 2011 From: kc2vrj at gmail.com (Paul M. Nannery) Date: Sun, 16 Jan 2011 22:59:23 -0500 Subject: [App_rpt-users] Echolink Message-ID: <000001cbb5fa$ee21e000$ca65a000$@gmail.com> Ok guys, I see reference to disabling echolink announcements on the web wiki however when you set eannmode=0 you still get the node number announced even with the just released update by jim. I looked at arr_rpt.c and notice thare is no setting in the code for disable would it be possible to add this? From kb2ear at kb2ear.net Mon Jan 17 04:45:12 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Sun, 16 Jan 2011 23:45:12 -0500 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, Message-ID: <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> I just installed it here. I now have callsigns again, but still can't turn of the announcements all together. Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Sunday, January 16, 2011 7:37 PM To: kb4fxc at inttek.net; kb2ear at kb2ear.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 17 05:41:41 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 16 Jan 2011 21:41:41 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> Message-ID: Frankly, I wasnt aware that you were supposed to be able to turn them off completely. Where did you get the idea that it does this?? JIM From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Sun, 16 Jan 2011 23:45:12 -0500 I just installed it here. I now have callsigns again, but still can?t turn of the announcements all together. Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Sunday, January 16, 2011 7:37 PM To: kb4fxc at inttek.net; kb2ear at kb2ear.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb2ear at kb2ear.net Mon Jan 17 16:08:33 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Mon, 17 Jan 2011 11:08:33 -0500 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> Message-ID: <03c001cbb660$ca693800$5f3ba800$@kb2ear.net> http://ohnosec.org/drupal/node/107 eannmode 0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both 1 echolinkdefault 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode 2 Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Monday, January 17, 2011 12:42 AM To: kb2ear at kb2ear.net; kb4fxc at inttek.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Frankly, I wasnt aware that you were supposed to be able to turn them off completely. Where did you get the idea that it does this?? JIM _____ From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Sun, 16 Jan 2011 23:45:12 -0500 I just installed it here. I now have callsigns again, but still can't turn of the announcements all together. Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Sunday, January 16, 2011 7:37 PM To: kb4fxc at inttek.net; kb2ear at kb2ear.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 17 16:17:58 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 17 Jan 2011 08:17:58 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: <03c001cbb660$ca693800$5f3ba800$@kb2ear.net> References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> , <03c001cbb660$ca693800$5f3ba800$@kb2ear.net> Message-ID: excellent point. Well, should I change the documentation to match the design, or change the design to match the documentation? JIM From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Mon, 17 Jan 2011 11:08:33 -0500 http://ohnosec.org/drupal/node/107 eannmode 0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both 1echolinkdefault 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode 2Thanks & 73,Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Monday, January 17, 2011 12:42 AM To: kb2ear at kb2ear.net; kb4fxc at inttek.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Frankly, I wasnt aware that you were supposed to be able to turn them off completely. Where did you get the idea that it does this?? JIM From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Sun, 16 Jan 2011 23:45:12 -0500I just installed it here. I now have callsigns again, but still can?t turn of the announcements all together. Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Sunday, January 16, 2011 7:37 PM To: kb4fxc at inttek.net; kb2ear at kb2ear.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Mon Jan 17 16:33:13 2011 From: jrorke at cogeco.ca (Jon Rorke) Date: Mon, 17 Jan 2011 11:33:13 -0500 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> , <03c001cbb660$ca693800$5f3ba800$@kb2ear.net> Message-ID: <4D346F49.9000407@cogeco.ca> Well, I dont have any Echolink on any of my nodes and I would like to disable all echolink connect and disconnect messages (on my end) that may come through when a node that does have echolink is connected. to mine. I'm not anti Echolink, but I find that people on echolink tend to connect to nodes, monitor for 1 nano second, and if they don't hear anything disconnect. What happens on the other end (my end) is 5 minutes of connect message and then 5 minutes of disconnect messages! So my vote is to make it work as described, that way it will be up to the node owner to customize as required. Jon On 1/17/2011 11:17 AM, Jim Duuuude wrote: > excellent point. Well, should I change the documentation to match the > design, or change > the design to match the documentation? > > JIM > > ------------------------------------------------------------------------ > From: kb2ear at kb2ear.net > To: telesistant at hotmail.com; kb4fxc at inttek.net > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Echolink announcements. > Date: Mon, 17 Jan 2011 11:08:33 -0500 > > http://ohnosec.org/drupal/node/107 > > eannmode > > > > 0 = do not announce Echolink nodes at all, 1 = announce only the node > number (Allstar-translated), 2 = announce only the call of the > echolink station, 3 = announce both > > > > 1 > > echolinkdefault > > > > 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry > output on command execution and for a short time thereafter, 3 = > follow local telemetry mode > > > > 2 > > Thanks & 73, > > Scott KB2EAR > > *From:*Jim Duuuude [mailto:telesistant at hotmail.com] > *Sent:* Monday, January 17, 2011 12:42 AM > *To:* kb2ear at kb2ear.net; kb4fxc at inttek.net > *Cc:* app_rpt mailing list > *Subject:* RE: [App_rpt-users] Echolink announcements. > > Frankly, I wasnt aware that you were supposed to be able to turn them > off completely. > Where did you get the idea that it does this?? > > JIM > > ------------------------------------------------------------------------ > > From: kb2ear at kb2ear.net > To: telesistant at hotmail.com; kb4fxc at inttek.net > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Echolink announcements. > Date: Sun, 16 Jan 2011 23:45:12 -0500 > > I just installed it here. I now have callsigns again, but still can?t > turn of the announcements all together. > > Thanks & 73, > > Scott KB2EAR > > *From:*Jim Duuuude [mailto:telesistant at hotmail.com] > *Sent:* Sunday, January 16, 2011 7:37 PM > *To:* kb4fxc at inttek.net; kb2ear at kb2ear.net > *Cc:* app_rpt mailing list > *Subject:* RE: [App_rpt-users] Echolink announcements. > > Yep, there was a problem introduced a while ago. Im surprised no one > found it until now. > The fixed version (app_rpt version 0.280) will be available from SVN > after 17:15 PST today. > > Thanks to everyone who helped point this out. > > JIM WB6NIL > > > > Date: Sun, 16 Jan 2011 17:00:24 -0500 > > From: kb4fxc at inttek.net > > To: kb2ear at kb2ear.net > > CC: app_rpt-users at ohnosec.org > > Subject: Re: [App_rpt-users] Echolink announcements. > > > > > > Hi everyone, > > > > I, too, noticed that echolink announcements went away after upgrading > > recently....After looking through the app_rpt.c code, I found a "new" > > variable that seems to need to be set, too. In the node stanza, try this: > > > > eannmode=2 > > tannmode=2 > > > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > > > 73, David kb4fxc > > > > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > > > Has anyone else noticed that the eannmode= and echolinkdefault= no > longer > > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > > announcements. Also when eannmode=2 or 3 I do not get callsigns > anymore. > > > > > > Thanks & 73, > > > Scott KB2EAR > > > > > > _______________________________________________ > > > App_rpt-users mailing list > > > App_rpt-users at ohnosec.org > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 17 16:43:28 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 17 Jan 2011 08:43:28 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: <4D346F49.9000407@cogeco.ca> References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , , , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net> , , <03c001cbb660$ca693800$5f3ba800$@kb2ear.net>, , <4D346F49.9000407@cogeco.ca> Message-ID: i see your point. Perhaps my documentation error was a Freudian slip.. Or was that what Sigmund Freud's wife wore under her skirt? :-). Anyway, I think I'll take the "change the design to match the documentation" option... JIM Date: Mon, 17 Jan 2011 11:33:13 -0500 From: jrorke at cogeco.ca To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Echolink announcements. Well, I dont have any Echolink on any of my nodes and I would like to disable all echolink connect and disconnect messages (on my end) that may come through when a node that does have echolink is connected. to mine. I'm not anti Echolink, but I find that people on echolink tend to connect to nodes, monitor for 1 nano second, and if they don't hear anything disconnect. What happens on the other end (my end) is 5 minutes of connect message and then 5 minutes of disconnect messages! So my vote is to make it work as described, that way it will be up to the node owner to customize as required. Jon On 1/17/2011 11:17 AM, Jim Duuuude wrote: excellent point. Well, should I change the documentation to match the design, or change the design to match the documentation? JIM From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Mon, 17 Jan 2011 11:08:33 -0500 http://ohnosec.org/drupal/node/107 eannmode 0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both 1 echolinkdefault 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode 2 Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Monday, January 17, 2011 12:42 AM To: kb2ear at kb2ear.net; kb4fxc at inttek.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Frankly, I wasnt aware that you were supposed to be able to turn them off completely. Where did you get the idea that it does this?? JIM From: kb2ear at kb2ear.net To: telesistant at hotmail.com; kb4fxc at inttek.net CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Echolink announcements. Date: Sun, 16 Jan 2011 23:45:12 -0500 I just installed it here. I now have callsigns again, but still can?t turn of the announcements all together. Thanks & 73, Scott KB2EAR From: Jim Duuuude [mailto:telesistant at hotmail.com] Sent: Sunday, January 16, 2011 7:37 PM To: kb4fxc at inttek.net; kb2ear at kb2ear.net Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink announcements. Yep, there was a problem introduced a while ago. Im surprised no one found it until now. The fixed version (app_rpt version 0.280) will be available from SVN after 17:15 PST today. Thanks to everyone who helped point this out. JIM WB6NIL > Date: Sun, 16 Jan 2011 17:00:24 -0500 > From: kb4fxc at inttek.net > To: kb2ear at kb2ear.net > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink announcements. > > > Hi everyone, > > I, too, noticed that echolink announcements went away after upgrading > recently....After looking through the app_rpt.c code, I found a "new" > variable that seems to need to be set, too. In the node stanza, try this: > > eannmode=2 > tannmode=2 > > ...This worked for me....Anyone know what "tannmode" is being used for?? > > 73, David kb4fxc > > > On Sun, 16 Jan 2011, Scott Weis wrote: > > > Has anyone else noticed that the eannmode= and echolinkdefault= no longer > > work? I have eannmode=0 and echolinkdefault=0 and still get echolink > > announcements. Also when eannmode=2 or 3 I do not get callsigns anymore. > > > > Thanks & 73, > > Scott KB2EAR > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 17 20:43:23 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 17 Jan 2011 12:43:23 -0800 Subject: [App_rpt-users] Echolink announcements. In-Reply-To: References: <00f901cbb5ab$3e478260$bad68720$@kb2ear.net>, , , , , , , <01e101cbb601$53acd7d0$fb068770$@kb2ear.net>, , , , <03c001cbb660$ca693800$5f3ba800$@kb2ear.net>, , , , <4D346F49.9000407@cogeco.ca>, Message-ID: The new version of app_rpt in SVN implements eannmode that reflects the documentation (you can turn off announcements by setting it to 0). JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Mon Jan 17 20:57:49 2011 From: jrorke at cogeco.ca (Jon Rorke) Date: Mon, 17 Jan 2011 15:57:49 -0500 Subject: [App_rpt-users] re updating nodes Message-ID: <4D34AD4D.6060006@cogeco.ca> What is the preferred method of updating nodes these days? I think the process was changed recently. Thanks, Jon VA3RQ From telesistant at hotmail.com Mon Jan 17 20:52:46 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 17 Jan 2011 12:52:46 -0800 Subject: [App_rpt-users] re updating nodes In-Reply-To: <4D34AD4D.6060006@cogeco.ca> References: <4D34AD4D.6060006@cogeco.ca> Message-ID: see https://allstarlink.org/support.html#astupgrade > Date: Mon, 17 Jan 2011 15:57:49 -0500 > From: jrorke at cogeco.ca > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] re updating nodes > > What is the preferred method of updating nodes these days? > > I think the process was changed recently. > > Thanks, > > Jon VA3RQ > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Mon Jan 17 23:25:19 2011 From: ke2n at cs.com (Ken) Date: Mon, 17 Jan 2011 18:25:19 -0500 Subject: [App_rpt-users] I should never be called! In-Reply-To: References: <000001cbb5c3$4c565e90$e5031bb0$@com>, <000301cbb5e0$7b27aa90$7176ffb0$@com>, <000301cbb62c$70d848f0$5288dad0$@com> Message-ID: <8CD84B4EAA5E1BD-1894-29F80@webmail-m025.sysops.aol.com> Thanks to Jim, I finally got the iaxRpt working. I could not see the extra comma no matter how long I stared at it (why I do not do software for my day job) The instructions on the Xelatec web site say to do this: [radio-gui] exten => NODENUMBER,1,rpt(NODENUMBER|X) if I do that, I get the famous "I should never be called!" warning message. With the comma plus parenthesis (as in my note below) it fails to connect. The syntax that works, without error messages, is exten => NODENUMBER,1,rpt,NODENUMBER|X where NODENUMBER is replaced with the digits of the asterisk node number. Tnx again Ken -----Original Message----- From: Jim Duuuude To: ke2n at cs.com Sent: Mon, Jan 17, 2011 8:45 am Subject: RE: I should never be called! [radio-gui] exten => 27021,1,rpt,(27021|X) Either get rid of the comma after the rpt or take the parenthesis off around the "27021|X" From: ke2n at cs.com To: telesistant at hotmail.com Subject: RE: I should never be called! Date: Mon, 17 Jan 2011 04:53:49 -0500 I assume that is a rhetorical question (if I knew the answer I would not be bothering you with it). But I would like to point out that it actually said it couldn?t find ?(27021? not ?27021? Executing [27021 at radio-gui:1] Rpt("IAX2/gui-9348", "(27021|X)") in new stack vs Executing [27061 at radio-gui:1] Rpt("IAX2/gui-5444", "27061|X") in new stack But none of this considers the ?I should never be called? message which would seem to indicate IAX is having indigestion even with the node that it does connect to successfully? Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki6psp at gmail.com Tue Jan 18 00:21:00 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Mon, 17 Jan 2011 16:21:00 -0800 Subject: [App_rpt-users] Half Duplex works fine, Kerchunks on Full Duplex...... Message-ID: At first I thought it was an RF problem, so I dropped filters in. Still the same problem, so I thought floating ground. I disconnected the TX Radio, and it still does it. When I key my handheld, the RX radio feeds the Discriminator audio to my URI and Asterisk hears me. But for some reason, it acts like I am just kerchunking it. I see the output in the Asterisk Console for the "Donk" every few seconds. I am not unkeying it, but it is acting like I am. Now granted, I don't have a service monitor to output the proper tone for the "radio tune rxtone" to set properly, but it works just fine on half duplex. Did I miss something? All I changed was the "Duplex=1" ---> "Duplex=2" I would really love to fully deploy this repeater, now that I have all of the parts I need. -- KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki6psp at gmail.com Tue Jan 18 01:14:58 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Mon, 17 Jan 2011 17:14:58 -0800 Subject: [App_rpt-users] Half Duplex works fine, Kerchunks on Full Duplex...... In-Reply-To: <6462C7F2-56D4-46A4-B0EC-F7C26E40B455@brannan.name> References: <6462C7F2-56D4-46A4-B0EC-F7C26E40B455@brannan.name> Message-ID: Ok, That was dumb. I added the Duplex line in the rpt.conf file, and didn't think about a conflict with the usbradio.conf. Next question, now that it works, I have an annoying squelch tail, how do I eliminate that? usbradio.conf [usb27179] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=103.5 rxctcssfreqs=103.5 txctcssfreqs=103.5 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=no invertptt=0 duplex=0 :Change this line as well as in the rpt.conf rxondelay=0 rxnoisefiltype=0 eeprom=0 usbradio_tune_usb27179.conf [usb27179] ; name=usb27179 ; devicenum=2 devstr=5-2 rxmixerset=500 txmixaset=15 txmixbset=500 rxvoiceadj=0.500000 rxctcssadj=0.500000 txctcssadj=500 rxsquelchadj=500 On Mon, Jan 17, 2011 at 4:40 PM, Buddy Brannan wrote: > Oh yeah, and also be sure to put > duplex=1 > in usbradio.conf > > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > On Jan 17, 2011, at 7:21 PM, KI6PSP (Ed) wrote: > > > At first I thought it was an RF problem, so I dropped filters in. Still > the same problem, so I thought floating ground. I disconnected the TX Radio, > and it still does it. > > > > When I key my handheld, the RX radio feeds the Discriminator audio to my > URI and Asterisk hears me. But for some reason, it acts like I am just > kerchunking it. I see the output in the Asterisk Console for the "Donk" > every few seconds. I am not unkeying it, but it is acting like I am. Now > granted, I don't have a service monitor to output the proper tone for the > "radio tune rxtone" to set properly, but it works just fine on half duplex. > > > > Did I miss something? > > All I changed was the "Duplex=1" ---> "Duplex=2" > > I would really love to fully deploy this repeater, now that I have all of > the parts I need. > > -- > > KI6PSP (Ed) > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -- KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Tue Jan 18 01:38:08 2011 From: ke2n at cs.com (Ken) Date: Mon, 17 Jan 2011 20:38:08 -0500 Subject: [App_rpt-users] Half Duplex works fine, Kerchunks on Full Duplex...... In-Reply-To: References: <6462C7F2-56D4-46A4-B0EC-F7C26E40B455@brannan.name> Message-ID: <000c01cbb6b0$5c5254f0$14f6fed0$@com> You probably need to tighten up the squelch - with no signal present do radio tune rxsquelch I usually set mine at 100 points above the strongest noise reading after several tries. Of course, your radio has to be set for receive tone squelch .. And the hang time on the repeater needs to be longer than the tone squelch on your radio (my radios need about 0.8 seconds of carrier with no tone, in order to completely eliminate any sound). Ken KE2N From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of KI6PSP (Ed) Sent: Monday, January 17, 2011 8:15 PM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Half Duplex works fine, Kerchunks on Full Duplex...... Ok, That was dumb. I added the Duplex line in the rpt.conf file, and didn't think about a conflict with the usbradio.conf. Next question, now that it works, I have an annoying squelch tail, how do I eliminate that? KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Tue Jan 18 01:55:45 2011 From: pete.elke at esquared.com (Peter Elke) Date: Tue, 18 Jan 2011 01:55:45 -0000 Subject: [App_rpt-users] Installation problems with Intel 525 mini-itx References: <4D34AD4D.6060006@cogeco.ca> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CC4A@webmail.esquared.net> Hi All, We selected the intel D525MW mini-itx board as the standard for our 12V systems. Last night we attempted a ACID install and all went well until the final reboot. The error we are getting (after downloading the config and rebooting) is: "mpg123 no process killed Asterisk ended with exit status 1 Asterisk died with code 1 Automatically restarting Asterisk." Rinse and repeat... It loops on this forever... I then tried a fresh burn CD and a new motherboard and the same issue was the final result. Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From conny at n5hc.com Tue Jan 18 16:55:28 2011 From: conny at n5hc.com (Conny Jonsson) Date: Tue, 18 Jan 2011 09:55:28 -0700 Subject: [App_rpt-users] Installation problems with Intel 525 mini-itx Message-ID: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> Hi, Had the same issue: "mpg123 no process killed Asterisk ended with exit status 1 Asterisk died with code 1 Automatically restarting Asterisk." This on a HP workstation that worked well in the past. In my case It turned out that the downloaded radio interface node configuration (usbradio.conf) is not correct. It used to work OK up till last week. What I did, even if you see the above errors coming on the screen, login as root and run astdn.sh to kill asterisk, that stopped the messages. Then I manually updated the config files in /etc/asterisk and after a reboot everything worked OK. If I run nodesetup.sh the files get downloaded from allstarlink.org and after reboot the same problem starts again because the usbradio.conf file is incorrect. 73 de N5HC Conny From telesistant at hotmail.com Tue Jan 18 17:18:01 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 18 Jan 2011 09:18:01 -0800 Subject: [App_rpt-users] Installation problems with Intel 525 mini-itx In-Reply-To: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> Message-ID: Sorry! I made a type-o in a SQL query in the php source that generates the usbradio.conf file! duh! It should work a whole lot better now. JIM WB6NIL > From: conny at n5hc.com > Date: Tue, 18 Jan 2011 09:55:28 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Installation problems with Intel 525 mini-itx > > Hi, > > Had the same issue: > > "mpg123 no process killed > > Asterisk ended with exit status 1 > > Asterisk died with code 1 > > Automatically restarting Asterisk." > > This on a HP workstation that worked well in the past. > > In my case It turned out that the downloaded radio interface node configuration (usbradio.conf) is not correct. > > It used to work OK up till last week. > > What I did, even if you see the above errors coming on the screen, login as root and run astdn.sh to kill asterisk, that stopped the messages. > > Then I manually updated the config files in /etc/asterisk and after a reboot everything worked OK. > > If I run nodesetup.sh the files get downloaded from allstarlink.org and after reboot the same problem starts again because the usbradio.conf file is incorrect. > > > 73 de N5HC > Conny > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From conny at n5hc.com Tue Jan 18 17:42:41 2011 From: conny at n5hc.com (Conny Jonsson) Date: Tue, 18 Jan 2011 10:42:41 -0700 Subject: [App_rpt-users] Installation problems with Intel 525 mini-itx In-Reply-To: References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> Message-ID: That worked for node 27578 & 27580 ! Thank's for the fast response!! /Conny On Jan 18, 2011, at 10:18 AM, Jim Duuuude wrote: > Sorry! I made a type-o in a SQL query in the php source that generates the usbradio.conf file! > duh! It should work a whole lot better now. > > JIM WB6NIL > > > From: conny at n5hc.com > > Date: Tue, 18 Jan 2011 09:55:28 -0700 > > To: app_rpt-users at ohnosec.org > > Subject: Re: [App_rpt-users] Installation problems with Intel 525 mini-itx > > > > Hi, > > > > Had the same issue: > > > > "mpg123 no process killed > > > > Asterisk ended with exit status 1 > > > > Asterisk died with code 1 > > > > Automatically restarting Asterisk." > > > > This on a HP workstation that worked well in the past. > > > > In my case It turned out that the downloaded radio interface node configuration (usbradio.conf) is not correct. > > > > It used to work OK up till last week. > > > > What I did, even if you see the above errors coming on the screen, login as root and run astdn.sh to kill asterisk, that stopped the messages. > > > > Then I manually updated the config files in /etc/asterisk and after a reboot everything worked OK. > > > > If I run nodesetup.sh the files get downloaded from allstarlink.org and after reboot the same problem starts again because the usbradio.conf file is incorrect. > > > > > > 73 de N5HC > > Conny > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Tue Jan 18 18:49:17 2011 From: pete.elke at esquared.com (Peter Elke) Date: Tue, 18 Jan 2011 18:49:17 -0000 Subject: [App_rpt-users] Installation problems with Intel 525 mini-itx References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CC5E@webmail.esquared.net> Thanks Jim, I will try it tonight and report back. Pete From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jim Duuuude Sent: Tuesday, January 18, 2011 9:18 AM To: conny at n5hc.com; app_rpt mailing list Subject: Re: [App_rpt-users] Installation problems with Intel 525 mini-itx Sorry! I made a type-o in a SQL query in the php source that generates the usbradio.conf file! duh! It should work a whole lot better now. JIM WB6NIL > From: conny at n5hc.com > Date: Tue, 18 Jan 2011 09:55:28 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Installation problems with Intel 525 mini-itx > > Hi, > > Had the same issue: > > "mpg123 no process killed > > Asterisk ended with exit status 1 > > Asterisk died with code 1 > > Automatically restarting Asterisk." > > This on a HP workstation that worked well in the past. > > In my case It turned out that the downloaded radio interface node configuration (usbradio.conf) is not correct. > > It used to work OK up till last week. > > What I did, even if you see the above errors coming on the screen, login as root and run astdn.sh to kill asterisk, that stopped the messages. > > Then I manually updated the config files in /etc/asterisk and after a reboot everything worked OK. > > If I run nodesetup.sh the files get downloaded from allstarlink.org and after reboot the same problem starts again because the usbradio.conf file is incorrect. > > > 73 de N5HC > Conny > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Thu Jan 20 05:38:24 2011 From: pete.elke at esquared.com (Peter Elke) Date: Thu, 20 Jan 2011 05:38:24 -0000 Subject: [App_rpt-users] Echolink "can't connect" References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CC91@webmail.esquared.net> Any Direction? app_rpt*CLI> echolink debug level Usage: echolink debug level {0-7} Enables debug messages in app_rpt [Jan 19 21:22:27] NOTICE[4938]: chan_echolink.c:2489 do_new_call: new CALL=WI6H,ip=216.69.181.220,name= iPhone User == Starting echolink/el0-1 at test,27430,1 failed so falling back to exten 's' == Starting echolink/el0-1 at test,s,1 still failed so falling back to context 'default' -- Sent into invalid extension 's' in context 'default' on echolink/el0-1 -- Executing [i at default:1] Hangup("echolink/el0-1", "") in new stack == Spawn extension (default, i, 1) exited non-zero on 'echolink/el0-1' [Jan 19 21:24:51] NOTICE[4939]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server1.echolink.org [Jan 19 21:24:51] NOTICE[4939]: chan_echolink.c:2383 do_el_directory: Directory pgm done downloading(partial,compressed), 317 records [Jan 19 21:26:47] NOTICE[4938]: chan_echolink.c:2489 do_new_call: new CALL=WI6H,ip=216.69.181.220,name= iPhone User == Starting echolink/el0-2 at test,27430,1 failed so falling back to exten 's' == Starting echolink/el0-2 at test,s,1 still failed so falling back to context 'default' -- Sent into invalid extension 's' in context 'default' on echolink/el0-2 -- Executing [i at default:1] Hangup("echolink/el0-2", "") in new stack == Spawn extension (default, i, 1) exited non-zero on 'echolink/el0-2' [Jan 19 21:26:52] NOTICE[4937]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server2.echolink.org [Jan 19 21:28:51] NOTICE[4939]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server1.echolink.org [Jan 19 21:28:51] NOTICE[4939]: chan_echolink.c:2383 do_el_directory: Directory pgm done downloading(partial,compressed), 348 records app_rpt*CLI> -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Thu Jan 20 14:55:05 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Thu, 20 Jan 2011 08:55:05 -0600 Subject: [App_rpt-users] Echolink Link Status Message-ID: <000e01cbb8b2$065a45e0$d502a8c0@main> Hello, My apologies if this has been covered.. I searched the archives this morning before posting.. I'm just getting my Echolink node connected, and curious if it's possible to report my node to Echolink's Link Status screen? http://www.echolink.org/links.jsp Thanks.. 73, Kyle K0KN -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Thu Jan 20 15:16:19 2011 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Thu, 20 Jan 2011 10:16:19 -0500 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <000e01cbb8b2$065a45e0$d502a8c0@main> References: <000e01cbb8b2$065a45e0$d502a8c0@main> Message-ID: <4D3851C3.2070503@bdboyle.com> On 1/20/11 9:55 AM, K&R Yoksh wrote: > Hello, > My apologies if this has been covered.. I searched the archives this > morning before posting.. > I'm just getting my Echolink node connected, and curious if it's > possible to report my node to Echolink's Link Status screen? > http://www.echolink.org/links.jsp > Thanks.. 73, > Kyle > K0KN I'm thinking not, since the verbiage at the bottom of the page says: "The table above shows information collected during the past several minutes from EchoLink "sysop" stations (those with a -L or -R suffix). The only stations shown are those which are *running EchoLink version 1.6 * or above, and have entered location information on the RF Info tab of Sysop Settings." We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language. Hey, it's free as in beer, fwiw. Not saying they shouldn't, but, that would seem to be the most logical explanation...because I'm sure that trying to support a published API for every version of off-brand, so to speak, software that wants to talk to their server is probably not going to happen any time soon. -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Thu Jan 20 16:05:13 2011 From: ke2n at cs.com (Ken) Date: Thu, 20 Jan 2011 11:05:13 -0500 (EST) Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3851C3.2070503@bdboyle.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> Message-ID: <8CD86D2F44C8DFA-1804-18A82@Webmail-d113.sysops.aol.com> >>Hey, it's free as in beer, fwiw. I posted something on this more than a year ago (in the bug list and desired features reflector). We figured out what the format of the required data was (as I recall it is encrypted info) but the whole thing was regarded as really a low priority, nice-to-have, item. My experience is that your node does show up in http://www.echolink.org/logins.jsp Interestingly enough, I found you can run the Windows version of the program at the same Internet address and put all your information in there and it will show up on the desired listing while Asterisk actually answers the call and talks to the radios. Ken KE2N -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Thu Jan 20 16:08:56 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Thu, 20 Jan 2011 08:08:56 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3851C3.2070503@bdboyle.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> Message-ID: <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> I suspect that the app_rpt echolink client is not reporting to the mothership, not that the mothership is ignoring us. If that's the case, maybe our exalted developer would add echolink status reporting. -- Tim :wq On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote: > We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language. From tim.sawyer at me.com Thu Jan 20 18:22:01 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Thu, 20 Jan 2011 10:22:01 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> Message-ID: Jim, I believe what people are asking for is to have app_rpt send status updates when connects and disconnects occur. Below is the format for echolink status reporting taken from Skip's WB6YMH source for thelinkbox. Looks like the connect message would be "=NNTECHTALK at 1530" for example. I assume the disconnect message would be " On @ 1545". EchoLink sends a packet once every 10 minutes to aprs.echolink.org. It also sends a packet when the node status changes (i.e., when somebody connects or disconnects, or the node comes online or goes offline). The packet is an RTP control packet, and thus is sent to port 5199. The CNAME portion is the node callsign (including -L/-R), followed by a slash, followed by a "password", which is actually a hash of the callsign. However, at this time, the password field is ignored by the server; a future release of the server will verify the authenticity of the packet by its source IP address. So the callsign can be repeated in this second field. The format of the LOC portion is as follows: )EL-nnnnnn!DDMM.HHNXDDDMM.HHW0PHGphgd/FFFFFF/PPPyyyyyyyyyyzzzzzzzz Where: nnnnnn is the 6 character node Name or Callsign (right-padded with spaces to 6 chars) DDMM.HHN DDDMM.HHW is the LAT/LONG of the node, using degrees, minutes, and 100ths of minutes, and E/W/N/S X is the letter "E", for EchoLink 0 is a "zero",the ICON character p is the power (encoded) h is the antenna height (encoded) g is the antenna gain (encoded) d is the antenna directivity (encoded) FFFFFF is the frequency in KHz /PPP is the PL in whole number Hz yyyyyyyyyy Second line on a D7 (11th to 20th on a D700) zzzzzzzz last 8 not shown on a D7 but are on the D700 Formats for the variable field YYYYYYYYYY and ZZZZZZZZ: Offline: " Off @HHMM........" can contain some comment On-Line: " On @ HHMM........" Time it returned to ON-Line Busy: " Busy HHMM........" Time it went busy Connected: "=NNnnnnnnn at HHMM" Shows call/Name of connection The encoding of the p/h/g/d fields is as follows: DIGITS 0 1 2 3 4 5 6 7 8 9 ------------------------------------------------------------------- POWER 0, 1, 4, 9, 16, 25, 36, 49, 64, 81 watts SQR(P) HEIGHT 10,20,40, 80,160,320,640,1280,2560,5120 feet LOG2(H/10) GAIN 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 dB DIR omni,45,90,135,180,225,270, 315, 360, . deg (D/45) For example: // )EL-K1RFD !4118.52NE07329.97W0PHG7430/144300/000 On @0444 Rdgfld -- Tim :wq On Jan 20, 2011, at 8:08 AM, Tim Sawyer wrote: > I suspect that the app_rpt echolink client is not reporting to the mothership, not that the mothership is ignoring us. If that's the case, maybe our exalted developer would add echolink status reporting. > -- > Tim > :wq > > On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote: > >> We're not running Echolink software...so, while we're able to register our nodes, I'm thinking that the Echolink mother ship is studiously ignoring, for the sake of display, alternative software that speaks their language. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Fri Jan 21 04:45:59 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Thu, 20 Jan 2011 22:45:59 -0600 Subject: [App_rpt-users] Echolink Link Status Message-ID: <001301cbb926$19f34420$d502a8c0@main> Yes, this is what I was referring to... TheLinkBox, TheBridge and RtpDir have all supported the Echolink AVRS system, so I was curious if App_rpt did as well.. 73. Kyle K0KN --- Original Message --- Jim, I believe what people are asking for is to have app_rpt send status updates when connects and disconnects occur. Below is the format for echolink status reporting taken from Skip's WB6YMH source for thelinkbox. Looks like the connect message would be "=NNTECHTALK at 1530" for example. I assume the disconnect message would be " On @ 1545". EchoLink sends a packet once every 10 minutes to aprs.echolink.org. It also sends a packet when the node status changes (i.e., when somebody connects or disconnects, or the node comes online or goes offline). The packet is an RTP control packet, and thus is sent to port 5199. The CNAME portion is the node callsign (including -L/-R), followed by a slash, followed by a "password", which is actually a hash of the callsign. However, at this time, the password field is ignored by the server; a future release of the server will verify the authenticity of the packet by its source IP address. So the callsign can be repeated in this second field. The format of the LOC portion is as follows: )EL-nnnnnn!DDMM.HHNXDDDMM.HHW0PHGphgd/FFFFFF/PPPyyyyyyyyyyzzzzzzzz Where: nnnnnn is the 6 character node Name or Callsign (right-padded with spaces to 6 chars) DDMM.HHN DDDMM.HHW is the LAT/LONG of the node, using degrees, minutes, and 100ths of minutes, and E/W/N/S X is the letter "E", for EchoLink 0 is a "zero",the ICON character p is the power (encoded) h is the antenna height (encoded) g is the antenna gain (encoded) d is the antenna directivity (encoded) FFFFFF is the frequency in KHz /PPP is the PL in whole number Hz yyyyyyyyyy Second line on a D7 (11th to 20th on a D700) zzzzzzzz last 8 not shown on a D7 but are on the D700 Formats for the variable field YYYYYYYYYY and ZZZZZZZZ: Offline: " Off @HHMM........" can contain some comment On-Line: " On @ HHMM........" Time it returned to ON-Line Busy: " Busy HHMM........" Time it went busy Connected: "=NNnnnnnnn at HHMM" Shows call/Name of connection The encoding of the p/h/g/d fields is as follows: DIGITS 0 1 2 3 4 5 6 7 8 9 ------------------------------------------------------------------- POWER 0, 1, 4, 9, 16, 25, 36, 49, 64, 81 watts SQR(P) HEIGHT 10,20,40, 80,160,320,640,1280,2560,5120 feet LOG2(H/10) GAIN 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 dB DIR omni,45,90,135,180,225,270, 315, 360, . deg (D/45) For example: // )EL-K1RFD !4118.52NE07329.97W0PHG7430/144300/000 On @0444 Rdgfld -- Tim :wq On Jan 20, 2011, at 8:08 AM, Tim Sawyer wrote: > I suspect that the app_rpt echolink client is not reporting to the > mothership, not that the mothership is ignoring us. If that's the case, > maybe our exalted developer would add echolink status reporting. > -- > Tim > :wq > > On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote: > >> We're not running Echolink software...so, while we're able to register >> our nodes, I'm thinking that the Echolink mother ship is studiously >> ignoring, for the sake of display, alternative software that speaks their >> language. > From yokshs at sbcglobal.net Fri Jan 21 06:31:17 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Fri, 21 Jan 2011 00:31:17 -0600 Subject: [App_rpt-users] DTMF decoding Message-ID: <003f01cbb934$cf7943e0$d502a8c0@main> Hello group, I have another question.. I've just switched to Allstar from EchoIRLP, and am having trouble with the software dtmf decoder. All of my radios could command the EchoIRLP system, using the hardware DTMF decoder, but I'm having an issue with 2 radios on app_rpt and the software decoder. Two rows of DTMF buttons are not decoding on 2 radios. On a few other radios, all buttons decode correctly. My node radios are the same, and my mobile and HT are also the same. Is there a twist setting or other possible setting I could try changing? I would be elated if the hardware DTMF decoder were supported, but I am pretty sure it's not supported in app_rpt. Thanks. 73. Kyle K0KN -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb3ors at windstream.net Fri Jan 21 12:22:24 2011 From: kb3ors at windstream.net (KB3ORS - Brian) Date: Fri, 21 Jan 2011 07:22:24 -0500 Subject: [App_rpt-users] DTMF decoding In-Reply-To: <003f01cbb934$cf7943e0$d502a8c0@main> References: <003f01cbb934$cf7943e0$d502a8c0@main> Message-ID: <99D0148024154064BCD0129404E3B32F@BrianPC> ?What type of radio are you using for the node radio? And what interface? (EX: Kenwood V71A to a URI through the data port) Just went through this with a another node one on one. The problem found was that the Kenwood V71A uses speaker audio not flat audio for the data port. Icom and Kenwood would decode but Yeasu DTMF was not recognized. On this same node I changed his status,1 and status,2 announcements to 11 and 12. Now the announcments do not play. If I issue rpt localplay nothing is generated over the rf side. If I issue playback from the cli it plays the script local not global. Any ideas? Brian KB3ORS From: K&R Yoksh Sent: Friday, January 21, 2011 1:31 AM To: app_rpt Subject: [App_rpt-users] DTMF decoding Hello group, I have another question.. I've just switched to Allstar from EchoIRLP, and am having trouble with the software dtmf decoder. All of my radios could command the EchoIRLP system, using the hardware DTMF decoder, but I'm having an issue with 2 radios on app_rpt and the software decoder. Two rows of DTMF buttons are not decoding on 2 radios. On a few other radios, all buttons decode correctly. My node radios are the same, and my mobile and HT are also the same. Is there a twist setting or other possible setting I could try changing? I would be elated if the hardware DTMF decoder were supported, but I am pretty sure it's not supported in app_rpt. Thanks. 73. Kyle K0KN -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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: 10.0.1191 / Virus Database: 1435/3392 - Release Date: 01/20/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Fri Jan 21 17:21:48 2011 From: pete.elke at esquared.com (Peter Elke) Date: Fri, 21 Jan 2011 17:21:48 -0000 Subject: [App_rpt-users] Location dependant squelch tail? References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com> <8035B62A7B044D4B81015D5C49D1627D43CC91@webmail.esquared.net> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CCB8@webmail.esquared.net> All, I have a strange one. When monitoring the local repeater local users have a squelch tail. If you monitor the same transmission on a remote note there is no tail. Why I think this is strange is that "tail removal" is generally a receiver function and I can't see how where it spits out would matter. (URI, discriminator connected, DSP, PL and Squelch) Pete From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Peter Elke Sent: Wednesday, January 19, 2011 9:38 PM To: app_rpt mailing list Subject: [App_rpt-users] Echolink "can't connect" Any Direction? app_rpt*CLI> echolink debug level Usage: echolink debug level {0-7} Enables debug messages in app_rpt [Jan 19 21:22:27] NOTICE[4938]: chan_echolink.c:2489 do_new_call: new CALL=WI6H,ip=216.69.181.220,name= iPhone User == Starting echolink/el0-1 at test,27430,1 failed so falling back to exten 's' == Starting echolink/el0-1 at test,s,1 still failed so falling back to context 'default' -- Sent into invalid extension 's' in context 'default' on echolink/el0-1 -- Executing [i at default:1] Hangup("echolink/el0-1", "") in new stack == Spawn extension (default, i, 1) exited non-zero on 'echolink/el0-1' [Jan 19 21:24:51] NOTICE[4939]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server1.echolink.org [Jan 19 21:24:51] NOTICE[4939]: chan_echolink.c:2383 do_el_directory: Directory pgm done downloading(partial,compressed), 317 records [Jan 19 21:26:47] NOTICE[4938]: chan_echolink.c:2489 do_new_call: new CALL=WI6H,ip=216.69.181.220,name= iPhone User == Starting echolink/el0-2 at test,27430,1 failed so falling back to exten 's' == Starting echolink/el0-2 at test,s,1 still failed so falling back to context 'default' -- Sent into invalid extension 's' in context 'default' on echolink/el0-2 -- Executing [i at default:1] Hangup("echolink/el0-2", "") in new stack == Spawn extension (default, i, 1) exited non-zero on 'echolink/el0-2' [Jan 19 21:26:52] NOTICE[4937]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server2.echolink.org [Jan 19 21:28:51] NOTICE[4939]: chan_echolink.c:2077 sendcmd: Received OK from Echolink server server1.echolink.org [Jan 19 21:28:51] NOTICE[4939]: chan_echolink.c:2383 do_el_directory: Directory pgm done downloading(partial,compressed), 348 records app_rpt*CLI> -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Fri Jan 21 17:51:28 2011 From: pete.elke at esquared.com (Peter Elke) Date: Fri, 21 Jan 2011 17:51:28 -0000 Subject: [App_rpt-users] Location dependant squelch tail? (V2 removed echolink text) References: <7C1727DB-E3D3-4E30-A806-4B376C2A98C5@n5hc.com><8035B62A7B044D4B81015D5C49D1627D43CC91@webmail.esquared.net> <8035B62A7B044D4B81015D5C49D1627D43CCB8@webmail.esquared.net> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CCBA@webmail.esquared.net> All, I have a strange one. When monitoring the local repeater local users have a squelch tail. If you monitor the same transmission on a remote note there is no tail. Why I think this is strange is that "tail removal" is generally a receiver function and I can't see how where it spits out would matter. (URI, discriminator connected, DSP, PL and Squelch) Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sat Jan 22 02:27:15 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Fri, 21 Jan 2011 18:27:15 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000e01cbb8b2$065a45e0$d502a8c0@main>, <4D3851C3.2070503@bdboyle.com>, <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com>, Message-ID: Chan_echolink now supports proper display/reporting to the echolink server stuff. Please download the new version of chan_echolink.c from SVN. For details on configuration, please see: http://209.159.155.200/drupal/node/56 Note the following additions to the echolink.conf file: freq=145.000 ; Freq in MHz tone=100.0 ; CTCSS Tone (0 for none) lat=34.74978 ; Latitude in decimal degrees lon=-92.27666 ; Longitude in decimal degrees power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) gain=7 ; Gain in db (0-9) dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Sat Jan 22 03:33:04 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Fri, 21 Jan 2011 19:33:04 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> Message-ID: <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com> Awesome! Thank you Jim. -- Tim :wq On Jan 21, 2011, at 6:27 PM, Jim Duuuude wrote: > Chan_echolink now supports proper display/reporting to the echolink server stuff. > > Please download the new version of chan_echolink.c from SVN. > > For details on configuration, please see: > > http://209.159.155.200/drupal/node/56 > > Note the following additions to the echolink.conf file: > > freq=145.000 ; Freq in MHz > tone=100.0 ; CTCSS Tone (0 for none) > lat=34.74978 ; Latitude in decimal degrees > lon=-92.27666 ; Longitude in decimal degrees > power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) > height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) > gain=7 ; Gain in db (0-9) > dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) > JIM WB6NIL > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Sat Jan 22 03:38:45 2011 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Fri, 21 Jan 2011 22:38:45 -0500 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com> Message-ID: <4D3A5145.5050005@bdboyle.com> On 1/21/2011 10:33 PM, Tim Sawyer wrote: > Awesome! Thank you Jim. > -- Agreed! Thank you for the added functionality. building now...and editing the file...:) Bryan WB0YLE Allstar 27294 From kb2ear at kb2ear.net Sat Jan 22 03:53:29 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Fri, 21 Jan 2011 22:53:29 -0500 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3A5145.5050005@bdboyle.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com> <4D3A5145.5050005@bdboyle.com> Message-ID: <012201cbb9e7$ee3d2680$cab77380$@kb2ear.net> The lat / lon format is incorrect.. Go to the link below and convert your dd.mmmmm to dd mm.mm and enter as 44.mmmm only the first 4 digits after the . count So for my location (KB2EAR-R / 2298) its: 40.2526 and not 40.421103 and -74.3392 and not -74.565346 http://www.csgnetwork.com/gpscoordconv.html -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan D. Boyle Sent: Friday, January 21, 2011 10:39 PM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Echolink Link Status On 1/21/2011 10:33 PM, Tim Sawyer wrote: > Awesome! Thank you Jim. > -- Agreed! Thank you for the added functionality. building now...and editing the file...:) Bryan WB0YLE Allstar 27294 _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From telesistant at hotmail.com Sat Jan 22 04:15:17 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Fri, 21 Jan 2011 20:15:17 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <012201cbb9e7$ee3d2680$cab77380$@kb2ear.net> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com>, <4D3A5145.5050005@bdboyle.com>, <012201cbb9e7$ee3d2680$cab77380$@kb2ear.net> Message-ID: oh poo!! Ill have to fix it. Its truly meant to be decimal degrees. JIM WB6NIL > From: kb2ear at kb2ear.net > To: bdboyle at bdboyle.com; app_rpt-users at ohnosec.org > Date: Fri, 21 Jan 2011 22:53:29 -0500 > Subject: Re: [App_rpt-users] Echolink Link Status > > The lat / lon format is incorrect.. Go to the link below and convert your > dd.mmmmm to dd mm.mm and enter as 44.mmmm only the first 4 digits after the > . count > > So for my location (KB2EAR-R / 2298) its: 40.2526 and not 40.421103 and > -74.3392 and not -74.565346 > > http://www.csgnetwork.com/gpscoordconv.html > > > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan D. Boyle > Sent: Friday, January 21, 2011 10:39 PM > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink Link Status > > On 1/21/2011 10:33 PM, Tim Sawyer wrote: > > Awesome! Thank you Jim. > > -- > > > Agreed! Thank you for the added functionality. > > building now...and editing the file...:) > > Bryan > WB0YLE > Allstar 27294 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Sat Jan 22 04:21:20 2011 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Fri, 21 Jan 2011 23:21:20 -0500 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com>, <4D3A5145.5050005@bdboyle.com>, <012201cbb9e7$ee3d2680$cab77380$@kb2ear.net> Message-ID: <4D3A5B40.9020509@bdboyle.com> On 1/21/2011 11:15 PM, Jim Duuuude wrote: > > oh poo!! Ill have to fix it. Its truly meant to be decimal degrees. > > JIM WB6NIL > Also....here's a good one...send up the frequency as 224.540...EL displays as 224.539...:) Talk about a little rounding error (or not...)...close enough for small tactical nukes...;). But, works nice so far. bryan wb0yle allstar 27294 From yokshs at sbcglobal.net Sat Jan 22 05:26:34 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Fri, 21 Jan 2011 23:26:34 -0600 Subject: [App_rpt-users] Echolink Link Status References: Message-ID: <000601cbb9f4$efae56d0$d502a8c0@main> ----- Original Message ----- > Date: Fri, 21 Jan 2011 18:27:15 -0800 > From: Jim Duuuude > Subject: Re: [App_rpt-users] Echolink Link Status > > Chan_echolink now supports proper display/reporting to the echolink server > stuff. Hello Jim (and the group), Many thanks for this great addition! 73. Kyle K0KN From yokshs at sbcglobal.net Sat Jan 22 05:37:12 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Fri, 21 Jan 2011 23:37:12 -0600 Subject: [App_rpt-users] DTMF decoding References: Message-ID: <000d01cbb9f6$6be4a0f0$d502a8c0@main> ----- Original Message ----- > From: "KB3ORS - Brian" > Subject: Re: [App_rpt-users] DTMF decoding > > ?What type of radio are you using for the node radio? And what interface? > (EX: Kenwood V71A to a URI through the data port) > > Just went through this with a another node one on one. The problem found > was that the Kenwood V71A uses speaker audio not flat audio for the data > port. > > Icom and Kenwood would decode but Yeasu DTMF was not recognized. Hello Brian (and the group), I'm running two nodes at my QTH. Both use GE Phoenix radios (2211 is on VHF, 2212 is on UHF) and each uses a CM108 fob. I'm using deemphasized speaker audio. I've narrowed down my problem to the microphone on my mobile radio (Icom 207). Oddly enough, it will control my node fine on UHF.. Tonight, I injected tones into the transmitter without the Icom hand mic, and Allstar decodes the tones on VHF and UHF. There seems to be quite a bit of distortion generated from the Icom hand mic. I suspect that the problem has been with me for some time, but I never noticed it, as my MT8870 hardware decoder will decode the tones (even with the distortion).. 73. Kyle K0KN From telesistant at hotmail.com Sat Jan 22 06:11:44 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Fri, 21 Jan 2011 22:11:44 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3A5B40.9020509@bdboyle.com> References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> <4261AA23-B6F8-4512-9B1D-BD902DC9A65E@me.com>, <4D3A5145.5050005@bdboyle.com>, <012201cbb9e7$ee3d2680$cab77380$@kb2ear.net> , <4D3A5B40.9020509@bdboyle.com> Message-ID: All righty... Lets try this again.. Please download the latest version of chan_echolink.c from SVN, and we'll see if this works better. JIM > Date: Fri, 21 Jan 2011 23:21:20 -0500 > From: bdboyle at bdboyle.com > To: telesistant at hotmail.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink Link Status > > On 1/21/2011 11:15 PM, Jim Duuuude wrote: > > > > oh poo!! Ill have to fix it. Its truly meant to be decimal degrees. > > > > JIM WB6NIL > > > > Also....here's a good one...send up the frequency as 224.540...EL > displays as 224.539...:) Talk about a little rounding error (or > not...)...close enough for small tactical nukes...;). > > But, works nice so far. > > bryan > wb0yle > allstar 27294 -------------- next part -------------- An HTML attachment was scrubbed... URL: From n3fe at repeater.net Sat Jan 22 13:48:29 2011 From: n3fe at repeater.net (Corey Dean N3FE) Date: Sat, 22 Jan 2011 08:48:29 -0500 Subject: [App_rpt-users] DTMF Allow Message-ID: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D1AED@exchange.mail.repeater.net> Is it possible to get a feature added the will allow DTMF to pass through? I know you can regenerate using the cops but it would be nice to be able to press a sequence and then anything that followed would not mute the touch tones. This would help if asterisk was used as a hub and the other repeaters linking in were using standard controllers. That way one repeater on one end could control one on the other end. Just a thought... I know as of recent this would have been very helpful!!! Corey N3FE -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sat Jan 22 13:58:54 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 05:58:54 -0800 Subject: [App_rpt-users] DTMF Allow In-Reply-To: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D1AED@exchange.mail.repeater.net> References: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D1AED@exchange.mail.repeater.net> Message-ID: Thats a REALLY BAD idea for security reasons. You REALLY dont want ALL your DTMF's being repeated on the air. JIM From: n3fe at repeater.net To: telesistant at hotmail.com; app_rpt-users at ohnosec.org Date: Sat, 22 Jan 2011 08:48:29 -0500 Subject: DTMF Allow Is it possible to get a feature added the will allow DTMF to pass through? I know you can regenerate using the cops but it would be nice to be able to press a sequence and then anything that followed would not mute the touch tones. This would help if asterisk was used as a hub and the other repeaters linking in were using standard controllers. That way one repeater on one end could control one on the other end. Just a thought... I know as of recent this would have been very helpful!!! Corey N3FE -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Sat Jan 22 14:42:49 2011 From: ke2n at cs.com (Ken) Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) Subject: [App_rpt-users] DTMF Allow In-Reply-To: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D1AED@exchange.mail.repeater.net> References: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D1AED@exchange.mail.repeater.net> Message-ID: <8CD8859C634CD79-24C-5935@Webmail-d107.sysops.aol.com> Cory I think there is a setting for this propagate_dtmf= see http://209.159.155.200/drupal/node/134 but, for controlling remote asterisk nodes from another asterisk node, you are supposed to use this: see http://209.159.155.200/drupal/node/21 *4node Enter command mode on a remote node *4node Enter command mode on a remote node *4node Enter command mode on a remote node Command mode means send all received DTMF digits to the node number specified (bypassing the local command decoder). Send # to exit command mode, and restore local command decoding. I have had mixed results with it GL Ken KE2N -----Original Message----- From: Corey Dean N3FE To: Jim Duuuude ; app_rpt mailing list Sent: Sat, Jan 22, 2011 9:09 am Subject: [App_rpt-users] DTMF Allow Is it possible to get a feature added the will allow DTMF to pass through? I know you can regenerate using the cops but it would be nice to be able to press a sequence and then anything that followed would not mute the touch tones. This would help if asterisk was used as a hub and the other repeaters linking in were using standard controllers. That way one repeater on one end could control one on the other end. Just a thought... I know as of recent this would have been very helpful!!! Corey N3FE _______________________________________________ pp_rpt-users mailing list pp_rpt-users at ohnosec.org ttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sat Jan 22 14:49:50 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 06:49:50 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: , Message-ID: Okay... try the latest version on chan_echolink.c from SVN now... Thanks for the help. I really appreciate it when people take the time to provide solutions. JIM WB6NIL > Date: Sat, 22 Jan 2011 01:58:15 -0500 > From: kb4fxc at inttek.net > To: telesistant at hotmail.com > Subject: Re: [App_rpt-users] Echolink Link Status > > > ...Actually, one more rounding adjustment is needed...Oops! > > ...snip... > > latb = (lata - floor(lata)) * 60; > latd = (latb - floor(latb)) * 100 + 0.5; > lonb = (lona - floor(lona)) * 60; > lond = (lonb - floor(lonb)) * 100 + 0.5; > ...snip... > > 73, David kb4fxc > > > > > On Sat, 22 Jan 2011, David McGough wrote: > > > > > Hi Jim, > > > > Here is my hacked version of code for chan_echolink.c....If's small enough > > I didn't generate a diff. > > > > > > ....snip.... > > > > lata = fabs(mylat); > > lona = fabs(mylon); > > latb = (lata - floor(lata)) * 60; > > latd = (latb - floor(latb)) * 100; > > lonb = (lona - floor(lona)) * 60; > > lond = (lonb - floor(lonb)) * 100; > > > > sprintf(aprsstr,")EL-%-6.6s!%02d%02d.%02d%cE%03d%02d.%02d%c0PHG%d%d%d%d/%06d/%03d%s",instp->mycall, > > (int)lata,(int)latb,(int)latd,latc, > > (int)lona,(int)lonb,(int)lond,lonc, > > > > instp->power,instp->height,instp->gain,instp->dir, > > (int)((instp->freq * 1000) + 0.5),(int)(instp->tone + 0.05),instp->aprs_display); > > > > ....snip.... > > > > 73, David kb4fxc > > > > > > > > > > On Sat, 22 Jan 2011, David McGough wrote: > > > > > > > > Hi Jim, > > > > > > The lat/lon are a lot closer now, but still off by a bit. > > > > > > lat=34.165298 ;;; Real Decimal!! > > > lon=-77.944299 ;;; Real Decimal!! > > > > > > ;;;lat=34.0992 ;;; Real GPS... > > > ;;;lon=-77.5666 ;;; Real GPS... > > > > > > Calulated by chan_echolink: > > > > > > 34.1055 > > > -77.5739 > > > > > > > > > Thanks for you help! > > > > > > 73, David kb4fxc > > > > > > > > > > > > > > > > > > On Fri, 21 Jan 2011, Jim Duuuude wrote: > > > > > > > > > > > All righty... Lets try this again.. > > > > > > > > Please download the latest version of chan_echolink.c from SVN, and we'll see > > > > if this works better. > > > > > > > > JIM > > > > > > > > > Date: Fri, 21 Jan 2011 23:21:20 -0500 > > > > > From: bdboyle at bdboyle.com > > > > > To: telesistant at hotmail.com; app_rpt-users at ohnosec.org > > > > > Subject: Re: [App_rpt-users] Echolink Link Status > > > > > > > > > > On 1/21/2011 11:15 PM, Jim Duuuude wrote: > > > > > > > > > > > > oh poo!! Ill have to fix it. Its truly meant to be decimal degrees. > > > > > > > > > > > > JIM WB6NIL > > > > > > > > > > > > > > > > Also....here's a good one...send up the frequency as 224.540...EL > > > > > displays as 224.539...:) Talk about a little rounding error (or > > > > > not...)...close enough for small tactical nukes...;). > > > > > > > > > > But, works nice so far. > > > > > > > > > > bryan > > > > > wb0yle > > > > > allstar 27294 > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete.elke at esquared.com Sat Jan 22 17:42:39 2011 From: pete.elke at esquared.com (Peter Elke) Date: Sat, 22 Jan 2011 17:42:39 -0000 Subject: [App_rpt-users] Local squelch tail problem clarification. (copy of message to Ken) for comment. Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CCC4@webmail.esquared.net> From: Peter Elke [mailto:pete.elke at esquared.com] Sent: Saturday, January 22, 2011 3:26 AM To: Ken Subject: RE: [App_rpt-users] Location dependant squelch tail? Hi Ken, What I meant to get across was... There is a squelch tail when the local mobile unkeys (before the hang time) but you only hear it if you are monitoring the local node's transmit frequency. Remotely connected stations don't hear the tail, only a soft click or nothing from the same transmission. The local repeater transmitter dropping does not cause a tail if the mobile is in PL decode. I thought this was just strange, so much so that I sound ignorant reporting it... 73's Pete (WI6H) -------------- next part -------------- An HTML attachment was scrubbed... URL: From akalexandrov at gmail.com Sat Jan 22 18:00:39 2011 From: akalexandrov at gmail.com (Alexander Alexandrov) Date: Sat, 22 Jan 2011 20:00:39 +0200 Subject: [App_rpt-users] Problem with app_rpt configuration and URI's audio interface Message-ID: Dear colleagues, I built a node configuration with ACID system and URI from DMKEngineering. After the import of the ACID/Asterisk/app_rpt configuration from Allstarlink.org I connected the URI to my reg and install IAX client to the PC. The system work well from IAX clent through URI to the reg - when I send audio or voice from IAX client to the reg through URI the reg transmit the audio very well and clear. The problem is that I can not send any audio signal from the REG to the IAX client. Practically the audio from the REG go to the MIC_AC pin of URI and after that dropped down. Practically I have only one way audio communication: Iax client ->Asterisk-> app_rpt -> URI -> reg Probably I use a wrong usbradio.conf configuration but have not idea where to start looking for the problem. I red in the mailing list content some similar cases and advices about URI MIC interface problems and tried to use them but unfortunately without success. I will be very grateful for any advice how to resolve the problem. 73! Alex LZ1AZA The configuration I use is the following: URI hardware interface: audio line output of the reg - to URI MIC_AC (pin 21) microphone input of the REG - to LEFT_AC(pin 22) PTT - to PTT pin of the URI (pin1) the URI's usbradio.conf file look like this: ; ; Usbradio channel driver Configuration File ; [general] [usb27371] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=100.0 rxctcssfreqs=100.0 txctcssfreqs=100.0 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=no invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 #includeifexists custom/usbradio.conf -------------- next part -------------- An HTML attachment was scrubbed... URL: From hwstar at rodgers.sdcoxmail.com Sat Jan 22 18:23:06 2011 From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers) Date: Sat, 22 Jan 2011 10:23:06 -0800 Subject: [App_rpt-users] Local squelch tail problem clarification. (copy of message to Ken) for comment. In-Reply-To: <8035B62A7B044D4B81015D5C49D1627D43CCC4@webmail.esquared.net> References: <8035B62A7B044D4B81015D5C49D1627D43CCC4@webmail.esquared.net> Message-ID: <4D3B208A.3070902@rodgers.sdcoxmail.com> On 01/22/2011 09:42 AM, Peter Elke wrote: > From: Peter Elke [mailto:pete.elke at esquared.com] > Sent: Saturday, January 22, 2011 3:26 AM > To: Ken > Subject: RE: [App_rpt-users] Location dependant squelch tail? > > > > Hi Ken, > > > > What I meant to get across was... There is a squelch tail when the > local mobile unkeys (before the hang time) but you only hear it if you > are monitoring the local node's transmit frequency. Remotely connected > stations don't hear the tail, only a soft click or nothing from the same > transmission. > > > > The local repeater transmitter dropping does not cause a tail if the > mobile is in PL decode. > > > > I thought this was just strange, so much so that I sound ignorant > reporting it... > > > > 73's Pete (WI6H) > > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users Packet propagation across an the Internet and the use of jitter buffers in Asterisk causes this. On a network-based connection, the unkey control message is reaching the far end before the audio packets containing the squelch tail noise. On a local connection, the audio packet delay is much less. I suppose a delay could be added to the local audio packet stream, but this impairs full duplex operation even more as the delay there is already annoying enough. Steve. WA6ZFT From pete.elke at esquared.com Sat Jan 22 18:48:25 2011 From: pete.elke at esquared.com (Peter Elke) Date: Sat, 22 Jan 2011 18:48:25 -0000 Subject: [App_rpt-users] Local squelch tail problem clarification. (copy of message to Ken) for comment. References: <8035B62A7B044D4B81015D5C49D1627D43CCC4@webmail.esquared.net> <4D3B208A.3070902@rodgers.sdcoxmail.com> Message-ID: <8035B62A7B044D4B81015D5C49D1627D43CCC5@webmail.esquared.net> Wow Steve, That is interesting, I guess I could find internal gated audio and skip the DSP for all the MSF5000s. I would have thought the COS/PTT controls would be time synced or in stream "ie:inband" with the audio packets so PTT-On would lead and PTT-Off would follow. I assumed that last audio packet had an "end-transmission" bit inside. I guess adapting existing phone controls with real-time PTT/COS is a bit tricky... Thanks for the clarification. Actually this may bring to light another issue. Does my problem show that the local RX DSP is not identifying the mobile's reverse burst phase shift? Should it? (Mobile = Spectra) 73's -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Stephen Rodgers Sent: Saturday, January 22, 2011 10:23 AM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Local squelch tail problem clarification. (copy of message to Ken) for comment. On 01/22/2011 09:42 AM, Peter Elke wrote: > From: Peter Elke [mailto:pete.elke at esquared.com] > Sent: Saturday, January 22, 2011 3:26 AM > To: Ken > Subject: RE: [App_rpt-users] Location dependant squelch tail? > > > > Hi Ken, > > > > What I meant to get across was... There is a squelch tail when the > local mobile unkeys (before the hang time) but you only hear it if you > are monitoring the local node's transmit frequency. Remotely connected > stations don't hear the tail, only a soft click or nothing from the same > transmission. > > > > The local repeater transmitter dropping does not cause a tail if the > mobile is in PL decode. > > > > I thought this was just strange, so much so that I sound ignorant > reporting it... > > > > 73's Pete (WI6H) > > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users Packet propagation across an the Internet and the use of jitter buffers in Asterisk causes this. On a network-based connection, the unkey control message is reaching the far end before the audio packets containing the squelch tail noise. On a local connection, the audio packet delay is much less. I suppose a delay could be added to the local audio packet stream, but this impairs full duplex operation even more as the delay there is already annoying enough. Steve. WA6ZFT _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From kt9ac at ameritech.net Sat Jan 22 20:26:22 2011 From: kt9ac at ameritech.net (Tony KT9AC) Date: Sat, 22 Jan 2011 14:26:22 -0600 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <000601cbb9f4$efae56d0$d502a8c0@main> References: <000601cbb9f4$efae56d0$d502a8c0@main> Message-ID: <4D3B3D6E.5000804@ameritech.net> Just updated my test system to 0.281 and verified that when idle it shows a [0/20] next to my QTH. When connected, shows the "In conference with..." status. Does this mean we can host 20 connections from Echolink per Allstar node? Also, when would the "ON" versus "BUSY" flag change. I don't use Echolink a lot, but its interesting... Thanks, Tony On 01/21/2011 11:26 PM, K&R Yoksh wrote: > > ----- Original Message ----- >> Date: Fri, 21 Jan 2011 18:27:15 -0800 >> From: Jim Duuuude >> Subject: Re: [App_rpt-users] Echolink Link Status >> >> Chan_echolink now supports proper display/reporting to the echolink >> server stuff. > > Hello Jim (and the group), > > Many thanks for this great addition! > > 73. > > Kyle > K0KN > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From telesistant at hotmail.com Sat Jan 22 22:14:44 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 14:14:44 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3B3D6E.5000804@ameritech.net> References: , <000601cbb9f4$efae56d0$d502a8c0@main>, <4D3B3D6E.5000804@ameritech.net> Message-ID: Our architecture for Echolink differs a great deal from most others. Since there is no sane reason in the universe to do otherwise, our Echolink presence is both more-or-less a "conference", since it will ALWAYS accept multiple inbound connections and tie them together (as any connection is on an app_rpt node), and have the ability to support multiple outbound connections (also tied together with everything else on the app_rpt node) simultaneously. There is no reason to create "artificial" limitations of this nature. Since the Echolink reporting system is really designed for implementation that basically do "one thing at a time", there is only a concept of a single status message. To make a (rather feeble) attempt at "fitting into the mold", I decided to report the "inbound" status when there are no outbound connections active. If outbound connections are active, it reports the information for the last one connected (if multiple outbound connections are active). Therefore, by definition, the node can *never* be "busy" according to the Echolink reporting definition of "busy". And yes, the "20" means "of 20 maximum connections". However, the connection limit was never implemented (after all, I try to avoid artifical limits on things). If and when there is a compelling reason do to so, I will. Currently, the system will take as many connections as there is bandwidth and CPU power for. JIM WB6NIL > Date: Sat, 22 Jan 2011 14:26:22 -0600 > From: kt9ac at ameritech.net > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink Link Status > > Just updated my test system to 0.281 and verified that when idle it > shows a [0/20] next to my QTH. When connected, shows the "In conference > with..." status. > > Does this mean we can host 20 connections from Echolink per Allstar > node? Also, when would the "ON" versus "BUSY" flag change. > > I don't use Echolink a lot, but its interesting... > > Thanks, > Tony > > On 01/21/2011 11:26 PM, K&R Yoksh wrote: > > > > ----- Original Message ----- > >> Date: Fri, 21 Jan 2011 18:27:15 -0800 > >> From: Jim Duuuude > >> Subject: Re: [App_rpt-users] Echolink Link Status > >> > >> Chan_echolink now supports proper display/reporting to the echolink > >> server stuff. > > > > Hello Jim (and the group), > > > > Many thanks for this great addition! > > > > 73. > > > > Kyle > > K0KN > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sat Jan 22 22:23:07 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 14:23:07 -0800 Subject: [App_rpt-users] Problem with app_rpt configuration and URI's audio interface In-Reply-To: References: Message-ID: Well, the first question is: Where does the audio come from in the receiver?? Does it come directly from the discriminator (without any de-emphasis or filtering), or is it line-level or speaker (de-emphasised) audio? JIM Date: Sat, 22 Jan 2011 20:00:39 +0200 From: akalexandrov at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Problem with app_rpt configuration and URI's audio interface Dear colleagues, I built a node configuration with ACID system and URI from DMKEngineering. After the import of the ACID/Asterisk/app_rpt configuration from Allstarlink.org I connected the URI to my reg and install IAX client to the PC. The system work well from IAX clent through URI to the reg - when I send audio or voice from IAX client to the reg through URI the reg transmit the audio very well and clear. The problem is that I can not send any audio signal from the REG to the IAX client. Practically the audio from the REG go to the MIC_AC pin of URI and after that dropped down. Practically I have only one way audio communication: Iax client ->Asterisk-> app_rpt -> URI -> reg Probably I use a wrong usbradio.conf configuration but have not idea where to start looking for the problem. I red in the mailing list content some similar cases and advices about URI MIC interface problems and tried to use them but unfortunately without success. I will be very grateful for any advice how to resolve the problem. 73! Alex LZ1AZA The configuration I use is the following: URI hardware interface: audio line output of the reg - to URI MIC_AC (pin 21) microphone input of the REG - to LEFT_AC(pin 22) PTT - to PTT pin of the URI (pin1) the URI's usbradio.conf file look like this: ; ; Usbradio channel driver Configuration File ; [general] [usb27371] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=100.0 rxctcssfreqs=100.0 txctcssfreqs=100.0 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=no invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 #includeifexists custom/usbradio.conf _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From vk3jed at vkradio.com Sat Jan 22 22:44:40 2011 From: vk3jed at vkradio.com (Tony Langdon, VK3JED) Date: Sun, 23 Jan 2011 09:44:40 +1100 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000601cbb9f4$efae56d0$d502a8c0@main> <4D3B3D6E.5000804@ameritech.net> Message-ID: <4d3b5dde.4a69e50a.0733.fffffe6b@mx.google.com> At 09:14 AM 1/23/2011, Jim Duuuude wrote: >Our architecture for Echolink differs a great deal from most others. >Since there is no sane >reason in the universe to do otherwise, our Echolink presence is >both more-or-less a "conference", >since it will ALWAYS accept multiple inbound connections and tie >them together (as any connection >is on an app_rpt node), and have the ability to support multiple >outbound connections (also tied together >with everything else on the app_rpt node) simultaneously. There is >no reason to create "artificial" >limitations of this nature. Actually, there are reasons to create such limitations, but always under the sysop's discretion. A few examples might help. 1. Connecting to a node that blocks conferences. Do you advertise Asterisk as a conference all the time? Some of the time (i.e. only when there's more than one connection, which is what Echolink and thelinkbox do). 2. Conferences are not welcome on other conferences (i.e. multiconferencing). Do you have the ability to prevent Asterisk from multiconferencing? Why is this a problem, you may ask? Several years ago (actually, just before Hurricane Katrina), I realised that the most common cause of unintentional interference was caused by stations (-L, -R or PC user) having multiconferencing enabled. Someone would connect to these stations and then put out a call without taking time to listen to what's going on. In some cases, these people would actually connect and get out a call in between overs, blocking emergency or priority traffic in the process. As a result of these observations, some conferences have been running scripts that disconnect any station found to have multiconferencing enabled. 3. The number of stations allowed to be in conference is sometimes important, i.e. when upstream bandwidth is limited. It's better to block the next connection, than have everyone breaking up. All of these would need to be sysop configurable variables, and in that way, I agree that the software shouldn't contain any hard coded limitations, but sometimes, sysops need to be able to add their own limites to suit their situation. >Since the Echolink reporting system is really designed for >implementation that basically do >"one thing at a time", there is only a concept of a single status >message. To make a (rather >feeble) attempt at "fitting into the mold", I decided to report the >"inbound" status when there >are no outbound connections active. If outbound connections are >active, it reports the information >for the last one connected (if multiple outbound connections are active). I had the same issues with EchoIRLP, because IRLP had no concept of multiple connections, so reporting the "connected station" was an exercise in reporting the most recently connected station, and hoping it made some kind of sense! :) >Therefore, by definition, the node can *never* be "busy" according >to the Echolink reporting >definition of "busy". > >And yes, the "20" means "of 20 maximum connections". However, the >connection limit was never >implemented (after all, I try to avoid artifical limits on things). >If and when there is a compelling reason >do to so, I will. Currently, the system will take as many >connections as there is bandwidth and CPU power for. Or better still, put that in the hands of the sysop, since this is most likely to be site dependent. 73 de VK3JED / VK3IRL http://vkradio.com From rpt2 at chuck.midlandsnetworking.com Sat Jan 22 23:39:56 2011 From: rpt2 at chuck.midlandsnetworking.com (Chuck Henderson) Date: Sat, 22 Jan 2011 17:39:56 -0600 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> Message-ID: I know how to download the entire set of source files, but how do I download just one file such as chan_echolink.c? On Fri, Jan 21, 2011 at 8:27 PM, Jim Duuuude wrote: > Chan_echolink now supports proper display/reporting to the echolink server > stuff. > > Please download the new version of chan_echolink.c from SVN. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kt9ac at ameritech.net Sun Jan 23 00:06:59 2011 From: kt9ac at ameritech.net (Tony KT9AC) Date: Sat, 22 Jan 2011 18:06:59 -0600 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: <000e01cbb8b2$065a45e0$d502a8c0@main> <4D3851C3.2070503@bdboyle.com> <57D25806-E360-4F71-AAB1-3CEEEECC9EDE@me.com> Message-ID: <4D3B7123.3050307@ameritech.net> http://app-rpt-svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/trunk/asterisk/channels/chan_echolink.c?revision=943&root=svn&view=co On 01/22/2011 05:39 PM, Chuck Henderson wrote: > I know how to download the entire set of source files, but how do I > download just one file such as chan_echolink.c? > > On Fri, Jan 21, 2011 at 8:27 PM, Jim Duuuude > wrote: > > Chan_echolink now supports proper display/reporting to the > echolink server stuff. > > Please download the new version of chan_echolink.c from SVN. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From kt9ac at ameritech.net Sun Jan 23 00:16:42 2011 From: kt9ac at ameritech.net (Tony KT9AC) Date: Sat, 22 Jan 2011 18:16:42 -0600 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: , <000601cbb9f4$efae56d0$d502a8c0@main>, <4D3B3D6E.5000804@ameritech.net> Message-ID: <4D3B736A.6050603@ameritech.net> Thanks for all your hard work Jim! If anyone is worried about how our nodes look on Echolink (the [0/20] thing), inside /etc/asterisk/echolink.conf is a line called "maxstns" that we can change. I set mine to 1 and still was able to outbound connect to two Echolink nodes at the same time, so its mostly cosmetic. Tony On 01/22/2011 04:14 PM, Jim Duuuude wrote: > Our architecture for Echolink differs a great deal from most others. > Since there is no sane > reason in the universe to do otherwise, our Echolink presence is both > more-or-less a "conference", > since it will ALWAYS accept multiple inbound connections and tie them > together (as any connection > is on an app_rpt node), and have the ability to support multiple > outbound connections (also tied together > with everything else on the app_rpt node) simultaneously. There is no > reason to create "artificial" > limitations of this nature. > > Since the Echolink reporting system is really designed for > implementation that basically do > "one thing at a time", there is only a concept of a single status > message. To make a (rather > feeble) attempt at "fitting into the mold", I decided to report the > "inbound" status when there > are no outbound connections active. If outbound connections are > active, it reports the information > for the last one connected (if multiple outbound connections are active). > > Therefore, by definition, the node can *never* be "busy" according to > the Echolink reporting > definition of "busy". > > And yes, the "20" means "of 20 maximum connections". However, the > connection limit was never > implemented (after all, I try to avoid artifical limits on things). If > and when there is a compelling reason > do to so, I will. Currently, the system will take as many connections > as there is bandwidth and CPU power for. > > JIM WB6NIL > > > > Date: Sat, 22 Jan 2011 14:26:22 -0600 > > From: kt9ac at ameritech.net > > To: app_rpt-users at ohnosec.org > > Subject: Re: [App_rpt-users] Echolink Link Status > > > > Just updated my test system to 0.281 and verified that when idle it > > shows a [0/20] next to my QTH. When connected, shows the "In conference > > with..." status. > > > > Does this mean we can host 20 connections from Echolink per Allstar > > node? Also, when would the "ON" versus "BUSY" flag change. > > > > I don't use Echolink a lot, but its interesting... > > > > Thanks, > > Tony > > > > On 01/21/2011 11:26 PM, K&R Yoksh wrote: > > > > > > ----- Original Message ----- > > >> Date: Fri, 21 Jan 2011 18:27:15 -0800 > > >> From: Jim Duuuude > > >> Subject: Re: [App_rpt-users] Echolink Link Status > > >> > > >> Chan_echolink now supports proper display/reporting to the echolink > > >> server stuff. > > > > > > Hello Jim (and the group), > > > > > > Many thanks for this great addition! > > > > > > 73. > > > > > > Kyle > > > K0KN > > > > > > _______________________________________________ > > > App_rpt-users mailing list > > > App_rpt-users at ohnosec.org > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Jan 23 00:20:48 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 16:20:48 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: <4D3B736A.6050603@ameritech.net> References: , <000601cbb9f4$efae56d0$d502a8c0@main>, <4D3B3D6E.5000804@ameritech.net> , <4D3B736A.6050603@ameritech.net> Message-ID: Actually, at this moment tis ENTIRELY cosmetic.. :-) JIM Date: Sat, 22 Jan 2011 18:16:42 -0600 From: kt9ac at ameritech.net To: telesistant at hotmail.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Echolink Link Status Thanks for all your hard work Jim! If anyone is worried about how our nodes look on Echolink (the [0/20] thing), inside /etc/asterisk/echolink.conf is a line called "maxstns" that we can change. I set mine to 1 and still was able to outbound connect to two Echolink nodes at the same time, so its mostly cosmetic. Tony On 01/22/2011 04:14 PM, Jim Duuuude wrote: Our architecture for Echolink differs a great deal from most others. Since there is no sane reason in the universe to do otherwise, our Echolink presence is both more-or-less a "conference", since it will ALWAYS accept multiple inbound connections and tie them together (as any connection is on an app_rpt node), and have the ability to support multiple outbound connections (also tied together with everything else on the app_rpt node) simultaneously. There is no reason to create "artificial" limitations of this nature. Since the Echolink reporting system is really designed for implementation that basically do "one thing at a time", there is only a concept of a single status message. To make a (rather feeble) attempt at "fitting into the mold", I decided to report the "inbound" status when there are no outbound connections active. If outbound connections are active, it reports the information for the last one connected (if multiple outbound connections are active). Therefore, by definition, the node can *never* be "busy" according to the Echolink reporting definition of "busy". And yes, the "20" means "of 20 maximum connections". However, the connection limit was never implemented (after all, I try to avoid artifical limits on things). If and when there is a compelling reason do to so, I will. Currently, the system will take as many connections as there is bandwidth and CPU power for. JIM WB6NIL > Date: Sat, 22 Jan 2011 14:26:22 -0600 > From: kt9ac at ameritech.net > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Echolink Link Status > > Just updated my test system to 0.281 and verified that when idle it > shows a [0/20] next to my QTH. When connected, shows the "In conference > with..." status. > > Does this mean we can host 20 connections from Echolink per Allstar > node? Also, when would the "ON" versus "BUSY" flag change. > > I don't use Echolink a lot, but its interesting... > > Thanks, > Tony > > On 01/21/2011 11:26 PM, K&R Yoksh wrote: > > > > ----- Original Message ----- > >> Date: Fri, 21 Jan 2011 18:27:15 -0800 > >> From: Jim Duuuude > >> Subject: Re: [App_rpt-users] Echolink Link Status > >> > >> Chan_echolink now supports proper display/reporting to the echolink > >> server stuff. > > > > Hello Jim (and the group), > > > > Many thanks for this great addition! > > > > 73. > > > > Kyle > > K0KN > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Jan 23 04:30:33 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 22 Jan 2011 20:30:33 -0800 Subject: [App_rpt-users] new stuff Message-ID: There have (obviously) been some changes/improvements made to the Echolink and APRS/GPS subsystems within app_rpt. Included in these is the ability for a node to report its "fixed" GPS coordinates to the APRS network, even if it does not have a GPS receiver connected. Please see the following: Setting up Echolink Connectivity http://209.159.155.200/drupal/node/56 Setting Up APRS and GPS Configuration http://209.159.155.200/drupal/node/179 Of course, the latest copies of app_gps and chan_echolink need to be downloaded from the SVN. JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpt2 at chuck.midlandsnetworking.com Sun Jan 23 10:53:15 2011 From: rpt2 at chuck.midlandsnetworking.com (Chuck Henderson) Date: Sun, 23 Jan 2011 04:53:15 -0600 Subject: [App_rpt-users] aprs password for app_gps Message-ID: I would like to set up my allstarlink system to report position information to the aprs system. Can someone tell me how to set up this password? Also, are the default server and port listed in the example below what should be used? I have searched the aprs site and couldn't find who to request this information from. Chuck Henderson, WB9UUS > > ; Configuration for app_gps > ; > [general] > > call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password = 12345 ; Password for APRS-IS server for above callsign* > comment = AllStar Node 27468 ; Text to be displayed associated with this station*server = second.aprs.net ; APRS-IS server to report information to**port = 10151 ; port on server to send data* > icon = r ; A CAR (default) Icon do be displayed for station on APRS display (see below) > comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only if using GPS receiver) > baudrate = 4800 ; Baud rate for GPS receiver (specify this only if using GPS receiver) > ;debug = y ; set this for debug output > freq=442.700 ; Display Frequency of station > tone=107.2 ; CTCSS tone of station (0.0 for none) > lat=40.508 ; Fixed (default) latitude in decimal degrees > lon=-88.988 ; Fixed (default) longitude in decimal degrees > elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > power=9 ; Power level (see below) > height=5 ; Antenna Height in HAAT (see below) > gain=8 ; Antenna Gain (see below) > dir=0 ; Antenna Direction (see below) > > On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude wrote: > >> There have (obviously) been some changes/improvements made to the >> Echolink and APRS/GPS subsystems within app_rpt. >> >> Included in these is the ability for a node to report its "fixed" GPS >> coordinates >> to the APRS network, even if it does not have a GPS receiver connected. >> >> Please see the following: >> >> Setting up Echolink Connectivity >> http://209.159.155.200/drupal/node/56 >> >> Setting Up APRS and GPS Configuration >> http://209.159.155.200/drupal/node/179 >> >> Of course, the latest copies of app_gps and chan_echolink need to be >> downloaded from the SVN. >> >> JIM WB6NIL >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke2n at cs.com Sun Jan 23 12:59:34 2011 From: ke2n at cs.com (Ken) Date: Sun, 23 Jan 2011 07:59:34 -0500 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: Message-ID: <000901cbbafd$62842230$278c6690$@com> Well - Google found this http://zielkeassociates.com/~jack/aprs-xo/aprspass/ I took the first link provided and looked at the first few entries and there are emails for sysops who will give you a "passcode" Apparently the passcode is generated from an algorithm using your call+SSID as input. I have not tried it (yet) Ken From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Chuck Henderson Sent: Sunday, January 23, 2011 5:53 AM To: app_rpt mailing list Subject: [App_rpt-users] aprs password for app_gps I would like to set up my allstarlink system to report position information to the aprs system. Can someone tell me how to set up this password? Also, are the default server and port listed in the example below what should be used? I have searched the aprs site and couldn't find who to request this information from. Chuck Henderson, WB9UUS ; Configuration for app_gps ; [general] call = wb9uus-2 ; callsign (including SSID) for APRS purposes password = 12345 ; Password for APRS-IS server for above callsign comment = AllStar Node 27468 ; Text to be displayed associated with this station server = second.aprs.net ; APRS-IS server to report information to port = 10151 ; port on server to send data icon = r ; A CAR (default) Icon do be displayed for station on APRS display (see below) comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only if using GPS receiver) baudrate = 4800 ; Baud rate for GPS receiver (specify this only if using GPS receiver) ;debug = y ; set this for debug output freq=442.700 ; Display Frequency of station tone=107.2 ; CTCSS tone of station (0.0 for none) lat=40.508 ; Fixed (default) latitude in decimal degrees lon=-88.988 ; Fixed (default) longitude in decimal degrees elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) power=9 ; Power level (see below) height=5 ; Antenna Height in HAAT (see below) gain=8 ; Antenna Gain (see below) dir=0 ; Antenna Direction (see below) On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude wrote: There have (obviously) been some changes/improvements made to the Echolink and APRS/GPS subsystems within app_rpt. Included in these is the ability for a node to report its "fixed" GPS coordinates to the APRS network, even if it does not have a GPS receiver connected. Please see the following: Setting up Echolink Connectivity http://209.159.155.200/drupal/node/56 Setting Up APRS and GPS Configuration http://209.159.155.200/drupal/node/179 Of course, the latest copies of app_gps and chan_echolink need to be downloaded from the SVN. JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From yo3iiu at yo3iiu.ro Sun Jan 23 13:49:55 2011 From: yo3iiu at yo3iiu.ro (Bogdan Diaconescu) Date: Sun, 23 Jan 2011 15:49:55 +0200 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: Message-ID: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> The APRS-IS password could be generated using the callpass utility that comes with xastir. Bogdan - YO3IIU > I would like to set up my allstarlink system to report position > information > to the aprs system. > > Can someone tell me how to set up this password? Also, are the default > server and port listed in the example below what should be used? > I have searched the aprs site and couldn't find who to request this > information from. > > Chuck Henderson, WB9UUS > > >> >> ; Configuration for app_gps >> ; >> [general] >> >> call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password >> = 12345 ; Password for APRS-IS server for above callsign* >> comment = AllStar Node 27468 ; Text to be displayed associated with this >> station*server = second.aprs.net ; APRS-IS server to report information >> to**port = 10151 ; port on server to send data* >> icon = r ; A CAR (default) Icon do be displayed for station on APRS >> display (see below) >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only >> if using GPS receiver) >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if >> using GPS receiver) >> ;debug = y ; set this for debug output >> freq=442.700 ; Display Frequency of station >> tone=107.2 ; CTCSS tone of station (0.0 for none) >> lat=40.508 ; Fixed (default) latitude in decimal degrees >> lon=-88.988 ; Fixed (default) longitude in decimal degrees >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) >> power=9 ; Power level (see below) >> height=5 ; Antenna Height in HAAT (see below) >> gain=8 ; Antenna Gain (see below) >> dir=0 ; Antenna Direction (see below) >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude >> wrote: >> >>> There have (obviously) been some changes/improvements made to the >>> Echolink and APRS/GPS subsystems within app_rpt. >>> >>> Included in these is the ability for a node to report its "fixed" GPS >>> coordinates >>> to the APRS network, even if it does not have a GPS receiver connected. >>> >>> Please see the following: >>> >>> Setting up Echolink Connectivity >>> http://209.159.155.200/drupal/node/56 >>> >>> Setting Up APRS and GPS Configuration >>> http://209.159.155.200/drupal/node/179 >>> >>> Of course, the latest copies of app_gps and chan_echolink need to be >>> downloaded from the SVN. >>> >>> JIM WB6NIL >>> >>> >>> >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From telesistant at hotmail.com Sun Jan 23 16:13:51 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 23 Jan 2011 08:13:51 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> References: , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> Message-ID: The heck with all this confusion regarding APRS passwords!! I just reverse engineered the password algorithm and will make a password generator (and will also automatically generate a password for Portal-generate configurations). JIM > Date: Sun, 23 Jan 2011 15:49:55 +0200 > From: yo3iiu at yo3iiu.ro > To: rpt2 at chuck.midlandsnetworking.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] aprs password for app_gps > > The APRS-IS password could be generated using the callpass utility that > comes with xastir. > > Bogdan - YO3IIU > > > I would like to set up my allstarlink system to report position > > information > > to the aprs system. > > > > Can someone tell me how to set up this password? Also, are the default > > server and port listed in the example below what should be used? > > I have searched the aprs site and couldn't find who to request this > > information from. > > > > Chuck Henderson, WB9UUS > > > > > >> > >> ; Configuration for app_gps > >> ; > >> [general] > >> > >> call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password > >> = 12345 ; Password for APRS-IS server for above callsign* > >> comment = AllStar Node 27468 ; Text to be displayed associated with this > >> station*server = second.aprs.net ; APRS-IS server to report information > >> to**port = 10151 ; port on server to send data* > >> icon = r ; A CAR (default) Icon do be displayed for station on APRS > >> display (see below) > >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only > >> if using GPS receiver) > >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > >> using GPS receiver) > >> ;debug = y ; set this for debug output > >> freq=442.700 ; Display Frequency of station > >> tone=107.2 ; CTCSS tone of station (0.0 for none) > >> lat=40.508 ; Fixed (default) latitude in decimal degrees > >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > >> power=9 ; Power level (see below) > >> height=5 ; Antenna Height in HAAT (see below) > >> gain=8 ; Antenna Gain (see below) > >> dir=0 ; Antenna Direction (see below) > >> > >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> wrote: > >> > >>> There have (obviously) been some changes/improvements made to the > >>> Echolink and APRS/GPS subsystems within app_rpt. > >>> > >>> Included in these is the ability for a node to report its "fixed" GPS > >>> coordinates > >>> to the APRS network, even if it does not have a GPS receiver connected. > >>> > >>> Please see the following: > >>> > >>> Setting up Echolink Connectivity > >>> http://209.159.155.200/drupal/node/56 > >>> > >>> Setting Up APRS and GPS Configuration > >>> http://209.159.155.200/drupal/node/179 > >>> > >>> Of course, the latest copies of app_gps and chan_echolink need to be > >>> downloaded from the SVN. > >>> > >>> JIM WB6NIL > >>> > >>> > >>> > >> > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Jan 23 17:14:53 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 23 Jan 2011 09:14:53 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: , , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro>, Message-ID: Okay, the web site now has automatic APRS password generation for Web-based configurations, and a page to do it manually (under "server"). JIM WB6NIL From: telesistant at hotmail.com To: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com Date: Sun, 23 Jan 2011 08:13:51 -0800 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] aprs password for app_gps The heck with all this confusion regarding APRS passwords!! I just reverse engineered the password algorithm and will make a password generator (and will also automatically generate a password for Portal-generate configurations). JIM > Date: Sun, 23 Jan 2011 15:49:55 +0200 > From: yo3iiu at yo3iiu.ro > To: rpt2 at chuck.midlandsnetworking.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] aprs password for app_gps > > The APRS-IS password could be generated using the callpass utility that > comes with xastir. > > Bogdan - YO3IIU > > > I would like to set up my allstarlink system to report position > > information > > to the aprs system. > > > > Can someone tell me how to set up this password? Also, are the default > > server and port listed in the example below what should be used? > > I have searched the aprs site and couldn't find who to request this > > information from. > > > > Chuck Henderson, WB9UUS > > > > > >> > >> ; Configuration for app_gps > >> ; > >> [general] > >> > >> call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password > >> = 12345 ; Password for APRS-IS server for above callsign* > >> comment = AllStar Node 27468 ; Text to be displayed associated with this > >> station*server = second.aprs.net ; APRS-IS server to report information > >> to**port = 10151 ; port on server to send data* > >> icon = r ; A CAR (default) Icon do be displayed for station on APRS > >> display (see below) > >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only > >> if using GPS receiver) > >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > >> using GPS receiver) > >> ;debug = y ; set this for debug output > >> freq=442.700 ; Display Frequency of station > >> tone=107.2 ; CTCSS tone of station (0.0 for none) > >> lat=40.508 ; Fixed (default) latitude in decimal degrees > >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > >> power=9 ; Power level (see below) > >> height=5 ; Antenna Height in HAAT (see below) > >> gain=8 ; Antenna Gain (see below) > >> dir=0 ; Antenna Direction (see below) > >> > >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> wrote: > >> > >>> There have (obviously) been some changes/improvements made to the > >>> Echolink and APRS/GPS subsystems within app_rpt. > >>> > >>> Included in these is the ability for a node to report its "fixed" GPS > >>> coordinates > >>> to the APRS network, even if it does not have a GPS receiver connected. > >>> > >>> Please see the following: > >>> > >>> Setting up Echolink Connectivity > >>> http://209.159.155.200/drupal/node/56 > >>> > >>> Setting Up APRS and GPS Configuration > >>> http://209.159.155.200/drupal/node/179 > >>> > >>> Of course, the latest copies of app_gps and chan_echolink need to be > >>> downloaded from the SVN. > >>> > >>> JIM WB6NIL > >>> > >>> > >>> > >> > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki6psp at gmail.com Sun Jan 23 19:42:04 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Sun, 23 Jan 2011 11:42:04 -0800 Subject: [App_rpt-users] Echolink Link Status Message-ID: I updated my node with the whole SVN as I don't know how to update just the portion of the echolink, but I don't see the gps.conf file under /etc/asterisk/ Did I miss something, or do I have to build that conf file manually? -- KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From yo3iiu at yo3iiu.ro Sun Jan 23 22:27:16 2011 From: yo3iiu at yo3iiu.ro (Bogdan Diaconescu) Date: Mon, 24 Jan 2011 00:27:16 +0200 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> Message-ID: <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> The protocol is quite simple and the source for callpass is included in the xastir source. Though, reverse engineering it seems a lot more fun :) Regards, Bogdan - YO3IIU > > The heck with all this confusion regarding APRS passwords!! > > I just reverse engineered the password algorithm and will make > a password generator (and will also automatically generate a password > for Portal-generate configurations). > > JIM > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 >> From: yo3iiu at yo3iiu.ro >> To: rpt2 at chuck.midlandsnetworking.com >> CC: app_rpt-users at ohnosec.org >> Subject: Re: [App_rpt-users] aprs password for app_gps >> >> The APRS-IS password could be generated using the callpass utility that >> comes with xastir. >> >> Bogdan - YO3IIU >> >> > I would like to set up my allstarlink system to report position >> > information >> > to the aprs system. >> > >> > Can someone tell me how to set up this password? Also, are the >> default >> > server and port listed in the example below what should be used? >> > I have searched the aprs site and couldn't find who to request this >> > information from. >> > >> > Chuck Henderson, WB9UUS >> > >> > >> >> >> >> ; Configuration for app_gps >> >> ; >> >> [general] >> >> >> >> call = wb9uus-2 ; callsign (including SSID) for APRS >> purposes*password >> >> = 12345 ; Password for APRS-IS server for above callsign* >> >> comment = AllStar Node 27468 ; Text to be displayed associated with >> this >> >> station*server = second.aprs.net ; APRS-IS server to report >> information >> >> to**port = 10151 ; port on server to send data* >> >> icon = r ; A CAR (default) Icon do be displayed for station on >> APRS >> >> display (see below) >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this >> only >> >> if using GPS receiver) >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if >> >> using GPS receiver) >> >> ;debug = y ; set this for debug output >> >> freq=442.700 ; Display Frequency of station >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) >> >> power=9 ; Power level (see below) >> >> height=5 ; Antenna Height in HAAT (see below) >> >> gain=8 ; Antenna Gain (see below) >> >> dir=0 ; Antenna Direction (see below) >> >> >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude >> >> wrote: >> >> >> >>> There have (obviously) been some changes/improvements made to the >> >>> Echolink and APRS/GPS subsystems within app_rpt. >> >>> >> >>> Included in these is the ability for a node to report its "fixed" >> GPS >> >>> coordinates >> >>> to the APRS network, even if it does not have a GPS receiver >> connected. >> >>> >> >>> Please see the following: >> >>> >> >>> Setting up Echolink Connectivity >> >>> http://209.159.155.200/drupal/node/56 >> >>> >> >>> Setting Up APRS and GPS Configuration >> >>> http://209.159.155.200/drupal/node/179 >> >>> >> >>> Of course, the latest copies of app_gps and chan_echolink need to be >> >>> downloaded from the SVN. >> >>> >> >>> JIM WB6NIL >> >>> >> >>> >> >>> >> >> >> > _______________________________________________ >> > App_rpt-users mailing list >> > App_rpt-users at ohnosec.org >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> > >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From tim.sawyer at me.com Sun Jan 23 23:51:38 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Sun, 23 Jan 2011 15:51:38 -0800 Subject: [App_rpt-users] Echolink Link Status In-Reply-To: References: Message-ID: <4815DEA3-A9B8-4267-831A-0E3E105C159D@me.com> Sample configs including one for gps are in /usr/src/astsrc/asterisk/configs -- Tim :wq On Jan 23, 2011, at 11:42 AM, KI6PSP (Ed) wrote: > I updated my node with the whole SVN as I don't know how to update just the portion of the echolink, but I don't see the gps.conf file under /etc/asterisk/ > > Did I miss something, or do I have to build that conf file manually? > > -- > KI6PSP (Ed) > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From telesistant at hotmail.com Mon Jan 24 00:42:33 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 23 Jan 2011 16:42:33 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> References: , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro>, , <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> Message-ID: it was!! :-) > Date: Mon, 24 Jan 2011 00:27:16 +0200 > Subject: RE: [App_rpt-users] aprs password for app_gps > From: yo3iiu at yo3iiu.ro > To: telesistant at hotmail.com > CC: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com; app_rpt-users at ohnosec.org > > The protocol is quite simple and the source for callpass is included in > the xastir source. Though, reverse engineering it seems a lot more fun :) > > Regards, > Bogdan - YO3IIU > > > > > The heck with all this confusion regarding APRS passwords!! > > > > I just reverse engineered the password algorithm and will make > > a password generator (and will also automatically generate a password > > for Portal-generate configurations). > > > > JIM > > > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 > >> From: yo3iiu at yo3iiu.ro > >> To: rpt2 at chuck.midlandsnetworking.com > >> CC: app_rpt-users at ohnosec.org > >> Subject: Re: [App_rpt-users] aprs password for app_gps > >> > >> The APRS-IS password could be generated using the callpass utility that > >> comes with xastir. > >> > >> Bogdan - YO3IIU > >> > >> > I would like to set up my allstarlink system to report position > >> > information > >> > to the aprs system. > >> > > >> > Can someone tell me how to set up this password? Also, are the > >> default > >> > server and port listed in the example below what should be used? > >> > I have searched the aprs site and couldn't find who to request this > >> > information from. > >> > > >> > Chuck Henderson, WB9UUS > >> > > >> > > >> >> > >> >> ; Configuration for app_gps > >> >> ; > >> >> [general] > >> >> > >> >> call = wb9uus-2 ; callsign (including SSID) for APRS > >> purposes*password > >> >> = 12345 ; Password for APRS-IS server for above callsign* > >> >> comment = AllStar Node 27468 ; Text to be displayed associated with > >> this > >> >> station*server = second.aprs.net ; APRS-IS server to report > >> information > >> >> to**port = 10151 ; port on server to send data* > >> >> icon = r ; A CAR (default) Icon do be displayed for station on > >> APRS > >> >> display (see below) > >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this > >> only > >> >> if using GPS receiver) > >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > >> >> using GPS receiver) > >> >> ;debug = y ; set this for debug output > >> >> freq=442.700 ; Display Frequency of station > >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) > >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees > >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > >> >> power=9 ; Power level (see below) > >> >> height=5 ; Antenna Height in HAAT (see below) > >> >> gain=8 ; Antenna Gain (see below) > >> >> dir=0 ; Antenna Direction (see below) > >> >> > >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> >> wrote: > >> >> > >> >>> There have (obviously) been some changes/improvements made to the > >> >>> Echolink and APRS/GPS subsystems within app_rpt. > >> >>> > >> >>> Included in these is the ability for a node to report its "fixed" > >> GPS > >> >>> coordinates > >> >>> to the APRS network, even if it does not have a GPS receiver > >> connected. > >> >>> > >> >>> Please see the following: > >> >>> > >> >>> Setting up Echolink Connectivity > >> >>> http://209.159.155.200/drupal/node/56 > >> >>> > >> >>> Setting Up APRS and GPS Configuration > >> >>> http://209.159.155.200/drupal/node/179 > >> >>> > >> >>> Of course, the latest copies of app_gps and chan_echolink need to be > >> >>> downloaded from the SVN. > >> >>> > >> >>> JIM WB6NIL > >> >>> > >> >>> > >> >>> > >> >> > >> > _______________________________________________ > >> > App_rpt-users mailing list > >> > App_rpt-users at ohnosec.org > >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb3ors at windstream.net Mon Jan 24 02:15:31 2011 From: kb3ors at windstream.net (KB3ORS - Brian) Date: Sun, 23 Jan 2011 21:15:31 -0500 Subject: [App_rpt-users] Problem with app_rpt configuration and URI's audiointerface In-Reply-To: References: Message-ID: <3159551CE59649899E53588F3EE90BFE@BrianPC> ?First thing I would do is turn off the PL in the software by changing ctcss=dsp to NO. To make sure your PL is not blocking you out. Brian KB3ORS From: Alexander Alexandrov Sent: Saturday, January 22, 2011 1:00 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Problem with app_rpt configuration and URI's audiointerface Dear colleagues, I built a node configuration with ACID system and URI from DMKEngineering. After the import of the ACID/Asterisk/app_rpt configuration from Allstarlink.org I connected the URI to my reg and install IAX client to the PC. The system work well from IAX clent through URI to the reg - when I send audio or voice from IAX client to the reg through URI the reg transmit the audio very well and clear. The problem is that I can not send any audio signal from the REG to the IAX client. Practically the audio from the REG go to the MIC_AC pin of URI and after that dropped down. Practically I have only one way audio communication: Iax client ->Asterisk-> app_rpt -> URI -> reg Probably I use a wrong usbradio.conf configuration but have not idea where to start looking for the problem. I red in the mailing list content some similar cases and advices about URI MIC interface problems and tried to use them but unfortunately without success. I will be very grateful for any advice how to resolve the problem. 73! Alex LZ1AZA The configuration I use is the following: URI hardware interface: audio line output of the reg - to URI MIC_AC (pin 21) microphone input of the REG - to LEFT_AC(pin 22) PTT - to PTT pin of the URI (pin1) the URI's usbradio.conf file look like this: ; ; Usbradio channel driver Configuration File ; [general] [usb27371] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=100.0 rxctcssfreqs=100.0 txctcssfreqs=100.0 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=no invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 #includeifexists custom/usbradio.conf -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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: 10.0.1191 / Virus Database: 1435/3396 - Release Date: 01/22/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki6psp at gmail.com Mon Jan 24 14:28:01 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Mon, 24 Jan 2011 06:28:01 -0800 Subject: [App_rpt-users] Suggested mod to default extensions.conf Message-ID: I am by no means an expert, but I have a suggestion. I nuked my extensions.conf file and rebuilt it from the web confuguration and I found a glitch in the default config. If the internet connection is down, and a call is made, the fast busy tone will sound, but it will not stop. If this is a simplex node, that is a problem. Here is my suggested default config: ; Un-comment out the following clause if you want Allstar Autopatch service [pstn-out] exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/\${EXTEN}) exten=_NXXNXXXXXX,2,Wait,3 exten=_NXXNXXXXXX,3,Hangup Thanks Ed KI6PSP -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki6psp at gmail.com Mon Jan 24 15:21:32 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Mon, 24 Jan 2011 07:21:32 -0800 Subject: [App_rpt-users] One Way local connect Message-ID: Internal Allstar Connect works only one way. Run Macro for connect from 27178 to 27179 [Jan 24 07:10:19] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char * duration 255 ms [Jan 24 07:10:19] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 192 ms [Jan 24 07:10:20] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 234 ms [Jan 24 07:10:20] NOTICE[3020]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 2 duration 256 ms [Jan 24 07:10:21] NOTICE[2699]: chan_iax2.c:9043 socket_process: Rejected connect attempt from 127.0.0.1, request '27179 at radio-secure' does not exist [Jan 24 07:10:21] WARNING[2700]: chan_iax2.c:9221 socket_process: Call rejected by 127.0.0.1: No such context/extension -- Hungup 'IAX2/127.0.0.1:4569-1476' -- Hungup 'Zap/pseudo-1926956532' -- Hungup 'Zap/pseudo-1808547294' -- Hungup 'Zap/pseudo-1160049049' -- Playing 'rpt/nodenames/27179' (language 'en') -- Playing 'rpt/connection_failed' (language 'en') -- Hungup 'Zap/pseudo-1659184301' Run Macro for connect from 27179 to 27178 [Jan 24 07:11:37] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char * duration 277 ms [Jan 24 07:11:38] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 170 ms [Jan 24 07:11:38] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 5 duration 216 ms [Jan 24 07:11:39] NOTICE[3021]: chan_usbradio.c:2985 usbradio_read: Got DTMF char 2 duration 256 ms -- Accepting UNAUTHENTICATED call from 127.0.0.1: > requested format = gsm, > requested prefs = (gsm|g726aal2|ulaw), > actual format = g726aal2, > host prefs = (g726aal2|gsm), > priority = mine -- Call accepted by 127.0.0.1 (format g726aal2) -- Format for call is g726aal2 -- Executing [27178 at radio-secure:1] Rpt("IAX2/127.0.0.1:4569-2496", "27178") in new stack == Spawn extension (radio-secure, 27178, 1) exited KEEPALIVE on 'IAX2/127.0.0.1:4569-2496' -- Playing 'rpt/nodenames/27178' (language 'en') -- Hungup 'Zap/pseudo-1169767949' -- Hungup 'Zap/pseudo-1558440647' -- Playing 'rpt/connected' (language 'en') -- Hungup 'Zap/pseudo-1043702359' -- Playing 'digits/2' (language 'en') -- Playing 'rpt/nodenames/27179' (language 'en') -- Playing 'rpt/nodenames/27178' (language 'en') -- Hungup 'Zap/pseudo-360302433' -- Playing 'rpt/connected' (language 'en') -- Playing 'digits/2' (language 'en') -- Playing 'rpt/nodenames/27179' (language 'en') -- Hungup 'Zap/pseudo-128502133' -- Hungup 'Zap/pseudo-1357185046' -- Hungup 'Zap/pseudo-1756365411' I thought it had something to do with the "Node=" line in extensions.conf, so I commented it out, but it still does this. I already found the register lines in the IAX.conf and uncommented it. Both nodes in the rpt.conf file have the same context and account names. -- KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpt2 at chuck.midlandsnetworking.com Mon Jan 24 15:32:41 2011 From: rpt2 at chuck.midlandsnetworking.com (Chuck Henderson) Date: Mon, 24 Jan 2011 09:32:41 -0600 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> Message-ID: *Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console..*. [Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call *I then enabled debugging in the gps.conf file and this is what I got...* [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M [Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps" [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M [Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M [Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M [Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps" [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M [Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call *I suspect that it is expecting a radio to be connected for it to send packets out over the air. * *How do I configure this so it can work or, if that isn't what it is about, then how do I get rid of the warning?* Chuck Henderson, WB9UUS On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude wrote: > it was!! :-) > > > Date: Mon, 24 Jan 2011 00:27:16 +0200 > > Subject: RE: [App_rpt-users] aprs password for app_gps > > From: yo3iiu at yo3iiu.ro > > To: telesistant at hotmail.com > > CC: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com; > app_rpt-users at ohnosec.org > > > > > The protocol is quite simple and the source for callpass is included in > > the xastir source. Though, reverse engineering it seems a lot more fun :) > > > > Regards, > > Bogdan - YO3IIU > > > > > > > > The heck with all this confusion regarding APRS passwords!! > > > > > > I just reverse engineered the password algorithm and will make > > > a password generator (and will also automatically generate a password > > > for Portal-generate configurations). > > > > > > JIM > > > > > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 > > >> From: yo3iiu at yo3iiu.ro > > >> To: rpt2 at chuck.midlandsnetworking.com > > >> CC: app_rpt-users at ohnosec.org > > >> Subject: Re: [App_rpt-users] aprs password for app_gps > > >> > > >> The APRS-IS password could be generated using the callpass utility > that > > >> comes with xastir. > > >> > > >> Bogdan - YO3IIU > > >> > > >> > I would like to set up my allstarlink system to report position > > >> > information > > >> > to the aprs system. > > >> > > > >> > Can someone tell me how to set up this password? Also, are the > > >> default > > >> > server and port listed in the example below what should be used? > > >> > I have searched the aprs site and couldn't find who to request this > > >> > information from. > > >> > > > >> > Chuck Henderson, WB9UUS > > >> > > > >> > > > >> >> > > >> >> ; Configuration for app_gps > > >> >> ; > > >> >> [general] > > >> >> > > >> >> call = wb9uus-2 ; callsign (including SSID) for APRS > > >> purposes*password > > >> >> = 12345 ; Password for APRS-IS server for above callsign* > > >> >> comment = AllStar Node 27468 ; Text to be displayed associated with > > >> this > > >> >> station*server = second.aprs.net ; APRS-IS server to report > > >> information > > >> >> to**port = 10151 ; port on server to send data* > > >> >> icon = r ; A CAR (default) Icon do be displayed for station on > > >> APRS > > >> >> display (see below) > > >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this > > >> only > > >> >> if using GPS receiver) > > >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > > >> >> using GPS receiver) > > >> >> ;debug = y ; set this for debug output > > >> >> freq=442.700 ; Display Frequency of station > > >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) > > >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees > > >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > > >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > > >> >> power=9 ; Power level (see below) > > >> >> height=5 ; Antenna Height in HAAT (see below) > > >> >> gain=8 ; Antenna Gain (see below) > > >> >> dir=0 ; Antenna Direction (see below) > > >> >> > > >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > >> >> wrote: > > >> >> > > >> >>> There have (obviously) been some changes/improvements made to the > > >> >>> Echolink and APRS/GPS subsystems within app_rpt. > > >> >>> > > >> >>> Included in these is the ability for a node to report its "fixed" > > >> GPS > > >> >>> coordinates > > >> >>> to the APRS network, even if it does not have a GPS receiver > > >> connected. > > >> >>> > > >> >>> Please see the following: > > >> >>> > > >> >>> Setting up Echolink Connectivity > > >> >>> http://209.159.155.200/drupal/node/56 > > >> >>> > > >> >>> Setting Up APRS and GPS Configuration > > >> >>> http://209.159.155.200/drupal/node/179 > > >> >>> > > >> >>> Of course, the latest copies of app_gps and chan_echolink need to > be > > >> >>> downloaded from the SVN. > > >> >>> > > >> >>> JIM WB6NIL > > >> >>> > > >> >>> > > >> >>> > > >> >> > > >> > _______________________________________________ > > >> > App_rpt-users mailing list > > >> > App_rpt-users at ohnosec.org > > >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > >> > > > >> > > >> > > >> _______________________________________________ > > >> App_rpt-users mailing list > > >> App_rpt-users at ohnosec.org > > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Mon Jan 24 16:00:06 2011 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Mon, 24 Jan 2011 11:00:06 -0500 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> Message-ID: <4D3DA206.70003@bdboyle.com> On 1/24/11 10:32 AM, Chuck Henderson wrote: > *Since adding the gps.conf, which is working and puts me on the aprs > maps, I started getting the following messages on the console..*. > [Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: > select failed: Interrupted system call > *****DELETIA**** > > Chuck Henderson, WB9UUS > seeing the same thing... Also...is there any variable possible to set to cut down the reporting interval? For a stationary system...like a repeater...every 30 seconds seems a bit much (maybe if it was located on the San Andreas fault, it would be moving, though...;)) -- 73 all...and thanks, Jim, for the great functionality. Bryan Echolink WB0YLE-R Allstar 27294 APRS WB0YLE-8 LS/MFT YMMV ROTFLMAO etc... -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 24 16:57:52 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 24 Jan 2011 08:57:52 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> , <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> , Message-ID: could you send me a tarball of your entire /etc/asterisk directory, so that I may duplicate the problem here? Thanks JIM From: rpt2 at chuck.midlandsnetworking.com Date: Mon, 24 Jan 2011 09:32:41 -0600 Subject: Re: [App_rpt-users] aprs password for app_gps To: app_rpt-users at ohnosec.org CC: telesistant at hotmail.com Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console...[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call I then enabled debugging in the gps.conf file and this is what I got... [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps"[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps"[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call I suspect that it is expecting a radio to be connected for it to send packets out over the air. How do I configure this so it can work or, if that isn't what it is about, then how do I get rid of the warning? Chuck Henderson, WB9UUS On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude wrote: it was!! :-) > Date: Mon, 24 Jan 2011 00:27:16 +0200 > Subject: RE: [App_rpt-users] aprs password for app_gps > From: yo3iiu at yo3iiu.ro > To: telesistant at hotmail.com > CC: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com; app_rpt-users at ohnosec.org > > The protocol is quite simple and the source for callpass is included in > the xastir source. Though, reverse engineering it seems a lot more fun :) > > Regards, > Bogdan - YO3IIU > > > > > The heck with all this confusion regarding APRS passwords!! > > > > I just reverse engineered the password algorithm and will make > > a password generator (and will also automatically generate a password > > for Portal-generate configurations). > > > > JIM > > > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 > >> From: yo3iiu at yo3iiu.ro > >> To: rpt2 at chuck.midlandsnetworking.com > >> CC: app_rpt-users at ohnosec.org > >> Subject: Re: [App_rpt-users] aprs password for app_gps > >> > >> The APRS-IS password could be generated using the callpass utility that > >> comes with xastir. > >> > >> Bogdan - YO3IIU > >> > >> > I would like to set up my allstarlink system to report position > >> > information > >> > to the aprs system. > >> > > >> > Can someone tell me how to set up this password? Also, are the > >> default > >> > server and port listed in the example below what should be used? > >> > I have searched the aprs site and couldn't find who to request this > >> > information from. > >> > > >> > Chuck Henderson, WB9UUS > >> > > >> > > >> >> > >> >> ; Configuration for app_gps > >> >> ; > >> >> [general] > >> >> > >> >> call = wb9uus-2 ; callsign (including SSID) for APRS > >> purposes*password > >> >> = 12345 ; Password for APRS-IS server for above callsign* > >> >> comment = AllStar Node 27468 ; Text to be displayed associated with > >> this > >> >> station*server = second.aprs.net ; APRS-IS server to report > >> information > >> >> to**port = 10151 ; port on server to send data* > >> >> icon = r ; A CAR (default) Icon do be displayed for station on > >> APRS > >> >> display (see below) > >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this > >> only > >> >> if using GPS receiver) > >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > >> >> using GPS receiver) > >> >> ;debug = y ; set this for debug output > >> >> freq=442.700 ; Display Frequency of station > >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) > >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees > >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > >> >> power=9 ; Power level (see below) > >> >> height=5 ; Antenna Height in HAAT (see below) > >> >> gain=8 ; Antenna Gain (see below) > >> >> dir=0 ; Antenna Direction (see below) > >> >> > >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> >> wrote: > >> >> > >> >>> There have (obviously) been some changes/improvements made to the > >> >>> Echolink and APRS/GPS subsystems within app_rpt. > >> >>> > >> >>> Included in these is the ability for a node to report its "fixed" > >> GPS > >> >>> coordinates > >> >>> to the APRS network, even if it does not have a GPS receiver > >> connected. > >> >>> > >> >>> Please see the following: > >> >>> > >> >>> Setting up Echolink Connectivity > >> >>> http://209.159.155.200/drupal/node/56 > >> >>> > >> >>> Setting Up APRS and GPS Configuration > >> >>> http://209.159.155.200/drupal/node/179 > >> >>> > >> >>> Of course, the latest copies of app_gps and chan_echolink need to be > >> >>> downloaded from the SVN. > >> >>> > >> >>> JIM WB6NIL > >> >>> > >> >>> > >> >>> > >> >> > >> > _______________________________________________ > >> > App_rpt-users mailing list > >> > App_rpt-users at ohnosec.org > >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Mon Jan 24 17:00:46 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Mon, 24 Jan 2011 09:00:46 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: , <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> , <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> , Message-ID: also, did you update everything to the latest SVN, or just app_gps and chan_echolink?? My copy of chan_usbradio.c does not have that line in the same location, which leads me to believe that you didnt update from the whole SVN. Heck, just send me a copy of your chan_usbradio.c file, too while youre at it. Thanks JIM From: rpt2 at chuck.midlandsnetworking.com Date: Mon, 24 Jan 2011 09:32:41 -0600 Subject: Re: [App_rpt-users] aprs password for app_gps To: app_rpt-users at ohnosec.org CC: telesistant at hotmail.com Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console...[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call I then enabled debugging in the gps.conf file and this is what I got... [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps"[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers "Asterisk app_gps"[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 [Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call I suspect that it is expecting a radio to be connected for it to send packets out over the air. How do I configure this so it can work or, if that isn't what it is about, then how do I get rid of the warning? Chuck Henderson, WB9UUS On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude wrote: it was!! :-) > Date: Mon, 24 Jan 2011 00:27:16 +0200 > Subject: RE: [App_rpt-users] aprs password for app_gps > From: yo3iiu at yo3iiu.ro > To: telesistant at hotmail.com > CC: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com; app_rpt-users at ohnosec.org > > The protocol is quite simple and the source for callpass is included in > the xastir source. Though, reverse engineering it seems a lot more fun :) > > Regards, > Bogdan - YO3IIU > > > > > The heck with all this confusion regarding APRS passwords!! > > > > I just reverse engineered the password algorithm and will make > > a password generator (and will also automatically generate a password > > for Portal-generate configurations). > > > > JIM > > > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 > >> From: yo3iiu at yo3iiu.ro > >> To: rpt2 at chuck.midlandsnetworking.com > >> CC: app_rpt-users at ohnosec.org > >> Subject: Re: [App_rpt-users] aprs password for app_gps > >> > >> The APRS-IS password could be generated using the callpass utility that > >> comes with xastir. > >> > >> Bogdan - YO3IIU > >> > >> > I would like to set up my allstarlink system to report position > >> > information > >> > to the aprs system. > >> > > >> > Can someone tell me how to set up this password? Also, are the > >> default > >> > server and port listed in the example below what should be used? > >> > I have searched the aprs site and couldn't find who to request this > >> > information from. > >> > > >> > Chuck Henderson, WB9UUS > >> > > >> > > >> >> > >> >> ; Configuration for app_gps > >> >> ; > >> >> [general] > >> >> > >> >> call = wb9uus-2 ; callsign (including SSID) for APRS > >> purposes*password > >> >> = 12345 ; Password for APRS-IS server for above callsign* > >> >> comment = AllStar Node 27468 ; Text to be displayed associated with > >> this > >> >> station*server = second.aprs.net ; APRS-IS server to report > >> information > >> >> to**port = 10151 ; port on server to send data* > >> >> icon = r ; A CAR (default) Icon do be displayed for station on > >> APRS > >> >> display (see below) > >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this > >> only > >> >> if using GPS receiver) > >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > >> >> using GPS receiver) > >> >> ;debug = y ; set this for debug output > >> >> freq=442.700 ; Display Frequency of station > >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) > >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees > >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > >> >> power=9 ; Power level (see below) > >> >> height=5 ; Antenna Height in HAAT (see below) > >> >> gain=8 ; Antenna Gain (see below) > >> >> dir=0 ; Antenna Direction (see below) > >> >> > >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> >> wrote: > >> >> > >> >>> There have (obviously) been some changes/improvements made to the > >> >>> Echolink and APRS/GPS subsystems within app_rpt. > >> >>> > >> >>> Included in these is the ability for a node to report its "fixed" > >> GPS > >> >>> coordinates > >> >>> to the APRS network, even if it does not have a GPS receiver > >> connected. > >> >>> > >> >>> Please see the following: > >> >>> > >> >>> Setting up Echolink Connectivity > >> >>> http://209.159.155.200/drupal/node/56 > >> >>> > >> >>> Setting Up APRS and GPS Configuration > >> >>> http://209.159.155.200/drupal/node/179 > >> >>> > >> >>> Of course, the latest copies of app_gps and chan_echolink need to be > >> >>> downloaded from the SVN. > >> >>> > >> >>> JIM WB6NIL > >> >>> > >> >>> > >> >>> > >> >> > >> > _______________________________________________ > >> > App_rpt-users mailing list > >> > App_rpt-users at ohnosec.org > >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon.hewit at gmail.com Mon Jan 24 17:34:05 2011 From: gordon.hewit at gmail.com (VE3GIH Gordon Hewit) Date: Mon, 24 Jan 2011 12:34:05 -0500 Subject: [App_rpt-users] DTMF passthru Message-ID: <0C011C49804B42A0BF1B3A44BA2B435C@T40> KE2N Ken suggested using the propagate_dtmf command in the rpt.conf file, as a way to propagate DTMF signals to other nodes. I need this capacity to allow our members access to the local phone patch. However with all nodes set to duplex=2 (full duplex) and propagate_dtmf=yes, I'm still not getting DTMF on the other local repeaters. The asterisk console sees the DTMF, but Asterisk isn't passing the digits onwards. Does anyone have a suggestion about what else I can try? VE3GIH Gord ______________________________________________ Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) From: Ken To: n3fe at repeater.net, telesistant at hotmail.com, app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] DTMF Allow Cory I think there is a setting for this propagate_dtmf= see http://209.159.155.200/drupal/node/134 GL Ken KE2N Gordon Hewit 289-800-1473 (home) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kt9ac at ameritech.net Mon Jan 24 17:41:33 2011 From: kt9ac at ameritech.net (Tony) Date: Mon, 24 Jan 2011 11:41:33 -0600 Subject: [App_rpt-users] DTMF passthru In-Reply-To: <0C011C49804B42A0BF1B3A44BA2B435C@T40> References: <0C011C49804B42A0BF1B3A44BA2B435C@T40> Message-ID: <4D3DB9CD.9070309@ameritech.net> From what I've read...I think the codes you are trying to pass must be different than the starting character (i.e. *), since once Allstar sees a sequence it will mute everything past that. Tony On 01/24/2011 11:34 AM, VE3GIH Gordon Hewit wrote: > KE2N Ken suggested using the propagate_dtmf command in the rpt.conf > file, as a way to propagate DTMF signals to other nodes. I need this > capacity to allow our members access to the local phone patch. > However with all nodes set to duplex=2 (full duplex) and > propagate_dtmf=yes, I'm still not getting DTMF on the other local > repeaters. The asterisk console sees the DTMF, but Asterisk isn't > passing the digits onwards. > Does anyone have a suggestion about what else I can try? > VE3GIH Gord > ______________________________________________ > Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) > From: Ken > > To: n3fe at repeater.net , > telesistant at hotmail.com , > app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] DTMF Allow > > Cory > > I think there is a setting for this > > propagate_dtmf= see http://209.159.155.200/drupal/node/134 > > GL > Ken > KE2N > > > > > Gordon Hewit > 289-800-1473 (home) > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From n3fe at repeater.net Mon Jan 24 17:56:05 2011 From: n3fe at repeater.net (Corey Dean N3FE) Date: Mon, 24 Jan 2011 12:56:05 -0500 Subject: [App_rpt-users] DTMF passthru In-Reply-To: <0C011C49804B42A0BF1B3A44BA2B435C@T40> References: <0C011C49804B42A0BF1B3A44BA2B435C@T40> Message-ID: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D6E41@exchange.mail.repeater.net> I am actually wanting things just a little different. Until I can get internet to each site so I can get asterisk there I would like to use a command that I could enter and anything following it would generate the DTMF. Here is my current scenario... I use one of my UHF machines as the hub (for now) and I have different machines that listen to the hub. At times other repeaters will connect in as well. DTMF muting is enabled on the local repeater but DTMF is NOT muted on the link side that goes to the hub. This way I can control the repeaters through the links if I need to until I can get some type of ip network setup. Say a cop command is created for this and I make 932 my dtmf for that cop command and I was to issue 1234 to turn on something at a remote site, I would like to enter *9321234 and have the controller either pass or regenerate the 1234. I hope this makes sense. I know a couple of groups that would like to do this as well and that is the only reason they haven't moved over to app_rpt. They have seen how powerful it is! One of the systems has 15 repeaters in it and the only way they would be able to do something would be a piece at a time. That is why this would be so handy!!!! Corey N3FE From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of VE3GIH Gordon Hewit Sent: Monday, January 24, 2011 12:34 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] DTMF passthru KE2N Ken suggested using the propagate_dtmf command in the rpt.conf file, as a way to propagate DTMF signals to other nodes. I need this capacity to allow our members access to the local phone patch. However with all nodes set to duplex=2 (full duplex) and propagate_dtmf=yes, I'm still not getting DTMF on the other local repeaters. The asterisk console sees the DTMF, but Asterisk isn't passing the digits onwards. Does anyone have a suggestion about what else I can try? VE3GIH Gord ______________________________________________ Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) From: Ken > To: n3fe at repeater.net, telesistant at hotmail.com, app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] DTMF Allow Cory I think there is a setting for this propagate_dtmf= see MailScanner warning: numerical links are often malicious: http://209.159.155.200/drupal/node/134 GL Ken KE2N Gordon Hewit 289-800-1473 (home) -- This message was scanned and is believed to be clean. Click here to report this message as spam.<%0d%0ahttp:/simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=523192F61F.A8CE3%0d%0a> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Mon Jan 24 21:17:14 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Mon, 24 Jan 2011 13:17:14 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: <4D3DA206.70003@bdboyle.com> References: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> <4D3DA206.70003@bdboyle.com> Message-ID: <6EFE1BE3-528E-48C8-A53E-C430054C7560@me.com> Agreed, it would be good if there was a way to set this interval. -- Tim :wq On Jan 24, 2011, at 8:00 AM, Bryan D. Boyle wrote: > Also...is there any variable possible to set to cut down the reporting interval? For a stationary system...like a repeater...every 30 seconds seems a bit much From kt9ac at ameritech.net Mon Jan 24 21:42:59 2011 From: kt9ac at ameritech.net (Tony) Date: Mon, 24 Jan 2011 15:42:59 -0600 Subject: [App_rpt-users] DTMF passthru In-Reply-To: <4BCC91CBCFD66C4489B4BD3233140C3E3D879D6E41@exchange.mail.repeater.net> References: <0C011C49804B42A0BF1B3A44BA2B435C@T40> <4BCC91CBCFD66C4489B4BD3233140C3E3D879D6E41@exchange.mail.repeater.net> Message-ID: <4D3DF263.6010304@ameritech.net> I replied to Cory privately but wanted to share a thought and some successes I have with the group. Jim graciously added MDC1200 support to Asterisk/Allstar last summer. I have been using MDC1200 as my primary method of control since. It does not mute like DTMF does and therefore could be used for control purposes. Some reasons: 1) MDC is a fixed-length data packet transmitted within 175mS, has built-in error correction and will ignore the packet if the correct number of bits are not received (checksum). DTMF is subject to partial command interpretation during signal drops. 2) MDC is equally as insecure as DTMF. It is a little harder to recreate by a jammer and can mask the real command digits. 3) While mobile, I have my radio programmed with different MDC systems (ID's). Changing modes or channels and keying up is enough to send the command over to the repeater. Contrast this to holding a mic and pushing numbers while driving, which is very prone to error and takes your eyes off the road. Allstar can both encode and decode MDC, so a suggestion instead of the propagate_dtmf and its current design would be to craft a series of ID codes to be sent between nodes over the air, and have the target side map these to DTMF commands and/or macros. I do just this on my systems. Some radios have a limitation of 8 unique MDC ID's, but Allstar node-to-node should be fine. Example: Radio Mode 1 - MDC ID = 1234. Allstar decodes and maps to DTMF command *32000 (link to node 2000). Radio Mode 2 - MDC ID = 1235. Allstar decodes and maps to DTMF command *12000 (disconnect node 2000). Radio Mode 3 - MDC ID = 1236. Allstar decodes and maps to DTMF command *987 (disconnect ALL nodes). [mdcmacro] I1234 = *32000 I1235 = *12000 I1236 = *987 I would be glad to help out with how this could work, or do some testing if asked. You'll need to copy the mdc1200.h and .c files from the extras directory and uncomment the #include files within app_rpt.c to get it to compile in. Tony On 01/24/2011 11:56 AM, Corey Dean N3FE wrote: > > I am actually wanting things just a little different. Until I can get > internet to each site so I can get asterisk there I would like to use > a command that I could enter and anything following it would generate > the DTMF. > > Here is my current scenario... I use one of my UHF machines as the > hub (for now) and I have different machines that listen to the hub. > At times other repeaters will connect in as well. DTMF muting is > enabled on the local repeater but DTMF is NOT muted on the link side > that goes to the hub. This way I can control the repeaters through > the links if I need to until I can get some type of ip network setup. > > Say a cop command is created for this and I make 932 my dtmf for that > cop command and I was to issue 1234 to turn on something at a remote > site, I would like to enter *9321234 and have the controller either > pass or regenerate the 1234. > > I hope this makes sense. I know a couple of groups that would like to > do this as well and that is the only reason they haven't moved over to > app_rpt. They have seen how powerful it is! One of the systems has > 15 repeaters in it and the only way they would be able to do something > would be a piece at a time. That is why this would be so handy!!!! > > Corey N3FE > > *From:*app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] *On Behalf Of *VE3GIH > Gordon Hewit > *Sent:* Monday, January 24, 2011 12:34 PM > *To:* app_rpt-users at ohnosec.org > *Subject:* [App_rpt-users] DTMF passthru > > KE2N Ken suggested using the propagate_dtmf command in the rpt.conf > file, as a way to propagate DTMF signals to other nodes. I need this > capacity to allow our members access to the local phone patch. > However with all nodes set to duplex=2 (full duplex) and > propagate_dtmf=yes, I'm still not getting DTMF on the other local > repeaters. The asterisk console sees the DTMF, but Asterisk isn't > passing the digits onwards. > > Does anyone have a suggestion about what else I can try? > > VE3GIH Gord > > ______________________________________________ > > Date: Sat, 22 Jan 2011 09:42:49 -0500 (EST) > From: Ken > > To: n3fe at repeater.net , > telesistant at hotmail.com , > app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] DTMF Allow > > Cory > > I think there is a setting for this > > propagate_dtmf= see *MailScanner warning: numerical links are > often malicious:* http://209.159.155.200/drupal/node/134 > > GL > Ken > KE2N > > > > Gordon Hewit > 289-800-1473 (home) > > > -- > This message was scanned and is believed to be clean. > Click here to report this message as spam. > <%0d%0ahttp:/simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=523192F61F.A8CE3%0d%0a> > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From gary.k7ek at gmail.com Mon Jan 24 22:52:08 2011 From: gary.k7ek at gmail.com (Gary - K7EK) Date: Mon, 24 Jan 2011 14:52:08 -0800 Subject: [App_rpt-users] aprs password for app_gps In-Reply-To: References: <45a3627d1c2005c950802682945fd88f.squirrel@www.yo3iiu.ro> <4e1d868275d97309409a5a8b3b780046.squirrel@www.yo3iiu.ro> Message-ID: Ladies & Gentlemen... The simplest solution to get individual APR passcodes is to use the APRSPASS program that's installed with APRSD. There's nothing mysterious or secret about acquiring APRS passcodes. Here's a cut and paste about APRSPASS: --- APRS passcode calculator (new in 2.1.1)The aprspass program is located in the /home/aprsd2 directory. You may move it to another more convienient location if you wish. To determine the aprs passcode required for a callsign "N0CALL": Change to the /home/aprsd2 directory. ./aprspass N0CALL APRS passcode for N0CALL = 12345 --- I've used APRSPASS to generate passwords for several programs, including UIVIEW32, javAPRS, APRSD, Xastir, etc. I hope this is what you were looking for, and has helped to solve your problems. -- Best regards, Gary E. Kohtala - K7EK / AFF0WA / AFA0IU / AFE0DM Personal Web Page: www dot k7ek dot net -- On Mon, Jan 24, 2011 at 8:57 AM, Jim Duuuude wrote: > could you send me a tarball of your entire /etc/asterisk directory, so that > I may duplicate > the problem here? > > Thanks > > JIM > > > ------------------------------ > From: rpt2 at chuck.midlandsnetworking.com > Date: Mon, 24 Jan 2011 09:32:41 -0600 > > Subject: Re: [App_rpt-users] aprs password for app_gps > To: app_rpt-users at ohnosec.org > CC: telesistant at hotmail.com > > > *Since adding the gps.conf, which is working and puts me on the aprs maps, > I started getting the following messages on the console..*. > [Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > > *I then enabled debugging in the gps.conf file and this is what I got...* > [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: > 4030.48N, long: 08859.28W, elev: 123.4M > [Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user > wb9uus-r pass 18598 vers "Asterisk app_gps" > [Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: > wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 > [Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, > long: 08859.28W, elev: 123.4M > [Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, > long: 08859.28W, elev: 123.4M > [Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, > long: 08859.28W, elev: 123.4M > [Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user > wb9uus-r pass 18598 vers "Asterisk app_gps" > [Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: > wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468 > [Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, > long: 08859.28W, elev: 123.4M > [Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select > failed: Interrupted system call > > *I suspect that it is expecting a radio to be connected for it to send > packets out over the air. * > *How do I configure this so it can work or, if that isn't what it is > about, then how do I get rid of the warning?* > > Chuck Henderson, WB9UUS > > > On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude wrote: > > it was!! :-) > > > Date: Mon, 24 Jan 2011 00:27:16 +0200 > > Subject: RE: [App_rpt-users] aprs password for app_gps > > From: yo3iiu at yo3iiu.ro > > To: telesistant at hotmail.com > > CC: yo3iiu at yo3iiu.ro; rpt2 at chuck.midlandsnetworking.com; > app_rpt-users at ohnosec.org > > > > > The protocol is quite simple and the source for callpass is included in > > the xastir source. Though, reverse engineering it seems a lot more fun :) > > > > Regards, > > Bogdan - YO3IIU > > > > > > > > The heck with all this confusion regarding APRS passwords!! > > > > > > I just reverse engineered the password algorithm and will make > > > a password generator (and will also automatically generate a password > > > for Portal-generate configurations). > > > > > > JIM > > > > > >> Date: Sun, 23 Jan 2011 15:49:55 +0200 > > >> From: yo3iiu at yo3iiu.ro > > >> To: rpt2 at chuck.midlandsnetworking.com > > >> CC: app_rpt-users at ohnosec.org > > >> Subject: Re: [App_rpt-users] aprs password for app_gps > > >> > > >> The APRS-IS password could be generated using the callpass utility > that > > >> comes with xastir. > > >> > > >> Bogdan - YO3IIU > > >> > > >> > I would like to set up my allstarlink system to report position > > >> > information > > >> > to the aprs system. > > >> > > > >> > Can someone tell me how to set up this password? Also, are the > > >> default > > >> > server and port listed in the example below what should be used? > > >> > I have searched the aprs site and couldn't find who to request this > > >> > information from. > > >> > > > >> > Chuck Henderson, WB9UUS > > >> > > > >> > > > >> >> > > >> >> ; Configuration for app_gps > > >> >> ; > > >> >> [general] > > >> >> > > >> >> call = wb9uus-2 ; callsign (including SSID) for APRS > > >> purposes*password > > >> >> = 12345 ; Password for APRS-IS server for above callsign* > > >> >> comment = AllStar Node 27468 ; Text to be displayed associated with > > >> this > > >> >> station*server = second.aprs.net ; APRS-IS server to report > > >> information > > >> >> to**port = 10151 ; port on server to send data* > > >> >> icon = r ; A CAR (default) Icon do be displayed for station on > > >> APRS > > >> >> display (see below) > > >> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this > > >> only > > >> >> if using GPS receiver) > > >> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if > > >> >> using GPS receiver) > > >> >> ;debug = y ; set this for debug output > > >> >> freq=442.700 ; Display Frequency of station > > >> >> tone=107.2 ; CTCSS tone of station (0.0 for none) > > >> >> lat=40.508 ; Fixed (default) latitude in decimal degrees > > >> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees > > >> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT) > > >> >> power=9 ; Power level (see below) > > >> >> height=5 ; Antenna Height in HAAT (see below) > > >> >> gain=8 ; Antenna Gain (see below) > > >> >> dir=0 ; Antenna Direction (see below) > > >> >> > > >> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > >> >> wrote: > > >> >> > > >> >>> There have (obviously) been some changes/improvements made to the > > >> >>> Echolink and APRS/GPS subsystems within app_rpt. > > >> >>> > > >> >>> Included in these is the ability for a node to report its "fixed" > > >> GPS > > >> >>> coordinates > > >> >>> to the APRS network, even if it does not have a GPS receiver > > >> connected. > > >> >>> > > >> >>> Please see the following: > > >> >>> > > >> >>> Setting up Echolink Connectivity > > >> >>> http://209.159.155.200/drupal/node/56 > > >> >>> > > >> >>> Setting Up APRS and GPS Configuration > > >> >>> http://209.159.155.200/drupal/node/179 > > >> >>> > > >> >>> Of course, the latest copies of app_gps and chan_echolink need to > be > > >> >>> downloaded from the SVN. > > >> >>> > > >> >>> JIM WB6NIL > > >> >>> > > >> >>> > > >> >>> > > >> >> > > >> > _______________________________________________ > > >> > App_rpt-users mailing list > > >> > App_rpt-users at ohnosec.org > > >> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > >> > > > >> > > >> > > >> _______________________________________________ > > >> App_rpt-users mailing list > > >> App_rpt-users at ohnosec.org > > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Tue Jan 25 05:02:27 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Mon, 24 Jan 2011 23:02:27 -0600 Subject: [App_rpt-users] manually issue COP command? Message-ID: <00cd01cbbc4d$104126c0$d502a8c0@main> Hello, I'm wondering if there is a way to manually issue a COP command? I've tried to issue it from the CLI> prompt, but so far no luck.. I have been working on my DTMF commands, and after the below commands didn't work, I wanted to check the syntax.. Is it possible, or do I have to assign a DTMF in rpt.conf, restart Asterisk, and retry? 1234 = cop,61,PP4=1 ; Turn on pp4 Thanks. 73, Kyle K0KN -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Tue Jan 25 05:08:11 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Mon, 24 Jan 2011 23:08:11 -0600 Subject: [App_rpt-users] Fan Script Message-ID: <00d401cbbc4d$ddb436b0$d502a8c0@main> Hello, I have another question for the group... I'm curious if it will be possible for me to write a script to control a fan for my transmitter to operate under app_rpt? I'm using my homebrew IRLP-compatible board for PTT and COS, and have managed to configure usbradio.conf to key the AUX1 port (pp3) along with the PTT using: pp3 = ptt I was considering building a hardware control circuit using a 555 timer, but thought I'd look into a software approach if possible. I used a similar script under IRLP/EchoIRLP by Robert Pectol, and it worked very well. Thanks. 73 Kyle K0KN -------------- next part -------------- An HTML attachment was scrubbed... URL: From n9udo at yellowthunder.org Tue Jan 25 13:44:39 2011 From: n9udo at yellowthunder.org (Steve Schulze) Date: Tue, 25 Jan 2011 07:44:39 -0600 Subject: [App_rpt-users] URI PTT Delay Message-ID: <4D3ED3C7.2060509@yellowthunder.org> Anyone experiencing PTT delays with DMK's URI? I have seen many instances of where Asterisk is sending voice to the URI (announcements, etc...), but the PTT is not engaged, nor is the TX LED lit. Anyone have any insight? Thanks! -- Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html From tim.sawyer at me.com Tue Jan 25 16:08:46 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Tue, 25 Jan 2011 08:08:46 -0800 Subject: [App_rpt-users] manually issue COP command? In-Reply-To: <00cd01cbbc4d$104126c0$d502a8c0@main> References: <00cd01cbbc4d$104126c0$d502a8c0@main> Message-ID: <3AAD94BF-8FB0-4A8F-8981-9F1A4A4875F0@me.com> You do not have to assign a dtmf. Example: CLI> rpt cmd 2535 cop 1 0 The above command is a warm boot. 2535 is my node number. Notice the trailing 0 is needed to satisfy the command interpreter but has no meaning. Asterisk has command line help. Type "rpt cmd" and press enter will show options. -- Tim :wq On Jan 24, 2011, at 9:02 PM, K&R Yoksh wrote: > > Hello, > > I'm wondering if there is a way to manually issue a COP command? I've tried to issue it from the CLI> prompt, but so far no luck.. > > I have been working on my DTMF commands, and after the below commands didn't work, I wanted to check the syntax.. Is it possible, or do I have to assign a DTMF in rpt.conf, restart Asterisk, and retry? > > 1234 = cop,61,PP4=1 ; Turn on pp4 > Thanks. 73, > > Kyle > K0KN > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Tue Jan 25 18:35:15 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Tue, 25 Jan 2011 12:35:15 -0600 Subject: [App_rpt-users] manually issue cop command? Message-ID: <005501cbbcbe$9c54ea90$d502a8c0@main> Hi Tim,Thanks for the reply.. I've been playing around at the CLI prompt, and can get functions such as this to work:rpt cmd 2211 cop 4 0However, I still can't seem to control my parallel port I/O pins. I've followed all of the advice onhttp://ohnosec.org/drupal/node/177Any suggestions?Thanks.. 73KyleK0KN --- Original Message ---You do not have to assign a dtmf. Example: CLI> rpt cmd 2535 cop 1 0 The above command is a warm boot. 2535 is my node number. Notice the trailing 0 is needed to satisfy the command interpreter but has no meaning. Asterisk has command line help. Type "rpt cmd" and press enter will show options. -- Tim :wq -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Tue Jan 25 19:29:23 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Tue, 25 Jan 2011 11:29:23 -0800 Subject: [App_rpt-users] manually issue cop command? In-Reply-To: <005501cbbcbe$9c54ea90$d502a8c0@main> References: <005501cbbcbe$9c54ea90$d502a8c0@main> Message-ID: <938B14F2-C531-4412-B0E1-AE7ADBEFE826@me.com> I've not played with this but my guess is... You in usbradio.conf you should put this in the [usb] stanza: pp2=out0 ; set parallel port pin 2 to low output. Then this should change it to high: CLI>rpt cmd 2211 cop 61 pp2=1 Jim or others please jump in here if I have it wrong. -- Tim :wq On Jan 25, 2011, at 10:35 AM, K&R Yoksh wrote: > Hi Tim, > Thanks for the reply.. I've been playing around at the CLI prompt, and can get functions such as this to work: > rpt cmd 2211 cop 4 0 > However, I still can't seem to control my parallel port I/O pins. I've followed all of the advice on > http://ohnosec.org/drupal/node/177 > Any suggestions? > Thanks.. 73 > Kyle > K0KN > > --- Original Message --- > You do not have to assign a dtmf. > > Example: > CLI> rpt cmd 2535 cop 1 0 > > The above command is a warm boot. 2535 is my node number. Notice the trailing 0 is needed to satisfy the command interpreter but has no meaning. > > Asterisk has command line help. Type "rpt cmd" and press enter will show options. > > -- > Tim > :wq > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From monty at ke7jvx.com Tue Jan 25 19:30:46 2011 From: monty at ke7jvx.com (Monty Dana) Date: Tue, 25 Jan 2011 12:30:46 -0700 Subject: [App_rpt-users] Rxnotch Message-ID: I found an old config file for app_rpt at voip-info.org and the rxnotch= caught my eye. Are we still able to use that? Monty -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Tue Jan 25 19:57:28 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Tue, 25 Jan 2011 13:57:28 -0600 Subject: [App_rpt-users] manually issue COP command? Message-ID: <005f01cbbcca$185e25b0$d502a8c0@main> Hi Tim (and the list),Thanks for the reply.. I have these entries in usbradio.conf: pp3 = ptt pp11 = cor ; pp10 = in ; in, cor or ctcss ; pp12 = in ; pins 10,12,13,15 are for DTMF ; pp13 = in ; pp15 = in pp4=out0 ; pins 4,5,6 are AUX 1,2,3, default off pp5=out0 pp6=out0 My PTT and COS via the parallel port work perfectly, but so far, the only success I've had controlling other pins has been by assigning them to PTT. For example, as a test I set: pp3 = ptt pp4 = ptt pp5 = ptt pp6 = ptt This keys all 4 outputs any time PTT is called for. I just wanted to make sure that app_rpt could control those pins.. Besides that, I've had no success trying to use COP 61 or 62 to control my pp4,5,6 I've tried the syntax you suggested: rpt cmd 2211 cop 61 pp4=1 I've also tried every other thing I could think of, including: rpt cmd 2211 cop 61 pp4=1,0 rpt cmd 2211 cop 61 pp4=1.0,0 rpt cmd 2211 cop 62 pp4=32767 73. Kyle K0KN --- Original Message ---I've not played with this but my guess is... You in usbradio.conf you should put this in the [usb] stanza: pp2=out0 ; set parallel port pin 2 to low output. Then this should change it to high: CLI>rpt cmd 2211 cop 61 pp2=1 Jim or others please jump in here if I have it wrong. -- Tim :wq -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Tue Jan 25 22:16:22 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 25 Jan 2011 14:16:22 -0800 Subject: [App_rpt-users] Rxnotch In-Reply-To: References: Message-ID: yes, if you un-comment in the app_rpt.c source file the #include "rpt_notch.h" as follows: /* Un-comment the following to include support for notch filters in the rx audio stream (using Tony Fisher's mknotch (mkfilter) implementation) */ #include "rpt_notch.c" Note the removal of the comments around the #include statement JIM From: monty at ke7jvx.com Date: Tue, 25 Jan 2011 12:30:46 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Rxnotch I found an old config file for app_rpt at voip-info.org and the rxnotch= caught my eye. Are we still able to use that? Monty _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Wed Jan 26 02:45:50 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 25 Jan 2011 18:45:50 -0800 Subject: [App_rpt-users] Happer system with APRS Message-ID: I found and fixed the problem (well, it wasnt really a problem, more of an irritation) that some of you were having while running APRS (the 'interrupted system call' thing). Please re-download app_gps from the SVN and it will fix this. JIM WB6NIL -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Wed Jan 26 04:12:31 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 25 Jan 2011 20:12:31 -0800 Subject: [App_rpt-users] manually issue COP command? In-Reply-To: <005f01cbbcca$185e25b0$d502a8c0@main> References: <005f01cbbcca$185e25b0$d502a8c0@main> Message-ID: How about rpt cmd 2211 cop 61 GPIO4=1 (since that's what would go in the line for a DTMF function) JIM From: yokshs at sbcglobal.net To: app_rpt-users at ohnosec.org Date: Tue, 25 Jan 2011 13:57:28 -0600 Subject: [App_rpt-users] manually issue COP command? Hi Tim (and the list), Thanks for the reply.. I have these entries in usbradio.conf: pp3 = ptt pp11 = cor ; pp10 = in ; in, cor or ctcss ; pp12 = in ; pins 10,12,13,15 are for DTMF ; pp13 = in ; pp15 = in pp4=out0 ; pins 4,5,6 are AUX 1,2,3, default off pp5=out0 pp6=out0 My PTT and COS via the parallel port work perfectly, but so far, the only success I've had controlling other pins has been by assigning them to PTT. For example, as a test I set: pp3 = ptt pp4 = ptt pp5 = ptt pp6 = ptt This keys all 4 outputs any time PTT is called for. I just wanted to make sure that app_rpt could control those pins.. Besides that, I've had no success trying to use COP 61 or 62 to control my pp4,5,6 I've tried the syntax you suggested: rpt cmd 2211 cop 61 pp4=1 I've also tried every other thing I could think of, including: rpt cmd 2211 cop 61 pp4=1,0 rpt cmd 2211 cop 61 pp4=1.0,0 rpt cmd 2211 cop 62 pp4=32767 73. Kyle K0KN --- Original Message ---I've not played with this but my guess is... You in usbradio.conf you should put this in the [usb] stanza: pp2=out0 ; set parallel port pin 2 to low output. Then this should change it to high: CLI>rpt cmd 2211 cop 61 pp2=1 Jim or others please jump in here if I have it wrong. -- Tim :wq _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Wed Jan 26 04:54:12 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 25 Jan 2011 20:54:12 -0800 Subject: [App_rpt-users] manually issue COP command? In-Reply-To: References: <005f01cbbcca$185e25b0$d502a8c0@main>, Message-ID: never mind... that was just a dumb suggestion. I wasnt paying attention fully. sorry From: telesistant at hotmail.com To: yokshs at sbcglobal.net; app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] manually issue COP command? Date: Tue, 25 Jan 2011 20:12:31 -0800 How about rpt cmd 2211 cop 61 GPIO4=1 (since that's what would go in the line for a DTMF function) JIM From: yokshs at sbcglobal.net To: app_rpt-users at ohnosec.org Date: Tue, 25 Jan 2011 13:57:28 -0600 Subject: [App_rpt-users] manually issue COP command? Hi Tim (and the list), Thanks for the reply.. I have these entries in usbradio.conf: pp3 = ptt pp11 = cor ; pp10 = in ; in, cor or ctcss ; pp12 = in ; pins 10,12,13,15 are for DTMF ; pp13 = in ; pp15 = in pp4=out0 ; pins 4,5,6 are AUX 1,2,3, default off pp5=out0 pp6=out0 My PTT and COS via the parallel port work perfectly, but so far, the only success I've had controlling other pins has been by assigning them to PTT. For example, as a test I set: pp3 = ptt pp4 = ptt pp5 = ptt pp6 = ptt This keys all 4 outputs any time PTT is called for. I just wanted to make sure that app_rpt could control those pins.. Besides that, I've had no success trying to use COP 61 or 62 to control my pp4,5,6 I've tried the syntax you suggested: rpt cmd 2211 cop 61 pp4=1 I've also tried every other thing I could think of, including: rpt cmd 2211 cop 61 pp4=1,0 rpt cmd 2211 cop 61 pp4=1.0,0 rpt cmd 2211 cop 62 pp4=32767 73. Kyle K0KN --- Original Message ---I've not played with this but my guess is... You in usbradio.conf you should put this in the [usb] stanza: pp2=out0 ; set parallel port pin 2 to low output. Then this should change it to high: CLI>rpt cmd 2211 cop 61 pp2=1 Jim or others please jump in here if I have it wrong. -- Tim :wq _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Wed Jan 26 13:02:20 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Wed, 26 Jan 2011 05:02:20 -0800 Subject: [App_rpt-users] manually issue COP command? In-Reply-To: <001401cbbd23$e49f47e0$d502a8c0@main> References: <005f01cbbcca$185e25b0$d502a8c0@main>, , <001401cbbd23$e49f47e0$d502a8c0@main> Message-ID: Ok, I have the answer: rpt cmd 2211 cop 61,pp4=1 0 JIM From: yokshs at sbcglobal.net To: telesistant at hotmail.com Subject: Re: [App_rpt-users] manually issue COP command? Date: Wed, 26 Jan 2011 00:40:15 -0600 No problem.. Any idea why I can't get the parallel port outputs to work with a COP? Thanks. 73. Kyle K0KN ----- Original Message ----- From: Jim Duuuude To: yokshs at sbcglobal.net ; app_rpt mailing list Sent: Tuesday, January 25, 2011 10:54 PM Subject: RE: [App_rpt-users] manually issue COP command? never mind... that was just a dumb suggestion. I wasnt paying attention fully. sorry From: telesistant at hotmail.com To: yokshs at sbcglobal.net; app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] manually issue COP command? Date: Tue, 25 Jan 2011 20:12:31 -0800 How about rpt cmd 2211 cop 61 GPIO4=1 (since that's what would go in the line for a DTMF function) JIM From: yokshs at sbcglobal.net To: app_rpt-users at ohnosec.org Date: Tue, 25 Jan 2011 13:57:28 -0600 Subject: [App_rpt-users] manually issue COP command? Hi Tim (and the list), Thanks for the reply.. I have these entries in usbradio.conf: pp3 = ptt pp11 = cor ; pp10 = in ; in, cor or ctcss ; pp12 = in ; pins 10,12,13,15 are for DTMF ; pp13 = in ; pp15 = in pp4=out0 ; pins 4,5,6 are AUX 1,2,3, default off pp5=out0 pp6=out0 My PTT and COS via the parallel port work perfectly, but so far, the only success I've had controlling other pins has been by assigning them to PTT. For example, as a test I set: pp3 = ptt pp4 = ptt pp5 = ptt pp6 = ptt This keys all 4 outputs any time PTT is called for. I just wanted to make sure that app_rpt could control those pins.. Besides that, I've had no success trying to use COP 61 or 62 to control my pp4,5,6 I've tried the syntax you suggested: rpt cmd 2211 cop 61 pp4=1 I've also tried every other thing I could think of, including: rpt cmd 2211 cop 61 pp4=1,0 rpt cmd 2211 cop 61 pp4=1.0,0 rpt cmd 2211 cop 62 pp4=32767 73. Kyle K0KN --- Original Message ---I've not played with this but my guess is... You in usbradio.conf you should put this in the [usb] stanza: pp2=out0 ; set parallel port pin 2 to low output. Then this should change it to high: CLI>rpt cmd 2211 cop 61 pp2=1 Jim or others please jump in here if I have it wrong. -- Tim :wq _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From yokshs at sbcglobal.net Wed Jan 26 15:30:47 2011 From: yokshs at sbcglobal.net (K&R Yoksh) Date: Wed, 26 Jan 2011 09:30:47 -0600 Subject: [App_rpt-users] manually issue COP command? Message-ID: <004a01cbbd6e$01890400$d502a8c0@main> Thanks to Jim, my aux ports are working now! The PP must be uppercase, as in the examples below: rpt cmd 2211 cop 61,PP4=1 0 ; Parallel Port 4 high rpt cmd 2211 cop 61,PP4=0 0 ; Parallel Port 4 low rpt cmd 2211 cop 61,PP5=1 0 ; Parallel Port 5 high rpt cmd 2211 cop 61,PP5=0 0 ; Parallel Port 5 low 73, Kyle K0KN --- Original Message --- Ok, I have the answer: rpt cmd 2211 cop 61,pp4=1 0 JIM -------------- next part -------------- An HTML attachment was scrubbed... URL: From k8khw at att.net Wed Jan 26 22:48:08 2011 From: k8khw at att.net (k8khw at att.net) Date: Wed, 26 Jan 2011 17:48:08 -0500 Subject: [App_rpt-users] WxScript Message-ID: <57553C80F0FC4985A831333E651AE929@joycet> ?Mark, Finally after a fresh install of all the files I have the get scripts running. When I try to play the scripts it acts like its running and goes back to the root prompt and nothing come out the speakers or transmitted over the air. Is there something I need to change in the play script to get it to play. I am using the W0ANM scripts. Brian KB3ORS 27321 Brain I ask the same question a while back and never did get the issue resolved. Actually here everything is working as it should which I bet is the case in your end as well. Here When we call for the script to play the Wx file it plays it fine but is only heard if someone else is talking on the system and has the Node keyed up. When they unkey or stop talking so does the Wx script. I bet if you havn,t fixed it ready try calling the Script and have a on going qso on your system and see if you hear the Wx report ect. if you have it working we would like to know what you did. Randy Node 27372 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon.hewit at gmail.com Thu Jan 27 00:15:17 2011 From: gordon.hewit at gmail.com (VE3GIH Gordon Hewit) Date: Wed, 26 Jan 2011 19:15:17 -0500 Subject: [App_rpt-users] DTMF Passthru Message-ID: <1B59E2199AAE4DE8911B8DE4161F23D9@T40> Thanks to those that responded to my previous request for help passing DTMF between nodes. Apparently, we agree that DTMF tones are not being passed thru Asterisk nodes on the same PC, regardless of the setting of rpt.conf parameter 'propagate_dtmf'. If someone has actually done passed DTMF via Asterisk, I'd appreciate hearing from them VE3GIH Gord Hewit Durham ARES 416-779-3740 mobile 289-800-1473 VoIP www.durhamares.ca website 4167793740 at txt.bell.ca SMS email VE3GIH at winlink.org Emerg. email -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb3ors at windstream.net Thu Jan 27 00:33:45 2011 From: kb3ors at windstream.net (KB3ORS - Brian) Date: Wed, 26 Jan 2011 19:33:45 -0500 Subject: [App_rpt-users] WxScript In-Reply-To: <57553C80F0FC4985A831333E651AE929@joycet> References: <57553C80F0FC4985A831333E651AE929@joycet> Message-ID: <962DB6CA4335469B97B14BC8E2E69371@BrianPC> ?I have the script running and down loading the file. I had to set up a rpt cmd to play the script and change where it saves the audio file. I have already moved the scripts to asterisk. The only thing I have not work out is playwxalertbg which is the script that is supposed to beacon the alert. However asterisk does not use the files of IRLP environment, COS ACTIVE, and PTTSTATE. On this note I was not able to get it to install on centos ACID. I have mine running on XIPAR which is REDHAT. Centos I had trouble getting all the libraries and deps installed. Brian KB3ORS From: k8khw at att.net Sent: Wednesday, January 26, 2011 5:48 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] WxScript ?Mark, Finally after a fresh install of all the files I have the get scripts running. When I try to play the scripts it acts like its running and goes back to the root prompt and nothing come out the speakers or transmitted over the air. Is there something I need to change in the play script to get it to play. I am using the W0ANM scripts. Brian KB3ORS 27321 Brain I ask the same question a while back and never did get the issue resolved. Actually here everything is working as it should which I bet is the case in your end as well. Here When we call for the script to play the Wx file it plays it fine but is only heard if someone else is talking on the system and has the Node keyed up. When they unkey or stop talking so does the Wx script. I bet if you havn,t fixed it ready try calling the Script and have a on going qso on your system and see if you hear the Wx report ect. if you have it working we would like to know what you did. Randy Node 27372 -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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: 10.0.1202 / Virus Database: 1435/3404 - Release Date: 01/26/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Thu Jan 27 00:59:39 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Wed, 26 Jan 2011 16:59:39 -0800 Subject: [App_rpt-users] DTMF Passthru In-Reply-To: <1B59E2199AAE4DE8911B8DE4161F23D9@T40> References: <1B59E2199AAE4DE8911B8DE4161F23D9@T40> Message-ID: What exactly to do you want to do? --- TIS On Jan 26, 2011, at 4:15 PM, VE3GIH Gordon Hewit wrote: Thanks to those that responded to my previous request for help passing DTMF between nodes. Apparently, we agree that DTMF tones are not being passed thru Asterisk nodes on the same PC, regardless of the setting of rpt.conf parameter 'propagate_dtmf'. If someone has actually done passed DTMF via Asterisk, I'd appreciate hearing from them VE3GIH Gord Hewit Durham ARES 416-779-3740 mobile 289-800-1473 VoIP www.durhamares.ca website 4167793740 at txt.bell.ca SMS email VE3GIH at winlink.org Emerg. email _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From k8khw at att.net Thu Jan 27 03:49:48 2011 From: k8khw at att.net (k8khw at att.net) Date: Wed, 26 Jan 2011 22:49:48 -0500 Subject: [App_rpt-users] Wx Script Message-ID: I have found using the WOANM wx Script plays on Asterisk Node using Playback just fine. His script now uses wavplay which wont key the Radio ect to play the files. Anyone know what I could to to get playback to be called to play the wx files instead of wavplay Randy -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at me.com Thu Jan 27 04:01:42 2011 From: tim.sawyer at me.com (Tim Sawyer) Date: Wed, 26 Jan 2011 20:01:42 -0800 Subject: [App_rpt-users] Wx Script In-Reply-To: References: Message-ID: I do newsline this way, may work for your wx files too. 91=localplay,/tmp/news ; play newsline 90=cop,24 ; flush telemetry including newsline -- Tim :wq On Jan 26, 2011, at 7:49 PM, k8khw at att.net wrote: > I have found using the WOANM wx Script plays on Asterisk Node using Playback > just fine. His script now uses wavplay which wont key the Radio ect to play the files. > Anyone know what I could to to get playback to be called to play the wx files instead > of wavplay > > > Randy > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From dshaw at ke6upi.com Thu Jan 27 14:25:04 2011 From: dshaw at ke6upi.com (David KE6UPI) Date: Thu, 27 Jan 2011 06:25:04 -0800 Subject: [App_rpt-users] Wx Script In-Reply-To: References: Message-ID: You might ry the auto dialer. http://www.voip-info.org/wiki/view/Asterisk+auto-dial+out I Haven't tried it with RPT. David On Wed, Jan 26, 2011 at 8:01 PM, Tim Sawyer wrote: > I do newsline this way, may work for your wx files too. > > 91=localplay,/tmp/news ; play newsline > 90=cop,24 ; flush telemetry including newsline > -- > Tim > :wq > > On Jan 26, 2011, at 7:49 PM, k8khw at att.net wrote: > > I have found using the WOANM wx Script plays on Asterisk Node using > Playback > just fine. His script now uses wavplay which wont key the Radio ect to play > the files. > Anyone know what I could to to get playback to be called to play the wx > files instead > of wavplay > > > Randy > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kris at kriskirkland.com Thu Jan 27 17:00:21 2011 From: kris at kriskirkland.com (Kris Kirkland) Date: Thu, 27 Jan 2011 11:00:21 -0600 Subject: [App_rpt-users] CTCSS Problem Message-ID: <4D41A4A5.1090306@kriskirkland.com> Howdy First I'd like to start off by saying thanks for such a great piece of software for asterisk, I've been using Asterisk for 6 years now. I'm a network engineer so I'm not a repeater guru by any means, but I'm having a problem with my setup using the URI Model: DMK URI My first problem is; if ctcssfrom is set to anything but dsp, the repeater keys up as soon as asterisk is started. I can even disconnect everything but PTT and Ground and it still keys up as soon as its started. I did this to eliminate the possibility of the device sensing CTCSS via the mic_in_ac. So my understanding was that if I set ctcssfrom=no then it would ignore ctcss, but it still keys up. Is this a bug in the software being that it happens even with everything but ptt/gnd is disconnected? -- ______________________ Kris Kirkland ~ K5KRK ______________________ From kb2ear at kb2ear.net Thu Jan 27 19:20:52 2011 From: kb2ear at kb2ear.net (Scott Weis) Date: Thu, 27 Jan 2011 14:20:52 -0500 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <4D41A4A5.1090306@kriskirkland.com> References: <4D41A4A5.1090306@kriskirkland.com> Message-ID: <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> It most likely means that your COS is active or your using DSP for the squelch and it's too loose. -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Kris Kirkland Sent: Thursday, January 27, 2011 12:00 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] CTCSS Problem Howdy First I'd like to start off by saying thanks for such a great piece of software for asterisk, I've been using Asterisk for 6 years now. I'm a network engineer so I'm not a repeater guru by any means, but I'm having a problem with my setup using the URI Model: DMK URI My first problem is; if ctcssfrom is set to anything but dsp, the repeater keys up as soon as asterisk is started. I can even disconnect everything but PTT and Ground and it still keys up as soon as its started. I did this to eliminate the possibility of the device sensing CTCSS via the mic_in_ac. So my understanding was that if I set ctcssfrom=no then it would ignore ctcss, but it still keys up. Is this a bug in the software being that it happens even with everything but ptt/gnd is disconnected? -- ______________________ Kris Kirkland ~ K5KRK ______________________ _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users From kt9ac at ameritech.net Thu Jan 27 19:35:12 2011 From: kt9ac at ameritech.net (Tony) Date: Thu, 27 Jan 2011 13:35:12 -0600 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> References: <4D41A4A5.1090306@kriskirkland.com> <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> Message-ID: <4D41C8F0.8050600@ameritech.net> I agree with the squelch mention. I had the opposite problem when going to DSP squelch versus USB COR, the rx didn't key at all. Try running "radio tune rxsquelch" to have it self-level. On 01/27/2011 01:20 PM, Scott Weis wrote: > It most likely means that your COS is active or your using DSP for the > squelch and it's too loose. > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Kris Kirkland > Sent: Thursday, January 27, 2011 12:00 PM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] CTCSS Problem > > Howdy > > First I'd like to start off by saying thanks for such a great piece of > software for asterisk, I've been using Asterisk for 6 years now. I'm a > network engineer so I'm not a repeater guru by any means, but I'm having a > problem with my setup using the URI Model: DMK URI My first problem is; if > ctcssfrom is set to anything but dsp, the repeater keys up as soon as > asterisk is started. I can even disconnect everything but PTT and Ground and > it still keys up as soon as its started. I did this to eliminate the > possibility of the device sensing CTCSS via the mic_in_ac. So my > understanding was that if I set ctcssfrom=no then it would ignore ctcss, but > it still keys up. Is this a bug in the software being that it happens even > with everything but ptt/gnd is disconnected? > > -- > ______________________ > > Kris Kirkland ~ K5KRK > ______________________ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From kris at kriskirkland.com Thu Jan 27 19:49:31 2011 From: kris at kriskirkland.com (Kris Kirkland) Date: Thu, 27 Jan 2011 13:49:31 -0600 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <4D41C8F0.8050600@ameritech.net> References: <4D41A4A5.1090306@kriskirkland.com> <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> <4D41C8F0.8050600@ameritech.net> Message-ID: <4D41CC4B.60000@kriskirkland.com> On 1/27/2011 1:35 PM, Tony wrote: > I agree with the squelch mention. I had the opposite problem when > going to DSP squelch versus USB COR, the rx didn't key at all. > > Try running "radio tune rxsquelch" to have it self-level. > > On 01/27/2011 01:20 PM, Scott Weis wrote: >> It most likely means that your COS is active or your using DSP for the >> squelch and it's too loose. >> >> -----Original Message----- >> From: app_rpt-users-bounces at ohnosec.org >> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Kris Kirkland >> Sent: Thursday, January 27, 2011 12:00 PM >> To: app_rpt-users at ohnosec.org >> Subject: [App_rpt-users] CTCSS Problem >> >> Howdy >> >> First I'd like to start off by saying thanks for such a great piece of >> software for asterisk, I've been using Asterisk for 6 years now. I'm a >> network engineer so I'm not a repeater guru by any means, but I'm >> having a >> problem with my setup using the URI Model: DMK URI My first problem >> is; if >> ctcssfrom is set to anything but dsp, the repeater keys up as soon as >> asterisk is started. I can even disconnect everything but PTT and >> Ground and >> it still keys up as soon as its started. I did this to eliminate the >> possibility of the device sensing CTCSS via the mic_in_ac. So my >> understanding was that if I set ctcssfrom=no then it would ignore >> ctcss, but >> it still keys up. Is this a bug in the software being that it happens >> even >> with everything but ptt/gnd is disconnected? >> >> -- >> ______________________ >> >> Kris Kirkland ~ K5KRK >> ______________________ >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users That brings up my next question; When setting the COR to usb and watching the debug you can see "carrierdetect=1" or "carrierdetect=0" is this speaking of the binary on/off or is this saying 1=high 2=low logic. -- ______________________ Kris Kirkland ~ K5KRK ______________________ From kt9ac at ameritech.net Thu Jan 27 19:53:23 2011 From: kt9ac at ameritech.net (Tony) Date: Thu, 27 Jan 2011 13:53:23 -0600 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <4D41CC4B.60000@kriskirkland.com> References: <4D41A4A5.1090306@kriskirkland.com> <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> <4D41C8F0.8050600@ameritech.net> <4D41CC4B.60000@kriskirkland.com> Message-ID: <4D41CD33.2030705@ameritech.net> Carrierdetect=1 or YES; carrierdetect=0 or NO. Its referring to the internal variable state. On 01/27/2011 01:49 PM, Kris Kirkland wrote: > On 1/27/2011 1:35 PM, Tony wrote: >> I agree with the squelch mention. I had the opposite problem when >> going to DSP squelch versus USB COR, the rx didn't key at all. >> >> Try running "radio tune rxsquelch" to have it self-level. >> >> On 01/27/2011 01:20 PM, Scott Weis wrote: >>> It most likely means that your COS is active or your using DSP for the >>> squelch and it's too loose. >>> >>> -----Original Message----- >>> From: app_rpt-users-bounces at ohnosec.org >>> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Kris Kirkland >>> Sent: Thursday, January 27, 2011 12:00 PM >>> To: app_rpt-users at ohnosec.org >>> Subject: [App_rpt-users] CTCSS Problem >>> >>> Howdy >>> >>> First I'd like to start off by saying thanks for such a great piece of >>> software for asterisk, I've been using Asterisk for 6 years now. I'm a >>> network engineer so I'm not a repeater guru by any means, but I'm >>> having a >>> problem with my setup using the URI Model: DMK URI My first problem >>> is; if >>> ctcssfrom is set to anything but dsp, the repeater keys up as soon as >>> asterisk is started. I can even disconnect everything but PTT and >>> Ground and >>> it still keys up as soon as its started. I did this to eliminate the >>> possibility of the device sensing CTCSS via the mic_in_ac. So my >>> understanding was that if I set ctcssfrom=no then it would ignore >>> ctcss, but >>> it still keys up. Is this a bug in the software being that it happens >>> even >>> with everything but ptt/gnd is disconnected? >>> >>> -- >>> ______________________ >>> >>> Kris Kirkland ~ K5KRK >>> ______________________ >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > That brings up my next question; When setting the COR to usb and > watching the debug you can see "carrierdetect=1" or "carrierdetect=0" is > this speaking of the binary on/off or is this saying 1=high 2=low logic. > From kris at kriskirkland.com Thu Jan 27 20:37:55 2011 From: kris at kriskirkland.com (Kris Kirkland) Date: Thu, 27 Jan 2011 14:37:55 -0600 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <4D41CD33.2030705@ameritech.net> References: <4D41A4A5.1090306@kriskirkland.com> <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> <4D41C8F0.8050600@ameritech.net> <4D41CC4B.60000@kriskirkland.com> <4D41CD33.2030705@ameritech.net> Message-ID: <4D41D7A3.2060609@kriskirkland.com> So if I set ctcssfrom=no will it disable ctcss checking all together and repeat based on COR? If I can disable CTCSS then I can narrow my problem down a little further. -- ______________________ Kris Kirkland ~ K5KRK ______________________ From kt9ac at ameritech.net Thu Jan 27 21:52:05 2011 From: kt9ac at ameritech.net (=?utf-8?B?VG9ueSBLVDlBQw==?=) Date: Thu, 27 Jan 2011 15:52:05 -0600 Subject: [App_rpt-users] =?utf-8?q?CTCSS_Problem?= Message-ID: <303123.50245.qm@smtp106.sbc.mail.gq1.yahoo.com> I believe that's what the documentation or even within the usbradio.conf file says. Ctcssfrom=no; system will be carrier access ----- Reply message ----- From: "Kris Kirkland" Date: Thu, Jan 27, 2011 2:37 pm Subject: [App_rpt-users] CTCSS Problem To: So if I set ctcssfrom=no will it disable ctcss checking all together and repeat based on COR? If I can disable CTCSS then I can narrow my problem down a little further. -- ______________________ Kris Kirkland ~ K5KRK ______________________ _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From kris at kriskirkland.com Fri Jan 28 03:32:58 2011 From: kris at kriskirkland.com (Kris Kirkland) Date: Thu, 27 Jan 2011 21:32:58 -0600 Subject: [App_rpt-users] CTCSS Problem In-Reply-To: <4D41D7A3.2060609@kriskirkland.com> References: <4D41A4A5.1090306@kriskirkland.com> <024601cbbe57$4fedd550$efc97ff0$@kb2ear.net> <4D41C8F0.8050600@ameritech.net> <4D41CC4B.60000@kriskirkland.com> <4D41CD33.2030705@ameritech.net> <4D41D7A3.2060609@kriskirkland.com> Message-ID: <4D4238EA.9050104@kriskirkland.com> I found that carrierfrom=usbinvert will sense the correct cor, but if I try turn ctcss off it starts keyed. After a couple restarts of asterisk the repeater will work once. These are the logs I have found. [Jan 27 21:21:16] WARNING[2225] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Jan 27 21:21:17] WARNING[2224] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Jan 27 21:21:17] WARNING[2224] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. Even when it works it will not send audio. Also when I try radio tune it will run through its tuning but not matter what tune command i run it always ends with adjust failed. Example radio tune rxnoise tune rxnoise maxtries=12, target=27000, tolerance=2750 tries=0, setting=2, meas=1 tries=1, setting=16, meas=1 tries=2, setting=16, meas=1 tries=3, setting=16, meas=1 tries=4, setting=16, meas=1 tries=5, setting=16, meas=1 tries=6, setting=16, meas=1 tries=7, setting=16, meas=1 tries=8, setting=16, meas=1 tries=9, setting=16, meas=1 tries=10, setting=16, meas=1 tries=11, setting=16, meas=1 DONE tries=12, setting=1000, meas=1, sqnoise=0 ERROR: RX INPUT ADJUST FAILED. Again I've disconnected everything buy cor/ptt/gnd and it will still starts keyed with ctcssfrom=no. -- Kris Kirkland ~ K5KRK Network Engineer From kt9ac at ameritech.net Fri Jan 28 04:08:37 2011 From: kt9ac at ameritech.net (Tony KT9AC) Date: Thu, 27 Jan 2011 22:08:37 -0600 Subject: [App_rpt-users] Nodes no longer in database Message-ID: <4D424145.6080800@ameritech.net> I'm playing around with my test system at home, and noticed that on the Allstar Link Network - Node list my three nodes are "no longer in the database" yet show up as green on the page. Some other nodes picked at random show up fine, and I did migrate them back when the new Portal first came out (removed the "A" from the registration section). I can connect to Jim's node 2000 just fine so I think all is working. Nodes 27129, 27418 and 27460 are mine. Thanks, Tony From g4rky at yahoo.co.uk Sat Jan 29 11:54:41 2011 From: g4rky at yahoo.co.uk (Matt Beasant) Date: Sat, 29 Jan 2011 11:54:41 +0000 Subject: [App_rpt-users] Messages log file question Message-ID: Hi, Is there any way that I can stop the Indian hackers who are constantly trying to find a valid extension / password combination on my SIP gateway into the repeaters? They're using up a bunch of my capped internet bandiwdth and making 10 days worth of messages log over 24Mb! If not, is there a way to stop such attempts filing the messages log with megs and megs of this stuff? Thanks Matt G4RKY -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sat Jan 29 16:23:48 2011 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 29 Jan 2011 08:23:48 -0800 Subject: [App_rpt-users] Messages log file question In-Reply-To: References: Message-ID: just change your default sip port to something unusual (not 5060) Date: Sat, 29 Jan 2011 11:54:41 +0000 From: g4rky at yahoo.co.uk To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Messages log file question Hi, Is there any way that I can stop the Indian hackers who are constantly trying to find a valid extension / password combination on my SIP gateway into the repeaters? They're using up a bunch of my capped internet bandiwdth and making 10 days worth of messages log over 24Mb! If not, is there a way to stop such attempts filing the messages log with megs and megs of this stuff? Thanks MattG4RKY _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From kc2wdz at gmail.com Sun Jan 30 03:19:40 2011 From: kc2wdz at gmail.com (KC2WDZ) Date: Sat, 29 Jan 2011 22:19:40 -0500 Subject: [App_rpt-users] Scheduling audio messages Message-ID: How would you schedule an audio message file to play every hour or so? As it seems, tailmessage wont work for me because I'm running a simplex node with no tones or hangtimes (duplex=0 in rpt.conf). -------------- next part -------------- An HTML attachment was scrubbed... URL: From kt9ac at ameritech.net Sun Jan 30 03:45:47 2011 From: kt9ac at ameritech.net (Tony KT9AC) Date: Sat, 29 Jan 2011 21:45:47 -0600 Subject: [App_rpt-users] Nodes no longer in database - solved In-Reply-To: <4D424145.6080800@ameritech.net> References: <4D424145.6080800@ameritech.net> Message-ID: <4D44DEEB.6030008@ameritech.net> Fixed it. Was missing the status_update lines in rpt.conf. I took them out for my production site that doesn't have internet, that I copied to the test system here at home. On 01/27/2011 10:08 PM, Tony KT9AC wrote: > I'm playing around with my test system at home, and noticed that on > the Allstar Link Network - Node list my three nodes are "no longer in > the database" yet show up as green on the page. > > Some other nodes picked at random show up fine, and I did migrate them > back when the new Portal first came out (removed the "A" from the > registration section). I can connect to Jim's node 2000 just fine so I > think all is working. > > Nodes 27129, 27418 and 27460 are mine. > > Thanks, > Tony > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > From ki6psp at gmail.com Sun Jan 30 17:34:21 2011 From: ki6psp at gmail.com (KI6PSP (Ed)) Date: Sun, 30 Jan 2011 09:34:21 -0800 Subject: [App_rpt-users] Scheduling audio messages Message-ID: Use something like this, and it will play a file every hour like you are wanting. [schedule] 10= 00 * * * * [functions] 910=playback,rpt/510 [macro] 10=*910# ;Information -- KI6PSP (Ed) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb5nfc at yahoo.com Mon Jan 31 01:47:18 2011 From: wb5nfc at yahoo.com (John (WB5NFC)) Date: Sun, 30 Jan 2011 17:47:18 -0800 (PST) Subject: [App_rpt-users] Quad Radio PCI Board Configuration Help Message-ID: <23872.91265.qm@web113517.mail.gq1.yahoo.com> I recently purchased a used Quad PCI board and find I need some help with configuration, especially with zaptel.conf and zapata.conf. I've read the setup instructions and sample files, but I'm still confused. Desired outcome is to configure all four channels as follows: Channels: 1 - Allstar node 2186 PL 100 Hz TX & RX Non-inverted COR 2 - Allstar node 2293 PL 100 Hz TX & RX Non-inverted COR 3 - Private Link Node (1000) DCS 365 (normal) Inverted COR 4 - Remote base IC-706 To be determined... (next on the project list) Example configs, suggestions and/or guidance greatly appreciated. John / WB5NFC -------------- next part -------------- An HTML attachment was scrubbed... URL: From hwstar at rodgers.sdcoxmail.com Mon Jan 31 02:40:47 2011 From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers) Date: Sun, 30 Jan 2011 18:40:47 -0800 Subject: [App_rpt-users] Quad Radio PCI Board Configuration Help In-Reply-To: <23872.91265.qm@web113517.mail.gq1.yahoo.com> References: <23872.91265.qm@web113517.mail.gq1.yahoo.com> Message-ID: <4D46212F.10701@rodgers.sdcoxmail.com> On 01/30/2011 05:47 PM, John (WB5NFC) wrote: > I recently purchased a used Quad PCI board and find I need some help with > configuration, especially with zaptel.conf and zapata.conf. I've read the setup > instructions and sample files, but I'm still confused. Desired outcome is to > configure all four channels as follows: > > > > Channels: > 1 - Allstar node 2186 > PL 100 Hz TX & RX > Non-inverted COR > 2 - Allstar node 2293 > PL 100 Hz TX & RX > Non-inverted COR > 3 - Private Link Node (1000) > DCS 365 (normal) > Inverted COR > 4 - Remote base IC-706 > To be determined... (next on the project list) > > Example configs, suggestions and/or guidance greatly appreciated. > > John / WB5NFC > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users There are example files /usr/src/astsrc/configs/pciradio. The files in this directory need to be placed in /etc/asterisk with the exception of zaptel.conf which goes in the /etc directory. These 4 files will get channel 1 working in carrier squelch mode. Once you have that working then you can try turning on ctcss encode and decode as well as changing the tone frequencies by editing zaptel.conf. Just a side note: The radio's CTCSS decoder may be better performer than the MX-828 chip used on the pciradio card. Once all that is working, then you can increase the channel count and configure other channels. Re-read the zaptel.conf, and zapata.conf and extensions.conf files. Steve WA6ZFT