I have a simplex node that I would like to get to play an ID messages X minutes after the repeater system is keyed. Basically I’m hoping to duplicate the idrecording fuctionality with events because the idrecording and tailmessage features aren’t working in ASL3 for simplex nodes. Looking at the event documentation on the wiki, I’m not sure if there is a way to make an action happen X minutes after an event, or if there is a way to reset the X minutes timer if the system is keyed again. Is anyone here doing anything like this with events?
Simplex nodes do not follow the same rules as repeaters do. you the operator ID the Simplex node when you use it. unless you have others using your simplex node you do not need to ID it. if you read in your rpt.conf file under Duplex = ? you will see the following:
; 0 = Half duplex with no telemetry tones or hang time.
; Special Case: Full duplex if linktolink is set to yes.
; This mode is preferred when interfacing with an external multiport repeater controller.
; Comment out idrecording and idtalkover to suppress IDs also
; 1 = Half duplex with telemetry tones and hang time. Does not repeat audio.
; This mode is preferred when interfacing a simplex node.
; 2 = Full Duplex with telemetry tones and hang time.
; This mode is preferred when interfacing a repeater.
; 3 = Full Duplex with telemetry tones and hang time, but no repeated audio.
; 4 = Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.
Duplex=1 for simplex node Half duplex with telemetry tones and hang time. Does not repeat audio.
** ; This mode is preferred when interfacing a simplex node.**
I don’t need repeated audio, I have a simplex node that is connected to a linked repeater system. The IDing works fine if someone connects via a phone connection like dvswitch. I need it to also ID when someone keys the radio. I looked at the code and it’s not easy to understand. Probably going to be difficult to fix that way.
Anyone doing anything like this with events?
If it is only for use with initial connect,
I would try some other path.
connpgm = yourconnectprogram
And use a shell script to play whatever ID you want.
Asking if anyone has any experience using events to do the IDing. Really just need a way to kick off a timer with an event that can reset after another key of the radio so that the idrecording will play x minutes after the last key up.
the problem is you are trying to run a simplex node as a repeater. STOP. it is not a repeater you do not need for it to ID as you are the one IDING it. if you are the only one using it then no ID is needed as it stops when you do. you can listen to it when connected to anyone with no issues.
The simplex node connects to a linked repeater system as I mentioned above. We want to use the allstar node to do voice ID and announcements.
What I’m asking for is if anyone has used events with a timer, like a typical repeater controller would. If anyone has any experience there, I would like to know.
you will need to set duplex =2 or 3 in the RPT.conf file to allow the announcements to go thru. then you can set your announcements to work thru either the scheduler in the rpt file or thru the crontab -e
your announcements need to be 8k mono and if you are running ASL3 they have to be .ulaw
hamvoip can be .gsm, .wav, .ul
This is incorrect for US operators. A simplex node must ID every 10 minutes:
§ 97.119 Station identification.
(a) Each amateur station, except a space station or telecommand station, must transmit its assigned call sign on its transmitting channel at the end of each communication, and at least every 10 minutes during a communication, for the purpose of clearly making the source of the transmissions from the station known to those receiving the transmissions. No station may transmit unidentified communications or signals, or transmit as the station call sign, any call sign not authorized to the station.
A simplex AllStarLink node is neither a “space station” or a “telecommand station” by rule and thus must ID. Using a simplex node, the ID requirements are no different than a full-duplex repeater - the system must ID upon the channel on which it transmitted according to the rule.If you have a duplex=1 setup, Asterisk/app_rpt will most certainly send its ID at the appropriate times and use CW by default. The only time it’s permissible to disable the IDing in app_rpt is when there is NO RF transmissions involved of any sort - i.e. a “hub node” or is working as a remote base to a repeater/repeater controller that is otherwide identifying (i.e. duplex=0).
1 Like
You can’t ID via cron since that becomes a beacon. I’m in the USA so that’s not how you are supposed to do it.
I’ve never done it, but presumably what you could do it set a variable with the event that is always setting the current time (which I think is available as a global variable) after a keyup. Then, run a cron job every minute that check that variable. If the variable is longer ago than 10 minutes (in seconds), play the sound you want with rpt localplay. However that would not be appropriate for a station ID because you could have a situation on a busy network where that variable is reset indefinitely and your node never IDs properly.
Excellent idea, that’s what I was wondering. And a little more logic to make it id every 10 minutes if the timer keeps getting reset would take care of the other part.
You should not use this at all to be your compliant ID process. In your described case, a localplay may not be played in time because that is queued and plays when it can. The identification process in app_RPT will play over any other transmission properly at the correct times.
Okay roger that. I was trying to think of a way to do idtalkover if needed. But in this specific case, the local 2M repeaters in our linked system do a CW id to keep us legal. People got used to the voices of Hector and Juliet from the ACC96 controller that has been removed after decades, and I have recordings of them that I’d like to play to do the voice id and net, club meeting announcements. So as long as I have something that will play after a period of traffic ends, that will be good enough. But I will see if there is a way to get legal with this while I’m at it.
Not if it is sitting idle or listening. only if it is transmitting. and the user has it linked to a repeater which he does then the repeater Id’s on the link. he is then not required for it to ID.
This is not correct. The transmitting station is the station of record that must ID. That is no different than a full-duplex repeater. In a full-duplex repeater even though individual talkers identify on the air the repeater itself still IDs every 10 minutes as well. The talkers are IDing for their transmission and the repeater is IDing for its transmissions. The same applies to a simplex node.
Yes I know this. But as a Link to the repeater the repeater itself is IDING as well as the operator of the link talking on it. there for he does not have to force an ID as it it is transmitting his and receiving the repeater ID.
Please STOP, I already got a good answer from someone who was trying to answer my question.