[arm-allstar] Still struggleing with NAT

[David McGough]

Hi Chris,

I'll work with you off list, since I believe this is a site specific 
issue, not a generalized problem.

The FreePBX NAT setting is in regard to SIP traffic, not IAX traffic. SIP 
is a more complex protocol that uses many UDP ports. Usually, SIP is much 
harder to get working, when behind a NAT firewall.


73, David KB4FXC

On Fri, 24 Jul 2020, "Chris Zenchenko via ARM-allstar" wrote:

> As mentioned in my previous message I can no longer stay connected when
> transmitting to nodes outside my network.
> With the 5268AC in DMZ and my router receiving the public address most
> everything works other than allstar.
> My Freepbx works just fine for both inbound and outbound SIP calls.
> That version of Asterisk has a configuration option that lets you set if you
> are using a NAT along with the info on the LAN being used.
> It seems to be just fine.
> If I switch to port forwarding and use the firewall and forwarding from the
> 5268AC to my router then Freepbx doesn't handle inbound calls.
> The techs at my VOIP supplier say the packets are showing double NAT and
> that is preventing inbound calls.
> There must be something associated with my IAX2 packets since I can easily
> connect to other nodes.
> I can listen forever but only transmit for about 5 seconds before the
> outbound TX quits.
> The next transmit attempt causes the node to try and reconnect but after a
> minute or so I get a node disconnected message.
> This might not be strictly a Allstar issue but if NAT options make other
> Asterisk installations function maybe there is something in the version we
> run that I am overlooking.
> If nothing else I'd sure like to know what is in the packets that is causing
> the TX to barf.
> tnx
> 
> _______________________________________________
> 
> 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/4 web page - http://hamvoip.org
>