[App_rpt-users] DTMF disable or rf side
telesistant at hotmail.com
Mon Mar 1 01:29:51 EST 2010
There is certainly no question that something needs to be done about this.
We will be considering some different options in the next few days, but I
have a good idea of overall what we can do, but need to refine it greatly
at this point. It needs to something well thought out that will fit different
requirements, not just this particular case.
I was thinking of something kind of like the "Gong Show", except
without Gene Gene the Dancing Machine and the Unknown Comic, and
Rip Taylor and his confetti.
Okay, maybe a little confetti. It never hurts. :-)
> Date: Sun, 28 Feb 2010 20:57:56 -0500
> From: Ramesh at va3uv.com
> To: app_rpt-users at qrvc.com
> Subject: Re: [App_rpt-users] DTMF disable or rf side
> On 28/02/2010 8:18 PM, REDBUTTON_CTRL wrote:
>> HI All, is there a function in APP_Rpt that can be used to disable any
>> DTMF from being decoded from the RF side but still work from the console?
>> Today there was an individual trying to linkup _*all*_ the Allstar nodes
>> to a particular node.
>> It might be useful to use this feature to lock down a node to prevent
>> his happening in the future if such an attack of the twitchy fingers
>> happens again.
> <-- Hi Jon and all; If we can lockdown the entire system, so perhaps a
> macro that gets sent to all nodes to activate lock down, so that the
> integrity of the connected nodes is preserved - but other nodes
> attempting to connect get a busy message.... until the lockdown is removed.
> I recall reading something about this during the early chan_irlp
> discussions... but that was to busy-out a single node; if someone can
> remind us of that, we can look at pushing this out via a macro to all
> connected nodes...
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
More information about the App_rpt-users