Total list of all Allstar commands

AllStarLink
1

Can some one point me to a listing of every available command defined that can used with Allstar.

I am have a heck of a time trying to configure my nodes so everything is all the same commands on all my nodes..
It seems whenever there is a different version other than the 1-5 ilink commands there is no standard numbering system between versions or platforms.
Realizing that it is up to me to standardize my own system I am about to start from scratch eliminating all the jumble.
It would certainly be helpful if there was a COMPLETE command list with explanations of their functions.

Larry - N7FM

2

in rpt.conf, (cut and paste ) the [functions] stanza to a seperate file labeled commands.include then delete or comment out all the commands in the stanza and replace with this line “#include commands.include” THEN put all the commands YOU want above and beyond what is required to be standard across everyones nodes 1-5 ilink etc. in the commands.include file. Use (winSCP) to copy the commands.include file to all your nodes and edit each nodes rpt.conf stanza to have the line in [functions] be #include commands.include. For each new system you just you build just add YOUR commands.include file and it will have all the same commands as the others.

…

outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - 2> /tmp/stream.status | /usr/bin/ezstream -qvc /etc/ezstream.xml

[functions]

#include commands.include

#include /etc/asterisk/local/localcmds.include

[morse]

speed=20

…

and a copy of a generic commands.include file for you to cut and paste if you wish.

root@N8THN:/etc/asterisk# cat commands.include

;commands.include

;Command common acrossed all nodes

;single digit public commands

0=autopatchdn

1=ilink,1 ; Disconnect Link

2=ilink,2 ; Connect Link MOnitor Only

3=ilink,3 ; Connect Link Transieve

4=ilink,4 ; Enter Command Mode on another Node

5=macro,1 ; Macro Prefix

6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up

;double digit public commands

70=ilink,5 ; System Status

71=ilink,6 ; Disconnect all Links

72=ilink,7 ; Play Last Node to Key Up

73=ilink,15 ; FULL system Status - all nodes

74=ilink,16 ; Reconnect disconnected links disconnected with disconnect all links command

75=ilink,8 ; Connect Link LOCAL monitor only

76=

77=

78=

79=

80=status,11 ;Force ID LOCAL ONLY

81=status,12 ; GIve Time of Day LOCAL ONLY

82=status,3 ; Give Software Verison

83=status,5 ; Last DTMF User

84=cop,32 ; DTMF TEST

85=

86=

87=

88=cop,55 ;Parrot Once if parrot mode is disabled

89=autopatchup,context=command_process,noct=1,farenddisconnect=1,dialtime=7000,quiet=1; Command Processing

99=cop,6 ; ptt phone mode

; Triple digit control operator /owner codes

900=cop,3 ;disable system

901=cop,2 ;enable system

903=cop,1 ;System warm boot

902=

903=

904=cop,4 ;Test Tone On/Off

905=cop,5 ;dump system variables

906=

907=cop,7 ;Time out timer enable

908=cop,8 ;Time out timer disable

909=cop,9 ;Autopatch enable

910=cop,10 ;Autopatch disable

911=cop,11 ;Link enable

912=cop,12 ;Link disable

913=cop,13 ;Query System State

914=cop,14 ;Change System State

915=cop,15 ;Scheduler Enable

916=cop,16 ;Scheduler Disable

917=cop,17 ;User functions (time, id, etc) enable

918=cop,18 ;User functions (time, id, etc) disable

919=cop,19 ;Select alternate hang timer

920=cop,20 ;Select standard hang timer

921=cop,21 ;Enable Parrot Mode

922=cop,22 ;Disable Parrot Mode

923=cop,23 ;Birdbath (Current Parrot Cleanup/Flush)

924=cop,24 ;Flush all telemetry

925=cop,25 ;Query !!!last node un-keyed!!!

926=cop,26 ;Query all nodes keyed/unkeyed

927=cop,27 ;Reset DAQ minimum on a pin

928=cop,28 ;Reset DAQ maximum on a pin

929=

930=cop,30 ;Recall Memory Setting in Attached Xcvr

931=cop,31 ;Channel Selector for Parallel Programmed Xcvr

932=

933=cop,33 ;Local Telemetry Output Enable

934=cop,34 ;Local Telemetry Output Disable

935=cop,35 ;Local Telemetry Output on Demand

936=cop,36 ;Foreign Link Local Output Path Enable

937=cop,37 ;Foreign Link Local Output Path Disable

938=cop,38 ;Foreign Link Local Output Path Follows Local Telemetry

939=cop,39 ;Foreign Link Local Output Path on Demand

940=cop,40 ;IRLP announce Enable

941=cop,41 ;IRLP announce Disable

942=cop,42 ;Echolink announce node # only

943=cop,43 ;Echolink announce node Callsign only

944=cop,44 ;Echolink announce node # & Callsign

945=cop,45 ;Link Activity timer enable

946=cop,46 ;Link Activity timer disable

947=cop,47 ;Reset “Link Config Changed” Flag

948=cop,48 ;Send Page-Tone specs separated by ( )

949=cop,49 ;Disable incoming connections (control state NOICE)

950=cop,50 ;Enable incoming connections (control state NOICD)

951=cop,51 ;Enable sleep mode

952=cop,52 ;Disable sleep mode

953=cop,53 ;Wake up from sleep

954=cop,54 ;Go to sleep

955=cop,60 ;SEND MDC-1200 Burst

956=cop,56 ;Rx CTCSS Enable

957=cop,57 ;Rx CTCSS Disable

958=cop,58 ;Tx CTCSS On Input only Enable

959=cop,59 ;Tx CTCSS On Input only Disable

; 98 series up to local nodes

···

On Fri, Jan 5, 2018 at 3:31 AM, larry larry@n7fm.com wrote:

Can some one point me to a listing of every available command defined that can used with Allstar.

I am have a heck of a time trying to configure my nodes so everything is all the same commands on all my nodes…

It seems whenever there is a different version other than the 1-5 ilink commands there is no standard numbering system between versions or platforms.

Realizing that it is up to me to standardize my own system I am about to start from scratch eliminating all the jumble.

It would certainly be helpful if there was a COMPLETE command list with explanations of their functions.

Larry - N7FM

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

–

Nathan Hardman

nhardman1428@gmail.com

N8THN@ARRL.NET

1 Like
3

The sample rpt.conf that is included with AllStarLink Asterisk is my attempt to include each command available. For the numbering system, except for a few commands, there is no standard. That is up to the node operator. The sample rpt.conf is at <https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf&gt; I'm sure I missed something. I would not be surprised if there are errors. As people point them out I'll make edits. We are working to fill out the wiki as the place to go for all things AllStarLink at <http://wiki.allstarlink.org/wiki/Main_Page&gt;

73, Steve N4IRS

···

On 1/5/2018 3:31 AM, larry wrote:

Can some one point me to a listing of every available command defined that can used with Allstar.

I am have a heck of a time trying to configure my nodes so everything is all the same commands on all my nodes..
It seems whenever there is a different version other than the 1-5 ilink commands there is no standard numbering system between versions or platforms.
Realizing that it is up to me to standardize my own system I am about to start from scratch eliminating all the jumble.
It would certainly be helpful if there was a COMPLETE command list with explanations of their functions.

Larry - N7FM
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

4

This needs to be called out.

If you can't code but you can write English, the wiki needs work. All you
need to do is signup online with your callsign and then start creating
content. Even if it's a minor edit, the only reason we have the accounts is
to prevent spam and defacement.

···

On 1/5/18 9:19 AM, Steve Zingman wrote:

We are working to fill out the
wiki as the place to go for all things AllStarLink at
<http://wiki.allstarlink.org/wiki/Main_Page&gt;

--
Bryan Fields

727-409-1194 - Voice
http://bryanfields.net

5

Thanks everyone for the feedback.

I didn't realize the WIKI was already up and running with so much updated info. All my searches including the old Drupal Site returned lists that were missing portions.

Well done Steve and to ALL that have contributed to the WIKI.

Larry - N7FM

···

On 01/05/2018 06:19 AM, Steve Zingman wrote:

The sample rpt.conf that is included with AllStarLink Asterisk is my attempt to include each command available. For the numbering system, except for a few commands, there is no standard. That is up to the node operator. The sample rpt.conf is at <https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf&gt; I'm sure I missed something. I would not be surprised if there are errors. As people point them out I'll make edits. We are working to fill out the wiki as the place to go for all things AllStarLink at <http://wiki.allstarlink.org/wiki/Main_Page&gt;

73, Steve N4IRS

On 1/5/2018 3:31 AM, larry wrote:

Can some one point me to a listing of every available command defined that can used with Allstar.

I am have a heck of a time trying to configure my nodes so everything is all the same commands on all my nodes..
It seems whenever there is a different version other than the 1-5 ilink commands there is no standard numbering system between versions or platforms.
Realizing that it is up to me to standardize my own system I am about to start from scratch eliminating all the jumble.
It would certainly be helpful if there was a COMPLETE command list with explanations of their functions.

Larry - N7FM
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

6

(Remember when the Pentium was discovered to have a bug that
approximated the mathematical results of some computations?
Yeah…that long ago)

  Anyway...did some digging, especially since more and more folks

are migrating to the Pi.

  But first: in order to implant these malware exploits, you have

to have access to the system. IF you are not practicing good
systems hygiene, and not keeping up to date, have a wide range of
ports open, etc…every port open is one more potential exploit.
Running web servers on the same host as app_rpt, for instance.
Having simple passwords for SSH login. Allowing ROOT login via
SSH. The list is long and ugly. But, but, but…the flexibility
of the event subsystem, macros, and dtmf functions really don’t
require anything other than the IAX2 port be opened to do 98% of
system maintenance. And if you really really need console access,
consider configuring a VPN with cryptographic id exchange. Limit
the attack surface…limit the possibility of exploit.

But, what about the Pi?

According to ARM themselves (),
the Raspberry Pi’s processor cores (for all versions) are affected.

    "The majority of Arm processors are not impacted by any

variation of this side-channel speculation mechanism. A
definitive list of the small subset of Arm-designed processors
that are susceptible can be found below.

The processor cores used by the Pis are:

of the attack (they are not listed at all, in fact, because there
is no known vulnerability to these attacks).

Spectre and Meltdown both require out-of-order execution. The Cortex-A7 used in the early Pi 2 and the Cortex A53 used in the later Pi 2 and the
Pi 3 is a strictly in-order architecture. The ARM11
used in the Pi 1 is partially out-of-order, but not in a way that
permits Spectre or Meltdown to work.

ARM confirms this : only a very limited
subset of ARM processors have hardware that makes them vulnerable
to Spectre, an even more limited subset are vulnerable to
Meltdown, and it’s believed that all of them permit mitigation of
the threat. Take that for what it’s worth.

  Bottom line, to me: should we worry about this?  Not to the point

of loosing sleep, at least on the allstar side of the house. It’s
something to be aware of, especially those running on Intel CPUs,
since the chance of it being exploited is greater than zero, but
the risk, at this point, of it happening is less than 100,
especially if you’ve locked down your ports on your ingress/egress
routers, have firewalls in place, etc., and generally practice
good system management and security hygiene.

  I'm thinking that when the necessary patches for the underlying

OS (Debian) are published, a side effort to respin the release
with the patches, after testing for performance and reliability of
the allstart code, be done and released, and that the USERS
implement the update. We can’t force anyone to do so…but, it’s
just doing the Right Thing to do so.

  Your Windows/Mac/etc desktop and office systems?  That's another

story. Keep a watch on the patch release cycles and fixes that
are offered from the software vendors. Apply them.

  Because these exploits use an acceleration feature in the

architecture to help them work faster…I’m predicting that any
software/OS patch to minimize the exposure will have a performance
hit, since it will essentially turn off a major pipeline speedup
function. So, wariness, both to prevent infection, as well as
implementing changes is certainly warranted.

Bryan

WB0YLE/W2FUV

···

https://developer.arm.com/support/security-updatenot

7

The functions in rpt.conf are touch tone pointers to the underlying command structure of app_rpt. For example 3 = ilink,3 in the functions stanza of rpt.conf means that when the touch tone function *3 is received the app_rpt command ilink 3 is executed, which, of course is the connect command.

This gives app_rpt unmatched flexibility. You could change what *3 does, although that would be ill advised. A better example would be ilink 6 which disconnects all nodes. You might prefer to use *86 rather than the current DIAL function *806 to disconnect all nodes. So in rpt.conf you would change 806 = ilink,6 to 86 = link,6.

DIAL has darn near all the app_rpt commands available mapped to touch tone functions. The complete list of all app_rpt commands is documented in the comments at the top of app_rpt.c available at https://github.com/AllStarLink/Asterisk/blob/master/asterisk/apps/app_rpt.c

···

On Fri, Jan 5, 2018 at 6:19 AM, Steve Zingman szingman@msgstor.com wrote:

The sample rpt.conf that is included with AllStarLink Asterisk is my attempt to include each command available. For the numbering system, except for a few commands, there is no standard. That is up to the node operator. The sample rpt.conf is at <https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf> I’m sure I missed something. I would not be surprised if there are errors. As people point them out I’ll make edits. We are working to fill out the wiki as the place to go for all things AllStarLink at <http://wiki.allstarlink.org/wiki/Main_Page>

73, Steve N4IRS

On 1/5/2018 3:31 AM, larry wrote:

Can some one point me to a listing of every available command defined that can used with Allstar.

I am have a heck of a time trying to configure my nodes so everything is all the same commands on all my nodes…

It seems whenever there is a different version other than the 1-5 ilink commands there is no standard numbering system between versions or platforms.

Realizing that it is up to me to standardize my own system I am about to start from scratch eliminating all the jumble.

It would certainly be helpful if there was a COMPLETE command list with explanations of their functions.

Larry - N7FM

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

–

Tim WD6AWP

8

Appreciate all the feedback Tim… and all

Have the listing all archived in my files finally.

Now I just need to reconfiguring all my nodes to be identical and

eliminate the confusion.

I have quite a mix of hardware and the different firmware versions

left things in a jumble between the different platforms.

Larry - N7FM
···

On 01/09/2018 08:09 PM, Tim Sawyer
wrote:

      The functions

in rpt.conf are touch tone pointers to the underlying command
structure of app_rpt. For example 3 = ilink,3 in the functions
stanza of rpt.conf means that when the touch tone function *3
is received the app_rpt command ilink 3 is executed, which, of
course is the connect command.

      This gives

app_rpt unmatched flexibility. You could change what *3 does,
although that would be ill advised. A better example would be
ilink 6 which disconnects all nodes. You might prefer to use
*86 rather than the current DIAL function *806 to disconnect
all nodes. So in rpt.conf you would change 806 = ilink,6 to 86
= link,6.

      DIAL has darn

near all the app_rpt commands available mapped to touch tone
functions. The complete list of all app_rpt commands is
documented in the comments at the top of app_rpt.c available
at https://github.com/AllStarLink/Asterisk/blob/master/asterisk/apps/app_rpt.c

      On Fri, Jan 5, 2018 at 6:19 AM, Steve

Zingman szingman@msgstor.com
wrote:

        The sample

rpt.conf that is included with AllStarLink Asterisk is my
attempt to include each command available. For the numbering
system, except for a few commands, there is no standard.
That is up to the node operator. The sample rpt.conf is at
<https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf >
I’m sure I missed something. I would not be surprised if
there are errors. As people point them out I’ll make edits.
We are working to fill out the wiki as the place to go for
all things AllStarLink at <http://wiki.allstarlink.org/wiki/Main_Page>

        73, Steve N4IRS




            On 1/5/2018 3:31 AM, larry wrote:

              Can some one point me to a listing of every available

command defined that can used with Allstar.

              I am have a heck of a time trying to configure my

nodes so everything is all the same commands on all my
nodes…

              It seems whenever there is a different version other

than the 1-5 ilink commands there is no standard
numbering system between versions or platforms.

              Realizing that it is up to me to standardize my own

system I am about to start from scratch eliminating
all the jumble.

              It would certainly be helpful if there was a COMPLETE

command list with explanations of their functions.

              Larry - N7FM

              _______________________________________________

              App_rpt-users mailing list

              App_rpt-users@lists.allstarlink.org

              [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



              To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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@lists.allstarlink.org

            [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



            To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

–
Tim WD6AWP




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit 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@lists.allstarlink.orghttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users