Hello!   I wanted to ask for guidence here as i have an issue at my work with our WiFi.   Some of our users (Not all of them) have issues in certain conference rooms when having meetings over teams.   The problems they have is that during the meetings the call can freeze and you see the "Trying to reconnect Call" message in teams and then 20 seconds later it's all fine.   What the users have seen when this happens is that the WiFi icon in windows drop from 3 to 1 bar and then it go back up to 3 again and everything is alright for the rest of the meeting.   This however is not a windows specific thing as employees with Mac and Linux have reported the issues as well.   Unfortunately when i have tested this in the specific conference rooms everything has worked as it should.   The only thing i have noticed is that when the issues occur the machine is connected to a AP that is where the user was sitting before the meeting and the machine then roams to a nearby AP. Why this would cause a 20 second freeze in teams i do not know however.   I have tried to change the transmit power to see if the computers will roam earlier but doesn't seem to make a difference.   What i have tried: Changed AP's from 6 year old devices to new CW9162I AP's Slightly changing the location of the AP's to try and not make them overlap too much Doing a netspot survey and it said everything was fine from what it could see Changing the roaming aggressivenes setting on the Windows machines. Disabling 2.4 GHz and only allowing 5&6 GHz Changing radio transmit power to 14-17dBm for 5 GHz and 17-20dBm for 6GHz Updated WiFi drivers on the Windows machines Added traffic shaping for the teams services with the Expedited forwarding DSCP tag   Sorry for the long text but i am a bit out of ideas. We don't have a large office and use 6 AP's. We have our office in a new wooden based building so no concrete walls that block signals either.   We use MX95 as the main router and then MS225-24 for the switches ... View more

Hello community!   Not sure this is the correct category but i hope it is.   I am using the early-access function access manager together with Entra ID to setup WiFi authorization at my company. Just a test for now to see if it works and are not a hassle for the end users.   I have got everything setup. It works in the sense that i can use my Entra ID credentials to access the SSID i have setup for this test and i get connected. But now the problem. When i get connected i do not get an IP from Meraki.   I can see that my access rules are added to my connection and that the VLAN ID is also added but Meraki doesn't seem to want to use that ID when requesting a IP for me.   In the event logs i see that it tries to request an IP from VLAN 1 and of course i do not give out any IP's on that VLAN and therefore it fails.   Is there some step that i have missed or why does it not want to use my access rule VLAN to request an IP? ... View more