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

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

Re: [App_rpt-users] Audio gateway issues??
by Steve Passmore 14 Jan '11

14 Jan '11

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@ohnosec.org > [mailto:app_rpt-users-bounces@ohnosec.org] *On Behalf Of *Steve Passmore > *Sent:* Tuesday, January 11, 2011 1:28 PM > *To:* app_rpt-users(a)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(a)gmail.com <mailto:ckraly@gmail.com> > Date: Tue, 11 Jan 2011 12:40:57 -0600 > To: app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@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, <n7pkt(a)picklejar.org > <mailto:n7pkt@picklejar.org>> 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(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

3 2

Re: [App_rpt-users] Audio gateway issues??
by n7pkt＠picklejar.org 14 Jan '11

14 Jan '11

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

1 0

Audio gateway issues??
by n7pkt＠picklejar.org 13 Jan '11

13 Jan '11

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

6 6

iax / Asterisk & I should never be called
by Ken 13 Jan '11

13 Jan '11

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@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@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' -- <Zap/pseudo-363503172 ((all the callsign readouts here)) -- Hungup 'Zap/pseudo-363503172' -- Hungup 'Zap/pseudo-135650357' The "I should never be called" message looks like something gone wrong in app-rpt .. except that it works. Ken

2 3

URI ptt current sink
by Scott Weis 11 Jan '11

11 Jan '11

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

2 1