[App_rpt-users] rpt.conf

[Bob]

Geoff,

Is the second morse stanza declared after the second node stanza header?

Example order:

[29655]

[morse29655]

[29657]

[morse29657]

With the common stanzas after this?

There IS the statement in rpt.conf example:

;
; Morse code parameters, these are common to all repeaters.
;

Which may be correct. Don't know.

Thanks,
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 6:31 AM
To: app_rpt-users at ohnosec.org
Subject: [App_rpt-users] rpt.conf

First off, thanks for all the help in getting a 2nd node running on the 
system.  It's been a learning experience and actually... a lot of help 
came from the drupal site.  Thanks, Tim for doing that.  I still fumble 
around, but finding things is getting *somewhat* easier.

Interesting bug I found, though, in rpt.conf... and I'm sure this is in 
a .c module, somewhere (morse.c?) but alas, I'm no programmer...

If I define a stanza in 29655 for Morse with the line
morse=morse29655

then app_rpt, using /etc/asterisk/rpt.conf *should* go to that stanza 
and read:

[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

All is fine and dandy, and when I key the repeater, I get exactly 
*that*.  Cool.


Here's where it gets *buggy*...

Using the same rpt.conf, as I define the morse stanza for node 29657 the 
same way I do in 29655, with the line
morse=morse29657

app_rpt *should* pick that up and do

[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

... but, that's not what happens.

If I key the repeater first, then I get what is defined in morse29655.  
Problem is, it doesn't change for 29657.  Meaning, whatever id/telem 
frequencies were defined, are used subsequently, depending on which 
stanza is used first.

If I key the simplex (29657) node -first-, the same thing happens, only 
both machine use the morse29657 stanza.

As a possible solution, I redefined the stanza with 
morse=29655morse29655 and, of course, renamed the stanza to reflect.  No 
typos... they've been checked and checked and re-checked.

Thoughts?

-Geoff/W5OMR

_______________________________________________
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.