Do you want successful Teams Development for Real time media/Teams call quality for your 1:1 or Conference, please ensure below rule’s followed.
Kudos to Jonathan, Steenan!
1) Make sure the right ports and protocols are opened.
Subnets, 13.107.64.0/18, 52.112.0.0/14, 52.122.0.0/15, 2603:1063: :/39 and Ports: UDP 3478-3481 & TCP 443,80 are needed for Teams signalling and real time media traffic (Real time modalities: Audio, Video and Screen sharing).
Note: 52.122.0.0/15 is a smaller range you should review in your firewall. However this overlaps within the 52.112.0.0/14 range.
2) Bypass Proxy and deep packet inspection
Bypass both on-premises and cloud-based proxy and inspection services.
3) Implement VPN split tunneling to bypass Real Time media
This ensures direct connectivity between Teams clients and Teams meeting services.
4) Local DNS resolution for automatic selection of closest endpoints
Microsoft services have a global presence and use geo-based DNS solutions to load balance and allocate services closest to the endpoint.
5) Ensure shortest path to the Microsoft Datacenter
Work with your ISP and make sure that the most direct path to the Microsoft datacenter is ensured,. This ensure real time media traffic enters the Microsoft managed network faster with fewer hops and points of failure in between.
6) Apply both outbound and Inbound QoS where needed
This specifically applies for congested network paths. Make sure large file transfers does not impact your neighbors Teams call, by prioritizing the Real time media packets with DSCP marking. Inbound tagging is done on the ingress on predefined media ports. Outbound can be done with DSCP marking policies on the Teams clients.
7) Exclude important Processes from anti-virus and / or Data Loss Prevention scanning services.
Teams.exe excluded prevents excess CPU load when making calls effectively slowing down the overall performance of your client and thus impacts the overall media call quality.
No comments:
Post a Comment