09-24-2014 05:33 AM
Device works fine in other environments. Found a T-Mobile related thread and they did their OTA upgrade. No change. Just setting up wifi calling, or at least just started attempting to use it.
In Monitor all APs show as Voice Access Points. AP-105 & AP-125 & AP-135 are in use.
[Seems the whole Tech Dept has the same Android version so I am unable, at this point, to know if other devices can connect.]
Solved! Go to Solution.
09-24-2014 05:40 AM
09-24-2014 06:52 AM
Pretty much all factory defaults. No Captive Portal etc. Basic setup is three SSIDs on three VLANS that route to single DHCP server for appropriate IP range. LightSpeed handles authentication / access issues for the network / internet.
I see in Stateful Firewall, Network Services, that sys-svc-natt udp 4500 is listed.
Security, Authentication, User Rules is empty.
09-24-2014 06:58 AM
09-24-2014 07:42 AM
Does not get that far. (I ran it anyway.) Enable WiFi Calling on device, takes forever but eventually times out with REG99 - or just hangs forever.
09-24-2014 08:05 AM
Name Firewall Policies Bandwidth Contract Actions
|authenticated||allowall/,v6-allowall/||Up:Not Enforced Down:Not Enforced|
|default-via-role||allowall/||Up:Not Enforced Down:Not Enforced|
|default-vpn-role||allowall/,v6-allowall/||Up:Not Enforced Down:Not Enforced|
|guest||dhcp-acl/,http-acl/,https-acl/,icmp-acl/,dns-acl/,v6-http-acl/,v6-https-acl/,v6-dhcp-acl/,v6-icmp-acl/,v6-dns-acl/,LightspeedProxynew/||Up:Not Enforced Down:Not Enforced|
|guest-logon||logon-control/,captiveportal/,v6-logon-control/,captiveportal6/||Up:Not Enforced Down:Not Enforced|
|logon||logon-control/,captiveportal/,vpnlogon/,v6-logon-control/,captiveportal6/||Up:Not Enforced Down:Not Enforced|
|voice||sip-acl/,noe-acl/,svp-acl/,vocera-acl/,skinny-acl/,h323-acl/,dhcp-acl/,tftp-acl/,dns-acl/,icmp-acl/||Up:Not Enforced Down:Not Enforced|
10-02-2014 06:41 AM
Turns out to be a phone problem, not an Aruba problem. Android 4.4.2 on T-Mobile will not do WiFi calling on Aruba. Does work on some other networks, but...
As of today, 4.4.3 or better is not yet availble from T-Mobile to solve this issue.