- App_rpt-users - lists.keekles.org

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

A Bit of Irony
by Buddy Brannan 11 Jan '11

11 Jan '11

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

4 5

Re: [App_rpt-users] A Bit of Irony
by Tony KT9AC 11 Jan '11

11 Jan '11

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" <buddy(a)brannan.name> Date: Mon, Jan 10, 2011 8:52 pm Subject: [App_rpt-users] A Bit of Irony To: "Scott Weis" <kb2ear(a)kb2ear.net> Cc: <app_rpt-users(a)ohnosec.org> 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(a)ohnosec.org > [mailto:app_rpt-users-bounces@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(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Two Servers Behind NAT Router?
by Tim Sawyer 08 Jan '11

08 Jan '11

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

1 0

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

03 Jan '11

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@radio-gui:1] Rpt("IAX2/gui-5701", "27061|X") in new stack The one that does not work looks like this: -- Executing [27021@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

1 0

COP commands
by k8khw＠att.net 02 Jan '11

02 Jan '11

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

2 1