By now I've written this off completely and any time a customer mentions VOIP, VPN, or port forwarding, I take the NAT out of the SM. Double NAT's do strange, stupid things.
Chris Wright Network Technician Velociter Wireless 209-838-1221 x115 -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of Bill Prince Sent: Thursday, March 12, 2015 12:49 PM To: [email protected] Subject: Re: [AFMUG] T-Mobile WiFi calling: Works with Canopy NAT? I'm ok with not "adding" new functionality. But the fragmented packet problem (for femtocells, and now some VoIP implementations) has been listed as a bug for quite a while (years in my book). Would be more comfortable that we could at least rely on bug fixes for a limited amount of time.. bp <part15sbs{at}gmail{dot}com> On 3/12/2015 12:38 PM, George Skorup (Cyber Broadcasting) wrote: > Yes, I believe it was part of the NAT throughput improvements in 13.2. > Which is yet another reason we need an updated release for FSK. Not to > mention all the new stuff we can't use, like the config import/export. > Aaron told me they know and they're working on it. > > On 3/12/2015 1:56 PM, Bill Prince wrote: >> So it's the fragmentation issue? >> >> bp >> <part15sbs{at}gmail{dot}com> >> >> On 3/12/2015 11:53 AM, George Skorup (Cyber Broadcasting) wrote: >>> Same as AT&T. And I think it was fixed it 13.2 (NAT fragmentation or >>> something), which obviously doesn't help FSK. >>> >>> On 3/12/2015 1:47 PM, Bill Prince wrote: >>>> >>>> One of our subscribers on a 900SM recently got T-Mobil WiFi calling. >>>> >>>> Unless there is something I'm missing, it appears that it will not >>>> work through Canopy NAT (SM and AP are on 13.1.3). >>>> >>>> We had their router (a "special" ASUS router no less) on the DMZ. >>>> It would make the UDP connection to T-Mobil through their port >>>> 4500, but would not go any further. When we turned off NAT in the >>>> SM, it started working. >>>> >>>> Any other tricks? >>>> >>> >> >
