Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1:  +
[[Category:Node Configuration]]
 +
[[Category:Config Files]]
 
Rpt.conf is where the majority of user-facing features, such as the node's CW and voice ID, DTMF commands and timers are set. There is a lot of capability here which can be difficult to grasp. Fortunately the default [https://github.com/PTTLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins.   
 
Rpt.conf is where the majority of user-facing features, such as the node's CW and voice ID, DTMF commands and timers are set. There is a lot of capability here which can be difficult to grasp. Fortunately the default [https://github.com/PTTLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins.   
   Line 20: Line 22:  
Status commands (functioncalss 'status') provide general information about the node.  
 
Status commands (functioncalss 'status') provide general information about the node.  
   −
Sample:
+
<syntaxhighlight lang="ini">712 = status,12  ; Give Time of Day (local only)</syntaxhighlight>
<pre>
  −
712 = status,12  ; Give Time of Day (local only)
  −
</pre>
      
{| class="wikitable"
 
{| class="wikitable"
Line 46: Line 45:  
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status.  
 
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status.  
   −
Sample:
+
<syntaxhighlight lang="ini">3 = ilink,3  ; Connect specified link -- transceive</syntaxhighlight>
<pre>
  −
3 = ilink,3  ; Connect specified link -- transceive
  −
</pre>
      
{| class="wikitable"
 
{| class="wikitable"
Line 92: Line 88:  
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference.  
 
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference.  
   −
Sample:
+
<syntaxhighlight lang="ini">99 = cop,7  ; enable timeout timer</syntaxhighlight>
<pre>
  −
99 = cop,7  ; enable timeout timer
  −
</pre>
      
Some COP commands can take multiple parameters. For example this COP 48 would send #3#607 on command.
 
Some COP commands can take multiple parameters. For example this COP 48 would send #3#607 on command.
   −
<pre>900 = cop,48,#,3,#,6,0,7</pre>  
+
<syntaxhighlight lang="ini">900 = cop,48,#,3,#,6,0,7</syntaxhighlight>
    
{| class="wikitable"
 
{| class="wikitable"
Line 310: Line 303:  
When [[#authlevel=|authlevel=]] is greater than zero, remote 99 is used to define a different dtmf sequence for each user authorized to use the remote base. The remote base will announce the callsign as access is granted.
 
When [[#authlevel=|authlevel=]] is greater than zero, remote 99 is used to define a different dtmf sequence for each user authorized to use the remote base. The remote base will announce the callsign as access is granted.
   −
Sample:
+
<syntaxhighlight lang="ini">
<pre>
+
[remote node#]
 +
authlevel = 2 ; Remote base authentication level
 +
; authlevel = 0 : Anyone can use it
 +
; authlevel = 1 : Requires log in, Waits for Tx key to ask for it
 +
; authlevel = 2 : Requires log in, asks for it automously
 +
 
 +
[remote-functions]
 +
8xx=remote,99,OK,E ; password
 +
</syntaxhighlight>
 +
<syntaxhighlight lang="ini">
 
9139583 = remote,99,WB6NIL,G  ; grant access to Jim (general)
 
9139583 = remote,99,WB6NIL,G  ; grant access to Jim (general)
 
9148351 = remote,99,WA6ZFT,E  ; grant access to Steve (extra)
 
9148351 = remote,99,WA6ZFT,E  ; grant access to Steve (extra)
</pre>
+
</syntaxhighlight>
 
When the remote base is disconnected from the originating node, the
 
When the remote base is disconnected from the originating node, the
 
user will be logged out.  
 
user will be logged out.  
Line 325: Line 327:     
For example:
 
For example:
[1000]
+
<syntaxhighlight lang="ini">
functions=functionsVHF
+
[1000]
+
functions=functionsVHF
[1001]
+
 
functions=functionsVHF
+
[1001]
+
functions=functionsVHF
[1002]
+
 
functions=functionsUHF
+
[1002]
+
functions=functionsUHF
[functionsVHF]
+
 
; Two meter Autopatch up is *6
+
[functionsVHF]
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000  
+
; Two meter Autopatch up is *6
0=autopatchdn      ; Autopatch down
+
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000  
+
0=autopatchdn      ; Autopatch down
[functionsUHF]
+
 
; 440 Autopatch up is *61
+
[functionsUHF]
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000  ; Autopatch up
+
; 440 Autopatch up is *61
0=autopatchdn      ; Autopatch down
+
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000  ; Autopatch up
 +
0=autopatchdn      ; Autopatch down
 
* controlstates=
 
* controlstates=
 
* functions=
 
* functions=
Line 350: Line 353:  
* telemetry=
 
* telemetry=
 
* wait_times=
 
* wait_times=
 +
</syntaxhighlight>
    
=Node Number Stanza=
 
=Node Number Stanza=
 
The node number stanza is the first stanza in rpt.conf.  
 
The node number stanza is the first stanza in rpt.conf.  
   −
<pre>
+
<syntaxhighlight lang="ini">[1999]    ; Replace with your assigned node number</syntaxhighlight>
[1999]    ; Replace with your assigned node number
  −
</pre>
      
The node number stanza contains the following key/value pairs.  
 
The node number stanza contains the following key/value pairs.  
Line 362: Line 364:  
This controls the length of the repeater hang time when the alternate hang timer is selected with a control operator function. It is specified in milliseconds.  
 
This controls the length of the repeater hang time when the alternate hang timer is selected with a control operator function. It is specified in milliseconds.  
   −
Sample:
+
<syntaxhighlight lang="ini">althangtime=4000  ; 4 seconds</syntaxhighlight>
<pre>
+
 
althangtime=4000  ; 4 seconds
  −
</pre>
   
==beaconing===
 
==beaconing===
 
When set to 1 will send the repeater ID at the idtime interval regardless of whether there was repeater activity or not. This feature appears to be required in the UK, but is probably illegal in the US.
 
When set to 1 will send the repeater ID at the idtime interval regardless of whether there was repeater activity or not. This feature appears to be required in the UK, but is probably illegal in the US.
   −
Sample:
+
<syntaxhighlight lang="ini">beaconing=1  ;Set to 1 to beacon. Defaults to 0</syntaxhighlight>
<pre>
+
 
beaconing=1  ;Set to 1 to beacon. Defaults to 0
  −
</pre>
   
==callerid===
 
==callerid===
 
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows
 
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows
 
+
<syntaxhighlight lang="ini">callerid="Repeater" <0000000000></syntaxhighlight>
<pre>
  −
callerid="Repeater" <0000000000>
  −
</pre>
      
''Note'': The value in quotes is the name of the autopatch caller, and the numbers in angle brackets are the originating telephone number to use.
 
''Note'': The value in quotes is the name of the autopatch caller, and the numbers in angle brackets are the originating telephone number to use.
Line 385: Line 380:     
Runs user defined scripts. Example from https://www.qsl.net/k0kn/swissarmy_debian
 
Runs user defined scripts. Example from https://www.qsl.net/k0kn/swissarmy_debian
<pre>
+
<syntaxhighlight lang="ini">
 
# Place these lines in rpt.conf for each node:
 
# Place these lines in rpt.conf for each node:
 
#    connpgm=/home/kyle/swissarmy 1
 
#    connpgm=/home/kyle/swissarmy 1
 
#    discpgm=/home/kyle/swissarmy 0
 
#    discpgm=/home/kyle/swissarmy 0
</pre>
+
</syntaxhighlight>
    
==context===
 
==context===
    
This setting directs the autopatch for the node to use a specific context in extensions.conf for outgoing autopatch calls. The default is to specify a context name of radio.
 
This setting directs the autopatch for the node to use a specific context in extensions.conf for outgoing autopatch calls. The default is to specify a context name of radio.
 
+
<syntaxhighlight lang="ini">context=radio</syntaxhighlight>
<pre>
  −
context=radio
  −
</pre>
      
==controlstates===
 
==controlstates===
 
This setting defines the name of the [[Structure of Config Files|variable named]] control state stanza. Control states are an optional feature which allows groups of control operator commands to be executed all at once. To use control states, define an entry in your node stanzas to point to a dedicated control state stanza like this:
 
This setting defines the name of the [[Structure of Config Files|variable named]] control state stanza. Control states are an optional feature which allows groups of control operator commands to be executed all at once. To use control states, define an entry in your node stanzas to point to a dedicated control state stanza like this:
<pre>
+
<syntaxhighlight lang="ini">controlstates = controlstates  ; points to control state stanza</syntaxhighlight>
controlstates = controlstates  ; points to control state stanza
  −
 
      +
<syntaxhighlight lang="ini">
 
[controlstates]
 
[controlstates]
 
0 = rptena,lnkena,apena,totena,ufena,noicd  ; Normal operation                                   
 
0 = rptena,lnkena,apena,totena,ufena,noicd  ; Normal operation                                   
 
1 = rptena,lnkena,apdis,totdis,ufena,noice  ; Net and news operation                                             
 
1 = rptena,lnkena,apdis,totdis,ufena,noice  ; Net and news operation                                             
 
2 = rptena,lnkdis,apdis,totena,ufdis,noice  ; Repeater only operation
 
2 = rptena,lnkdis,apdis,totena,ufdis,noice  ; Repeater only operation
</pre>
+
</syntaxhighlight>
    
The [[#Control States Stanza|control state stanza]] describes these mnemonics.
 
The [[#Control States Stanza|control state stanza]] describes these mnemonics.
Line 429: Line 420:  
|}
 
|}
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
duplex = 0    ; 0 = Half duplex with no telemetry tones or hang time.
 
duplex = 0    ; 0 = Half duplex with no telemetry tones or hang time.
</pre>
+
</syntaxhighlight>
    
==endchar===
 
==endchar===
Line 439: Line 429:  
==erxgain===
 
==erxgain===
 
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node.  
 
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node.  
 
+
<syntaxhighlight lang="ini">erxgain = -3</syntaxhighlight>
<pre>
  −
erxgain = -3
  −
</pre>
      
See [[:Category:How to|Echolink How to]]
 
See [[:Category:How to|Echolink How to]]
Line 448: Line 435:  
==etxgain===
 
==etxgain===
 
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node.  
 
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node.  
 
+
<syntaxhighlight lang="ini">etxgain = 3</syntaxhighlight>
<pre>
  −
etxgain = 3
  −
</pre>
      
See [[:Category:How to|Echolink How to]]
 
See [[:Category:How to|Echolink How to]]
Line 461: Line 445:  
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].
 
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].
   −
Sample:
+
<syntaxhighlight lang="ini">functions = functionsUHF  ; pointer to 440 repeater functions stanza</syntaxhighlight>
<pre>
  −
functions = functionsUHF  ; pointer to 440 repeater functions stanza
  −
</pre>
      
== GUI ==
 
== GUI ==
Line 523: Line 504:  
= Putting it all Together =
 
= Putting it all Together =
 
A small excerpt from the function stanza of rpt.conf is hown below.
 
A small excerpt from the function stanza of rpt.conf is hown below.
[functions]
+
<syntaxhighlight lang="ini">
1=ilink,1                                              ; Specific link disconnect
+
[functions]
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000  ; Autopatch up
+
1=ilink,1                                              ; Specific link disconnect
 +
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000  ; Autopatch up
 +
</syntaxhighlight>
 
The above example contains DTMF functions with all of the parameters discussed on previous pages.
 
The above example contains DTMF functions with all of the parameters discussed on previous pages.
   Line 535: Line 518:  
This controls the length of the repeater hang time. It is specified in milliseconds.  
 
This controls the length of the repeater hang time. It is specified in milliseconds.  
   −
Sample:
+
<syntaxhighlight lang="ini">hangtime = 1000  ;Set hang time for 1 second</syntaxhighlight>
<pre>
  −
hangtime = 1000  ;Set hang time for 1 second
  −
</pre>
      
==holdofftelem===
 
==holdofftelem===
 
This node stanza configuration key forces all telemetry to be held off until a local user on the receiver or a remote user over a link unkeys. There is one exception to this behavior: When an ID needs to be sent and there is activity coming from a linked node.
 
This node stanza configuration key forces all telemetry to be held off until a local user on the receiver or a remote user over a link unkeys. There is one exception to this behavior: When an ID needs to be sent and there is activity coming from a linked node.
   −
Sample:
+
<syntaxhighlight lang="ini">holdofftelem = 1  ;Set to 1 to hold off. Default is 0</syntaxhighlight>
<pre>
  −
holdofftelem = 1  ;Set to 1 to hold off. Default is 0
  −
</pre>
      
== telemdefault= ==
 
== telemdefault= ==
<pre>
+
<syntaxhighlight lang="ini">telemdefault =  0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter. Default is 1</syntaxhighlight>
telemdefault =  0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter. Default is 1
  −
</pre>
      
== telemdynamic= ==
 
== telemdynamic= ==
<pre>
+
<syntaxhighlight lang="ini">telemdynamic = 0 = disallow users to change the local telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command. Default is 1</syntaxhighlight>
telemdynamic = 0 = disallow users to change the local telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command. Default is 1
  −
</pre>
      
== phonelinkdefault= ==
 
== phonelinkdefault= ==
<pre>
+
<syntaxhighlight lang="ini">phonelinkdefault = 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode  Default is 1</syntaxhighlight>
phonelinkdefault = 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode  Default is 1
  −
</pre>
      
== phonelinkdynamic= ==
 
== phonelinkdynamic= ==
<pre>
+
<syntaxhighlight lang="ini">phonelinkdynamic = 0 = disallow users to change phone telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command  Default is 1</syntaxhighlight>
phonelinkdynamic = 0 = disallow users to change phone telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command  Default is 1
  −
</pre>
      
==idrecording===
 
==idrecording===
 
The identifier message is stored in the node stanza using the idrecording key. It can be changed to a different call sign by changing the value to something different. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds.  
 
The identifier message is stored in the node stanza using the idrecording key. It can be changed to a different call sign by changing the value to something different. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds.  
   −
Sample:
+
<syntaxhighlight lang="ini">idrecording = |iwa6zft/r  ; Morse Code ID</syntaxhighlight>
<pre>
  −
idrecording = |iwa6zft/r  ; Morse Code ID
  −
</pre>
   
or
 
or
<pre>
+
<syntaxhighlight lang="ini">idrecording = /var/lib/asterisk/sounds/myid  ; Voice ID</syntaxhighlight>
idrecording = /var/lib/asterisk/sounds/myid  ; Voice ID
  −
</pre>
   
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
 
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
   Line 584: Line 548:  
The ID talkover message is stored in the node stanza using the idtalkover setting. The purpose of idtalkover is to specify an alternate ID to use when the ID must be sent over the top of a user transmission, This can be a shorter voice ID or an ID in morse code. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. Example usages are as follows:
 
The ID talkover message is stored in the node stanza using the idtalkover setting. The purpose of idtalkover is to specify an alternate ID to use when the ID must be sent over the top of a user transmission, This can be a shorter voice ID or an ID in morse code. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. Example usages are as follows:
   −
Sample:
+
<syntaxhighlight lang="ini">idtalkover = |iwa6zft/r  ; Morse Code ID</syntaxhighlight>
<pre>
  −
idtalkover = |iwa6zft/r  ; Morse Code ID
  −
</pre>
   
or
 
or
<pre>
+
<syntaxhighlight lang="ini">idtalkover = /var/lib/asterisk/sounds/myid  ; Voice ID</syntaxhighlight>
idtalkover = /var/lib/asterisk/sounds/myid  ; Voice ID
  −
</pre>
   
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
 
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
   Line 607: Line 566:  
* dialtone is optional. Set to Y for dial tone on successful funcchars.
 
* dialtone is optional. Set to Y for dial tone on successful funcchars.
   −
Sample:
+
<syntaxhighlight lang="ini">inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys</syntaxhighlight>
<pre>
  −
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys
  −
</pre>
      
==link_functions===
 
==link_functions===
Line 617: Line 573:  
The link_functions setting directs the node to use a particular function stanza for functions dialed by users accessing the node via a link from another node. The traditional default is to point it to a function stanza named "functions".
 
The link_functions setting directs the node to use a particular function stanza for functions dialed by users accessing the node via a link from another node. The traditional default is to point it to a function stanza named "functions".
   −
Sample:
+
<syntaxhighlight lang="ini">link_functions = functions ; pointer to the Link Function stanza</syntaxhighlight>
<pre>
  −
link_functions = functions ; pointer to the Link Function stanza
  −
</pre>
      
==linkmongain===
 
==linkmongain===
 
Link Monitor Gain adjusts the audio level of monitored nodes when a signal from another node or the local receiver is received. If linkmongain is set to a negative number the monitored audio will decrease by the set amount in db. If linkmongain set to a positive number monitored audio will increase by the set amount in db. The value of linkmongain is in db. The default value is 0 db.
 
Link Monitor Gain adjusts the audio level of monitored nodes when a signal from another node or the local receiver is received. If linkmongain is set to a negative number the monitored audio will decrease by the set amount in db. If linkmongain set to a positive number monitored audio will increase by the set amount in db. The value of linkmongain is in db. The default value is 0 db.
   −
Sample:
+
<syntaxhighlight lang="ini">linkmongain = -20  ; reduce link volume 20dB</syntaxhighlight>
<pre>
  −
linkmongain = -20  ; reduce link volume 20dB
  −
</pre>
      
==linktolink===
 
==linktolink===
 
When operating in duplex mode 0, this forces the radio interface to operate in full duplex mode, but keeps all the other duplex mode 0 semantics. This is used when a radio interface is connected to a multiport analog repeater controller. The linktolink= key can take two values: yes or no.
 
When operating in duplex mode 0, this forces the radio interface to operate in full duplex mode, but keeps all the other duplex mode 0 semantics. This is used when a radio interface is connected to a multiport analog repeater controller. The linktolink= key can take two values: yes or no.
   −
Sample:
+
<syntaxhighlight lang="ini">linktolink = yes  ; set to yes to enable. Default is no.</syntaxhighlight>
<pre>
  −
linktolink = yes  ; set to yes to enable. Default is no.
  −
</pre>
      
==linkunkeyct===
 
==linkunkeyct===
 
The linkunkeyct setting selects the courtesy tone to send when a connected remote node unkeys. The default is no courtesy tone when a remote node unkeys.
 
The linkunkeyct setting selects the courtesy tone to send when a connected remote node unkeys. The default is no courtesy tone when a remote node unkeys.
   −
Sample:
+
<syntaxhighlight lang="ini">linkunkeyct = ct8  ; use courtesy tone 8</syntaxhighlight>
<pre>
  −
linkunkeyct = ct8  ; use courtesy tone 8
  −
</pre>
      
==macro===
 
==macro===
 
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts.  
 
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts.  
   −
Sample:
+
<syntaxhighlight lang="ini">macro=macro  ; use stanza names 'macros'
<pre>
  −
macro=macro  ; use stanza names 'macros'
      
[macro]
 
[macro]
 
1 = *32000*32001    ; connect to nodes 2000 and 2001
 
1 = *32000*32001    ; connect to nodes 2000 and 2001
</pre>
+
</syntaxhighlight>
    
==nounkeyct===
 
==nounkeyct===
 
The nounkeyct node stanza key completely disables the courtesy tone. This is useful for eliminating TX time in applications using simplex uplinks to repeaters on the repeater pair itself.  This practice is '''strongly''' discouraged.
 
The nounkeyct node stanza key completely disables the courtesy tone. This is useful for eliminating TX time in applications using simplex uplinks to repeaters on the repeater pair itself.  This practice is '''strongly''' discouraged.
   −
Sample:
+
<syntaxhighlight lang="ini">nounkeyct = yes  ; :(</syntaxhighlight>
<pre>
  −
nounkeyct = yes  ; :(
  −
</pre>
      
==politeid===
 
==politeid===
 
The politeid setting specified the number of milliseconds prior to the end of the id cycle where the controller will attempt to play the ID in the tail when a user unkeys. If the controller does not get a chance to send the ID in the tail, the ID will be played over the top of the user transmission. Optional, default 30000.
 
The politeid setting specified the number of milliseconds prior to the end of the id cycle where the controller will attempt to play the ID in the tail when a user unkeys. If the controller does not get a chance to send the ID in the tail, the ID will be played over the top of the user transmission. Optional, default 30000.
   −
Sample:
+
<syntaxhighlight lang="ini">politeid = 30000  ; 30 seconds</syntaxhighlight>
<pre>
  −
politeid = 30000  ; 30 seconds
  −
</pre>
      
==propagate_dtmf===
 
==propagate_dtmf===
Line 677: Line 613:  
This setting is meant to be used in conjunction with linktolink, inxlat, and outxlat when interfacing a radio port to a multiport analog repeater controller on an RF-linked system.
 
This setting is meant to be used in conjunction with linktolink, inxlat, and outxlat when interfacing a radio port to a multiport analog repeater controller on an RF-linked system.
   −
Sample:
+
<syntaxhighlight lang="ini">propagate_dtmf = no</syntaxhighlight>
<pre>
  −
propagate_dtmf = no
  −
</pre>
   
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.
 
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.
   Line 686: Line 619:  
The remotect setting allows the selection of the remote linked courtesy tone so that the users can tell there is a [[:Category:Remote Base|remote base]] connected locally.
 
The remotect setting allows the selection of the remote linked courtesy tone so that the users can tell there is a [[:Category:Remote Base|remote base]] connected locally.
   −
Sample:
+
<syntaxhighlight lang="ini">remotect = ct3  ; use courtesy tone 3</syntaxhighlight>
<pre>
  −
remotect = ct3  ; use courtesy tone 3
  −
</pre>
      
==rxburstfreq===
 
==rxburstfreq===
 
If rx tone burst operation is desired, specify the frequency in hertz of the desired tone burst. Setting to 0 (or not specifying) indicates no tone burst operation.
 
If rx tone burst operation is desired, specify the frequency in hertz of the desired tone burst. Setting to 0 (or not specifying) indicates no tone burst operation.
   −
Sample:
+
<syntaxhighlight lang="ini">rxburstfreq = 1000</syntaxhighlight>
<pre>
  −
rxburstfreq = 1000
  −
</pre>
      
==rxburstthreshold===
 
==rxburstthreshold===
Line 714: Line 641:  
| dahdi/pseudo || No radio, used for hubs
 
| dahdi/pseudo || No radio, used for hubs
 
|-  
 
|-  
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]]  
+
| SimpleUSB/usb_1999 || [[SimpleUSB_Channel_Driver|SimpleUSB (limited DSP)]]  
 
|-  
 
|-  
 
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]]  
 
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]]  
Line 728: Line 655:  
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP
 
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP
 
|}
 
|}
Sample:
+
<syntaxhighlight lang="ini">rxchannel = dahdi/pseudo    ; No radio (hub)</syntaxhighlight>
<pre>
  −
rxchannel = dahdi/pseudo    ; No radio (hub)
  −
</pre>
      
''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.
 
''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.
Line 738: Line 662:  
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.
 
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.
   −
Sample:
+
<syntaxhighlight lang="ini">scheduler = schedule  ; name scheduler to 'schedule'
<pre>
  −
scheduler = schedule  ; name scheduler to 'schedule'
      
[schedule]
 
[schedule]
 
...
 
...
</pre>
+
</syntaxhighlight>
    
==sleeptime===
 
==sleeptime===
 
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep.  
 
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep.  
   −
Sample:
+
<syntaxhighlight lang="ini">sleeptime = 300  ; go to sleep after 5 mins of no activity</syntaxhighlight>
<pre>
  −
sleeptime = 300  ; go to sleep after 5 mins of no activity
  −
</pre>
      
==startup_macro===
 
==startup_macro===
 
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.
 
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.
   −
Sample:
+
<syntaxhighlight lang="ini">startup_macro = *31000 *31001 *31002  ; Connect to 1000, 1001 and 1002 at startup</syntaxhighlight>
<pre>
+
 
startup_macro = *31000*31001*31002  ; Connect to 1000, 1001 and 1002 at startup
+
One string of one or multiple commands executed in order.
</pre>
+
Note that this line of commands does NOT terminate with a # like a normal macro. And you can call any number of regular macros with it.
    
==tailmessagelist===
 
==tailmessagelist===
 
The tailmessagelist setting allows a comma separated list of audio files to be specified for the tail message function. The tail messages will rotate from one to the next until the end of the list is reached at which point the first message in the list will be selected. If no absolute path name is specified, the directory var/lib/asterisk/sounds will be searched for the sound file. The file extension should be omitted.
 
The tailmessagelist setting allows a comma separated list of audio files to be specified for the tail message function. The tail messages will rotate from one to the next until the end of the list is reached at which point the first message in the list will be selected. If no absolute path name is specified, the directory var/lib/asterisk/sounds will be searched for the sound file. The file extension should be omitted.
   −
Sample:
+
<syntaxhighlight lang="ini">tailmessagelist = welcome,clubmeeting,wx  ; rotate 3 tail messages</syntaxhighlight>
<pre>
  −
tailmessagelist = welcome,clubmeeting,wx  ; rotate 3 tail messages
  −
</pre>
      
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
 
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]
Line 775: Line 691:  
This sets the amount of time in milliseconds between tail messages. Tail Messages are played when a user unkeys on the repeater input at the point where the hang timer expires after the courtesy tone is sent.
 
This sets the amount of time in milliseconds between tail messages. Tail Messages are played when a user unkeys on the repeater input at the point where the hang timer expires after the courtesy tone is sent.
   −
Sample:
+
<syntaxhighlight lang="ini">tailmessagetime = 900000  ; 15 minutes between tail messages</syntaxhighlight>
<pre>
  −
tailmessagetime = 900000  ; 15 minutes between tail messages
  −
</pre>
      
==tailsquashedtime===
 
==tailsquashedtime===
 
If a tail message is "squashed" by a user keying up over the top of it, a separate time value can be loaded to make the tail message be retried at a shorter time interval than the standard tailmessagetime= setting. The tailsquashedtime= setting takes a value in milliseconds.
 
If a tail message is "squashed" by a user keying up over the top of it, a separate time value can be loaded to make the tail message be retried at a shorter time interval than the standard tailmessagetime= setting. The tailsquashedtime= setting takes a value in milliseconds.
   −
Sample:
+
<syntaxhighlight lang="ini">tailsquashedtime = 300000  ; 5 minutes</syntaxhighlight>
<pre>
  −
tailsquashedtime = 300000  ; 5 minutes
  −
</pre>
      
==totime===
 
==totime===
This defines the time out timer interval. The value is in milliseconds.
+
This defines the time out timer interval. The value is in milliseconds. The default value is 180000.
   −
Sample:
+
<syntaxhighlight lang="ini">totime = 180000  ; Repeater timeout 3 minutes </syntaxhighlight>
<pre>
+
 
totime = 180000  ; 3 minutes
+
Related: [[#COP Commands | COP Commands 7 and 8]] and [[#controlstates= | controlstates=]] and [[#Control States Stanza | Control States Stanza]]
</pre>
      
==unlinkedct===
 
==unlinkedct===
 
The unlinkedct setting selects the courtesy tone to be used when the system has no remote nodes connected and is operating as a standalone repeater.
 
The unlinkedct setting selects the courtesy tone to be used when the system has no remote nodes connected and is operating as a standalone repeater.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
unlinkedct = ct2  ; use courtesy tone 2
 
unlinkedct = ct2  ; use courtesy tone 2
</pre>
+
</syntaxhighlight>
    
==wait-times===
 
==wait-times===
 
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].
 
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
wait-times = wait-times  ; name wait-times to 'wait-times'
 
wait-times = wait-times  ; name wait-times to 'wait-times'
</pre>
+
</syntaxhighlight>
    
=Functions Stanza=
 
=Functions Stanza=
 
The functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#functions=|function=]] key/value pair.  Functions within this stanza are used to decode DTMF commands when accessing the node from its receiver.  This stanza is typically named 'functions'.   
 
The functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#functions=|function=]] key/value pair.  Functions within this stanza are used to decode DTMF commands when accessing the node from its receiver.  This stanza is typically named 'functions'.   
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
functions = functions  ; name the functions stanza 'functions'
 
functions = functions  ; name the functions stanza 'functions'
    
[functions]
 
[functions]
 
...
 
...
</pre>
+
</syntaxhighlight>
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
   Line 827: Line 733:  
The link functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#link_functions=|link_function=]] key/value pair.  Functions within this stanza are used decode DTMF commands when accessing the node via a link from another node. The traditional usage is to point link_functions= to the same stanza as named  by [[#functions=|functions=]] thereby having functions from a linked node and from the local node the same.
 
The link functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#link_functions=|link_function=]] key/value pair.  Functions within this stanza are used decode DTMF commands when accessing the node via a link from another node. The traditional usage is to point link_functions= to the same stanza as named  by [[#functions=|functions=]] thereby having functions from a linked node and from the local node the same.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
functions = functions        ; name the functions stanza 'functions'
 
functions = functions        ; name the functions stanza 'functions'
 
link_functions = functions  ; use the same stanza  
 
link_functions = functions  ; use the same stanza  
Line 834: Line 739:  
[functions]
 
[functions]
 
...
 
...
</pre>
+
</syntaxhighlight>
 
If a different set of either limited or more capable functions is desired:
 
If a different set of either limited or more capable functions is desired:
<pre>
+
<syntaxhighlight lang="ini>
 
functions = functions                ; name the functions stanza 'functions'
 
functions = functions                ; name the functions stanza 'functions'
 
link_functions = my_link_functions  ; use a different stanza
 
link_functions = my_link_functions  ; use a different stanza
Line 845: Line 750:  
[my_link_functions]
 
[my_link_functions]
 
...
 
...
</pre>
+
</syntaxhighlight>
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
   Line 851: Line 756:  
The phone functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#phone_functions=|phone_function=]] key/value pair.  Functions within this stanza are used decode DTMF commands when accessing the node from a telephone. The traditional usage is to point phone_functions= to the same stanza as named  by [[#functions=|functions=]] thereby having functions from a phone and from the local node the same.  
 
The phone functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#phone_functions=|phone_function=]] key/value pair.  Functions within this stanza are used decode DTMF commands when accessing the node from a telephone. The traditional usage is to point phone_functions= to the same stanza as named  by [[#functions=|functions=]] thereby having functions from a phone and from the local node the same.  
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
functions = functions        ; name the functions stanza 'functions'
 
functions = functions        ; name the functions stanza 'functions'
 
phone_functions = functions  ; use the same stanza  
 
phone_functions = functions  ; use the same stanza  
Line 858: Line 762:  
[functions]
 
[functions]
 
...
 
...
</pre>
+
</syntaxhighlight>
 
If a different set of either limited or more capable functions is desired:
 
If a different set of either limited or more capable functions is desired:
<pre>
+
<syntaxhighlight lang="ini>
 
functions = functions                  ; name the functions stanza 'functions'
 
functions = functions                  ; name the functions stanza 'functions'
 
phone_functions = my_phone_functions  ; use a different stanza
 
phone_functions = my_phone_functions  ; use a different stanza
Line 869: Line 773:  
[my_phone_functions]
 
[my_phone_functions]
 
...
 
...
</pre>
+
</syntaxhighlight>
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
 
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.
   Line 875: Line 779:  
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts.  
 
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts.  
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
macro=macro  ; use stanza names 'macros'
 
macro=macro  ; use stanza names 'macros'
    
[macro]
 
[macro]
 
1 = *32000*32001    ; connect to nodes 2000 and 2001
 
1 = *32000*32001    ; connect to nodes 2000 and 2001
</pre>
+
</syntaxhighlight>
 +
 
 +
[https://wiki.allstarlink.org/index.php?title=Macro_use_and_format&modqueued=1 Full Macro Use And Format]
    
=Remote Base Stanza=
 
=Remote Base Stanza=
Line 893: Line 798:  
* authlevel=2 Enables access control, and prompts for the access code at the time of connection
 
* authlevel=2 Enables access control, and prompts for the access code at the time of connection
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
autllevel = 0  ; allow all comers  
 
autllevel = 0  ; allow all comers  
</pre>
+
</syntaxhighlight>
    
==civaddr===
 
==civaddr===
 
civaddr= is used with ICOM band radios to set the CIV address. The value is a 2 digit hexadecimal number. If this key is not specified, then the CIV address will be set to the default of 88.  
 
civaddr= is used with ICOM band radios to set the CIV address. The value is a 2 digit hexadecimal number. If this key is not specified, then the CIV address will be set to the default of 88.  
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
civaddr = 98  ; set CIV to 98
 
civaddr = 98  ; set CIV to 98
</pre>
+
</syntaxhighlight>
    
==Remote Base functions===
 
==Remote Base functions===
 
functions= is a pointer to a remote base function stanza.  
 
functions= is a pointer to a remote base function stanza.  
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
functions = functions-remote  ; name the functions stanza 'functions-remote'
 
functions = functions-remote  ; name the functions stanza 'functions-remote'
    
[functions-remote]
 
[functions-remote]
 
...
 
...
</pre>
+
</syntaxhighlight>
    
See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].
 
See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].
Line 922: Line 824:  
ioaddr= refers to a parallel port I/O address. It is specified as a hexadecimal number with a 0x prefix. The parallel port is used when the Doug Hall RBI-1 interface is employed.
 
ioaddr= refers to a parallel port I/O address. It is specified as a hexadecimal number with a 0x prefix. The parallel port is used when the Doug Hall RBI-1 interface is employed.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
ioaddr = 0x378  ; set RB-1 address
 
ioaddr = 0x378  ; set RB-1 address
</pre>
+
</syntaxhighlight>
    
==ioport===
 
==ioport===
 
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.
 
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
ioport = /dev/ttyS1  ; Linux com1
 
ioport = /dev/ttyS1  ; Linux com1
</pre>
+
</syntaxhighlight>
    
==Remote Base phone_functions===
 
==Remote Base phone_functions===
 
phone_functions= is a pointer to a remote base phone function stanza. It is equivalent to phone_functions in the [[#Phone Functions Stanza|Phone Functions Stanza]] but provides a separate set of commands.   
 
phone_functions= is a pointer to a remote base phone function stanza. It is equivalent to phone_functions in the [[#Phone Functions Stanza|Phone Functions Stanza]] but provides a separate set of commands.   
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
phone_functions = functions-remote
 
phone_functions = functions-remote
</pre>
+
</syntaxhighlight>
    
==remote===
 
==remote===
 
remote= sets the type of radio. It also ensures that the node will be defined as a remote base node and not a standard node.
 
remote= sets the type of radio. It also ensures that the node will be defined as a remote base node and not a standard node.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
remote = xcat  ; set xcat interface
 
remote = xcat  ; set xcat interface
</pre>
+
</syntaxhighlight>
    
{| class="wikitable"
 
{| class="wikitable"
Line 965: Line 863:  
|-
 
|-
 
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=
 
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=
 +
|-
 +
| Doug Hall || rbi || Requires Parallel Port Address https://wiki.allstarlink.org/wiki/Remote_Base:_Doug_Hall_RBI-1=
 
|}
 
|}
   Line 971: Line 871:  
Specifies the amount of time without keying from the link. Set to 0 to disable timeout.
 
Specifies the amount of time without keying from the link. Set to 0 to disable timeout.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
remote_inact_timeout = 0  ; do not time out
 
remote_inact_timeout = 0  ; do not time out
</pre>
+
</syntaxhighlight>
    
==remote_timeout===
 
==remote_timeout===
 
Session time out for remote base. Set to 0 to disable.
 
Session time out for remote base. Set to 0 to disable.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
remote_timeout = 0  ; do not timeout
 
remote_timeout = 0  ; do not timeout
</pre>
+
</syntaxhighlight>
    
==remote_timeout_warning===
 
==remote_timeout_warning===
Line 991: Line 889:  
This should contain the name of a usb radio interface which has been defined in [[usbradio.conf]] or a zaptel interface number if using a Quad Radio PCI Card.
 
This should contain the name of a usb radio interface which has been defined in [[usbradio.conf]] or a zaptel interface number if using a Quad Radio PCI Card.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
rxchannel = usbRadio/usb1
 
rxchannel = usbRadio/usb1
</pre>
+
</syntaxhighlight>
    
==Sample Remote Configuration==
 
==Sample Remote Configuration==
<pre>
+
<syntaxhighlight lang="ini>
 
[1234]
 
[1234]
 
; Rx audio/signaling channel                                                                                   
 
; Rx audio/signaling channel                                                                                   
Line 1,016: Line 913:  
; Authorization level                                         
 
; Authorization level                                         
 
authlevel = 0       
 
authlevel = 0       
</pre>
+
</syntaxhighlight>
    
=Nodes Stanza=
 
=Nodes Stanza=
The [nodes] stanza is a list of nodes, their IP addresses, port and "NONE" for non-remote base nodes. The nodes stanza is used to identify which node is mapped to which Internet call and to determine the destination to send the call to. If you are using automatic update for PTTLink (public) nodes, no PTTLink nodes should be defined here. Only place a definition for your local nodes, and private (off of PTTLink) nodes or nodes behind the same NAT router here.
+
The [nodes] stanza is a list of nodes, their IP addresses, port and "NONE" for non-remote base nodes. The nodes stanza is used to identify which node is mapped to which Internet call and to determine the destination to send the call to. If you are using automatic update for Allstar link (public) nodes, no Allstar link nodes should be defined here. Only place a definition for your local nodes, and private (off of allstar link) nodes or nodes behind the same NAT router here.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
[nodes]
 
[nodes]
1000 = radio@127.0.0.1/1000,NONE              ; Private hub on this server
+
1000 = radio@127.0.0.1/1000,NONE              ; Private hub on this server  
 
1001 = radio@host.domain.com/1001,NONE        ; Private node on another server
 
1001 = radio@host.domain.com/1001,NONE        ; Private node on another server
 
2501 = radio@127.0.0.1/2501,NONE              ; Public node on this server
 
2501 = radio@127.0.0.1/2501,NONE              ; Public node on this server
 
2502 = radio@127.0.0.1/2502,NONE              ; Another public node on this server
 
2502 = radio@127.0.0.1/2502,NONE              ; Another public node on this server
 
2503 = radio@192.168.1.20:4570/2503,NONE      ; Public node behind the same NAT router
 
2503 = radio@192.168.1.20:4570/2503,NONE      ; Public node behind the same NAT router
</pre>
+
</syntaxhighlight>
The [nodes] stanza performs a function similar to an OS hosts file. When looking up node information, app_rpt looks in the [nodes] stanza first then searches (what could be called the PTTLink DNS) the /var/lib/asterisk/rpt_extnodes file.
+
The [nodes] stanza performs a function similar to an OS hosts file. When looking up node information, app_rpt looks in the [nodes] stanza first then searches (what could be called the Allstar DNS) the /var/lib/asterisk/rpt_extnodes file.
    
=Telemetry Stanza=
 
=Telemetry Stanza=
Line 1,044: Line 940:  
**Specify the path to a sound file on the server. Do not include file extension.
 
**Specify the path to a sound file on the server. Do not include file extension.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
[telemetry]
 
[telemetry]
 
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
 
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
Line 1,072: Line 967:  
   |-------------------------Tone 1
 
   |-------------------------Tone 1
   −
</pre>
+
</syntaxhighlight>
    
=Morse Stanza=
 
=Morse Stanza=
 
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.
 
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
[morse]
 
[morse]
 
speed = 20            ; Approximate speed in WPM
 
speed = 20            ; Approximate speed in WPM
Line 1,085: Line 979:  
idfrequency = 746    ; Morse ID Frequency   
 
idfrequency = 746    ; Morse ID Frequency   
 
idamplitude = 768    ; Morse ID Amplitude
 
idamplitude = 768    ; Morse ID Amplitude
</pre>
+
</syntaxhighlight>
    
=Wait Times Stanza=
 
=Wait Times Stanza=
 
This stanza is named by the [[#wait-times=|wait-times=]] key/value pair. The wait time stanza is used to set delay time between various node actions and their response. Values are in milliseconds.
 
This stanza is named by the [[#wait-times=|wait-times=]] key/value pair. The wait time stanza is used to set delay time between various node actions and their response. Values are in milliseconds.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
wait-times = wait-times  ; name the stanza 'wait-times'
 
wait-times = wait-times  ; name the stanza 'wait-times'
   Line 1,099: Line 992:  
unkeywait = 2000
 
unkeywait = 2000
 
calltermwait = 2000
 
calltermwait = 2000
</pre>
+
</syntaxhighlight>
    
=Remote Base Memory Stanza=
 
=Remote Base Memory Stanza=
Line 1,106: Line 999:  
memory = rxfreq,plfreq,txpower,offset,tone
 
memory = rxfreq,plfreq,txpower,offset,tone
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
[memory]
 
[memory]
 
00 = 146.580,100.0,m
 
00 = 146.580,100.0,m
Line 1,115: Line 1,007:  
04 = 146.460,100.0,m
 
04 = 146.460,100.0,m
 
05 = 146.550,100.0,m
 
05 = 146.550,100.0,m
</pre>
+
</syntaxhighlight>
    
=Control States Stanza=
 
=Control States Stanza=
   −
There are several predefined nmemonics (keywords) used in the control state stanza to enable and disable the various features of the controller. These nmemonics correspond to the control operator command to be executed and most of these are the same groups of letters sent back when a single control operator command is executed on the controller.
+
There are several predefined nmemonics (keywords) used in the [controlstates] stanza to enable and disable the various features of the controller. These nmemonics correspond to the control operator command to be executed and most of these are the same groups of letters sent back when a single control operator command is executed on the controller.
    
{| class="wikitable"
 
{| class="wikitable"
Line 1,164: Line 1,056:  
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.
 
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.
   −
Sample:
+
<syntaxhighlight lang="ini>
<pre>
   
scheduler=schedule  ; name the stanza 'schedule'
 
scheduler=schedule  ; name the stanza 'schedule'
   Line 1,171: Line 1,062:  
;dtmf_function =  m h dom mon dow  ; ala cron, star is implied                                                   
 
;dtmf_function =  m h dom mon dow  ; ala cron, star is implied                                                   
 
2 = 00 00 * * *  ; at midnight every day, execute macro 2.
 
2 = 00 00 * * *  ; at midnight every day, execute macro 2.
</pre>
+
</syntaxhighlight>
    
=DAQ List Stanza=
 
=DAQ List Stanza=
Line 1,177: Line 1,068:  
=Meter Faces Stanza=
 
=Meter Faces Stanza=
   −
=Alarms Stanza=
+
=Alarms Stanza
 
  −
[[Category:Node Configuration]]
  −
[[Category:Config Files]]
 

Navigation menu