"PTTLink Wiki" - User contributions [en]

NNX

2020-05-24T14:42:59Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title. Replace xxxxx with your original node number.
rxchannel=DAHDI/pseudo ; Example Rx audio/signalling channel. There is no need to change what you have.
</pre>

and then change the nodes stanza

<pre>
[nodes]
xxxxx0 = radio@127.0.0.1:pppp/xxxxx0,NONE ; replace xxxxx with your original node number. If :pppp (the port number) exists do not change
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; Modify this line. Replace xxxxx with your original node number.

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is no different than building a new server, or exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:41:12Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title. Replace xxxxx with your original node number.
rxchannel=DAHDI/pseudo ; Example Rx audio/signalling channel. There is no need to change what you have.
</pre>

and then change the nodes stanza

<pre>
[nodes]
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE ; replace xxxxx with your original node number
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; Modify this line. Replace xxxxx with your original node number.

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is no different than building a new server, or exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:39:02Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title. Replace xxxxx with your original node number.
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; Modify this line. Replace xxxxx with your original node number.

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is no different than building a new server, or exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:38:21Z

Wd6awp: /* extensions.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; Modify this line. Replace xxxxx with your original node number.

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is no different than building a new server, or exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:33:32Z

Wd6awp: /* Add Subsequent NNX Node(s) */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is no different than building a new server, or exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:31:27Z

Wd6awp: /* Add Subsequent NNX Node(s) */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is exactly the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:30:44Z

Wd6awp: /* Add Subsequent NNX Node(s) */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add an NNX node to a new server, the process is the same as [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:24:49Z

Wd6awp: /* Add Subsequent NNX Node */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node(s) =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:24:00Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required syntax, do not change
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:22:38Z

Wd6awp: /* extensions.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upper case X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required as part of the port
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:22:10Z

Wd6awp: /* extensions.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN} ; the upcast X is required syntax, do not change.
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required as part of the port
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:20:47Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
In this example nnnnn is used to indicate your original node number. Just add a zero as above.

For ASL registration:
<pre>
register=nnnnn0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=nnnnn0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required as part of the port
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:17:25Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==

For ASL registration:
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this:
<pre>
register=#####0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required as part of the port
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:17:11Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==

For ASL registration:
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

HamVoIP registration will look like this
<pre>
register=#####0#pppp:password@register.hamvoip.org ; where #pppp is the port, the # is required as part of the port
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:10:41Z

Wd6awp: /* extensions.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

If the radio-secure stanza looks more like this, then change it.
<pre>
[radio-secure]
exten => xxxxx0,1,rpt,xxxxx0
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:02:31Z

Wd6awp: /* extensions.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in extensions.conf can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:01:55Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and then change the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T14:01:01Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf. First change the node number stanza title.
<pre>
[xxxxx0] ; node stanza title
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and and then the nodes stanza

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T13:57:56Z

Wd6awp: /* rpt.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changed on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T13:45:24Z

Wd6awp: /* Add Subsequent NNX Node */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

If you want to add another node to a new server see these instructions: [[Media:ASL two servers one netwrok.pdf|PDF explaining how to have two servers behind a NAT router.]]

NNX

2020-05-24T13:41:07Z

Wd6awp: /* Add Subsequent NNX Node */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as [[Two_Nodes_on_One_Server]].

NNX

2020-05-24T13:35:27Z

Wd6awp:

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

= Add Subsequent NNX Node =
If you want to add another node to the same server server, the process is exactly the same as ....

NNX

2020-05-24T11:07:01Z

Wd6awp: /* NNX on your AllStar Node */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number. Don't forget to make a backup copy of these files before any edits.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

NNX

2020-05-24T11:04:08Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure your new node number is registered and can connect.

NNX

2020-05-24T11:02:29Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@register.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure you new node number is registered and can connect.

NNX

2020-05-24T11:02:09Z

Wd6awp: /* iax.conf */

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@uregister.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure you new node number is registered and can connect.

NNX

2020-05-24T11:00:30Z

Wd6awp: Add example of how to change conf files for NNX.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers per current policy.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files include rpt.conf, extensions.conf, iax.conf and allmon.inc.php (if using Allmon2 or Subermon). Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

= NNX on your AllStar Node =
The existing node number must be changed by adding a zero. There are 3 files which require minor edits. These examples show xxxxx for your node number. In all examples you are simply adding a 0 to your existing node number.

== rpt.conf ==
The node number must be changes on two lines in rpt.conf
<pre>
[xxxxx0] ; node stanza
rxchannel=DAHDI/pseudo ; Rx audio/signalling channel
</pre>

and

<pre>
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your locak nodes, and private (off of allstar link) nodes here.
xxxxx0 = radio@127.0.0.1/xxxxx0,NONE
</pre>

== extensions.conf ==
The change in this file can vary depending on the vintage/distro of your node. But typically you modify this one line:
<pre>
[globals]
HOMENPA=714
NODE=xxxxx0 ; modify this line

[default]
exten => i,1,Hangup

[radio-secure]
exten => _XXXX!,n,rpt,${EXTEN}
</pre>

== iax.conf ==
<pre>
register=xxxxx0:password@us.reg.allstarlink.org
</pre>

That's it! Now restart your node for the changes to take effect. Make sure you new node number is registered and can connect.

NNX

2020-05-24T10:28:30Z

Wd6awp: /* Requirements */

Add or Change DTMF Functions

2020-05-04T15:37:59Z

Wd6awp: Add returns to clarify examples

[[category:How to]]
This howto explains how the DTMF function decoder works in app_rpt and how to add and change DTMF function codes.

How DTMF Function Decoding Works
The function decoder's job is to collect DTMF digits until a match with a command is found. The function decoder will start collecting digits when the start character (usually *) is seen, and will continue collecting until the digit time out is reached, or a match is found. The start character is not included in the match. The function decoder does not care what the state of COR or CTCSS are. In other words, if you unkey and re-key in the middle of entering a function, the unkey does not affect the digits collected. Four things will clear the collected digits in the function decoder:

Lack of a match and a digit timer time out.
The detection of another start character (usually *).
The recognition and execution of a valid DTMF command
The digit buffer is completely filled and no match is found

Matching Mechanism
A match occurs when the collected digits match a function on the right hand side of an entry in the function stanza. Here's an example:

[functions]
1=ilink,1
Above is an example of a function stanza with one entry defined. Since the start character is implied, it is not present on the right hand side of the entry. In this particular case, a *1 will execute the method 1 of the ilink function (which is disconnect link). Once a match is detected, any additional digits belong to the function which matched. In this particular case, the digits which follow *1 will be passed to the disconnect link function where it will attempt to make a match with a connected node.

The first match found will be the one which is chosen. What this means is that you cannot have two DTMF functions same sequence of digits and one having one additional digit because the shorter one will always win and be executed first.

Will not work as intended:

[functions]
80=ilink,1
800=ilink,2

Will work as intended:

[functions]
800=ilink,1
801=ilink,2

Function Classes And Methods
Let;s now devote our attention to the stuff on the right hand side of the equals sign. The right hand side is a list of arguments separated by commas. The first argument is the function class identifier which is a text string. The second argument can be a method number associated with the function class, one or more configuration arguments, or a combination of both. One example of a function class is the ilink used above. Another example would be the cop function class used for control operator functions. Additionally, instead of or in addition to a method number, the function class itself might accept additional arguments for customizing how it behaves. The autopatchup method is a good example of this:

6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000
A complete list of the function classes and methods are documented at the top of app_rpt.c source code file. The app_rpt source file is located in /usr/src/asterisk/apps on your ACID installation, and in the same directory on a Limey Linux installation after the getsrc script is executed in /usr/src.

User talk:Tmcsys

2020-04-12T22:49:38Z

Wd6awp: Welcome!

[]

User:Tmcsys

2020-04-12T22:49:38Z

Wd6awp: Creating user page for new user.

Tim, Todd, and Kevin on the Board can vouch for me.

Thanks

Undocumented

2019-12-18T19:48:22Z

Wd6awp: Removee connpgm and discpgm

The following parameters still need to be documented:
alt_functions
archivedir
ctgroup
dphone_functions
extnodefile
extnodes
idtime
iobase
iospeed
locallist
mars
memory
monminblocks
nobusyout
nodes
nolocallinkct
notelemtx
outxlat
parrot
parrottime
propagate_phonedtmf
rptnode
rptinactmacro Macro to execute when inactivity timer expires
rptinacttime Inactivity timer time in seconds (0 seconds disables feature)
rxnotch
simplexphonedelay
statpost_program
statpost_url
tonemacro
tonezone
txlimits

Rpt.conf

2019-12-18T19:46:36Z

Wd6awp: Added connpgm and discpgm

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/AllStarLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins.

=DTMF Commands=
DTMF commands are placed in any one of three [[Structure of Config Files|named stanzas]]. Function stanzas control access to DTMF commands that a user can issue from various
control points.
* The [[#Functions Stanza|fuctions stanza]] - to decode DTMF from the node's local receiver.
* The [[#Link Functions Stanza|link_functions stanza]] - to decode DTMF from linked nodes.
* The [[#Phone Functions Stanza|phone_functions stanza]] - to decode DTMF from telephone connects.

A function stanza key/value pair has the following format:

dtmfcommand=functionclass,[functionmethod],[parameters]
Where:
* dtmfcommand is a DTMF digit sequence '''minus''' the [[#funcchar=|start character]] (usually *)
* functionclass is a string which defines what class of command; link, status or COP
* functionmethod defines the optional method number to use in the function class.
* functionoptions are one or more optional comma separated parameters which further define a command.

==Status Commands==
Status commands (functioncalss 'status') provide general information about the node.

Sample:
<pre>
712 = status,12 ; Give Time of Day (local only)
</pre>

{| class="wikitable"
! Status !! Description
|-
| 1 || Force ID (global)
|-
| 2 || Give Time of Day (global)
|-
| 3 || Give software Version (global)
|-
| 4 || Give GPS location info
|-
| 5 || Speak the last (dtmf) user
|-
| 11 || Force ID (local only)
|-
| 12 || Give Time of Day (local only)
|}

==Link Commands==
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status.

Sample:
<pre>
3 = ilink,3 ; Connect specified link -- transceive
</pre>

{| class="wikitable"
! ilink !! Description
|-
| 1 || Disconnect specified link
|-
| 2 || Connect specified link -- monitor only
|-
| 3 || Connect specified link -- tranceive
|-
| 4 || Enter command mode on specified link
|-
| 5 || System status
|-
| 6 || Disconnect all links
|-
| 7 || Last Node to Key Up
|-
| 8 || Connect specified link -- local monitor only
|-
| 9 || Send Text Message (9,<destnodeno or 0 (for all)>,Message Text, etc.
|-
| 10 || Disconnect all RANGER links (except permalinks)
|-
| 11 || Disconnect a previously permanently connected link
|-
| 12 || Permanently connect specified link -- monitor only
|-
| 13 || Permanently connect specified link -- tranceive
|-
| 15 || Full system status (all nodes)
|-
| 16 || Reconnect links disconnected with "disconnect all links"
|-
| 17 || MDC test (for diag purposes)
|-
| 18 || Permanently Connect specified link -- local monitor only
|}

==COP Commands==
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference.

Sample:
<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.

<pre>900 = cop,48,#,3,#,6,0,7</pre>

{| class="wikitable"
|-
! COP !! Description
|-
| 1 || System warm boot
|-
| 2 || System enable
|-
| 3 || System disable
|-
| 4 || Test Tone On/Off
|-
| 5 || Dump System Variables on Console (debug)
|-
| 6 || PTT (phone mode only)
|-
| 7 || Time out timer enable
|-
| 8 || Time out timer disable
|-
| 9 || Autopatch enable
|-
| 10 || Autopatch disable
|-
| 11 || Link enable
|-
| 12 || Link disable
|-
| 13 || Query System State
|-
| 14 || Change System State
|-
| 15 || Scheduler Enable
|-
|-
| 16 || Scheduler Disable
|-
| 17 || User functions (time, id, etc) enable
|-
| 18 || User functions (time, id, etc) disable
|-
| 19 || Select alternate hang timer
|-
| 20 || Select standard hang timer
|-
| 21 || Enable Parrot Mode
|-
| 22 || Disable Parrot Mode
|-
| 23 || Birdbath (Current Parrot Cleanup/Flush)
|-
| 24 || Flush all telemetry
|-
| 25 || Query last node un-keyed
|-
| 26 || Query all nodes keyed/unkeyed
|-
| 27 || Reset DAQ minimum on a pin
|-
| 28 || Reset DAQ maximum on a pin
|-
| 30 || Recall Memory Setting in Attached Xcvr
|-
| 31 || Channel Selector for Parallel Programmed Xcvr
|-
| 32 || Touchtone pad test: command + Digit string + # to playback all digits pressed
|-
| 33 || Local Telemetry Output Enable
|-
| 34 || Local Telemetry Output Disable
|-
| 35 || Local Telemetry Output on Demand
|-
| 36 || Foreign Link Local Output Path Enable
|-
| 37 || Foreign Link Local Output Path Disable
|-
| 38 || Foreign Link Local Output Path Follows Local Telemetry
|-
| 39 || Foreign Link Local Output Path on Demand
|-
| 42 || Echolink announce node # only
|-
| 43 || Echolink announce node Callsign only
|-
| 44 || Echolink announce node # & Callsign
|-
| 45 || Link Activity timer enable
|-
| 46 || Link Activity timer disable
|-
| 47 || Reset "Link Config Changed" Flag
|-
| 48 || Send Page Tone (Tone specs separated by parenthesis)
|-
| 49 || Disable incoming connections (control state noice)
|-
| 50 || Enable incoming connections (control state noicd)
|-
| 51 || Enable sleep mode
|-
| 52 || Disable sleep mode
|-
| 53 || Wake up from sleep
|-
| 54 || Go to sleep
|-
| 55 || Parrot Once if parrot mode is disabled
|-
| 56 || Rx CTCSS Enable
|-
| 57 || Rx CTCSS Disable
|-
| 58 || Tx CTCSS On Input only Enable
|-
| 59 || Tx CTCSS On Input only Disable
|-
| 60 || Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])
Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call
(SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.
DestID and subcode are only specified for the 'C' type message.
UnitID is the local systems UnitID. DestID is the MDC1200 ID of
the radio being called, and the subcodes are as follows:
Subcode '8205' is Voice Selective Call for Spectra ('Call')
Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or
Astro-Saber('Call')
Subcode '810D' is Call Alert (like Maxtrac 'CA')
|-
| 61 || Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,GPIO4=1].....)
|-
| 62 || Send Message to USB to control GPIO pins, quietly (cop,62,GPIO1=0[,GPIO4=1].....)
|-
| 63 || Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])
|-
| 64 || Send pre-configred APRSTT notification, quietly (cop,64,CALL[,OVERLAYCHR])
|-
| 65 || Send POCSAG page (equipped channel types only)
|}

==Remote Base Commands==
Remote base commands (functionclass 'remote') provide remote base control. This stanza is [[Structure of Config Files#Settings to name other Stanzas|named by]] the remote base [[#Remote Base Functions=|Remote Base Functions]] key/value pair.

{| class="wikitable"
! remote !! Description
|-
| 1 || Retrieve Memory
|-
| 2 || Set freq.
|-
| 3 || Set tx PL tone
|-
| 4 || Set rx PL tone
|-
| 5 || Long status query
|-
| 99,CALLSIGN,LICENSETAG || Remote Base login
|-
| 100 || Rx PL off
|-
| 101 || Rx PL on
|-
| 102 || Tx PL off
|-
| 103 || Tx PL on
|-
| 104 || Low Power
|-
| 105 || Medium Power
|-
| 106 || High Power
|-
| 107 || Bump -20
|-
| 108 || Bump -100
|-
| 109 || Bump -500
|-
| 110 || Bump +20
|-
| 111 || Bump +100
|-
| 112 || Bump +500
|-
| 113 || Scan - slow
|-
| 114 || Scan - quick
|-
| 115 || Scan - fast
|-
| 116 || Scan + slow
|-
| 117 || Scan + quick
|-
| 118 || Scan + fast
|-
| 119 || Tune
|-
| 140 || Short status query
|-
| 210 || Send a *
|-
| 211 || Send a #
|}

Not all commands above are supported by all radios. For example radios which don't support SSB, would not be able to be placed in LSB or USB mode.

===Remote Base Login===
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:
<pre>
9139583 = remote,99,WB6NIL,G ; grant access to Jim (general)
9148351 = remote,99,WA6ZFT,E ; grant access to Steve (extra)
</pre>
When the remote base is disconnected from the originating node, the
user will be logged out.

The LICENSETAG argument is used to enforce
tx frequency limits. Need info [txlimits].

= Settings to name other Stanzas =
Within the node stanza, some key=value pairs point to other stanzas. This allows nodes on the same Asterisk/app_rpt server to have the same settings (without duplicate entries) or different settings in some cases. For example the phone patch command may be *6 on one node, yet *61 on another.

For example:
[1000]
functions=functionsVHF

[1001]
functions=functionsVHF

[1002]
functions=functionsUHF

[functionsVHF]
; Two meter Autopatch up is *6
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000
0=autopatchdn ; Autopatch down

[functionsUHF]
; 440 Autopatch up is *61
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
0=autopatchdn ; Autopatch down
* controlstates=
* functions=
* link_functions=
* macro=
* phone_functions=
* telemetry=
* wait_times=

=Node Number Stanza=
The node number stanza is the first stanza in rpt.conf.

<pre>
[1999] ; Replace with your assigned node number
</pre>

The node number stanza contains the following key/value pairs.
==althangtime===
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:
<pre>
althangtime=4000 ; 4 seconds
</pre>
==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.

Sample:
<pre>
beaconing=1 ;Set to 1 to beacon. Defaults to 0
</pre>
==callerid===
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows

<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.

==connpgm= and discpgm= ==

Runs user defined scripts. Example from https://www.qsl.net/k0kn/swissarmy_debian
<pre>
# Place these lines in rpt.conf for each node:
# connpgm=/home/kyle/swissarmy 1
# discpgm=/home/kyle/swissarmy 0
</pre>

==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.

<pre>
context=radio
</pre>

==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:
<pre>
controlstates = controlstates ; points to control state stanza

[controlstates]
0 = rptena,lnkena,apena,totena,ufena,noicd ; Normal operation
1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation
2 = rptena,lnkdis,apdis,totena,ufdis,noice ; Repeater only operation
</pre>

The [[#Control States Stanza|control state stanza]] describes these mnemonics.

==duplex===
The duplex key/value pairs sets the duplex mode for desired radio operation. Duplex mode 2 is the default if none specified.
{| class="wikitable"
! Duplex Mode !! Description
|-
| 0 || Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.
|-
| 1 || Half duplex with telemetry tones and hang time. Does not repeat audio. This mode is preferred when interfacing a simplex node.
|-
| 2 || Full Duplex with telemetry tones and hang time. This mode is preferred when interfacing a repeater.
|-
| 3 || Full Duplex with telemetry tones and hang time, but no repeated audio. [[Duplex Mode 3|See details]]
|-
| 4 || Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.
|}

Sample:
<pre>
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.
</pre>

==endchar===
This setting allows the end character used by some control functions to be changed. By default this is a #. The endchar value must not be the same as the funcchar default or overridden value.

==erxgain===
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node.

<pre>
erxgain = -3
</pre>

See [[:Category:How to|Echolink How to]]

==etxgain===
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node.

<pre>
etxgain = 3
</pre>

See [[:Category:How to|Echolink How to]]

==funcchar===
This setting can be used to change the default function starting character of * to something else. Please note that the new value chosen must not be the same as the default or overridden value for endchar=.

==functions===
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].

Sample:
<pre>
functions = functionsUHF ; pointer to 440 repeater functions stanza
</pre>

== GUI ==
{| class="wikitable"
!Key
!Valid Values
!Default
|-
|guilinkdefault
|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
|1
|-
|guilinkdynamic
|0 = disallow users to change the gui telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command
|1
|}

= Function Classes =
Function classes are names for categories of functions. There are several function classes defined. They are described in the table below:
{| class="wikitable"
!Class
!Description
|-
|cop
|Control operator commands
|-
|ilink
|Internet linking commands
|-
|status
|User Status Commands
|-
|autopatchup
|Autopatch up commands
|-
|autopatchdn
|Autopatch down commands
|-
|remote
|Remote base commands
|-
|macro
|Command Macros
|}
Most of the above command classes require a function method and possibly one or more additional command parameters. Function methods are discussed next.

= Function Methods =
Function methods are numbers which identify a specific function to execute within a function class. Function Methods are optional and in some cases should be omitted (Such as with the autopatchup method) A complete and up-to-date description of all functon methods can be found in the app_rpt.c source file. Some function methods are shown below as an example below:
1 - Force ID (global)
2 - Give Time of Day (global)
3 - Give software Version (global)
11 - Force ID (local only)
12 - Give Time of Day (local only)

= Function Options =
Some Function Methods can take function options. These are specified after the Function Method separated with commas. Not all commands require or take Function options. An example of a method which can accept Function Options is the autopatchup method.

= Putting it all Together =
A small excerpt from the function stanza of rpt.conf is hown below.
[functions]
1=ilink,1 ; Specific link disconnect
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000 ; Autopatch up
The above example contains DTMF functions with all of the parameters discussed on previous pages.

In the above example:
* *1 followed by a node number disconnects a specific link. The function class is ''ilink'' and the function method is ''1''
* *6 followed by a phone number brings up the autopatch with the function options specified. Note that there is no function method defined, but there are function options present.

==hangtime===
This controls the length of the repeater hang time. It is specified in milliseconds.

Sample:
<pre>
hangtime = 1000 ;Set hang time for 1 second
</pre>

==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.

Sample:
<pre>
holdofftelem = 1 ;Set to 1 to hold off. Default is 0
</pre>

== telemdefault= ==
<pre>
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= ==
<pre>
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= ==
<pre>
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= ==
<pre>
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===
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:
<pre>
idrecording = |iwa6zft/r ; Morse Code ID
</pre>
or
<pre>
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]]

==idtalkover===
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:
<pre>
idtalkover = |iwa6zft/r ; Morse Code ID
</pre>
or
<pre>
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]]

==inxlat===
The inxlat setting allows complete remapping of the funcchar and endchar digits to different digits or digit sequences.
inxlat acts on the digits received by the radio receiver on the node.

Format: inxlat = funchars,endchars,passchars,dialtone

where:

* funcchars is the digit or digit sequence to replace funcchar
* endchars is the digit or digit sequence to replace endchar
* passchars are the digits to pass through (can be used to block certain digits)
* dialtone is optional. Set to Y for dial tone on successful funcchars.

Sample:
<pre>
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys
</pre>

==link_functions===
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the link_functions stanza.

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:
<pre>
link_functions = functions ; pointer to the Link Function stanza
</pre>

==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.

Sample:
<pre>
linkmongain = -20 ; reduce link volume 20dB
</pre>

==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.

Sample:
<pre>
linktolink = yes ; set to yes to enable. Default is no.
</pre>

==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.

Sample:
<pre>
linkunkeyct = ct8 ; use courtesy tone 8
</pre>

==macro===
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts.

Sample:
<pre>
macro=macro ; use stanza names 'macros'

[macro]
1 = *32000*32001 ; connect to nodes 2000 and 2001
</pre>

==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.

Sample:
<pre>
nounkeyct = yes ; :(
</pre>

==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.

Sample:
<pre>
politeid = 30000 ; 30 seconds
</pre>

==propagate_dtmf===
Takes either yes or no. When set to yes, DTMF will be regenerated from out-of-band signalling or from from the receiver dtmf decoder whenever a function start character is NOT detected and command decoding has not begun. When set to no, no tones will be regenerated. The default for this setting is no.
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:
<pre>
propagate_dtmf = no
</pre>
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.

==remotect===
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:
<pre>
remotect = ct3 ; use courtesy tone 3
</pre>

==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.

Sample:
<pre>
rxburstfreq = 1000
</pre>

==rxburstthreshold===
In rx toneburst mode, specifies the minimum signal to noise ratio in db that qualifies a valid tone.
Defaults to 16 (db).

==rxbursttime===
For rx toneburst operation, specifies minimum amount of time that tone needs to be valid for recognition (in milliseconds). Defaults to 250.

==rxchannel===
The rxchannel key/value pair selects the radio interface. There must be one (and only one) rxchannel per node. The selections are:

{| class="wikitable"
! Value !! Description
|-
| dahdi/pseudo || No radio, used for hubs
|-
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]]
|-
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]]
|-
| voter/1990 || [[Voter.conf|RTCM]]
|-
| Pi/1 || Raspberry Pi PiTA
|-
| Dahdi/1 || PCI Quad card
|-
| Beagle/1 || BeagleBoard
|-
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP
|}
Sample:
<pre>
rxchannel = dahdi/pseudo ; No radio (hub)
</pre>

''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.

==scheduler===
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.

Sample:
<pre>
scheduler = schedule ; name scheduler to 'schedule'

[schedule]
...
</pre>

==sleeptime===
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep.

Sample:
<pre>
sleeptime = 300 ; go to sleep after 5 mins of no activity
</pre>

==startup_macro===
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.

Sample:
<pre>
startup_macro = *31000*31001*31002 ; Connect to 1000, 1001 and 1002 at startup
</pre>

==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.

Sample:
<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]]

==tailmessagetime===
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:
<pre>
tailmessagetime = 900000 ; 15 minutes between tail messages
</pre>

==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.

Sample:
<pre>
tailsquashedtime = 300000 ; 5 minutes
</pre>

==totime===
This defines the time out timer interval. The value is in milliseconds.

Sample:
<pre>
totime = 180000 ; 3 minutes
</pre>

==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.

Sample:
<pre>
unlinkedct = ct2 ; use courtesy tone 2
</pre>

==wait-times===
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].

Sample:
<pre>
wait-times = wait-times ; name wait-times to 'wait-times'
</pre>

=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'.

Sample:
<pre>
functions = functions ; name the functions stanza 'functions'

[functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Link Functions Stanza=
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:
<pre>
functions = functions ; name the functions stanza 'functions'
link_functions = functions ; use the same stanza

[functions]
...
</pre>
If a different set of either limited or more capable functions is desired:
<pre>
functions = functions ; name the functions stanza 'functions'
link_functions = my_link_functions ; use a different stanza

[functions]
...

[my_link_functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Phone Functions Stanza=
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:
<pre>
functions = functions ; name the functions stanza 'functions'
phone_functions = functions ; use the same stanza

[functions]
...
</pre>
If a different set of either limited or more capable functions is desired:
<pre>
functions = functions ; name the functions stanza 'functions'
phone_functions = my_phone_functions ; use a different stanza

[functions]
...

[my_phone_functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Macro Stanza=
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts.

Sample:
<pre>
macro=macro ; use stanza names 'macros'

[macro]
1 = *32000*32001 ; connect to nodes 2000 and 2001
</pre>

=Remote Base Stanza=
Here are [[Structure of Config Files|key/value pairs]] required to configure a remote base.

==authlevel===
The authlevel= key is used to enable or disable login requirements for a remote base.

* authlevel=0 Disables all access control (not recommended, unsecured)
* authlevel=1 Enables access control, and waits for key up before prompting for the access code
* authlevel=2 Enables access control, and prompts for the access code at the time of connection

Sample:
<pre>
autllevel = 0 ; allow all comers
</pre>

==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.

Sample:
<pre>
civaddr = 98 ; set CIV to 98
</pre>

==Remote Base functions===
functions= is a pointer to a remote base function stanza.

Sample:
<pre>
functions = functions-remote ; name the functions stanza 'functions-remote'

[functions-remote]
...
</pre>

See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].

==ioaddr===
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:
<pre>
ioaddr = 0x378 ; set RB-1 address
</pre>

==ioport===
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.

Sample:
<pre>
ioport = /dev/ttyS1 ; Linux com1
</pre>

==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.

Sample:
<pre>
phone_functions = functions-remote
</pre>

==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.

Sample:
<pre>
remote = xcat ; set xcat interface
</pre>

{| class="wikitable"
! Radio !! Value !! Comments
|-
| Dumb || y || Use for single channel remote base radios
|-
| FT-897 || ft897 || Must specify serial port using ioport=
|-
| TMG-707 || kenwood || Must specify serial port using ioport=
|-
| IC-706 || ic706 || Must specify serial port using ioport=. Must specify civaddr using civaddr=
|-
| TM-271 || tm271 || Must specify serial port using ioport=
|-
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=
|}

==remote_inact_timeout===

Specifies the amount of time without keying from the link. Set to 0 to disable timeout.

Sample:
<pre>
remote_inact_timeout = 0 ; do not time out
</pre>

==remote_timeout===
Session time out for remote base. Set to 0 to disable.

Sample:
<pre>
remote_timeout = 0 ; do not timeout
</pre>

==remote_timeout_warning===

==remote_timeout_freq===

==Remote Base rxchannel===
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:
<pre>
rxchannel = usbRadio/usb1
</pre>

==Sample Remote Configuration==
<pre>
[1234]
; Rx audio/signaling channel
rxchannel = Radio/usb

; Serial port for control
ioport = /dev/ttyS1

; Radio Type
remote = ft897

; Function list from link
functions = functions-remote

; Function list from phone
phone_functions = functions-remote

; Authorization level
authlevel = 0
</pre>

=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 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:
<pre>
[nodes]
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
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
2503 = radio@192.168.1.20:4570/2503,NONE ; Public node behind the same NAT router
</pre>
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=
This stanza is named by the telemetry= key/value pair. Telemetry entries can be shared across all nodes on the Asterisk/app_rpt server, or defined for each node. Can be a tone sequence, morse string, or a file as follows:

* |t - Tone escape sequence:
** Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude). Single frequencies are created by setting freq1 or freq2 to zero.
* |m - Morse escape sequence:
**Sends Morse code at the '''telemetry amplitude and telemetry frequency''' as defined in the [morse] section. Follow with an alphanumeric string.
* |i - Morse ID escape sequence:
**Sends Morse code at the '''ID amplitude and ID frequency''' as defined in the [morse] section. Follow with an alphanumeric string.
* Path to sound file:
**Specify the path to a sound file on the server. Do not include file extension.

Sample:
<pre>
[telemetry]
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2=|t(660,880,150,2048)
ct3=|t(440,0,150,4096)
ct4=|t(550,0,150,2048)
ct4=|t(2475,0,250,768)
ct5=|t(660,0,150,2048)
ct6=|t(880,0,150,2048)
ct7=|t(660,440,150,2048)
ct8=|t(700,1100,150,2048)
ct9=|t(1633,0,50,1000)(0,0,30,0)(1209,0,50,1000);
;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
remotetx=|t(880,0,150,2048)
remotemon=|t(1209,0,50,2048)
cmdmode=|t(900,903,200,2048)
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
patchup=rpt/callproceeding
patchdown=rpt/callterminated

What the numbers mean,
(000,000,010,000)
| | | |-------amplitude
| | |-------------duration
| |-------------------Tone 2
|-------------------------Tone 1

</pre>

=Morse Stanza=
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.

Sample:
<pre>
[morse]
speed = 20 ; Approximate speed in WPM
frequency = 900 ; Morse Telemetry Frequency
amplitude = 4096 ; Morse Telemetry Amplitude
idfrequency = 746 ; Morse ID Frequency
idamplitude = 768 ; Morse ID Amplitude
</pre>

=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.

Sample:
<pre>
wait-times = wait-times ; name the stanza 'wait-times'

[wait-times]
telemwait = 2000
idwait = 500
unkeywait = 2000
calltermwait = 2000
</pre>

=Remote Base Memory Stanza=
Remote base memories are in the format of:

memory = rxfreq,plfreq,txpower,offset,tone

Sample:
<pre>
[memory]
00 = 146.580,100.0,m
01 = 147.030,103.5,m+t
02 = 147.240,103.5,m+t
03 = 147.765,79.7,m-t
04 = 146.460,100.0,m
05 = 146.550,100.0,m
</pre>

=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.

{| class="wikitable"
! Nmemonic !! Description !! COP Method
|-
| rptena || Repeater Enable || 2
|-
| rptdis || Repeater Disable || 3
|-
| totena || Timeout Timer Enable || 7
|-
| totdis || Timeout Timer Disable || 8
|-
| apena || Autopatch Enable || 9
|-
| apdis || Autopatch Disable || 10
|-
| lnkena || Link Enable || 11
|-
| lnkdis || Link Disable || 12
|-
| skena || Scheduler Enable || 15
|-
| skdis || Scheduler Disable || 16
|-
| ufena || User Functions Enable || 17
|-
| ufdis || User Functions Disable || 18
|-
| atena || Alternate Hangtime Enable || 19
|-
| atdis || Alternate Hangtime Disable || 20
|-
| noice || No Incoming Connections Enable || 49
|-
| noicd || No Incoming Connections Disable || 50
|-
| slpen || Sleep Mode Enable || 51
|-
| slpds || Sleep Mode Disable || 52
|}

=Schedule Stanza=
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.

Sample:
<pre>
scheduler=schedule ; name the stanza 'schedule'

[schedule]
;dtmf_function = m h dom mon dow ; ala cron, star is implied
2 = 00 00 * * * ; at midnight every day, execute macro 2.
</pre>

=DAQ List Stanza=

=Meter Faces Stanza=

=Alarms Stanza=

[[Category:Node Configuration]]
[[Category:Config Files]]

Topic:Vc6d5zacjy9bgdg5

2019-12-02T04:20:42Z

Wd6awp (talk | contribs) commented on "For Any Pi 4?" (As there is no public version of ASL for the Pi4 yet, do we know if these instructions will work for any Raspberry Pi4?)

Admin Committee

2019-11-29T02:36:07Z

Wd6awp:

The Admin Committee/Team is the core server admins for AllStarLink.

Fundamentally it's a meritocracy, people who can get stuff done work with others to get stuff done. If you have the ability, time and want to help out, please reach out to an existing member or send an email to [mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org].

= Responsibilities =
The below are general responsibilities of the Admin Committee. This is not a complete list and we don't expect every member to be able to do everything.

* Maintain all AllStarLink services for the community
* Develop new methods and procedures enabling the goal of always available services
* Work with and take direction from the AllStarLink Board of Directors
* Communicate with the community via app_rpt list
* Work tickets in the helpdesk

= Qualifications =

We encourage anyone interested to assist and reach out to [mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org] or another admin team member if they want to help out. With many people working on the same problem we can make easy work.

* Express an interest in committing time to help
* Be well known to an existing member of the team
* Be present in the slack, email and possibly IRC channel
* Have time to devote to working tickets or working on the other parts of the project
* Protect the secure information of our members and do not disclose any sensitive information outside of the admin committee with out prior board approval.

= Needs =

The project has needs for anyone with any of the following skills:

* Front End HTML/PHP/SQL (LAMP programer)
* Linux sysadmin
* MariaDB
* Networking
* Perl (not for new use)
* Python
* Ansible/puppet
* Linux/KVM
* VMware
* more people to work tickets
* Technical Writers

Admin Committee

2019-11-29T02:35:18Z

Wd6awp: Remover inappropriate edit

The Admin Committee/Team is the core server admins for AllStarLink.

Fundamentally it's a meritocracy, people who can get stuff done work with others to get stuff done. If you have the ability, time and want to help out, please reach out to an existing member or send an email to [mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org].

= Responsibilities =
The below are general responsibilities of the Admin Committee. This is not a complete list and we don't expect every member to be able to do everything.

* Maintain all AllStarLink services for the community
* Develop new methods and procedures enabling the goal of always available services
* Work with and take direction from the AllStarLink Board of Directors
* Communicate with the community via app_rpt list
* Work tickets in the helpdesk

= Qualifications =

We encourage anyone interested to assist and reach out to [mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org] or another admin team member if they want to help out. With many people working on the same problem we can make easy work.

* Express an interest in committing time to help
* Be well known to an existing member of the team
* Be present in the slack, email and possibly IRC channel
* Have time to devote to working tickets or working on the other parts of the project
* Protect the secure information of our members and do not disclose any sensitive information outside of the admin committee with out prior board approval.

= Needs =

The project has needs for anyone with any of the following skills:

* Front End HTML/PHP/SQL
* Linux sysadmin
* MariaDB
* Networking
* Perl (not for new use)
* Python
* Ansible/puppet
* Linux/KVM
* VMware
* more people to work tickets
* Technical Writers

Two Nodes on One Server

2019-08-30T03:33:15Z

Wd6awp: /* Procedure */

[[category:How to]]

This how-to describes how to go from a 1 node system to a 2 node system.

Changing a system from one node to two nodes requires that 4 text files be modified:

extensions.conf

iax.conf

rpt.conf

usbradio.conf

=== USB Device Enumeration ===
Because of the way USB bus device identification works, new USB fobs must be added one at a time. In other words, you must have a working single node system before you can make it a two node system. This is because the USB channel driver remembers where all the previously defined nodes are located, and when it finds new hardware, it will find the next unassigned stanza in usbradio.conf and assign the new hardware to that node. It is very important the order that the USB fobs connected to the computer are not disturbed or plugged in to different USB sockets, as this will confuse the USB channel driver and require that usbradio.conf have all the interfaces removed or commented out and added back in one at a time.

=== A Word About USB Hubs ===
The use of USB hubs should be avoided if at all possible as we have found that some hubs corrupt the audio streams coming form and going to the USB fobs. If you must use a USB hub, use only multi-TT types, but be forewarned that you may have to test several models until you find one which works acceptably, if at all.

=== Procedure ===

The procedure to configure a Multi-node system consisting of fictional nodes 1234 and 5678 is as follows:
# Make backup copies of rpt.conf, extensions.conf, iax.conf, and usbradio.conf.
# Edit the usbradio.conf file. Make a copy of the [usb] stanza in usbradio.conf.
# Paste the copy just below the original stanza.
# Rename the stanza name of the copy to [usb1]
# Change the configuration settings of [usb1] to suit the new radio.
# Save the new usbradio.conf file.
# Edit the rpt.conf file. Make a copy of your Node stanza in rpt.conf
# Paste the copy just below the original node stanza 1234
# Change the node stanza of the copy to the new node number 5678. and change rxchannel to point to the name of the device in usbradio.conf

<code>[1234]</code>

<code>rxchannel=SimpleUSB/usb</code>

<code>.</code>

<code>.</code>

<code>.</code>

<code>[5678]</code>

<code>rxchannel=SimpleUSB/usb1</code>

<code>.</code>

<code>.</code>

<code>.</code>
# Change any configuration settings in the new node stanza to suit the new radio
# Add a second local entry for node 5678 to the nodes stanza to allow local connections to be made:
<code>[nodes]</code>

<code>1234 = radio@127.0.0.1/1234,NONE</code>

<code>5678 = radio@127.0.0.1/5678,NONE</code>
# Save the new rpt.conf file
# Edit the iax.conf file
# Add an additional register statement for the second node, 5678 just below the first statement.
<code>register=1234:12345678@register.allstarlink.org ; First Node</code>

<code>register=5678:12345678@register.allstarlink.org ; Second Node</code>
# Save the new iax.conf file.
# Edit the extensions.conf file
# Add the 5678 extension in the radio-secure context to call the rpt application using the new node number:
<code>[radio-secure]</code>

<code>exten => 1234,1,rpt,1234</code>

<code>exten => 5678,1,rpt,5678</code>
# Save extensions.conf and exit the text editor.
# Stop and restart asterisk
# Adjust the signal levels on the new interface using the usbradio audio setup procedure documented in the previous HOWTO. Issue the command radio active usb1 from the Asterisk CLI to switch to the new USB interface (usb1) before starting the audio adjustment process.

NNX

2019-08-19T21:38:02Z

Wd6awp:

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

Rpt.conf

2019-06-16T18:14:53Z

Wd6awp: /* duplex= */

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/AllStarLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins.

=DTMF Commands=
DTMF commands are placed in any one of three [[Structure of Config Files|named stanzas]]. Function stanzas control access to DTMF commands that a user can issue from various
control points.
* The [[#Functions Stanza|fuctions stanza]] - to decode DTMF from the node's local receiver.
* The [[#Link Functions Stanza|link_functions stanza]] - to decode DTMF from linked nodes.
* The [[#Phone Functions Stanza|phone_functions stanza]] - to decode DTMF from telephone connects.

A function stanza key/value pair has the following format:

dtmfcommand=functionclass,[functionmethod],[parameters]
Where:
* dtmfcommand is a DTMF digit sequence '''minus''' the [[#funcchar=|start character]] (usually *)
* functionclass is a string which defines what class of command; link, status or COP
* functionmethod defines the optional method number to use in the function class.
* functionoptions are one or more optional comma separated parameters which further define a command.

==Status Commands==
Status commands (functioncalss 'status') provide general information about the node.

Sample:
<pre>
712 = status,12 ; Give Time of Day (local only)
</pre>

{| class="wikitable"
! Status !! Description
|-
| 1 || Force ID (global)
|-
| 2 || Give Time of Day (global)
|-
| 3 || Give software Version (global)
|-
| 4 || Give GPS location info
|-
| 5 || Speak the last (dtmf) user
|-
| 11 || Force ID (local only)
|-
| 12 || Give Time of Day (local only)
|}

==Link Commands==
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status.

Sample:
<pre>
3 = ilink,3 ; Connect specified link -- transceive
</pre>

{| class="wikitable"
! ilink !! Description
|-
| 1 || Disconnect specified link
|-
| 2 || Connect specified link -- monitor only
|-
| 3 || Connect specified link -- tranceive
|-
| 4 || Enter command mode on specified link
|-
| 5 || System status
|-
| 6 || Disconnect all links
|-
| 7 || Last Node to Key Up
|-
| 8 || Connect specified link -- local monitor only
|-
| 9 || Send Text Message (9,<destnodeno or 0 (for all)>,Message Text, etc.
|-
| 10 || Disconnect all RANGER links (except permalinks)
|-
| 11 || Disconnect a previously permanently connected link
|-
| 12 || Permanently connect specified link -- monitor only
|-
| 13 || Permanently connect specified link -- tranceive
|-
| 15 || Full system status (all nodes)
|-
| 16 || Reconnect links disconnected with "disconnect all links"
|-
| 17 || MDC test (for diag purposes)
|-
| 18 || Permanently Connect specified link -- local monitor only
|}

==COP Commands==
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference.

Sample:
<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.

<pre>900 = cop,48,#,3,#,6,0,7</pre>

{| class="wikitable"
|-
! COP !! Description
|-
| 1 || System warm boot
|-
| 2 || System enable
|-
| 3 || System disable
|-
| 4 || Test Tone On/Off
|-
| 5 || Dump System Variables on Console (debug)
|-
| 6 || PTT (phone mode only)
|-
| 7 || Time out timer enable
|-
| 8 || Time out timer disable
|-
| 9 || Autopatch enable
|-
| 10 || Autopatch disable
|-
| 11 || Link enable
|-
| 12 || Link disable
|-
| 13 || Query System State
|-
| 14 || Change System State
|-
| 15 || Scheduler Enable
|-
|-
| 16 || Scheduler Disable
|-
| 17 || User functions (time, id, etc) enable
|-
| 18 || User functions (time, id, etc) disable
|-
| 19 || Select alternate hang timer
|-
| 20 || Select standard hang timer
|-
| 21 || Enable Parrot Mode
|-
| 22 || Disable Parrot Mode
|-
| 23 || Birdbath (Current Parrot Cleanup/Flush)
|-
| 24 || Flush all telemetry
|-
| 25 || Query last node un-keyed
|-
| 26 || Query all nodes keyed/unkeyed
|-
| 27 || Reset DAQ minimum on a pin
|-
| 28 || Reset DAQ maximum on a pin
|-
| 30 || Recall Memory Setting in Attached Xcvr
|-
| 31 || Channel Selector for Parallel Programmed Xcvr
|-
| 32 || Touchtone pad test: command + Digit string + # to playback all digits pressed
|-
| 33 || Local Telemetry Output Enable
|-
| 34 || Local Telemetry Output Disable
|-
| 35 || Local Telemetry Output on Demand
|-
| 36 || Foreign Link Local Output Path Enable
|-
| 37 || Foreign Link Local Output Path Disable
|-
| 38 || Foreign Link Local Output Path Follows Local Telemetry
|-
| 39 || Foreign Link Local Output Path on Demand
|-
| 42 || Echolink announce node # only
|-
| 43 || Echolink announce node Callsign only
|-
| 44 || Echolink announce node # & Callsign
|-
| 45 || Link Activity timer enable
|-
| 46 || Link Activity timer disable
|-
| 47 || Reset "Link Config Changed" Flag
|-
| 48 || Send Page Tone (Tone specs separated by parenthesis)
|-
| 49 || Disable incoming connections (control state noice)
|-
| 50 || Enable incoming connections (control state noicd)
|-
| 51 || Enable sleep mode
|-
| 52 || Disable sleep mode
|-
| 53 || Wake up from sleep
|-
| 54 || Go to sleep
|-
| 55 || Parrot Once if parrot mode is disabled
|-
| 56 || Rx CTCSS Enable
|-
| 57 || Rx CTCSS Disable
|-
| 58 || Tx CTCSS On Input only Enable
|-
| 59 || Tx CTCSS On Input only Disable
|-
| 60 || Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])
Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call
(SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.
DestID and subcode are only specified for the 'C' type message.
UnitID is the local systems UnitID. DestID is the MDC1200 ID of
the radio being called, and the subcodes are as follows:
Subcode '8205' is Voice Selective Call for Spectra ('Call')
Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or
Astro-Saber('Call')
Subcode '810D' is Call Alert (like Maxtrac 'CA')
|-
| 61 || Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,GPIO4=1].....)
|-
| 62 || Send Message to USB to control GPIO pins, quietly (cop,62,GPIO1=0[,GPIO4=1].....)
|-
| 63 || Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])
|-
| 64 || Send pre-configred APRSTT notification, quietly (cop,64,CALL[,OVERLAYCHR])
|-
| 65 || Send POCSAG page (equipped channel types only)
|}

==Remote Base Commands==
Remote base commands (functionclass 'remote') provide remote base control. This stanza is [[Structure of Config Files#Settings to name other Stanzas|named by]] the remote base [[#Remote Base Functions=|Remote Base Functions]] key/value pair.

{| class="wikitable"
! remote !! Description
|-
| 1 || Retrieve Memory
|-
| 2 || Set freq.
|-
| 3 || Set tx PL tone
|-
| 4 || Set rx PL tone
|-
| 5 || Long status query
|-
| 99,CALLSIGN,LICENSETAG || Remote Base login
|-
| 100 || Rx PL off
|-
| 101 || Rx PL on
|-
| 102 || Tx PL off
|-
| 103 || Tx PL on
|-
| 104 || Low Power
|-
| 105 || Medium Power
|-
| 106 || High Power
|-
| 107 || Bump -20
|-
| 108 || Bump -100
|-
| 109 || Bump -500
|-
| 110 || Bump +20
|-
| 111 || Bump +100
|-
| 112 || Bump +500
|-
| 113 || Scan - slow
|-
| 114 || Scan - quick
|-
| 115 || Scan - fast
|-
| 116 || Scan + slow
|-
| 117 || Scan + quick
|-
| 118 || Scan + fast
|-
| 119 || Tune
|-
| 140 || Short status query
|-
| 210 || Send a *
|-
| 211 || Send a #
|}

Not all commands above are supported by all radios. For example radios which don't support SSB, would not be able to be placed in LSB or USB mode.

===Remote Base Login===
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:
<pre>
9139583 = remote,99,WB6NIL,G ; grant access to Jim (general)
9148351 = remote,99,WA6ZFT,E ; grant access to Steve (extra)
</pre>
When the remote base is disconnected from the originating node, the
user will be logged out.

The LICENSETAG argument is used to enforce
tx frequency limits. Need info [txlimits].

= Settings to name other Stanzas =
Within the node stanza, some key=value pairs point to other stanzas. This allows nodes on the same Asterisk/app_rpt server to have the same settings (without duplicate entries) or different settings in some cases. For example the phone patch command may be *6 on one node, yet *61 on another.

For example:
[1000]
functions=functionsVHF

[1001]
functions=functionsVHF

[1002]
functions=functionsUHF

[functionsVHF]
; Two meter Autopatch up is *6
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000
0=autopatchdn ; Autopatch down

[functionsUHF]
; 440 Autopatch up is *61
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
0=autopatchdn ; Autopatch down
* controlstates=
* functions=
* link_functions=
* macro=
* phone_functions=
* telemetry=
* wait_times=

=Node Number Stanza=
The node number stanza is the first stanza in rpt.conf.

<pre>
[1999] ; Replace with your assigned node number
</pre>

The node number stanza contains the following key/value pairs.
==althangtime===
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:
<pre>
althangtime=4000 ; 4 seconds
</pre>
==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.

Sample:
<pre>
beaconing=1 ;Set to 1 to beacon. Defaults to 0
</pre>
==callerid===
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows

<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.

==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.

<pre>
context=radio
</pre>

==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:
<pre>
controlstates = controlstates ; points to control state stanza

[controlstates]
0 = rptena,lnkena,apena,totena,ufena,noicd ; Normal operation
1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation
2 = rptena,lnkdis,apdis,totena,ufdis,noice ; Repeater only operation
</pre>

The [[#Control States Stanza|control state stanza]] describes these mnemonics.

==duplex===
The duplex key/value pairs sets the duplex mode for desired radio operation. Duplex mode 2 is the default if none specified.
{| class="wikitable"
! Duplex Mode !! Description
|-
| 0 || Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.
|-
| 1 || Half duplex with telemetry tones and hang time. Does not repeat audio. This mode is preferred when interfacing a simplex node.
|-
| 2 || Full Duplex with telemetry tones and hang time. This mode is preferred when interfacing a repeater.
|-
| 3 || Full Duplex with telemetry tones and hang time, but no repeated audio. [[Duplex Mode 3|See details]]
|-
| 4 || Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.
|}

Sample:
<pre>
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.
</pre>

==endchar===
This setting allows the end character used by some control functions to be changed. By default this is a #. The endchar value must not be the same as the funcchar default or overridden value.

==erxgain===
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node.

<pre>
erxgain = -3
</pre>

See [[:Category:How to|Echolink How to]]

==etxgain===
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node.

<pre>
etxgain = 3
</pre>

See [[:Category:How to|Echolink How to]]

==funcchar===
This setting can be used to change the default function starting character of * to something else. Please note that the new value chosen must not be the same as the default or overridden value for endchar=.

==functions===
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].

Sample:
<pre>
functions = functionsUHF ; pointer to 440 repeater functions stanza
</pre>

== GUI ==
{| class="wikitable"
!Key
!Valid Values
!Default
|-
|guilinkdefault
|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
|1
|-
|guilinkdynamic
|0 = disallow users to change the gui telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command
|1
|}

= Function Classes =
Function classes are names for categories of functions. There are several function classes defined. They are described in the table below:
{| class="wikitable"
!Class
!Description
|-
|cop
|Control operator commands
|-
|ilink
|Internet linking commands
|-
|status
|User Status Commands
|-
|autopatchup
|Autopatch up commands
|-
|autopatchdn
|Autopatch down commands
|-
|remote
|Remote base commands
|-
|macro
|Command Macros
|}
Most of the above command classes require a function method and possibly one or more additional command parameters. Function methods are discussed next.

= Function Methods =
Function methods are numbers which identify a specific function to execute within a function class. Function Methods are optional and in some cases should be omitted (Such as with the autopatchup method) A complete and up-to-date description of all functon methods can be found in the app_rpt.c source file. Some function methods are shown below as an example below:
1 - Force ID (global)
2 - Give Time of Day (global)
3 - Give software Version (global)
11 - Force ID (local only)
12 - Give Time of Day (local only)

= Function Options =
Some Function Methods can take function options. These are specified after the Function Method separated with commas. Not all commands require or take Function options. An example of a method which can accept Function Options is the autopatchup method.

= Putting it all Together =
A small excerpt from the function stanza of rpt.conf is hown below.
[functions]
1=ilink,1 ; Specific link disconnect
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000 ; Autopatch up
The above example contains DTMF functions with all of the parameters discussed on previous pages.

In the above example:
* *1 followed by a node number disconnects a specific link. The function class is ''ilink'' and the function method is ''1''
* *6 followed by a phone number brings up the autopatch with the function options specified. Note that there is no function method defined, but there are function options present.

==hangtime===
This controls the length of the repeater hang time. It is specified in milliseconds.

Sample:
<pre>
hangtime = 1000 ;Set hang time for 1 second
</pre>

==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.

Sample:
<pre>
holdofftelem = 1 ;Set to 1 to hold off. Default is 0
</pre>

== telemdefault= ==
<pre>
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= ==
<pre>
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= ==
<pre>
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= ==
<pre>
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===
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:
<pre>
idrecording = |iwa6zft/r ; Morse Code ID
</pre>
or
<pre>
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]]

==idtalkover===
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:
<pre>
idtalkover = |iwa6zft/r ; Morse Code ID
</pre>
or
<pre>
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]]

==inxlat===
The inxlat setting allows complete remapping of the funcchar and endchar digits to different digits or digit sequences.
inxlat acts on the digits received by the radio receiver on the node.

Format: inxlat = funchars,endchars,passchars,dialtone

where:

* funcchars is the digit or digit sequence to replace funcchar
* endchars is the digit or digit sequence to replace endchar
* passchars are the digits to pass through (can be used to block certain digits)
* dialtone is optional. Set to Y for dial tone on successful funcchars.

Sample:
<pre>
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys
</pre>

==link_functions===
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the link_functions stanza.

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:
<pre>
link_functions = functions ; pointer to the Link Function stanza
</pre>

==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.

Sample:
<pre>
linkmongain = -20 ; reduce link volume 20dB
</pre>

==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.

Sample:
<pre>
linktolink = yes ; set to yes to enable. Default is no.
</pre>

==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.

Sample:
<pre>
linkunkeyct = ct8 ; use courtesy tone 8
</pre>

==macro===
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts.

Sample:
<pre>
macro=macro ; use stanza names 'macros'

[macro]
1 = *32000*32001 ; connect to nodes 2000 and 2001
</pre>

==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.

Sample:
<pre>
nounkeyct = yes ; :(
</pre>

==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.

Sample:
<pre>
politeid = 30000 ; 30 seconds
</pre>

==propagate_dtmf===
Takes either yes or no. When set to yes, DTMF will be regenerated from out-of-band signalling or from from the receiver dtmf decoder whenever a function start character is NOT detected and command decoding has not begun. When set to no, no tones will be regenerated. The default for this setting is no.
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:
<pre>
propagate_dtmf = no
</pre>
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.

==remotect===
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:
<pre>
remotect = ct3 ; use courtesy tone 3
</pre>

==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.

Sample:
<pre>
rxburstfreq = 1000
</pre>

==rxburstthreshold===
In rx toneburst mode, specifies the minimum signal to noise ratio in db that qualifies a valid tone.
Defaults to 16 (db).

==rxbursttime===
For rx toneburst operation, specifies minimum amount of time that tone needs to be valid for recognition (in milliseconds). Defaults to 250.

==rxchannel===
The rxchannel key/value pair selects the radio interface. There must be one (and only one) rxchannel per node. The selections are:

{| class="wikitable"
! Value !! Description
|-
| dahdi/pseudo || No radio, used for hubs
|-
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]]
|-
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]]
|-
| voter/1990 || [[Voter.conf|RTCM]]
|-
| Pi/1 || Raspberry Pi PiTA
|-
| Dahdi/1 || PCI Quad card
|-
| Beagle/1 || BeagleBoard
|-
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP
|}
Sample:
<pre>
rxchannel = dahdi/pseudo ; No radio (hub)
</pre>

''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.

==scheduler===
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.

Sample:
<pre>
scheduler = schedule ; name scheduler to 'schedule'

[schedule]
...
</pre>

==sleeptime===
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep.

Sample:
<pre>
sleeptime = 300 ; go to sleep after 5 mins of no activity
</pre>

==startup_macro===
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.

Sample:
<pre>
startup_macro = *31000*31001*31002 ; Connect to 1000, 1001 and 1002 at startup
</pre>

==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.

Sample:
<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]]

==tailmessagetime===
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:
<pre>
tailmessagetime = 900000 ; 15 minutes between tail messages
</pre>

==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.

Sample:
<pre>
tailsquashedtime = 300000 ; 5 minutes
</pre>

==totime===
This defines the time out timer interval. The value is in milliseconds.

Sample:
<pre>
totime = 180000 ; 3 minutes
</pre>

==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.

Sample:
<pre>
unlinkedct = ct2 ; use courtesy tone 2
</pre>

==wait-times===
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].

Sample:
<pre>
wait-times = wait-times ; name wait-times to 'wait-times'
</pre>

=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'.

Sample:
<pre>
functions = functions ; name the functions stanza 'functions'

[functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Link Functions Stanza=
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:
<pre>
functions = functions ; name the functions stanza 'functions'
link_functions = functions ; use the same stanza

[functions]
...
</pre>
If a different set of either limited or more capable functions is desired:
<pre>
functions = functions ; name the functions stanza 'functions'
link_functions = my_link_functions ; use a different stanza

[functions]
...

[my_link_functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Phone Functions Stanza=
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:
<pre>
functions = functions ; name the functions stanza 'functions'
phone_functions = functions ; use the same stanza

[functions]
...
</pre>
If a different set of either limited or more capable functions is desired:
<pre>
functions = functions ; name the functions stanza 'functions'
phone_functions = my_phone_functions ; use a different stanza

[functions]
...

[my_phone_functions]
...
</pre>
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.

=Macro Stanza=
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts.

Sample:
<pre>
macro=macro ; use stanza names 'macros'

[macro]
1 = *32000*32001 ; connect to nodes 2000 and 2001
</pre>

=Remote Base Stanza=
Here are [[Structure of Config Files|key/value pairs]] required to configure a remote base.

==authlevel===
The authlevel= key is used to enable or disable login requirements for a remote base.

* authlevel=0 Disables all access control (not recommended, unsecured)
* authlevel=1 Enables access control, and waits for key up before prompting for the access code
* authlevel=2 Enables access control, and prompts for the access code at the time of connection

Sample:
<pre>
autllevel = 0 ; allow all comers
</pre>

==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.

Sample:
<pre>
civaddr = 98 ; set CIV to 98
</pre>

==Remote Base functions===
functions= is a pointer to a remote base function stanza.

Sample:
<pre>
functions = functions-remote ; name the functions stanza 'functions-remote'

[functions-remote]
...
</pre>

See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].

==ioaddr===
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:
<pre>
ioaddr = 0x378 ; set RB-1 address
</pre>

==ioport===
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.

Sample:
<pre>
ioport = /dev/ttyS1 ; Linux com1
</pre>

==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.

Sample:
<pre>
phone_functions = functions-remote
</pre>

==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.

Sample:
<pre>
remote = xcat ; set xcat interface
</pre>

{| class="wikitable"
! Radio !! Value !! Comments
|-
| Dumb || y || Use for single channel remote base radios
|-
| FT-897 || ft897 || Must specify serial port using ioport=
|-
| TMG-707 || kenwood || Must specify serial port using ioport=
|-
| IC-706 || ic706 || Must specify serial port using ioport=. Must specify civaddr using civaddr=
|-
| TM-271 || tm271 || Must specify serial port using ioport=
|-
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=
|}

==remote_inact_timeout===

Specifies the amount of time without keying from the link. Set to 0 to disable timeout.

Sample:
<pre>
remote_inact_timeout = 0 ; do not time out
</pre>

==remote_timeout===
Session time out for remote base. Set to 0 to disable.

Sample:
<pre>
remote_timeout = 0 ; do not timeout
</pre>

==remote_timeout_warning===

==remote_timeout_freq===

==Remote Base rxchannel===
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:
<pre>
rxchannel = usbRadio/usb1
</pre>

==Sample Remote Configuration==
<pre>
[1234]
; Rx audio/signaling channel
rxchannel = Radio/usb

; Serial port for control
ioport = /dev/ttyS1

; Radio Type
remote = ft897

; Function list from link
functions = functions-remote

; Function list from phone
phone_functions = functions-remote

; Authorization level
authlevel = 0
</pre>

=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 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:
<pre>
[nodes]
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
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
2503 = radio@192.168.1.20:4570/2503,NONE ; Public node behind the same NAT router
</pre>
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=
This stanza is named by the telemetry= key/value pair. Telemetry entries can be shared across all nodes on the Asterisk/app_rpt server, or defined for each node. Can be a tone sequence, morse string, or a file as follows:

* |t - Tone escape sequence:
** Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude). Single frequencies are created by setting freq1 or freq2 to zero.
* |m - Morse escape sequence:
**Sends Morse code at the '''telemetry amplitude and telemetry frequency''' as defined in the [morse] section. Follow with an alphanumeric string.
* |i - Morse ID escape sequence:
**Sends Morse code at the '''ID amplitude and ID frequency''' as defined in the [morse] section. Follow with an alphanumeric string.
* Path to sound file:
**Specify the path to a sound file on the server. Do not include file extension.

Sample:
<pre>
[telemetry]
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2=|t(660,880,150,2048)
ct3=|t(440,0,150,4096)
ct4=|t(550,0,150,2048)
ct4=|t(2475,0,250,768)
ct5=|t(660,0,150,2048)
ct6=|t(880,0,150,2048)
ct7=|t(660,440,150,2048)
ct8=|t(700,1100,150,2048)
ct9=|t(1633,0,50,1000)(0,0,30,0)(1209,0,50,1000);
;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
remotetx=|t(880,0,150,2048)
remotemon=|t(1209,0,50,2048)
cmdmode=|t(900,903,200,2048)
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
patchup=rpt/callproceeding
patchdown=rpt/callterminated

What the numbers mean,
(000,000,010,000)
| | | |-------amplitude
| | |-------------duration
| |-------------------Tone 2
|-------------------------Tone 1

</pre>

=Morse Stanza=
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.

Sample:
<pre>
[morse]
speed = 20 ; Approximate speed in WPM
frequency = 900 ; Morse Telemetry Frequency
amplitude = 4096 ; Morse Telemetry Amplitude
idfrequency = 746 ; Morse ID Frequency
idamplitude = 768 ; Morse ID Amplitude
</pre>

=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.

Sample:
<pre>
wait-times = wait-times ; name the stanza 'wait-times'

[wait-times]
telemwait = 2000
idwait = 500
unkeywait = 2000
calltermwait = 2000
</pre>

=Remote Base Memory Stanza=
Remote base memories are in the format of:

memory = rxfreq,plfreq,txpower,offset,tone

Sample:
<pre>
[memory]
00 = 146.580,100.0,m
01 = 147.030,103.5,m+t
02 = 147.240,103.5,m+t
03 = 147.765,79.7,m-t
04 = 146.460,100.0,m
05 = 146.550,100.0,m
</pre>

=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.

{| class="wikitable"
! Nmemonic !! Description !! COP Method
|-
| rptena || Repeater Enable || 2
|-
| rptdis || Repeater Disable || 3
|-
| totena || Timeout Timer Enable || 7
|-
| totdis || Timeout Timer Disable || 8
|-
| apena || Autopatch Enable || 9
|-
| apdis || Autopatch Disable || 10
|-
| lnkena || Link Enable || 11
|-
| lnkdis || Link Disable || 12
|-
| skena || Scheduler Enable || 15
|-
| skdis || Scheduler Disable || 16
|-
| ufena || User Functions Enable || 17
|-
| ufdis || User Functions Disable || 18
|-
| atena || Alternate Hangtime Enable || 19
|-
| atdis || Alternate Hangtime Disable || 20
|-
| noice || No Incoming Connections Enable || 49
|-
| noicd || No Incoming Connections Disable || 50
|-
| slpen || Sleep Mode Enable || 51
|-
| slpds || Sleep Mode Disable || 52
|}

=Schedule Stanza=
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.

Sample:
<pre>
scheduler=schedule ; name the stanza 'schedule'

[schedule]
;dtmf_function = m h dom mon dow ; ala cron, star is implied
2 = 00 00 * * * ; at midnight every day, execute macro 2.
</pre>

=DAQ List Stanza=

=Meter Faces Stanza=

=Alarms Stanza=

[[Category:Node Configuration]]
[[Category:Config Files]]

Duplex Mode 3

2019-06-16T18:10:44Z

Wd6awp:

This duplex mode allows a repeater (rather than app_rpt) to perform the repeat function. This is also known as in-cabinet repeat. Duplex Mode 3 is unique to repeaters and is not likely to be used on simplex, half-duplex nodes or hotspots. Setting '''duplex=3''' in rpt.conf prevents Rx repeater audio from being sent to the repeater Tx. However, courtesy tones, morse code, voice messages and link audio are still sent to the repeater. PTT is continuously asserted upon a valid Rx signal.

Duplex mode 3 might be used with a repeater where in-cabinet repeat cannot be disabled. It has the advantage of no audio delay introduced from app_rpt. However, the disadvantage is reduced repeater control: time out timer, Tx on/off, CTCSS on/off and repeat audio level adjustment must be provided external to app_rpt.

The duplex mode 3 setting in an [[RTCM_Client#Menus|RTCM (menu 18)]] is complementary to app_rpt duplex mode 3. Rather than preventing a repeat audio path it provides one. In other words the RTCM performs in-cabinet repeat. This would be used to eliminate repeat audio delay. Duplex=3 must be set in app_rpt otherwise there would be two audio repeat paths and thus an echo.

Duplex Mode 3

2019-06-16T17:52:23Z

Wd6awp:

This duplex mode allows a repeater (rather than app_rpt) to perform the repeat function. This is also known as in-cabinet repeat. Duplex Mode 3 is unique to repeaters and is not likely to be used on simplex, half-duplex nodes or hotspots. Setting '''duplex=3''' in rpt.conf prevents Rx repeater audio from being sent to the repeater Tx. However, courtesy tones, morse code, voice messages and link audio are still sent to the repeater. PTT is continuously asserted upon a valid Rx signal.

Duplex mode 3 might be used with a repeater where in-cabinet repeat cannot be disabled. It has the advantage of no audio delay introduced from app_rpt. However, the disadvantage is reduced repeater control: time out timer, Tx on/off, CTCSS on/off and repeat audio level adjustment must be provided external to app_rpt.

The duplex mode 3 setting in an RTCM (menu 18) is complementary to app_rpt duplex mode 3. Rather than preventing a repeat audio path it provides one. In other words the RTCM performs in-cabinet repeat. This would be used to eliminate repeat audio delay. Duplex=3 must be set in app_rpt otherwise there would be two audio repeat paths and thus an echo.

Duplex Mode 3

2019-06-16T17:19:01Z

Wd6awp: Page created.

Main Page

2019-04-24T13:31:26Z

Wd6awp:

Welcome to the AllStarLink WiKi. AllStarLink is a world wide network of [https://en.wikipedia.org/wiki/Amateur_radio Amateur Radio] repeaters, remote base stations and hot spots accessible to each other via the Internet and/or private IP networks. AllStarLink runs on a dedicated Linux computer (including the Raspberry Pi) that you host at your home, radio site or computer center. It is based on the open source Asterisk PBX. The app_rpt module is a powerful radio/repeater controller. AllStarLink is open source GPL software free for anyone to use.

Recently we've moved some things off of this front page. If you don't see what you are looking for look at the [[:Category:How to|How To's]] or use search located on the top of every page. We have completed moving the content from the docs site [http://docs.allstarlink.org docs.allstarlink.org].

__NOTOC__
==Organization==
*[[The Organization - AllStarLink Inc. ]] - Who is AllStarLink?
*[[The Beginning - AllStarLink Inc]] - How AllStarLink came to be.

==AllStarLink Menu==
*[[Features]] - List of the many AllStarLink Features
*[[Beginners Guide]] - Step by step instructions to create your account and AllStarLink node.
*[[ASL FAQ]] - Questions and answers about the AllStarLink software distribution.
*[[:Category:How to|How To's]] - A collection of AllStarLink how to's.
*[[:Category:Node Configuration|Node Configuration]] - Detailed configuration settings.
*[[:Category:Development|Development]] - Information regarding development of the AllStarLink software (i.e., contributing, etc).
*[[Radio Connections]] - Instructions to Connect Radios, Repeaters and Other Devices to AllStar.
*[[Troubleshooting]] - Troubleshooting common problems, things to try, and hints to solve the problem.

==Downloads==
* [https://github.com/AllStarLink/Asterisk/releases/tag/ASL-1.01 ASL AMD] Latest AllStarLink installer for x86/AMD (main site)
* [http://dvswitch.org/files/ASL_Images/Intel-AMD/Stretch/ ASL AMD] Latest AllStarLink installer for x86/AMD (alternative site)
* [http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ Pi] Latest AllStarLink image for the Raspberry Pi
* [http://dvswitch.org/files/ASL_Images/ ASL Repo] AllStarLink Image Repository
* [[ASL FAQ]] - Install ASL on your existing Debian box or VM

Note: The ASL 1.01 installer is a Network installer and still uses the dvswitch.org site to download the .deb install files.

==Related Links==
* [https://allstarlink.org/ AllStarLink Portal] - If you are looking to set up your own AllStarLink node.
* [https://web-tpa.allstarlink.org/ AllStarLink Portal - Beta] - Our beta portal site. Check out the searchable and sortable [https://web-tpa.allstarlink.org/nodelist/ Node List].
* [http://stats.allstarlink.org/ AllStarLink Stats] - shows all the existing public nodes.
* [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users AllStarLink users mailing list]- This is the app_rpt mailing list for discussion, help and helping others.
* [https://github.com/AllStarLink/ Source Code] - All of the source code for the AllStarLink Asterisk and app_rpt is available on GitHub.

==History==
* [[History]] from the Duuude, Jim Dixon WB6NIL SK 12/16/2016.
* [[Thru-hole_Voter_Board|Thru-hole Voter Board]] from Jim Dixon

RTCM Channel Driver

2019-03-31T19:09:09Z

Wd6awp: /* Asterisk CLI Commands */

The chan_voter channel driver is the interface between Asterisk and the [[RTCM/VOTER Interfaces | RTCM/VOTER]] radio/repeater hardware interface. It allows receiver voting, simulcast transmitters, or just a plain repeater interface when used with the appropriate hardware.

This page will document configuring the channel driver, done through voter.conf, as well as some common issues and more obscure features that may not be widely known.

=Basic Information On How chan_voter Works=
Each node has a number of potential "clients" associated with it. In the voter.conf file, each stanza (category) is named by the node number that the clients specified within the stanza are to be associated with. Each entry consists of an arbitrary (relatively meaningless, just included for easy identification purposes within this channel driver, and has nothing to do with its operation) identifier equated to a unique password. This password is programmed into the client. '''All clients must have unique passwords, as that is what is used by this channel driver to identify them.'''

Each channel instance (as opened by app_rpt as a main radio channel, e.g. rxchannel=Voter/1999 in rpt.conf) and is directly associated with the node that opened it.

Each client has a pair of circular buffers, one for mu-law audio data, and one for RSSI value. The allocated buffer length in all clients is determined by the "buflen" parameter, which is specified in the "global" stanza in the voter.conf file in milliseconds, and represented in the channel driver as number of samples (actual buffer length, which is 8 * milliseconds).

Every channel instance has a index ("drainindex"), indicating the next position within the physical buffer(s) where the audio will be taken from the buffers and presented to the Asterisk channel stream as VOICE frames. Therefore, there is an abstraction of a "buffer" that exists starting at drainindex and ending (modulo) at drainindex - 1, with length of buflen.

Buflen is selected so that there is enough time (delay) for any straggling packets to arrive before it is time to present the data to the Asterisk channel.

The idea is that the current audio being presented to Asterisk is from some time shortly in the past. Therefore, "Now" is the position in the abstracted buffer of 'bufdelay' (generally buflen - 160, you gotta at least leave room for an entire frame) and the data is being presented from the start of the abstracted buffer. As the physical buffer moves along, what was once "now" will eventually become far enough in the "past" to be presented to Asterisk (gosh, doesn't this sound like a scene from "Spaceballs"??.. I too always drink coffee while watching "Mr. Radar").

During the processing of an audio frame to be presented to Asterisk, all client's buffers that are associated with a channel instance (node) are examined by taking an average of the RSSI value for each sample in the associated time period (the first 160 samples of the abstracted buffer (which is the physical buffer from drainindex to drainindex + 159) and whichever one, if any that has the largest RSSI average greater then zero is selected as the audio source for that frame. The corresponding audio buffer's contents (in the corresponding offsets) are presented to Asterisk, then ALL the clients corresponding RSSI data is set to 0, ALL the clients corresponding audio is set to quiet (0x7f). The overwriting of the buffers after their use/examination is done so that the next time those positions in the physical buffer are examined, they will not contain any data that was not actually put there, since all client's buffers are significant regardless of whether they were populated or not. This allows for the true 'connectionless-ness' of this protocol implementation.

=Asterisk CLI Commands=
These are the CLI commands that Asterisk and chan/voter supports:
*voter debug level {0-7}
**Prints debug information from the channel driver at increasing verbosity

*voter test instance_id [test value]
**Specifies/Queries test mode for voter instance
**Test Value can be:
***0 - Normal voting operation
***1 - Randomly pick which client of all that are receiving at the max RSSI value to use
***>1 - Cycle thru all the clients that are receiving at the max RSSI value with a cycle time of (test mode - 1) frames. In other words, if you set it to 2, it will change every single time. If you set it to 11, it will change every 10 times. This is serious torture test.

*voter prio instance_id [client_id] [priority value]
**Specifies/Queries priority value for voter client
*** *CLI> <code>voter prio 1999</code> ''will query node 1999. Not overridden = the value from voter.conf is being used''
*** *CLI> <code>voter prio 1999 North</code> ''will query node 1999 site North''
*** *CLI> <code>voter prio 1999 North 10</code> ''Highest priority will always vote (value 0 - 100)''
*** *CLI> <code>voter prio 1999 North -1</code> ''will stop node 1999 site North from voting. Shuts off receiver.''
*** *CLI> <code>voter prio 1999 North -2</code> ''Returns site to normal. ie "prio: 0 (not overridden)". Can also use off or disable in place of -2."''

*voter record instance_id [record filename]
**Enables/Specifies (or disables) recording file for chan/voter

*voter tone instance_id [new_tone_level(0-250)]
**Sets/Queries Tx CTCSS level for specified chan/voter instance

*voter reload
**Reload chan/voter parameters

*voter display [instance]
**Display voter instance clients

*voter txlockout [instance] <client_list>
**Set Tx Lockout for voter instance clients
*** *CLI> <code>voter txlockout 1999</code> ''will show a list of locked-out and able to transmit sites''
*** *CLI> <code>voter txlockout 1999 +North</code> ''will add lock-out the North site. Transmit disabled.''
*** *CLI> <code>voter txlockout 1999 -North</code> ''will remove lock-out of the North site. Transmit enabled.''

*voter ping [client] <# pings, 0 to abort>
**Ping (check connectivity) to client

=voter.conf Variables=
This is a dump of variables found in the source... they'll need to be fleshed out with some descriptions and applications:

<pre>
linger (uses default if not specified)
plfilter <--this doesn't seem to work?
hostdeemp
duplex (defaults to 1)
mixminus (defaults to 0)
streams
txctcss
txctcssfreq
txctcsslevel (defaults to 62)
txtoctype (defaults to none?, options phase and notone)
primary
isprimary
thresholds
gtxgain (defaults to default_gtxgain)

password
sanity
puckit
dyntime
buflen
utos
port
bindaddr

These are options allowed for each site:
transmit
master
adpcm
nulaw
dynamic
gpsid
buflen
nodeemp <-- this works, bypasses the deemp filter (sets the switch H)
hostdeemp
noplfilter <-- this works, toggles the pl filter in the rtcm (sets the switch L, default seems to be H so the filter is in)
prio
</pre>

=Less Known Facts/Features=
==ADPCM Functionality==
The original intent was to change this driver to use signed linear internally, but after some thought, it was determined that it was prudent to continue using mulaw as the "standard" internal audio format (with the understanding of the slight degradation in dynamic range when using ADPCM resulting in doing so). This was done because existing external entities (such as the recording files and the streaming stuff) use mulaw as their transport, and changing all of that to signed linear would be cumbersome, inefficient and undesirable.

=="Dynamic" client functionality==
'''DON'T USE IT!!'''. It is intentionally '''NOT''' documented to encourage non-use of this feature. It is for demo purposes '''ONLY'''. The chan/voter driver will '''NOT''' properly
perform reliably in a production environment if this option is used.

==Duplex Mode 3/Hostdeemp==
As of VOTER board firmware 1.19 (7/19/2013), there is a set of options in both the firmware ("Offline Menu Item 12, "DUPLEX3 support"), and the "hostdeemp" option (instance-wide) in the voter.conf file on the host.

Duplex Mode 3 in app_rpt allows for "in-cabinet" repeat audio (where the actual radio hardware supplies the repeated audio directly itself, and app_rpt simply "adds" all of the other audio as appropriate.

The RTCM/VOTER board now has an option to do the same functionality itself, for a case where local repeat audio is desired without the "network audio delay" normally associated with RTCM/VOTER board operation, and for a radio that doesn't have the option of providing "in cabinet" repeat audio (along with externally provided audio) itself.

Because of limitations with the RTCM/VOTER board hardware (being that there is only 1 audio path into the processor, and it either has de-emphasis in its "hardware path" or not), it is necessary if you:
#Wish to have the "duplex=3" functionality in app_rpt
#Have the "DUPLEX3" support enabled in the RTCM/VOTER board
#Have a transmitter that you are "modulating directly" (with flat audio)

If all of the above is true, then you need to use the "hostdeemp" option in chan/voter (voter.conf), which basically "forces" the RTCM '''NOT''' to do de-emphasis in hardware (it will send the non-de-emphasized audio to the host), and have the host "do" the de-emphasis (in software) instead.

This will allow the RTCM/VOTER board to be able to "pass" the non-de-emphaszed audio back into the "direct modulation audio" stream, since that is what will be "presented" to the processor in the RTCM/VOTER board, as the hardware de-emphasis is disabled in this mode.

If you have a transmitter that you are "feeding" line-level (mic) audio, then this mode is not necessary, as the RTCM/VOTER board is fully capable of providing the functionality all by itself.

Obviously, it is not valid to use '''ANY''' of the duplex=3 modes in a voted and/or simulcasted system.

==Redundant "Proxy" Mode==
A "Redundant" (backup) server may be set up, so that if the "primary" server fails, clients can detect this failure, and connect to the designated "backup" (or "secondary")
server.

Needless to say, since Internet connectivity is not by any means guaranteed to be consistent, it is possible for some clients to have working connectivity to the "primary" server and not others, even though the "primary" server is functional.

If this was to occur, actual voting and/or simulcast clients would have a "broken" system (being that all the clients need to be on the same server for any sort of functional operation).

To eliminate this possibility, functionality has been added so that a "secondary" server will "proxy" (forward) all of its VOTER packets to the "primary" (if the "primary" is
on line), and the "primary" will generate all of the outbound VOTER packets, which (for clients "connected" to the "secondary" server) get sent to the "secondary" server to distribution to its clients.

This allows for a "unity" of all of the clients on a network, even though they may be connected to different servers.

In addition, it is assumed that "permanent linking" (at least of some sort) will be provided between the channel side of the chan/voter instances (presumably through a "perma-link" provided by app_rpt).

When the "secondary" is "proxying" (to the "primary") it does not provide direct connectivity to/from its locally-connected clients, thus allowing them to "connect" via the "primary" server instead. In "normal" mode, it works "normally".

The operation is performed by more-or-less "encapsulating" the VOTER packets received by the "secondary" server, and forwarding them on to the "primary" server, where they are "un-encapsulated" and appear to that serer to be coming from clients connected directly to it (and keeps track of which ones are connected in this manner, etc). When it needs to send VOTER packets to a client connected through the "secondary", it "encapsulates" them, and sends them to the "secondary", where they get "un-enacpsulated" and sent to their associated connected clients, based upon information in the "encapsulation".

If the "secondary" server loses (or does not make) connection to the "primary", it operates as normal, until such time as it can make the connection.

The server redundancy feature is local to each chan/voter instance.

For each chan_voter instance served by both the "primary" and "secondary" servers, the client list (parameters, etc) '''MUST''' be identical.

In addition, the following things must be added uniquely on each server:
*In the "primary" server, there needs to be a "primary connectivity" client specified for each "secondary" server for which it is "primary". Basically, this is a client that does NOTHING other then providing a means by which the "secondary" can determine whether the "primary" is on line.

*It is a standard chan/voter client, with nothing else specified other then its password. Again, although it is a "legitimate" client (technically), its only purpose '''MUST''' be to allow the secondary server to connect to it.

*The "primary" server also needs to have the following in all of its instances that require redundancy:
<pre>
isprimary = y
</pre>

*The "secondary" server needs to have the following in all of its instances that require redundancy:
<pre>
primary = 12.34.56.78:667,mypswd
</pre>
Where 12.34.56.78:667 is the IPADDDR:PORT of the "primary" server, and mypswd is the password of the "primary connectivity" client

Note: Master timing sources '''MUST''' be local to their associated server, and therefore, can not be operated in a redundant configuration. If a radio needs server redundancy, it '''CAN NOT''' be connected to a master timing source. Also, the master timing source '''MUST''' be associated with a chan/voter instance that '''DOES NOT''' have redundancy configured for it, even if a separate instance needs to be created just for this purpose.

Also, if non-GPS-based operation is all that is needed, just the use of redundancy within the clients is sufficient, and does not require any use of the server redundancy features.

=Voter Recording and Playback=
chan_voter has the ability to record VOTER streams by the channel driver live on the air (using the 'voter record' command in Asterisk). This also records time-stamped data and the voted receiver at that particular time along with RSSI readings. This can then be played back using the VoterPal GUI JAVA applet.

==How to setup playback==
# Download the [https://allstarlink.org/voterpal/VoterPal.jar VoterPal application].
# Download the [https://allstarlink.org/voterpal/lib/appframework-1.0.3.jar appframework-1.0.3.jar] and [https://allstarlink.org/voterpal/lib/swing-worker-1.1.jar swing-worker-1.1.jar] files. Place these in a folder called lib in the same directory as the VoterPal application
# Run VoterPal.jar. You may come across issues with running Java such as security permissions. Most of these can be allowed.
# Once running, you will see the applications GUI. File > Open to select your voter data files. A bunch of test files have been made already to test [https://allstarlink.org/voterpal/datafiles/ here]
[[File:Voterpal.png|left|thumb|549x549px]]

'''Reset'''

Resets the file back to start

'''Play'''

Plays the recorded file

'''Stop'''

Stops the current playing file in it's current position

'''CTCSS Filter Enable'''

Removes CTCSS hum from any recorded audio stream

'''File Play Position'''

Drag this slider to skip

'''Activity'''

This will show time-stamped information including RSSI of the selected VOTER client within the recorded data stream

'''Voter Clients'''

This will show the real time voted client. This is also dependent of the Mode setting

'''Mode'''

Various modes can be selected in VoterPal

0 - Normal Voting Mode

1 - Randomly pick which client of all that are receiving at the max RSSI value to use

> 1 - Cycle thru all the clients that are receiving at the max RSSI value with a cycle time of (test mode - 1) frames. In other words, if you set it to 2, it will change every single frame. If you set it to 11, it will change every 10 frames. This is a serious torture test.

< 0 - Any value less than zero will force select the Voter Client (i.e. -1 is the first client, -2 is the 2nd client)

==Node Configuration==
As mentioned above the Asterisk CLI is as follows -
* voter record instance_id [record filename] - Enables/Specifies (or disables) recording file for chan/voter
Where

- instance_id = voter number instance

- record filename is the filename of the recording to be stored

A script can be made and placed in cron.hourly which will run every hour. Every time the above command is run in Asterisk, it creates a new file. An example of such a script is below
#!/bin/sh asterisk -r -x "voter record instance_id /tmp/voter-record"`date +%F-%H-%M` >> /var/log/voterrecordlog
the /tmp/ directory can be substituted for mounted USB HDD.

[[Category:How to]]
[[Category:Node Configuration]]

NNX

2019-03-24T13:30:27Z

Wd6awp: /* AllStar Portal */

= Draft 2019.03.23 =
This document is currently a draft proposal. Alpha test software has been developed and is working as described. A public announcement and request for comments is forthcoming.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= NNX on the AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially since implementation of NNX. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

NNX

2019-03-24T13:28:18Z

Wd6awp:

= Draft 2019.03.23 =
This document is currently a draft proposal. Alpha test software has been developed and is working as described. A public announcement and request for comments is forthcoming.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
Requesting a new node has not changed substantially. It's basically the same process described in our [[Beginners Guide]]. To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. You can change that later. 3) Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

NNX

2019-03-24T13:22:34Z

Wd6awp:

= Draft 2019.03.23 =
This document is currently a draft proposal. Alpha test software has been developed and is working as described. A public announcement and request for comments is forthcoming.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

= AllStar Portal =
Node number extension implementation on the AllStar portal is shown here.

== Request Node ==
To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. 3) You can change that later. Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

NNX

2019-03-24T13:16:19Z

Wd6awp: /* Remove Node */

= Draft 2019.03.23 =
This document is currently a draft proposal. Alpha test software has been developed and is working as described. A public announcement and request for comments is forthcoming.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

== Request Node ==
To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. 3) You can change that later. Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.
[[Image:Remove NNX node.png|none|alt=NNX node returned to INN|left|thumb]]

NNX

2019-03-24T13:14:48Z

Wd6awp: /* Remove Node */

= Draft 2019.03.23 =
This document is currently a draft proposal. Alpha test software has been developed and is working as described. A public announcement and request for comments is forthcoming.

= AllStar Node Number Extensions =

A Node Number Extension is a method to expand any issued node number to as many as ten node numbers. The reasons for this are to allow users to assign themselves sequential node numbers while preserving and expanding valuable node number space. The concept is very simple; allow users to optionally expand the length of any of their node numbers by one digit.

== Example ==
When a user with an existing node number selects to expand the number, they go to the portal and select to add a node, rather than request a new node. The portal converts node xxxx to xxxx0 and adds node xxxx1 to the user’s node list. An additional eight NNX nodes may be added for a total of 10 sequential (xxxx0 thru xxxx9) node numbers. The reason xxxx has to be changed to xxxx0 is because AllStar would connect to node xxxx when attempting to dial node xxxx1.

Once the node user has reconfigured their node computer, both node numbers register, show on the AllStar nodes list, show on stats page, appear in Allmon2 and of course can connect or be connected to.

New users that have not yet been issued a node number would request, rather than add a new node number via the portal. This process has not changed and is documented on the [[Beginners Guide]].

== Requirements ==
Use of NNX node numbers is totally optional. The prior node request process still exists. Existing and new users may continue to request new node numbers as in the past.

Users who opt to expand an existing node number will need to make configuration changes to their node. That is (using the example numbers above) all references to node xxxx will need to change to xxxx0. These files may include but are not limited to rpt.conf, extensions.conf, iax.conf and allmon.inc.php. Reconfiguring all occurrences of the existing node number is critical. Such an oversight may confuse users and put an extra support load on system admins, at least initially. The menus that are built into newer AllStar installs simplify this task greatly.

Adding NNX nodes xxxx1 thru xxxx9 is the same change that would be made when adding any additional node.

== Considerations ==
* NNX nodes can be assigned to any of the user’s servers, assigned a password and otherwise modified as desired.
* No changes to the AllStar registration system, the Stats Server or Allmon2 systems are required.
* Any existing node number (aka Issued Node Number or INN) can be converted to an NNX. INN and NNX node numbers can run on the same server. NNX Nodes can be split across different servers.
* Users who desire more than ten sequential node numbers and have not already been assigned sequential node numbers, may opt to request new node numbers in sequential order. Two subsequent INNs may expand to 20 NNX numbers, or three to 30 NNX nodes, etc. All with little impact on node number resource. It’s conceivable that some users may opt to relinquish their non-sequential INN node numbers after converting, further easing any pressure on node number space.
* A provision for releasing no longer used INN numbers has been included on the new portal page as has a provision to revert NNX nodes back to the original INN number.

== Request Node ==
To begin requesting a new node number from the admin team, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]

1) The "Request" option will be selected. 2) Then choose the server you want the node assigned to. 3) You can change that later. Type an optional message and press Submit
[[Image:Request a Node.png|none|alt=Request a node screen shot|left|thumb]]

You will then see a pending node request in your nodes list.
[[Image:Pending node request.png|none|alt=Pending node request screen shot|left|thumb]]

== Add Node ==
Adding a new node converts an existing node to an NNX node or if the node is already an NNX, adds another NNX node as described above.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Add (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.[[Image:Add a node.png|none|alt=Add a node screenshot|left|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 2501 has been changed to 25010 and 25011.
[[Image:New NNX Nodes.png|none|alt=Screen shot of two NNX nodes|left|thumb]]

== Remove Node ==
Select Remove to convert an NNX node back to a non-NNX type node.

Removing a non-NNX node returns the node to the pool of free nodes for reassignment. See our reassignment policy.

To begin adding a new node number, select the Portal menu, then Node Settings, then "THIS LINK" as shown below.
[[Image:Node req add del.png|none|alt=node menu|left|thumb]]Next click green Remove (1) and the form change and will look similar to the one below. The dropdown (2) shows all your nodes including NNX nodes.

[[Image:Remove node screen shot.png|none|alt=Remove node screen shot|thumb|left]]
[[File:Remove NNX node.png|alt=NNX node returned to INN|thumb]]
Select the node you wish, click Continue and on the next screen confirm the action. Below shows node 25010 and 25011 have been changed back to 2501.

File:Remove NNX node.png

2019-03-24T13:14:03Z

Wd6awp:

Screen shot after NNX node removed