[arm-allstar] Status report

[David McGough]

Hi Chris,

This node seems to be registered to me in the HamVoIP system?? 

[root at hamvoip-kb4fxc ~]# dns-query 29883
+OK|radio at 71.95.13.254:4569/29883,71.95.13.254

If your results still show -ER|NOT FOUND, then make sure the firmware is 
updated on that system to the latest version from 08/14 (or later).

If the firmware is updated, confirm that DNS resolution works:

[root at hamvoip-kb4fxc ~]# ping -nc 4 google.com
PING google.com (172.217.12.110) 56(84) bytes of data.
64 bytes from 172.217.12.110: icmp_seq=1 ttl=52 time=47.2 ms
64 bytes from 172.217.12.110: icmp_seq=2 ttl=52 time=47.7 ms
64 bytes from 172.217.12.110: icmp_seq=3 ttl=52 time=46.7 ms
64 bytes from 172.217.12.110: icmp_seq=4 ttl=52 time=47.9 ms


73, David KB4FXC




On Fri, 17 Aug 2018, "C B via arm-allstar" wrote:

> Doug
this is what i got running check_reg.sh
what have i done wrong?


[root at BURBANK-HUB asterisk]# check_reg.sh
Node - 29883#4569 at IP address- 71.95.13.254, Port- 4569 is Registered at ServerIP- 74.91.126.182 (hvdallas2.hamvoip.org.), Port- 4569
 DNS lookup returns - -ER|NOT FOUND
[root at BURBANK-HUB asterisk]#

      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
 To: ARM Allstar <arm-allstar at hamvoip.org> 
Cc: Doug Crompton <wa3dsp at gmail.com>
 Sent: Thursday, August 16, 2018 9:12 PM
 Subject: [arm-allstar] Status report
   
I am pleased to report that things have settled down some after our release
of the dns node lookup to all hamvoip V1.5 users earlier this week. The
Asterisk registration site is still showing some severe problems with
registration times varying all over the place from 10's of seconds to
minutes in some cases. This is totally unacceptable for a registration
server. Our registration server is about to go live so stay tuned for that
and be sure to update!

If you are still experiencing registration problems please let us know and
we can give you temporary registration with the hamvoip servers. To check
whether you are registered use the check_reg.sh script. Here is an example
of a node that is registered with hamvoip at our Dallas server but not
allstar. Who knows why and I really don't care. This node works fine within
the hamvoip system as dns-query returns the correct routing information.

check_reg.sh

Node - 40961 at IP address- 76.117.192.17, Port- 4568 is Registered at
Server
IP- 74.91.126.182 (hvdallas2.hamvoip.org.), Port- 4569

 DNS lookup returns - +OK|radio at 76.117.192.17:4568/40961,76.117.192.17

Node - 40961 at IP address- 76.117.192.17, Port- 4568 is Request at Server
IP- 44.98.254.145 (145.PTR.allstarlink.org. register-tpa.allstarlink.org.),
Port- 4569

 DNS lookup returns - +OK|radio at 76.117.192.17:4568/40961,76.117.192.17


*73 Doug*

*WA3DSP*

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

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org


   
_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org