- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Echolink Link Status
by K&R Yoksh 21 Jan '11

21 Jan '11

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. >

1 0

re updating nodes
by Jon Rorke 18 Jan '11

18 Jan '11

What is the preferred method of updating nodes these days? I think the process was changed recently. Thanks, Jon VA3RQ

3 2

Re: [App_rpt-users] Half Duplex works fine, Kerchunks on Full Duplex......
by KI6PSP (Ed) 18 Jan '11

18 Jan '11

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 <buddy(a)brannan.name> 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(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -- KI6PSP (Ed)

2 1

Half Duplex works fine, Kerchunks on Full Duplex......
by KI6PSP (Ed) 18 Jan '11

18 Jan '11

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)

1 0

Re: [App_rpt-users] I should never be called!
by Ken 17 Jan '11

17 Jan '11

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 <telesistant(a)hotmail.com> To: ke2n(a)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(a)cs.com To: telesistant(a)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@radio-gui:1] Rpt("IAX2/gui-9348", "(27021|X)") in new stack vs Executing [27061@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

1 0

Echolink announcements.
by Scott Weis 17 Jan '11

17 Jan '11

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

5 11

Echolink
by Paul M. Nannery 17 Jan '11

17 Jan '11

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?

1 0

scripts to lockout other connections during an IRLP connection
by Matt Beasant 15 Jan '11

15 Jan '11

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

1 0

double ID fixed
by Jim Duuuude 15 Jan '11

15 Jan '11

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

1 0

Re: [App_rpt-users] Audio gateway issues??
by Tony Langdon, VK3JED 14 Jan '11

14 Jan '11

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

1 0