Wireless Access

Does anyone use the WiFi Phone Unidata 7800 with an Aruba infrastructure?!

I have some problems about continuos deauthentication received by this phone, so I would to compare myself with someone else that have implemented the same situation.

Thanks,

Massimo

What encryption are you using with the Unidata Phone?

Have you turned on user debugging for the phone, to see what is actually happening with that phone?  http://community.arubanetworks.com/t5/Technology-Blog/Two-Different-Ways-to-Debug-a-User-on-Aruba-and-Why-You-Would/ba-p/77006

Yes, I turned on user debugging on the phone. I use WPA2-PSK/AES for encryption, but the phone doesn't have problem with encryption. The messagges of deauthentication are these:

Oct 29 10:44:46  stm[2310]: <501105> <NOTI> |stm|  Deauth from sta: 00:03:2a:25:1b:4a: AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Reason Tx fail reached maximum
Oct 29 10:44:46  authmgr[4251]: <522036> <INFO> |authmgr|  MAC=00:03:2a:25:1b:4a Station DN: BSSID=00:24:6c:80:ae:b4 ESSID=WiFi_RED VLAN=3 AP-name=
Oct 29 10:44:46  authmgr[4251]: <522234> <DBUG> |authmgr|  Setting idle timer for user 00:03:2a:25:1b:4a to 15300 seconds (idle timeout: 15300 ageout: 0).
Oct 29 10:44:46  stm[2310]: <501000> <DBUG> |stm|  Station 00:03:2a:25:1b:4a: Clearing state
Oct 29 10:44:46  stm[685]: <501106> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU handle_sapcp
Oct 29 10:44:46  stm[685]: <501080> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Tx fail reached maximum
Oct 29 10:44:46  stm[685]: <501000> <DBUG> |AP APADU@10.20.0.39 stm|  Station 00:03:2a:25:1b:4a: Clearing state
Oct 29 10:45:49  stm[685]: <501106> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU handle_sapcp
Oct 29 10:45:49  stm[2310]: <501105> <NOTI> |stm|  Deauth from sta: 00:03:2a:25:1b:4a: AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Reason Tx fail reached maximum
Oct 29 10:45:49  stm[2310]: <501044> <NOTI> |stm|  Station 00:03:2a:25:1b:4a: No authentication found trying to de-authenticate to BSSID 00:24:6c:80:ae:b4 on AP APADU
Oct 29 10:45:49  stm[685]: <501080> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Tx fail reached maximum
Oct 29 10:46:51  stm[685]: <501106> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU handle_sapcp
Oct 29 10:46:51  stm[2310]: <501105> <NOTI> |stm|  Deauth from sta: 00:03:2a:25:1b:4a: AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Reason Tx fail reached maximum
Oct 29 10:46:51  stm[2310]: <501044> <NOTI> |stm|  Station 00:03:2a:25:1b:4a: No authentication found trying to de-authenticate to BSSID 00:24:6c:80:ae:b4 on AP APADU
Oct 29 10:46:51  stm[685]: <501080> <NOTI> |AP APADU@10.20.0.39 stm|  Deauth to sta: 00:03:2a:25:1b:4a: Ageout AP 10.20.0.39-00:24:6c:80:ae:b4-APADU Tx fail reached maximum

This happens randomly; today for example it happens continuosly, but for the three days ago It was never happened.

Others WIFi Phone (e.g. Snom or Polycom) connected to the same SSID don't show any problem.

Is it easy to replicate?  If so, we can attempt to increase the max-tx-fail parameter in the Advanced Settings of the SSID to see if it improves things.  By default it is zero, so change it to 25 and give it some time to see if things improve:

I set Maximum Trasìnsmit Failure = 20 from the beginning. If I change it to 25 I think I obtain only more times between deauthentications.

The strange thing is that with other phones this not happens.

---

@msmgll87 wrote:

I set Maximum Trasìnsmit Failure = 20 from the beginning. If I change it to 25 I think I obtain only more times between deauthentications.

The strange thing is that with other phones this not happens.

---

You can put it higher than 25.  The Unidata is not really a well supported phone, so if there is any incompatibility and issues, it will probably not get fixed like the other phones.  That is why we have to increase the maximum TX failures to allow for some of that.  You can increase it to even more than 25 if you are committed to making this phone work.  Otherwise, I can only hope that you can get some sort of help from Unidata, or you can replace it with a better supported phone.

Was the issue resolved with the maximum TX retries?

No, the issue is not resolved. It is still present. We will not give to our costumer Unidata phone with Aruba WiFi. I think that Unidata is not a very good product and it also hasn't a proper support.