[arm-allstar] Nodes Unable to Connect

Sat Aug 10 14:33:38 EDT 2019

A congestion error usually indicates there is not routing back to this node
at the other end. The way to check this is to have Asterisk client open at
the other end and see what messages come up. If you see nothing then the
data never got there. If you see errors then it is probably because that
end does not have a way to get back either because there is no info or it
is in error.  You need to do either a dns-query in Linux or a  rpt lookup
in the client for that node. Here is an example -

dns-query 50227
+OK|radio at 173.209.207.202:4569/50227,173.209.207.202

dns-query 49608
+OK|radio at 24.101.55.178:4569/49608,24.101.55.178

27225-HUB*CLI> rpt lookup 50227
Node: 27225, Method:   DNS, Actual:   DNS, Data:
radio at 173.209.207.202:4569/50227,173.209.207.202

27225-HUB*CLI> rpt lookup 49608
Node: 27225, Method:   DNS, Actual:   DNS, Data:
radio at 24.101.55.178:4569/49608,24.101.55.178

I tried connecting to both nodes and I was successful to 49608 but not
50227.  I suspect 50227 is the hotspot node. Please be aware that just
because a hotspot has port forwarding does not mean you will be able to
connect inbound. Many are behind double nat'ing and do not allow inbound
connections. You usually need a static public IP address with the provider
to do this which is big bucks if it is available.

If this is the case and 50227 is the hotspot is should be able to connect
outbound. Are you getting an IP address issued from the hotspot? One thing
you can do is connect a monitor and keyboard to the Pi connecting to the
hotspot and then do some troubleshooting.

Logged into the hotspot end you can see what the IP address is  - ifconfig
and see it in the wlan0 data. You can also do a dns-query of the node you
are trying to connect to and also you can try manually connecting in the
client and see the results. BOTH ends need to have correct dns-query info
for the other end.

I am not sure exactly what you are planing there but using a hotspot as a
repeater connection is probably not a good idea long term.

*73 Doug*

*WA3DSP*

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

On Sat, Aug 10, 2019 at 2:08 PM "Mike Sullivan via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I am trying to connect our club's node with another club's node that I am
> testing right now before deploying. When I connect from theirs (50227) to
> ours (49608) the connection fails and the Allstar log spits out the line
> above. When I connect from ours to theirs, it also fails but is giving me a
> congestion error. Hotspot is a Netgear Unite that I have laying around
> using Unreal Mobile, which runs off AT&T's network through their own
> servers. I have the node DMZ'd, and all appropriate ports forwarded to the
> node. It is registering with both the Allstar and Hamvoip servers fine.
>
> Mike
>
> On Sat, Aug 10, 2019 at 1:47 PM "Doug Crompton via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Refresh my memory what are you trying to do? Connect out through a
> hotspot?
> > There is no reason this should not work. Like I said connecting in on a
> > hotspot regardless of any port forwarding is questionable at best. What
> > hotspot device are you using? Who is the provider? Are you connecting to
> > the hotspot and getting an IP address? *A1 should give you an IP address.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Sat, Aug 10, 2019 at 1:42 PM "Mike Sullivan via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Update.. registration is good, but still cannot connect. Still giving
> me
> > > the same messages. Sounds like the cellphone provider is causing it to
> > me..
> > >
> > > Guess my only option is to run a proxy? Anyone have a quick and easy
> way
> > to
> > > set up? And preferably free?
> > >
> > > [Aug 10 13:37:22] WARNING[778] app_rpt.c: Node 50227 IP
> > > xxx.yyy.zzz.202 does not match link IP xxx.yyy.zzz.203!!
> > >
> > >
> > >
> > > On Thu, Aug 8, 2019 at 4:55 PM "Danny K5CG via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > "remember you cannot normally have incoming connections on a hotspot
> as
> > > > they do not have port forwarding."
> > > >
> > > > It is entirely dependent on the model of Hostspot. The one I have
> does
> > (a
> > > > Franklin R850 on Sprint).
> > > >
> > > > The Allstar node must have a static IP on the Pi's wireless adapter
> > > > naturally. And it works.
> > > >
> > > > Danny
> > > > K5CG
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "ARM Allstar" <arm-allstar at hamvoip.org>
> > > > To: "ARM Allstar" <arm-allstar at hamvoip.org>
> > > > Cc: "wa3dsp" <wa3dsp at gmail.com>
> > > > Sent: Thursday, August 8, 2019 3:19:58 PM
> > > > Subject: Re: [arm-allstar] Nodes Unable to Connect
> > > >
> > > > Mike,
> > > >
> > > >   This is a classic Allstar registration problem. Send a personal
> email
> > > to
> > > > me with your node numbers and I will get you Hamvoip registrations.
> > This
> > > > should solve your problem but remember you cannot normally have
> > incoming
> > > > connections on a hotspot as they do not have port forwarding.
> > Connecting
> > > > from a hotspot to other nodes should work fine.
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > >
> > > > On Thu, Aug 8, 2019 at 4:16 PM "Mike Sullivan via ARM-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > I am helping a club set up an Allstar node.. we are using a
> temporary
> > > > > hotspot from Unreal Mobile which uses AT&T's network. I've done all
> > > > > the required port forwarding and such, but when I try to connect
> > their
> > > > > node to ours (mind you, not plugged in to the repeater) the
> > connection
> > > > > is failing.
> > > > >
> > > > > When I try to connect from theirs to ours, my Allstar log displays
> > > > > this message (IP's removed for protection)
> > > > > [Aug  8 15:50:59] WARNING[22390] app_rpt.c: Node 50227 IP
> > > > > xxx.yyy.zzz.202 does not match link IP xxx.yyy.zzz.201!!
> > > > >
> > > > > When I try to connect from ours to theirs, I get this notice in the
> > > > > Allstar log
> > > > > [Aug  8 15:52:51] NOTICE[21609] chan_iax2.c: Auto-congesting call
> due
> > > > > to slow response
> > > > >
> > > > > I'm not entirely sure how to fix this, it's almost like the hotspot
> > is
> > > > > producing two IP's somehow. Any ideas?
> > > > >
> > > > > Mike
> > > > > _______________________________________________
> > > > >
> > > > > 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
> > > > _______________________________________________
> > > >
> > > > 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
> > >
> > _______________________________________________
> >
> > 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
>