Changes

==Description/Explanation ==

==Description/Explanation ==

Occasionally there is a need to have an Allstar Link Server in an 'itinerant' location (one that is non-permanent and possibly even moving). In such a situation it is certainly quite likely that the device's IP address may change quite often (perhaps even several times per hour or more). Also, the form of IP connectivity available to the device may not necessarily be suitable for normal Server operation (such as being behind NAT translation, firewalls, etc. that the Server owner has no control of). Normal operation requires farily stable IP addressing and full public access to at least UDP port 4569 (for IAX2 connectivity) to the Server. Typical examples of 'itinerant' environments include setting up a tiny portable node in a hotel room, utilizing the Internet connectivity provided by the hotel, or having a mobile node on a mobile data network that provides connectivity via some sort of NAT arrangement.

Occasionally there is a need to have an PTTLink Server in an 'itinerant' location (one that is non-permanent and possibly even moving). In such a situation it is certainly quite likely that the device's IP address may change quite often (perhaps even several times per hour or more). Also, the form of IP connectivity available to the device may not necessarily be suitable for normal Server operation (such as being behind NAT translation, firewalls, etc. that the Server owner has no control of). Normal operation requires farily stable IP addressing and full public access to at least UDP port 4569 (for IAX2 connectivity) to the Server. Typical examples of 'itinerant' environments include setting up a tiny portable node in a hotel room, utilizing the Internet connectivity provided by the hotel, or having a mobile node on a mobile data network that provides connectivity via some sort of NAT arrangement.

In a situation like this, it is possible to set up a Proxy relationship between such a Server and a Server located in a permanent position with a permanent IP address and good connectivity. For the purposes of explanation, the Server in the 'itinerant' location/situation will be referred to as the Server Proxy Client, and the Server that is in the Permanent/Stable location/situation will be referred to as the Server Proxy Server.

In a situation like this, it is possible to set up a Proxy relationship between such a Server and a Server located in a permanent position with a permanent IP address and good connectivity. For the purposes of explanation, the Server in the 'itinerant' location/situation will be referred to as the Server Proxy Client, and the Server that is in the Permanent/Stable location/situation will be referred to as the Server Proxy Server.

== Portal-Based Configuration for Server Proxy Clients ==

== Portal-Based Configuration for Server Proxy Clients ==

Since any Allstar Link Server can be a Server Proxy Server, it can not be assumed that both the Server Proxy Client and the Server Proxy Server belong to the same Allstar Link User (or even the same organization, etc.). Therefore, designation and specification of these Proxy relationships are not allowed to be done directly from the Portal (it must be requested by email to Allstar Link Network Validation Staff by both the party that owns the Server Proxy Client, and the party that owns the Server Proxy Server). Once configured by the Staff, the Portal will automatically generate configuration for the Server Proxy Client appropriately. The Server Proxy Server configuration must always be done manually. This provides the ability for a Portal-Configured Server Proxy Client to be in a Proxy relationship with any appropriately configured Server Proxy Server.

We don't support configuration of clients in the portal. The best way is to set it up manually, and then add the IP of the proxy server in the portal for the client.

First, you must configure a peering arrangement with the Server Proxy Server.  

 

 

 

First, you must configure a peering arrangement with the Proxy Server.  

This is done by adding the following into the /etc/asterisk/iax.conf file:

This is done by adding the following into the /etc/asterisk/iax.conf file:

using Agreed-Upon Passwords.

using Agreed-Upon Passwords.

If the Server Proxy Server is the Allstar Network Registration Server, then

If the Server Proxy Server is the PTTLink Network Registration Server, then

the IP Address will be 67.215.233.178, the Username and Password will be node number

the IP Address will be 67.215.233.178, the Username and Password will be node number

and node password of one of the nodes on the system that is registered with it, and

and node password of one of the nodes on the system that is registered with it, and

<Stuff that was already there, etc....>

<Stuff that was already there, etc....>

_20XX = radio-proxy-out/0%s

_20XX = radio-proxy-out/0%s

_21XX = radio-proxy-out/0%s

_21XX = radio-proxy-out/0%s

_22XX = radio-proxy-out/0%s

_22XX = radio-proxy-out/0%s

_23XX = radio-proxy-out/0%s

_23XX = radio-proxy-out/0%s

_24XX = radio-proxy-out/0%s

_24XX = radio-proxy-out/0%s

_25XX = radio-proxy-out/0%s

_25XX = radio-proxy-out/0%s

_26XX = radio-proxy-out/0%s

_26XX = radio-proxy-out/0%s

_27XXX = radio-proxy-out/0%s

_27XXX = radio-proxy-out/0%s

_28XXX = radio-proxy-out/0%s

_28XXX = radio-proxy-out/0%s

_29XXX = radio-proxy-out/0%s

_29XXX = radio-proxy-out/0%s

</pre>

</pre>

<pre>

<pre>

[radio-secure-proxy]

[radio-secure-proxy]

exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1)

exten => _0X.,1,Goto(pttlink-sys|${EXTEN:1}|1)

</pre>

</pre>

Plus, for each node on the system (also to be put in the radio-secure-proxy section):

Plus, for each node on the system (also to be put in the radio-secure-proxy section):

exten => <Node Number>,1,rpt,<Node Number>|X

exten => <Node Number>,1,rpt,<Node Number>|X

</pre>

</pre>

=Configuration for Server Proxy Servers=

=Configuration for Server Proxy Servers=

exten=_28XXX,1,Rpt,${EXTEN}

exten=_28XXX,1,Rpt,${EXTEN}

exten=_29XXX,1,Rpt,${EXTEN}

exten=_29XXX,1,Rpt,${EXTEN}

</pre>

</pre>

The following needs to be added to the [allstar-sys] section:

The following needs to be added to the [pttlink-sys] section:

<pre>

<pre>