[App_rpt-users] rpt.conf

Tue Mar 4 19:04:34 UTC 2014

also have about the same thing, except via scripts on a web server that use some php trickery to send commands to asterisk via the manager interface when Lids annoy me.  change the input PL, etc.  since they probably can't scan for the input code due to signal strength...they usually go off and bother some other machine.  yeah, not totally effective, but have only had to use it a couple times in the last 4 years...:)

--
Bryan
Sent from my iPhone 5...small
keyboard, big fingers...please
forgive misspellings...

> On Mar 4, 2014, at 13:24, Matt Beasant <g4rky at yahoo.co.uk> wrote:
> 
> Hey there,
> 
> Matt here, just commenting on your closing comment ( sorry you didn't mention your name ) about the Morse ID's etc. 
> 
> I just wanted to share with you an idea I had a while ago and it seems to work really well in practice so maybe some of you out there in Allstar land would like to copy this.
> 
> On my node, I have two completely separate RPT.CONF files, one is called rptconn.conf and the other rptdis.conf.
> 
> I have two simple bash scripts that gets called by the "connectprog=" and "disconnprog=" statements in rpt,conf. 
> 
> The function of the connectprog script is to rename rptconn.conf as rpt.conf and then execute the rpt reload command on the node, thereby making it effective. 
> 
> Similarly the function of the disconnprog script is to rename the rptdis.conf file as rpt.conf and then rpt reload.
> 
> What all this means is that I can have two completely different behaviors for my node depending upon whether it is connected to another node or not. 
> 
> When it is not connected to another node, I have a long list of tail messages, time announcements on the quarter hour and voice ID's that play out.
> 
> When it is connected ( i.e. in use ) then the other rpt.conf file suppresses all the time announcements, tail messages and other stuff and just has CW ID's and thats it.
> 
> I thought it was quite an elegant solution, perhaps done in a strange way but it seems to work really well.
> 
> Hopefully someone will come up with an improvement on my (nasty) method but it just goes to show another aspect of the wonderfully versatile Allstar system!
> 
> Cheers,
> Matt., G4RKY 
> 
> 
>> On 4 March 2014 15:16, ARS W5OMR <ars.w5omr at gmail.com> wrote:
>> Sorry for the l-o-n-g delay... found this in my 'Drafts' folder.  Maybe my phone rang, or the door-bell rang - don't know why I didn't finish it, but it's pertinent to discussion of app_rpt
>> -Geoff
>> 
>> 
>>> On 01/22/2014 11:13 AM, Tim Sawyer wrote:
>> 
>>> Good point. And the telemetry stanza comments say:
>>> 
>>> ; Telemetry entries can be shared across all repeaters, or defined for each repeater.
>>> 
>>> So I’d say you CANNOT have separate morse stanzas.
>>> 
>> 
>> Well... kinda...
>> 
>> Technically, yes - only one morse stanza can be defined, but different ID strings can be entered for each node.
>> 
>> What's funny is, (it's really comical) my node 29657 (2m simplex node) is the *3rd* node defined in rpt.conf.
>> If I key up the simplex node *first*, upon an asterisk re-start, then the morse stanza for 29657 is used through out rpt.conf.
>> 
>> Meaning
>> 
>> [morse29655]
>> speed=20                ; Approximate speed in WPM
>> frequency=500           ; Morse Telemetry Frequency
>> amplitude=2048          ; Morse Telemetry Amplitude
>> idfrequency=1000        ; Morse ID Frequency    
>> idamplitude=2048        ; Morse ID Amplitude
>> 
>> [morse29657]
>> speed=20                ; Approximate speed in WPM
>> frequency=1000           ; Morse Telemetry Frequency
>> amplitude=2048          ; Morse Telemetry Amplitude
>> idfrequency=500         ; Morse ID Frequency       
>> idamplitude=2048        ; Morse ID Amplitude
>> 
>> If I key up the 2m simplex node, the freqency of the ID is low, and enjoyable.  If the repeater is keyed first, there's a 1k tone used for the ID.  (I'm old school - not that 'up' on voice ID's)  CW doesn't bother the on-going conversation like a voice-id does.
>> 
>> 
>> 
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>> 
>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140304/3dff69bf/attachment.html>