topic Microsoft Teams IP Routing WiFi vs Ethernet in ExtremeCloud IQ

Microsoft Teams IP Routing WiFi vs Ethernet

jason_hills — Wed, 17 Jun 2020 16:37:37 GMT

Extreme/Aerohive and Teams routing:
I don't think we have a WiFi problem (AP550s) but would like to rule the APs as a cause.
Customer has Teams with media traffic terminated at the intended provider's point. Unfortunately the WiFi connected laptops running Teams selects the Microsoft Teams end point (52.112.0.0/14) instead of the intended Provider's local end point. When same laptop is connected to Wired ethernet, Teams correctly routes to the provider's end point. Interestingly a tracert from the WiFi connected laptop successfully reaches the provider's end point.

We then enabled a firewall on the APs blocking the 52.112.0.0/14 range, the WiFi connected laptop was attempting to reach the provider's endpoint (PCAP results) but could not complete the call - the phone would only ring. Something along the route may be blocking the ports for the provider's endpoint.

The APs do not have any firewall enabled. Application port-based sets are used to identify Teams to assign DSCP QoS.

Wondering where else to investigate.

Re: Microsoft Teams IP Routing WiFi vs Ethernet

Ronald_Dvorak — Wed, 17 Jun 2020 18:22:10 GMT

Does the LAN and WLAN use the same subnet/VLAN = has the laptop the same IP subnet in WLAN/LAN.

If different VLANs are used for LAN/WLAN setup a test and put the WLAN client in the same and check the result or vice-versa if that is easier put a LAN client in the WLAN VLAN.

-Ron

Re: Microsoft Teams IP Routing WiFi vs Ethernet

jason_hills — Thu, 18 Jun 2020 03:36:58 GMT

Thanks Ronald. Different subnets are used for the LAN and WLAN. This was also what I first asked to be checked. They assure that the firewall gateway is the same for both subnets.

A tracert succeeds from the WLAN client to the provider’s local end point.

I will ask to put the Wireless client on the LAN subnet - good idea.

cheers

Jason

Re: Microsoft Teams IP Routing WiFi vs Ethernet

jason_hills — Thu, 18 Jun 2020 07:42:29 GMT

Once again, we can proclaim: “It’s not the WiFi”

They found a static route was missed on the WLAN that was included on the LAN. This was one of the first areas we had asked to be checked, before looking at WLAN config.

Thanks for your recommendation @Ronald Dvorak