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

Re: [App_rpt-users] Echolink Link Status
by Jim Duuuude 22 Jan '11

22 Jan '11

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(a)inttek.net > To: telesistant(a)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(a)bdboyle.com > > > > > To: telesistant(a)hotmail.com; app_rpt-users(a)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 > > > > > > > > > > > > > > >

1 0

DTMF Allow
by Corey Dean N3FE 22 Jan '11

22 Jan '11

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

3 2

Re: [App_rpt-users] DTMF decoding
by K&R Yoksh 22 Jan '11

22 Jan '11

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

1 0

Re: [App_rpt-users] Installation problems with Intel 525 mini-itx
by Conny Jonsson 21 Jan '11

21 Jan '11

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

3 6

DTMF decoding
by K&R Yoksh 21 Jan '11

21 Jan '11

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

2 1

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