[App_rpt-users] rpt.conf

[Mike/W5JR]

Well this will be interesting to experiment with. Yes, I see where one could use different speed, pitch and levels for two cases by utilizing the ID or Message morse settings. 

I also see an option would be to upload a "recording" to play at whatever speed, pitch and level is desired and definitely can be per node. 

For the case of "idrecording" and "idtalkover" being the same, the former stops and latter "restarts" the ID sequence if a signal is received during the former. Took me a few head scratches to figure out the latter ought to be commented out if the former was not voice.

It would really be slick if the latter could just change to a different defined level rather than start over. That change/tweak to app_rpt.c is beyond my ability at the moment...

tnx
Mike / W5JR
Milton GA

> On Jan 22, 2014, at 7:43 PM, "Bob" <kk6ecm at gmail.com> wrote:
> 
> It seems to me the Morse stanza only establishes the following in
> app_rpt.conf:
> 
> ;[morse]
> 
> ;speed=20        ; Approximate speed in WPM
> ;frequency=800        ; Morse Telemetry Frequency
> ;amplitude=4096        ; Morse Telemetry Amplitude
> ;idfrequency=330        ; Morse ID Frequency    
> ;idamplitude=2048    ; Morse ID Amplitude
> 
> The string is established by: 
> 
> idrecording = |iW6XYZ
> 
> and 
> 
> idtalkover=|iW6XYZ
> 
> (Which seems to me is established for each node separately)
> 
> Where 
> 
> ; Telemetry entries are shared across all repeaters
> ; Can be a tone sequence, morse string, or a file
> ;
> ; |t - Tone escape sequence
> ;
> ; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2,
> duration, amplitude)
> ; Single frequencies are created by setting freq1 or freq2 to zero.
> ;
> ; |m - Morse escape sequence
> ; 
> ; Sends Morse code at the telemetry amplitude and telemetry frequency as
> defined in the
> ; [morse] section.
> ;
> ; Follow with an alphanumeric string
> ;
> ; |i - Morse ID escape sequence
> ;
> ; Sends Morse code at the ID amplitude and ID frequency as defined in the
> 
> If you are not using the |m for telemetry, or don't care, you could use it
> with a different frequency and amplitude in the [morse] section as
> 
> idrecording = |mW6XYZ ; second node.
> 
> Just a thought,
> Bob
> kk6ecm
> 
> -----Original Message-----
> From: app_rpt-users-bounces at ohnosec.org
> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Geoff
> Sent: Tuesday, January 21, 2014 4:21 PM
> To: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] rpt.conf
> 
> 
>> On 01/22/2014 09:32 AM, Tim Sawyer wrote:
>> After you make changes to rpt.conf, are you restarting asterisk with
> "service asterisk restart" or "rpt reload"?
>> --
> 
> Hi, Tim - well, I did it a couple of different ways...
> 
> /etc/init.d/asterisk stop
> 
> then
> 
> /etc/init.d/asterisk restart
> 
> Of course, shutting down asterisk failed (it was already stopped) but 
> restarting was just fine.
> When that didn't change anything, I thought "well, they're probably 
> doing something funky with the scripting".  So,
> 
> ~#>astdn.sh
> and
> ~#>astup.sh
> 
> were used.  The issue remained.
> 
> Bob said (and this seems to hold true with what a friend said he thinks 
> he remembers on the subject) that the example of rpt.conf says that the 
> morse stanza would be the same for all nodes.  With that explanation, it 
> would make sense to still define different morse stanzas, for different 
> callsigns, but that the telemetry and CW ID frequencies would be the 
> same throughout all nodes.  Only the CW strings would change.  This is 
> the case in my situation.
> 
> -Geoff
> 
> 
> 
> _______________________________________________
> 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.