[arm-allstar] Notice of Allstar problems and how to diagnose

Doug Crompton wa3dsp at gmail.com
Sun Aug 12 22:49:33 EDT 2018


As I pointed out earlier the Allstar group has created a mess with their
supposed new and improved (and previously untested) registration system.
The problem is that some routers in fact many (it is about 700 in the
current list) do not report proper ports. Since the new Allstar
registration SW does not use the Allstarlink.org supplied port and your
router does not either then you are out of luck under the current system.
If you are having problems do the following.

First see if you are registered.

      check_reg.sh    or     asterisk -rx "iax2 show registry"

You will see something like this -

DNS lookup returns - +OK|radio at 67.165.29.63:4569/40561,67.165.29.63

Look at the IP address after the @ and ensure it is correct for your public
IP address. Then and more importantly check the IAX port - the number after
the ":"   It is shown as this example as 4569

If you use the iax2 show registry method it will be under the perceived
column.

If this number does not match the IAX port you have set in your
/etc/asterisk/iax.conf file on the bindport=  line then you will not be
able to use your node. Changing the bindport setting will NOT fix the
problem as the perceived port at the Allstar end is random.

If your system is one currently experiencing this problem there is nothing
you can do at your end to fix it besides maybe getting a new router which
we do not recommend. The Allsar end has to fix the problem which we are
hoping they will do. If not just watch here for an update due to come out
very soon to fix the problem.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


More information about the arm-allstar mailing list