Node Registration - Revision history

KM4NNO at 16:09, 1 January 2021

2021-01-01T16:09:21Z

N8THN: /* Manual setup Instructions */

2019-01-27T04:02:46Z

Manual setup Instructions

N8THN: formatting

2019-01-27T04:02:05Z

formatting

N8THN: created page

2019-01-27T03:59:15Z

created page

New page

[[Category:How to]]
== How It Works ==

There is a registration server located at register.allstarlink.org which receives registration requests from all Allstar link nodes. If the node number is valid, and the password matches what is on file for the node, then a master list of valid Allstar link nodes is updated with the latest IP address seen by the registration server. This master list is then periodically retrieved by another set of entirely different Allstar link node servers which are located in different geographical locations. All valid Allstar nodes can then request and retrieve a copy of the master node list by running the rc.updatenodelist script at periodic intervals. App_rpt reads the output of this script and will allow incoming connections originating from nodes in this list, and will also allow outgoing connections for any node listed in the script.

@@ Line 2: / Line 2: @@
 == How It Works ==
-There is a registration server located at register.allstarlink.org which receives registration requests from all Allstar link nodes. If the node number is valid, and the password matches what is on file for the node, then a master list of valid Allstar link nodes is updated with the latest IP address seen by the registration server. This master list is then periodically retrieved by another set of entirely different Allstar link node servers which are located in different geographical locations. All valid Allstar nodes can then request and retrieve a copy of the master node list by running the rc.updatenodelist script at periodic intervals. App_rpt reads the output of this script and will allow incoming connections originating from nodes in this list, and will also allow outgoing connections for any node listed in the script.
+There is a registration server located at register.pttlink.org which receives registration requests from all PTTLink nodes. If the node number is valid, and the password matches what is on file for the node, then a master list of valid PTTLink nodes is updated with the latest IP address seen by the registration server. This master list is then periodically retrieved by another set of entirely different PTTLink node servers which are located in different geographical locations. All valid PTTLink nodes can then request and retrieve a copy of the master node list by running the rc.updatenodelist script at periodic intervals. App_rpt reads the output of this script and will allow incoming connections originating from nodes in this list, and will also allow outgoing connections for any node listed in the script.
 == Manual setup Instructions ==
-In order to use the registration feature, you will need to know both your Allstar link node number and Allstar Link access password. If you have forgotten your Allstar link access password, you can retrieve it from allstarlink.org, if you know the email address you registered the node to, and the node number of the node.
+In order to use the registration feature, you will need to know both your PTTLink node number and PTTLink access password. If you have forgotten your PTTLink access password, you can retrieve it from pttlink.org, if you know the email address you registered the node to, and the node number of the node.
 To use the new update process, a registration statement is added to the general section of /etc/asterisk/iax.conf using a text editor such as vi, emacs, or nano. The format of the register statement is:
-<code>register=node:password@register.allstarlink.org</code>
+<code>register=node:password@register.pttlink.org</code>
 where:
-node is your assigned Allstar link node number.
+node is your assigned PTTLink node number.
-password is your assigned Allstar Link node access password.
+password is your assigned PTTLink node access password.
 For example, node 1234 which has a password of 12345678 would put the following line in [general] section /etc/asterisk/iax.conf:
@@ Line 28: / Line 28: @@
 <code>.</code>
-<code>register=1234:12345678@register.allstarlink.org.</code>
+<code>register=1234:12345678@register.pttlink.org.</code>
 Note: You will need to issue an iax2 reload command from the Asterisk Command line, or restart Asterisk after you save iax.conf.
 == Obsolete variations: ==
-As of 7/1/2008, dynamic DNS and/or static IP addresses are no longer required for nodes which are part of the Allstar Link network. The new node identification method uses an iax.conf register statement to update the Allstar Link registration server with the latest IP address in use by the Allstar Link node. Depending upon the distribution
+As of 7/1/2008, dynamic DNS and/or static IP addresses are no longer required for nodes which are part of the PTTLink network. The new node identification method uses an iax.conf register statement to update the PTTLink registration server with the latest IP address in use by the PTTLink node. Depending upon the distribution
 ==== ACID ====

@@ Line 16: / Line 16: @@
 node is your assigned Allstar link node number.
-password is your assigned Allstar Link access password.
+password is your assigned Allstar Link node access password.
 For example, node 1234 which has a password of 12345678 would put the following line in [general] section /etc/asterisk/iax.conf:

← Older revision		Revision as of 04:02, 27 January 2019
Line 3:		Line 3:

	There is a registration server located at register.allstarlink.org which receives registration requests from all Allstar link nodes. If the node number is valid, and the password matches what is on file for the node, then a master list of valid Allstar link nodes is updated with the latest IP address seen by the registration server. This master list is then periodically retrieved by another set of entirely different Allstar link node servers which are located in different geographical locations. All valid Allstar nodes can then request and retrieve a copy of the master node list by running the rc.updatenodelist script at periodic intervals. App_rpt reads the output of this script and will allow incoming connections originating from nodes in this list, and will also allow outgoing connections for any node listed in the script.		There is a registration server located at register.allstarlink.org which receives registration requests from all Allstar link nodes. If the node number is valid, and the password matches what is on file for the node, then a master list of valid Allstar link nodes is updated with the latest IP address seen by the registration server. This master list is then periodically retrieved by another set of entirely different Allstar link node servers which are located in different geographical locations. All valid Allstar nodes can then request and retrieve a copy of the master node list by running the rc.updatenodelist script at periodic intervals. App_rpt reads the output of this script and will allow incoming connections originating from nodes in this list, and will also allow outgoing connections for any node listed in the script.
		+
		+	== Manual setup Instructions ==
		+
		+	In order to use the registration feature, you will need to know both your Allstar link node number and Allstar Link access password. If you have forgotten your Allstar link access password, you can retrieve it from allstarlink.org, if you know the email address you registered the node to, and the node number of the node.
		+
		+	To use the new update process, a registration statement is added to the general section of /etc/asterisk/iax.conf using a text editor such as vi, emacs, or nano. The format of the register statement is:
		+
		+	<code>register=node:password@register.allstarlink.org</code>
		+
		+	where:
		+
		+	node is your assigned Allstar link node number.
		+
		+	password is your assigned Allstar Link access password.
		+
		+	For example, node 1234 which has a password of 12345678 would put the following line in [general] section /etc/asterisk/iax.conf:
		+
		+	<code>[general]</code>
		+
		+	<code>.</code>
		+
		+	<code>.</code>
		+
		+	<code>.</code>
		+
		+	<code>register=1234:12345678@register.allstarlink.org.</code>
		+
		+	Note: You will need to issue an iax2 reload command from the Asterisk Command line, or restart Asterisk after you save iax.conf.
		+
		+	== Obsolete variations: ==
		+	As of 7/1/2008, dynamic DNS and/or static IP addresses are no longer required for nodes which are part of the Allstar Link network. The new node identification method uses an iax.conf register statement to update the Allstar Link registration server with the latest IP address in use by the Allstar Link node. Depending upon the distribution
		+
		+	==== ACID ====
		+	Please note that in the ACID Distribution, node registration is automatically configured for you. You will be prompted for your node number and node password at the completion of the installation process.
		+
		+	==== Limey Linux ====
		+	Limey Linux has the <code>nodesetup</code> script available. Just type <code>nodesetup</code> at the shell prompt, and you will be prompted for your node number, password, and node callsign.