Re: [App_rpt-users] Audio gateway issues??
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@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@gmail.com <mailto:ckraly@gmail.com> Date: Tue, 11 Jan 2011 12:40:57 -0600 To: app_rpt-users@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@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@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@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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
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 <k6kya@hokeynet.net> 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@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@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@gmail.com Date: Tue, 11 Jan 2011 12:40:57 -0600 To: 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@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
-- Randy Hammock Phone: 818-925-4576
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
participants (3)
-
Matt Beasant -
Randy Hammock -
Steve Passmore