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
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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Geoff Sent: Tuesday, January 21, 2014 6:31 AM To: app_rpt-users@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@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.
On 01/22/2014 09:25 AM, Bob wrote:
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.
That's the message I got, Bob, after I sent the initial message (yours is the first reply). Something, somewhere is stuck in the back of a buddy's head, that even if there are multiple nodes defined in rpt.conf, only the actual I.D. string can be changed. Frequencies stay the same. Seems to be the case. -Geoff
Geoff, I've found the same to be true for my implementation. The first stanza defined is what is used by all subsequent stanzas regardless of inserting what I would have expected to get for each node. And yes, there seems to be "insight" in the note telling you that will be the case. Which for me, running several "local" repeaters, it would be helpful to have a different pitch for them to more easily recognize which is ID'ing rather than waiting for any post callsign add-on I've placed in the ID string. tnx Mike / W5JR Milton GA
On Jan 22, 2014, at 10:25 AM, "Bob" <kk6ecm@gmail.com> wrote:
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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Geoff Sent: Tuesday, January 21, 2014 6:31 AM To: app_rpt-users@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@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@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.
On 01/22/2014 10:51 AM, Mike/W5JR wrote:
Geoff, I've found the same to be true for my implementation. The first stanza defined is what is used by all subsequent stanzas regardless of inserting what I would have expected to get for each node. And yes, there seems to be "insight" in the note telling you that will be the case. Which for me, running several "local" repeaters, it would be helpful to have a different pitch for them to more easily recognize which is ID'ing rather than waiting for any post callsign add-on I've placed in the ID string.
Correct. Now, if you're fairly proficient at CW, you could -start- the ID string with, say, the last 2 (or 3) numbers of your node, defined in each morse stanza for each node followed by your callsign. ie: [morse29929] speed=20 ; Approximate speed in WPM frequency=500 ; Morse Telemetry Frequency amplitude=2048 ; Morse Telemetry Amplitude idfrequency=1000 ; Morse ID Frequency idamplitude=2048 then define the callsign in each main node stanza with the line [node29929] ; ; (...getting there...) ; idrecording = |i29,W5JR/R Then, let's say you've got 29930, you could define the [node29930] stanza with ; idrecording = |;30,W5RJ/R I agree - different pitched ID's would make it easier to .. uh, well... "ID" each node is which when you hear it ;-) -Geoff/W5OMR
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. -- Tim :wq On Jan 22, 2014, at 7:25 AM, Bob <kk6ecm@gmail.com> wrote:
There IS the statement in rpt.conf example:
; ; Morse code parameters, these are common to all repeaters. ;
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 - (from my experience) 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 (simplex node) is the *3rd* node defined in rpt.conf. If I key up the simplex node *first*, upon 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=1026 ; Morse ID Amplitude if I key up 657 first, then the ID frequency is low and subdued, and the telmetry CW strings are ear-piercing . If I key up 655 first, the ID frequency is high and piercing, and the telemtry CW strings are low and subdued. It makes a difference. -Geoff/W5OMR
If an update were to be made to the Morse function, I'd like to have a 4th option, i, m, t, and (x), where amplitude associated with x could be used when a lower level Morse idtalkover ID. Thanks, Bob kk6ecm Sent from iPad On Jan 22, 2014, at 9:13 AM, Tim Sawyer <tim.sawyer@mac.com> 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. -- Tim :wq
On Jan 22, 2014, at 7:25 AM, Bob <kk6ecm@gmail.com> wrote:
There IS the statement in rpt.conf example:
; ; Morse code parameters, these are common to all repeaters. ;
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.
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@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@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.
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@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@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@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@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.
After you make changes to rpt.conf, are you restarting asterisk with “service asterisk restart” or “rpt reload”? -- Tim :wq On Jan 21, 2014, at 6:31 AM, Geoff <ars.w5omr@gmail.com> wrote:
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.
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
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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Geoff Sent: Tuesday, January 21, 2014 4:21 PM To: app_rpt-users@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@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.
On 01/22/2014 06:43 PM, Bob wrote:
It seems to me the Morse stanza only establishes the following in app_rpt.conf:
Right - I said I had to define different morse stanzas, and let me correct myself - no, you do NOT have to define different stanzas - only 1 is going to be used. You -can- use different ID strings (or files, or a tone sequence) for each separate node, for distinction. Speaking of tone sequences, why not use different tones, for each node? Got me thinking, now... ;-)
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@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Geoff Sent: Tuesday, January 21, 2014 4:21 PM To: app_rpt-users@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@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@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.
participants (8)
-
ARS W5OMR -
Bob -
Bryan D. Boyle -
Geoff
-
kk6ecm
-
Matt Beasant -
Mike/W5JR -
Tim Sawyer