How to and Sundry

I have Allstar loaded on a HP, I see my node in the node lists, see my node on the map. so apparently I’ve made it past the registration and install. I’m waiting on an interface (URI or Master). From what I’ve been able to glean in the literature, one I have an interface installed, the connected radio is connected “by magic” to the Allstair and its a matter of key and call. Is that right or too simplistic. How does it work. Is there a “cheat sheet” or tutorial that shows a novice how Allstar/Asterisk connects to others, able to listen to others, etc?

I installed Allmon2 on the HP. All I get is a web page that tells what it is. What do I invoke to see what it offers?

Hi J_D, welcome to AllStar.

Once your URI arrives, that is basically your radio interface into your Node. Your Node is also essentially your Server. Both Node and Server are configured (some aspects) from the Allstar Portal, which I think you’re familiar with.

The URI (as well as other radio interfaces, including homebrew ones you can even make yourself) takes signals from the radio and make them available to your PC.

Depending on the make/model of your radio, the URI->radio connection options may vary.

More of the radio inter-connection info can be found here => https://wiki.allstarlink.org/wiki/Radio_Connections

Once your radio is connected and available on your Node/Server, others can dial your node number and connect their Node to yours… e.g. *3 12345 where 12345 is the node # etc.

More of the info on Node connection/disconnection can be found here => https://wiki.allstarlink.org/wiki/AllStar_Link_Standard_Commands

Active (online) Nodes are show on the Stats page => http://stats.allstarlink.org/
Nodes keyed-down right “now” are even shown here => http://stats.allstarlink.org/maps/allstarNodesMapKey.php

Everything runs on top of Asterisk and app_rpt. Allmon2, for example, connects to a manager port running underneath the Asterisk running on your node. Not sure of a good Wiki read for this one, but the Community board may have some posts here and there that get more into how the backend works.

Thanks Byron - that helps

Two questions.  Until I get the computer-radio interface delivered

and installed, is there a configuration where the “server” can
monitor connections and listen to the audio?

What changes are needed to the managers port to make Allmon2 work?

  jd
···

On 4/19/20 8:24 PM, Byron Felts via
AllStarLink Discussion Groups wrote:

k4sip
k4sip

              April 20

Hi J_D, welcome to
AllStar.

Once your URI arrives,
that is basically your radio interface into your Node.
Your Node is also essentially your Server. Both Node and
Server are configured (some aspects) from the Allstar
Portal, which I think you’re familiar with.

The URI (as well as
other radio interfaces, including homebrew ones you can
even make yourself) takes signals from the radio and make
them available to your PC.

Depending on the
make/model of your radio, the URI->radio connection
options may vary.

More of the radio
inter-connection info can be found here => https://wiki.allstarlink.org/wiki/Radio_Connections

Once your radio is
connected and available on your Node/Server, others can
dial your node number and connect their Node to yours…
e.g. *3 12345 where 12345 is the node # etc.

More of the info on Node
connection/disconnection can be found here => https://wiki.allstarlink.org/wiki/AllStar_Link_Standard_Commands

Active (online) Nodes
are show on the Stats page => http://stats.allstarlink.org/
Nodes keyed-down right “now” are even shown here => http://stats.allstarlink.org/maps/allstarNodesMapKey.php

Everything runs on top
of Asterisk and app_rpt. Allmon2, for example, connects to
a manager port running underneath the Asterisk running on
your node. Not sure of a good Wiki read for this one, but
the Community board may have some posts here and there
that get more into how the backend works.


Visit
Topic
or reply to this email to respond.

You are receiving this because you enabled mailing list
mode.

To unsubscribe from these emails, click here.

(Regarding getting Allmon2 to work)

If you’re running Allmon2 on your Pi node, it’s should just be working.

In /etc/asterisk/manager.conf there are lines that control what Allmon2 needs to connect to:

port = 5038

bindaddr = 127.0.0.1

[admin]
secret = yoursecret (whatever you chose for one in your initial install)

^^ These above items need to correspond with whatever you find set in the Allmon2 file, which is usually found at /etc/asterisk/allmon.ini.php.

In the allmon.ini.php file they look like this:

[12345] <— your node #
host=127.0.0.1:5038
user=admin
passwd=yoursecret
nomenu=no
hideNodeURL=no

If this isn’t just working as such right now, check the above items. See if they match each other, and see if that fixes the issue you might be having?

Reply back if you need more help.

Byron

Re-read your last reply again. Here are some more things to consider for monitoring your Node(s).

  1. You can use the Web Transceiver to monitor your Node… (requires Java, is not supported easily by many web browsers anymore… kind of a PITA to get going at first… This is a feature within the AllStarLink portal itself.
    Web Transceiver-capable Nodes are noted with a “wt” character, in this list => https://www.allstarlink.org/nodelist/ (Click the link, get the Web Transceiver for that node, try doing the same on yours?)

  2. You can enable IAXRPT support on your Server Node(s), and then use an app on your phone or computer to listen/transmit on your Nodes without a radio.
    Instructions for that here => https://wiki.allstarlink.org/wiki/Setup_IAXRPT_use
    IAXRPT windows client => http://dvswitch.org/files/AllStarLink/setup_iaxrpt_xipar_010146.exe

  3. You can also Icecast your Node audio out to an Icecast server. (Bit of setup before this works, but its an option) Once you Icecast your node audio, you can listen-only from pretty much any device. I don’t have a good recent thread to point you towards for this one, but there is this one => ices plugin

Good luck,
Byron

Thanmks Byron, that gives me something to
learn with on this rainy day

     jd
···

On 4/20/20 9:59 AM, Byron Felts via
AllStarLink Discussion Groups wrote:

k4sip
k4sip

              April 20

Re-read your last reply
again. Here are some more things to consider for
monitoring your Node(s).

  1. You can use the Web
    Transceiver to monitor your Node… (requires Java, is
    not supported easily by many web browsers anymore…
    kind of a PITA to get going at first… This is a
    feature within the AllStarLink portal itself.
    Web Transceiver-capable Nodes are noted with a “wt”
    character, in this list => https://www.allstarlink.org/nodelist/
    (Click the link, get the Web Transceiver for that
    node, try doing the same on yours?)
  1. You can enable
    IAXRPT support on your Server Node(s), and then use an
    app on your phone or computer to listen/transmit on
    your Nodes without a radio.
    Instructions for that here => https://wiki.allstarlink.org/wiki/Setup_IAXRPT_use
    IAXRPT windows client => http://dvswitch.org/files/AllStarLink/setup_iaxrpt_xipar_010146.exe
  1. You can also Icecast
    your Node audio out to an Icecast server. (Bit of
    setup before this works, but its an option) Once you
    Icecast your node audio, you can listen-only from
    pretty much any device. I don’t have a good recent
    thread to point you towards for this one, but there is
    this one => ices plugin

Good luck,
Byron


Visit Topic
or reply to this email to respond.


In Reply To

k4sip
k4sip

              April 20

(Regarding getting Allmon2 to
work) If you’re running Allmon2 on your Pi node, it’s should
just be working. In /etc/asterisk/manager.conf there are
lines that control what Allmon2 needs to connect to: port =
5038 … bindaddr = 127.0.0.1 … [admin] secret = yoursecret
(whatever you c…


Visit
Topic
or reply to this email to respond.

You are receiving this because you enabled mailing list
mode.

To unsubscribe from these emails, click here.

We hope it helped out and you stayed dry in the process!

Byron

I tried Bryon (to stay dry)

  Another question.  Is there a need/requirement for the 5-digit

nodes to move to 6-digit ones to make for more number
availability?

     jd
···

On 4/29/20 1:41 PM, Byron Felts via
AllStarLink Discussion Groups wrote:

k4sip
k4sip

              April 29

We hope it helped out
and you stayed dry in the process!

Byron


Visit Topic
or reply to this email to respond.


In Reply To

J_D
J_D

              April 20

Thanmks Byron, that gives me
something to learn with on this rainy day jd
··· (click for more details)


Visit
Topic
or reply to this email to respond.

You are receiving this because you enabled mailing list
mode.

To unsubscribe from these emails, click here.

Not really sure. I think it was just to increase availability of nodes overall.

Someone who knows can comment here and set that matter straight.

Byron

Yes that is the thought, we want to conserve 5 digit node numbers so that we do not run out.

Due to this COVID 19 thing, and everyone staying home, we are issuing a higher than normal amount of new node numbers this past month.

So, if you requested more than 2 node numbers we automatically deny the additional numbers. This is to conserve node numbers so that we do not run out. However, we have a workable solution which will provide up to 20 node numbers. We call it NNX. Please read about NNX nodes on our WiKi at

https://wiki.allstarlink.org/wiki/NNX.

The wiki page explains the very easy process to add additional node numbers without consuming additional resources. NNX also saves you time and assures your numbers are sequential.

If you really need more than 20 nodes please let us know in a message.

Thank you for your cooperation and understanding.

73

Marshall - ke6pcv

Tnx Marshall

  No, I'm only working on one node for now.  So I assume that I can

convert to six digits optionally but y’all would prefer it

     jd
···

On 5/1/20 3:56 PM, Marshall Oldham via
AllStarLink Discussion Groups wrote:

KE6PCV
KE6PCV ASL Admin

              May 1

Yes that is the thought,
we want to conserve 5 digit node numbers so that we do not
run out.

Due to this COVID 19
thing, and everyone staying home, we are issuing a higher
than normal amount of new node numbers this past month.

So, if you requested
more than 2 node numbers we automatically deny the
additional numbers. This is to conserve node numbers so
that we do not run out. However, we have a workable
solution which will provide up to 20 node numbers. We call
it NNX. Please read about NNX nodes on our WiKi at

https://wiki.allstarlink.org/wiki/NNX.

The wiki page explains
the very easy process to add additional node numbers
without consuming additional resources. NNX also saves you
time and assures your numbers are sequential.

If you really need more
than 20 nodes please let us know in a message.

Thank you for your
cooperation and understanding.

73

Marshall - ke6pcv


Visit Topic
or reply to this email to respond.


In Reply To

J_D
J_D

              May 1

I tried Bryon (to stay dry)
Another question. Is there a need/requirement for the
5-digit
nodes to move to 6-digit ones to make for more number
availability? jd
··· (click for more details)


Visit
Topic
or reply to this email to respond.

You are receiving this because you enabled mailing list
mode.

To unsubscribe from these emails, click here.

JD,

If your only using one node for now, just keep it as a 5 digit node number.

You can always change later to 6 digit if you need too.

73

Marshall

···

From: JD Delancy via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org]
Sent: Friday, May 01, 2020 5:55 PM
To: ke6pcv@cal-net.org
Subject: [AllStarLink Discussion Groups] [App_rpt-users] How to and Sundry

J_D
May 2

Tnx Marshall

  No, I'm only working on one node for now.  So I assume that I can

convert to six digits optionally but y’all would prefer it

     jd

··· (click for more details)


Visit Topic or reply to this email to respond.


In Reply To

KE6PCV ASL Admin
May 1

Yes that is the thought, we want to conserve 5 digit node numbers so that we do not run out. Due to this COVID 19 thing, and everyone staying home, we are issuing a higher than normal amount of new node numbers this past month. So, if you requested more than 2 node numbers we automatically deny th…

Previous Replies

KE6PCV ASL Admin
May 1

Yes that is the thought, we want to conserve 5 digit node numbers so that we do not run out.

Due to this COVID 19 thing, and everyone staying home, we are issuing a higher than normal amount of new node numbers this past month.

So, if you requested more than 2 node numbers we automatically deny the additional numbers. This is to conserve node numbers so that we do not run out. However, we have a workable solution which will provide up to 20 node numbers. We call it NNX. Please read about NNX nodes on our WiKi at

https://wiki.allstarlink.org/wiki/NNX.

The wiki page explains the very easy process to add additional node numbers without consuming additional resources. NNX also saves you time and assures your numbers are sequential.

If you really need more than 20 nodes please let us know in a message.

Thank you for your cooperation and understanding.

73

Marshall - ke6pcv

k4sip
May 1

Not really sure. I think it was just to increase availability of nodes overall.

Someone who knows can comment here and set that matter straight.

Byron

J_D
May 1

I tried Bryon (to stay dry)

  Another question.  Is there a need/requirement for the 5-digit

nodes to move to 6-digit ones to make for more number
availability?

     jd

··· (click for more details)

k4sip
April 29

We hope it helped out and you stayed dry in the process!

Byron

J_D
April 20

Thanmks Byron, that gives me something to
learn with on this rainy day

     jd

··· (click for more details)


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.