[arm-allstar] arm-allstar Digest, Vol 28, Issue 33

[Bryan D. Boyle]

The problem is, as Doug points out, that AT&T is doing some NATing somewhere along the way, and as you switch cells, reassigning the IP address.

I've been, since November last, had a node on an AT&T hotspot working fine.  There is the capability to proxy an IAX connection; basically a fixed hub registers for you, and your hotspot node auth's to that hub on a regular basis.  

Scott KB2EAR is my upstream proxy for node 42366; you may want to contact him for more information (I'm on business travel this week, so can't be more help).  But, I am on AT&T, and it seems to work ok; not as good as a fixed node, but it does work at about 95% reliability...

--
Bryan
Sent from my iPhone 6S...No electrons were harmed in the sending of this message.



> 
> Message: 2
> Date: Wed, 21 Sep 2016 03:01:38 -0400
> From: Doug Crompton <doug at crompton.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] AT&T Wireless
> Message-ID: <BLU171-W46F173FE0CA32361E37AB6BAF60 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> James,
> 
>  I have not known anyone to be successful with AT&T phone hotspots and Allstar. Thats not to say it can't be done you would just need to use a VPN. We are working on a likely fix for this that will be in a future code update. 
> 
> I know of several people who have switched to Verizon or some other service just because of this. The problem lies in the perceived public IP address in Allstar. It is not the same as the phone actual assigned public IP address. There is some form of NAT'ing going on in the AT&T system. Using AT&T your server will receive a public IP but either never register with Allstar or register but never get a node list.
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160921/38c31eae/attachment.html>