[arm-allstar] Connecting to node 29332

Doug Crompton wa3dsp at gmail.com
Thu Oct 11 00:39:22 EDT 2018


Gerry,

Go into the asterisk client - item 11 on the menu.  At the CLI prompt type
-  rpt fun yournode# *3connect-node#   in your case -

rpt fun 49111 *329332

It is possible that 29332 does not have something setup right or is not
getting routing information for those nodes. If that is the case it should
try to connect. If it does nothing and you know for sure that dns-query
returns an address for 29332 then try rebooting.

Also in the client type -

rpt lookup 29332

and see what you get.


*73 Doug*

*WA3DSP*

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

On Thu, Oct 11, 2018 at 12:33 AM "Gerry Filby via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Well this is weird ...
>
> All 4 of my nodes (48035, 48063, 48866, 49111) answer dns-query and
> check_reg.sh correctly (see below) - so I don't think it's configuration
> on my end.
>
> ALL four nodes successfully ping 69.178.108.173, so it's not likely
> network routing, maybe.
>
> However, 48063 and 48035 can connect to 29332 just fine - but 49111 and
> 48866 CAN NOT connect to 29332.
>
> Is there a CLI connect command I can run that will be give me more
> information on why the connection is being refused or failing ?
>
> g
>
> (48035)
> [root at node48035 818ctl]# dns-query 29332
> +OK|radio at 69.178.108.173:4569/29332,69.178.108.173
> [root at node48035 818ctl]# check_reg.sh
>
> Node - 48035 at IP address- 173.228.113.7, Port- 4569 is "Registered" at
> Server
> IP- 44.98.254.145 (145.PTR.allstarlink.org.
> register-tpa.allstarlink.org.), Port- 4569
>
>   DNS lookup returns - +OK|radio at 173.228.113.7:4569/48035,173.228.113.7
>
> (48063)
> [root at node48063 tmp]# dns-query 29332
> +OK|radio at 69.178.108.173:4569/29332,69.178.108.173
> [root at node48063 tmp]# check_reg.sh
>
> Node - 48063 at IP address- 198.27.190.130, Port- 4569 is Registered at
> Server
> IP- 44.98.254.145 (145.PTR.allstarlink.org.
> register-tpa.allstarlink.org.), Port- 4569
>
>   DNS lookup returns - +OK|radio at 198.27.190.130:4569/48063,198.27.190.130
>
> (48866)
> [root at node48866 asterisk]# dns-query 29332
> +OK|radio at 69.178.108.173:4569/29332,69.178.108.173
> [root at node48866 asterisk]# check_reg.sh
>
> Node - 48866 at IP address- 173.228.113.7, Port- 4567 is "Registered" at
> Server
> IP- 44.98.254.145 (145.PTR.allstarlink.org.
> register-tpa.allstarlink.org.), Port- 4569
>
>   DNS lookup returns - +OK|radio at 173.228.113.7:4579/48866,173.228.113.7
>
> (49111)
> [root at node49111 tmp]# dns-query 29332
> +OK|radio at 69.178.108.173:4569/29332,69.178.108.173
> [root at node49111 tmp]# check_reg.sh
>
> Node - 49111 at IP address- 198.27.190.130, Port- 4559 is "Registered"
> at Server
> IP- 44.98.254.145 (145.PTR.allstarlink.org.
> register-tpa.allstarlink.org.), Port- 4569
>
>   DNS lookup returns - +OK|radio at 198.27.190.130:4559/49111,198.27.190.130
>
>
> David McGough wrote on 10/10/18 2:11 PM:
> >
> > Hi Gerry,
> >
> > Yes, the most recent versions of the HamVoIP release do use the DNS
> lookup
> > method. To test the lookups, from a bash prompt (admin menu option #9),
> > use this command:
> >
> >
> > [root at Allstar-kb4fxc ~]# dns-query 29332
> > +OK|radio at 69.178.108.173:4569/29332,69.178.108.173
> >
> >
> >
> > Or from the Asterisk CLI:
> >
> > Allstar-kb4fxc*CLI> rpt lookup 29332
> > Node:  2288, Method:   DNS, Actual:   DNS, Data:
> radio at 69.178.108.173:4569/29332,69.178.108.173
> > Node:  2289, Method:   DNS, Actual:   DNS, Data:
> radio at 69.178.108.173:4569/29332,69.178.108.173
> >
> >
> > Also, confirm that you node is properly registered using the check_reg.sh
> > command from a bash prompt (admin menu option #9), like:
> >
> > [root at kb4fxc-portable asterisk]# check_reg.sh
> >
> > Node - 41331 at IP address- 12.17.29.6, Port- 4569 is "Registered" at
> Server
> > IP- 44.98.254.145 (145.PTR.allstarlink.org. register-tpa.allstarlink.org.),
> Port- 4569
> >
> >   DNS lookup returns - +OK|radio at 12.17.29.6:4569/41331,12.17.29.6
> >
> > Node - allstar/41331#4569 at IP address- 12.17.29.6, Port- 4569 is
> "Registered" at Server
> > IP- 74.91.126.182 (hvdallas2.hamvoip.org.), Port- 4569
> >
> >   DNS lookup returns - +OK|radio at 12.17.29.6:4569/41331,12.17.29.6
> >
> >
> > Please try these commands and report back.
> >
> >
> > 73, David KB4FXC
> >
> >
> >
> > On Wed, 10 Oct 2018, "Gerry Filby via ARM-allstar" wrote:
> >
> >> The past several days I have not been able to connect to node 29332
> >> (Alaska hub) from any of my nodes (all latest Hamvoip images).
> >>
> >> I contacted allstarlink.org and Bryan W9CR had me go looking for:
> >>
> >> /var/lib/asterisk/rpt_extnodes
> >>
> >> ... which is indeed not there.
> >>
> >> It just occurred to me that it might be to do with the changes in
> >> hamvoip to implement "DNS" ?
> >>
> >> I apologize I haven't kept up with this thread - can you steer me in the
> >> right direction - is this something I fix in my node, or is there a
> >> problem with 29332 - Allstarlink says 29332 is registered and shouldn't
> >> be a problem.
> >>
> >> Thx !
> >>
> >> Gerry
> >> W6WNG
> >> _______________________________________________
> >>
> >> 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
>


More information about the ARM-allstar mailing list