[App_rpt-users] Rx disable command

[James Nessen]

likewise.  Thanks!

Jim, K6JWN

On 6/15/2011 12:17 PM, Steve Passmore wrote:
> Please send me the scripts.  That will save some time,  Thanks.
>
> For some reason I was under the impression that usbradio.conf settings 
> could only be changed by restarting Asterisk so I had ignored that 
> approach.
>
> Steve
>
> On 6/15/2011 11:22, Bryan D. Boyle wrote:
>> On 6/15/11 9:54 AM, Bryan D. Boyle wrote:
>>> On 6/15/11 7:34 AM, Tony KT9AC wrote:
>>>> Too bad you can't just switch the input PL required during those 
>>>> times.
>>>>
>>>>
>>>
>>> I'll give it a try...thinking this would be a quick and dirty way of 
>>> accomplishing it...???
>>>
>>> Thoughts?
>>>
>> Gave it a try (why not...little downtime here at the office...
>>
>> Created a script called nodenumberlid.sh (where nodenumber is the 
>> numeric representation of the node in question), put it in my scripts 
>> directory (which I have in /etc/asterisk to aggregate my various 
>> 'stuff') that copies a usbradiolid.conf over the running 
>> usbradio.conf, sleeps for 3 seconds (lets things calm down...), then 
>> issues an rasterisk -rx "reload" command.  Does very nicely in 
>> changing the ctcss for the receive to something other than the 
>> published.  (also wrote the reverse script to copy the original 
>> usbradionorm.conf back...don't want to screw up things...;)  Yeah, 
>> more files to keep track of, but, I'm thinking at this level, things 
>> don't change too much.
>>
>> Put it in a long 
>> XXXXXXXX=cmd,/etc/asterisk/scripts/nodenumber[lid|norm] function 
>> command in rpt.conf, reloaded, and over the iax connection, it makes 
>> the changes, reloads in both directions...seems to work just fine.  
>> Well, at least the execution and file changes ok...will check when I 
>> get home to see if it actually changes over the RF side of the 
>> equation...how's that?
>>
>> Why don't I have the lid script backup the running script?  Well..if 
>> you issue the lid script twice in a row...you'll end up with the 
>> changed ctcss-containing file being copied back by the norm script 
>> (which would be written to do so...); better to have a fixed config 
>> file that doesn't get touched except to edit.  Now...if you want to 
>> edit the running or standard config, just edit the usbradionorm.conf 
>> file, then issue a nodenumbernorm function command...:)
>>
>> I can see this being used, rather than sed inline..which gives me a 
>> shudder, but I know that's how some like to do it...and not making a 
>> judgment, just stating my preference.  But, it is eminently doable 
>> (and the index card with the list of function commands I can execute 
>> from the DTMF pad is getting longer...sigh...)
>>
>> Scripts available, if anyone wants to see how I did it...simple 4 
>> lines...
>>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users