i have this shiny new ASL3 Appliance going, tested, and functional! hooray me and props to the documentation.
i see in a config file (specifically rpt.conf) a long list of commented-out commands which i think could be invoked by DTMF sequences - please correct me if i'm wrong.
i would like to do from my HT with DTMF the same basic linking commands i can do for my node using the Allmon3 console. i think enabling system commands is mostly not a good idea, and invite comments on enabling any of those.
the commands in rpt.conf look like they are divided into cop, status, ilink, and remote categories? did i get that right? the commands also look like they are intended to be all defined in advance but not active until added to the specific node's template? is that also right?
if i am looking at the right config file, which of the commands and how should go about enabling them to allow the node linking to be controlled from the HT with DTMF tones?
sorry, i have previously encountered the document, but to me it really is a firehose of definitions.
the inactive commands in rpt.conf look to this untrained eye to offer more than one way to do a thing. which can be good or bad. furthermore, there is a suggestion in the rpt.conf comments about changing some of the number codes:
Change these to something other than these codes listed below!
can this great big gob of information be whittled down to offer a good place to start and begin to educate the newbie?
If you remove the leading ; from the line(s) then those DTMF commands would be enabled.
Keep in mind that we process each DTMF digit as it is received. Once we find a match, we process the associated function. So, if you define both *81 and *815 you would not have access to the latter.
It's your node so you get to decide what is enabled.
thank you for that. once upon long time ago, i made a techlab PBX with the Asterisk available at the time using some Grandstream equipment.
but now this is ASL3 territory, and i'm working on grasping what it means to do setup the "ASL Way". i just couldn't tell which of the *7, *8, or *9 and others are intended for the most basic DTMF commands. and i didn't know if i was expected just to uncomment lines or copy selected ones to where the specific node lines are.
"monitor only" means my hotspot emits RF but ignores the HT if i transmit, yes?
i will dive into the config file guided by new knowledge and your kindly supplied context to see if i can work out which command is for a 'permanent' link versus a temporary link, in addition to the very most basic DTMF controlled actions.
am i correct that if a command like *813 is not uncommented in rpt.conf, then it can't be invoked in the Asterisk console rpt fun <node#> *813<linknode#> ?
That's the DTMF code, so yes it cannot be invoked with fun either. However as an ilink command it's always available from the conosle - rpt cmd <node#> ilink 13 <linknode#>.
that much is sinking in for the cop, status, ilink, and remote categories
oh! also goes for macro category
and if by using the console, i wanted to temporarily suspend CWID and courtesy tone locally, there is a way to manipulate the variables idrecording and ?variable-name?, respectively?
use case: temporarily suspend CWID and courtesy tone and ID by voice when the node is functioning as a long mic cable to an interface with radio tuned to a local repeater
this document on courtesy tones tells me i'm in the right part of rpt.conf, if i wanted to edit the file and restart Asterisk. oh, but i see the document is for ASL prior to v3. searching the community posts can turn up deprecated information. i see this document is for ASL3.
none can offer guidance? have i not waited long enough for a small drop of guidance or have i stepped into something whiffy?
i have two simultaneous branches of techlab project in the works, and i have a minimalistic hotspot made, so, yay for Branch 1
end result of Branch 1 in cheatsheet form:
$ grep -iP "^[ \t]*[\dA-D]+ =" /etc/asterisk/rpt.conf | grep -vP "rptena|radio"
1 = ilink,1 ; Disconnect specified link
2 = ilink,2 ; Connect specified link -- monitor only
3 = ilink,3 ; Connect specified link -- transceive
4 = ilink,4 ; Enter command mode on specified link
70 = ilink,5 ; System status
99 = cop,6 ; PTT (phone mode only)
5 = macro
721 = status,1 ; Force ID (global)
722 = status,2 ; Give Time of Day (global)
723 = status,3 ; Give software Version (global)
724 = status,4 ; Give GPS location info
725 = status,5 ; Last (DTMF) user
711 = status,11 ; Force ID (local only)
712 = status,12 ; Give Time of Day (local only)
806 = ilink,6 ; Disconnect all links
811 = ilink,11 ; Disconnect a previously permanently connected link
812 = ilink,12 ; Permanently connect specified link -- monitor only
813 = ilink,13 ; Permanently connect specified link -- transceive
816 = ilink,16 ; Reconnect links disconnected with "disconnect all links"
(the above detailing which DTMF commands are active)
Branch 2 turns out to be very very easy to accomplish! wow, success already.
changing duplex = 1 in the node-specific part of rpt.conf to duplex = 0 sets up for proper reverse hotspot operation with a "real radio" (FT8900, in this case) using a DINAH interface.
SimpleUSB config for DINAH needs only a change to carrierfrom versus the hotspot USB radio dongle, and then it's all good from there.
n.b. my terminology: hotspot uses RF in to ASL3 Appliance to access the ASL Network. reverse hotspot uses ASL Network to ASL3 Appliance and then RF out to access over-the-airwaves equipment. (please do correct me if there's better terminology customarily in use)
