I experience strange behavior I our conductor/controller/Eduroam environment,
after upgrading to 188.8.131.52_85105. on sep. 30.
There are logon problems, and MS Teams cut off trouble.
The logon is rejected numerus times, all on MS window, Ios, and Android devices,
before one successful.
Some MS Teams works flawless for the duration of the call.
Some AP's blink with orange led…
I have identified this to be related to only AP-655,
and Teams calling one to one. (Teams meeting ok)
On a one to one call, an extreme packed loss,
and connection failures is experienced.
It is on all SSID's, intra ssid, or from one to one-other
Anyone else ?
All clients, win10/11, Ios, Android, no ping loss, and no other application with problems.
And duly noted, at Microsoft (Teams admin center)
Other Aruba AP
We are experiencing similar issues with 184.108.40.206. We currently have an open case that has been escalated to engineering. With Teams one to one calls we get a delay starting (around 11 seconds) with no issues on conferences calls generally, users to report teams experience being "rubbish". With skype for business we get one way audio and the call drops after around 30 seconds or so; the captures we sent over to Aruba TAC have shown the packets being sent over the air to the client but their not in the client packet capture. Oddly when the client has one way audio they also can't access dropbox.com!We have this issue on both 515 and 535 APs. We found yesterday that a 303h AP connected to the same controller doens't have the issue.
Thank you all,
Yes yesterday I had a whole day with tac
aviating report, but no change, however it revealed that the problem
extended to series 5xx as well.
Only when under coverage of 2xx/3xx, Teams calls are flawless.
No other than stating a lot off small packed (UDP), at the clients; are observed,
Most of the packet length is below 600 on a 655; and above 1000 bytes when it is connected to working AP(2xx/3xx)