Skip to content

Commit 687410c

Browse files
committed
Added step 2.3, reciprocal link, and TOC entry
Reciprocal link from Network recommendations
1 parent 2744dc9 commit 687410c

File tree

3 files changed

+17
-13
lines changed

3 files changed

+17
-13
lines changed

articles/communication-services/concepts/voice-video-calling/network-requirements.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ This article summarizes how the network environment affects voice and video call
2020

2121
## Network quality
2222

23-
The quality of real-time media over IP is significantly affected by the quality of the underlying network connectivity, but especially by the amount of:
23+
The the quality of the underlying network connectivity can adversely affect real-time media over IP. The most important contributing factors include:
2424

25-
* **Latency**. The time it takes to get an IP packet from point A to point B on the network. This network propagation delay is determined by the physical distance between the two points and any other overhead incurred by the devices that your traffic flows through. Latency is measured as one-way or round-trip time (RTT).
25+
* **Latency**. The time it takes to get an IP packet from point A to point B on the network. Network propagation delay is a factor of the physical distance between the two points and any other overhead incurred by the devices that your traffic flows through. Latency is measured as one-way or round-trip time (RTT).
2626
* **Packet loss**. A percentage of packets that are lost in a specific window of time. Packet loss directly affects audio quality—from small, individual lost packets having almost no impact to back-to-back burst losses that cause complete audio cut-out.
2727
* **Inter-packet arrival jitter, also known as jitter**. The average change in delay between successive packets. Communication Services can adapt to some levels of jitter through buffering. It's only when the jitter exceeds the buffering that a participant notices its effects.
2828

@@ -56,15 +56,15 @@ The following bandwidth requirements are for the native Windows, Android, and iO
5656

5757
## Firewall configuration
5858

59-
Communication Services connections require internet connectivity to specific ports and IP addresses to deliver high-quality multimedia experiences. Without access to these ports and IP addresses, Communication Services won't work properly. The list of IP ranges and allow listed domains that need to be enabled are:
59+
Communication Services connections require internet connectivity to specific ports and IP addresses to deliver high-quality multimedia experiences. Without access to these ports and IP addresses, Communication Services don't work properly. The list of IP ranges and allow listed domains that need to be enabled are:
6060

6161
| Category | IP ranges or FQDN | Ports |
6262
| :-- | :-- | :-- |
63-
| Media traffic | Range of Azure public cloud IP addresses 20.202.0.0/16 The range provided above is the range of IP addresses on either Media processor or Azure Communication Services TURN service. | UDP 3478 through 3481, TCP ports 443 |
63+
| Media traffic | Range of Azure public cloud IP addresses 20.202.0.0/16. The range provided here are the range of IP addresses on either Media processor or Azure Communication Services TURN service. | UDP 3478 through 3481, TCP ports 443 |
6464
| Signaling, telemetry, registration| *.skype.com, *.microsoft.com, *.azure.net, *.azure.com, *.office.com| TCP 443, 80 |
6565

6666

67-
The endpoints below should be reachable for U.S. Government GCC High customers only.
67+
Only U.S. Government GCC High customers can reach the following endpoints.
6868

6969
| Category | IP ranges or FQDN | Ports |
7070
| :-- | :-- | :-- |
@@ -75,11 +75,12 @@ The endpoints below should be reachable for U.S. Government GCC High customers o
7575
## Network optimization
7676

7777
The following tasks are optional and aren't required for rolling out Communication Services. Use this guidance to optimize your network and Communication Services performance or if you know you have some network limitations.
78+
7879
You might want to optimize further if:
7980

8081
* Communication Services runs slowly. Maybe you have insufficient bandwidth.
81-
* Calls keep dropping. Drops might be caused by firewall or proxy blockers.
82-
* Calls have static and cut out, or voices sound like robots. These issues might be caused by jitter or packet loss.
82+
* Calls keep dropping. Firewalls and proxy blockers can cause call drops.
83+
* Calls have static and cut out, or voices sound like robots. Jitter or packet loss can cause these problems.
8384

8485
| Network optimization task | Details |
8586
| :-- | :-- |
@@ -90,7 +91,7 @@ Validate NAT pool size | Validate the NAT pool size required for user connectivi
9091
| Intrusion detection and prevention guidance | If your environment has an [intrusion detection system](../../../network-watcher/network-watcher-intrusion-detection-open-source-tools.md) or intrusion prevention system deployed for an extra layer of security for outbound connections, allow all Communication Services URLs. |
9192
| Configure split-tunnel VPN | Provide an alternate path for Teams traffic that bypasses the virtual private network (VPN), commonly known as [split-tunnel VPN](/windows/security/identity-protection/vpn/vpn-routing). Split tunneling means that traffic for Communication Services doesn't go through the VPN but instead goes directly to Azure. Bypassing your VPN has a positive impact on media quality, and it reduces load from the VPN devices and the organization's network. To implement a split-tunnel VPN, work with your VPN vendor. Other reasons why we recommend bypassing the VPN: <ul><li> VPNs are typically not designed or configured to support real-time media.</li><li> VPNs might also not support UDP, which is required for Communication Services.</li><li>VPNs also introduce an extra layer of encryption on top of media traffic that's already encrypted.</li><li>Connectivity to Communication Services might not be efficient because of hair-pinning traffic through a VPN device.</li></ul>|
9293
| Implement QoS | [Use Quality of Service (QoS)](/microsoftteams/qos-in-teams) to configure packet prioritization. QoS improves call quality and helps you monitor and troubleshoot call quality. QoS should be implemented on all segments of a managed network. Even when a network is adequately provisioned for bandwidth, QoS provides risk mitigation if unanticipated network events occur. With QoS, voice traffic is prioritized so that these unanticipated events don't negatively affect quality. |
93-
| Optimize Wi-Fi | Similar to VPN, Wi-Fi networks aren't necessarily designed or configured to support real-time media. Planning for, or optimizing, a Wi-Fi network to support Communication Services is an important consideration for a high-quality deployment. Consider these factors: <ul><li>Implement QoS or Wi-Fi Multimedia to ensure that media traffic is getting prioritized appropriately over your Wi-Fi networks.</li><li>Plan and optimize the Wi-Fi bands and access point placement. The 2.4-GHz range might provide an adequate experience depending on access point placement, but access points are often affected by other consumer devices that operate in that range. The 5-GHz range is better suited to real-time media because of its dense range, but it requires more access points to get sufficient coverage. Endpoints also need to support that range and be configured to use those bands accordingly.</li><li>If you're using dual-band Wi-Fi networks, consider implementing band steering. Band steering is a technique implemented by Wi-Fi vendors to influence dual-band clients to use the 5-GHz range.</li><li>When access points of the same channel are too close together, they can cause signal overlap and unintentionally compete, which results in a degraded user experience. Ensure that access points next to each other are on channels that don't overlap.</li></ul> Each wireless vendor has its own recommendations for deploying its wireless solution. Consult your Wi-Fi vendor for specific guidance.|
94+
| Optimize Wi-Fi | Similar to VPN, Wi-Fi networks aren't necessarily designed or configured to support real-time media. Planning for, or optimizing, a Wi-Fi network to support Communication Services is an important consideration for a high-quality deployment. Consider these factors: <ul><li>Implement QoS or Wi-Fi Multimedia to ensure that media traffic is getting prioritized appropriately over your Wi-Fi networks.</li><li>Plan and optimize the Wi-Fi bands and access point placement. The 2.4-GHz range might provide an adequate experience depending on access point placement. Other consumer devices that operate in that range can also negatively affect access points. The 5-GHz range is better suited to real-time media because of its dense range, but it requires more access points to get sufficient coverage. Endpoints also need to support that range and configured to use those bands accordingly.</li><li>If you're using dual-band Wi-Fi networks, consider implementing band steering. Band steering is a technique implemented by Wi-Fi vendors to influence dual-band clients to use the 5-GHz range.</li><li>When access points of the same channel are too close together, they can cause signal overlap and unintentionally compete, which results in a degraded user experience. Ensure that access points next to each other are on channels that don't overlap.</li></ul> Each wireless vendor has its own recommendations for deploying its wireless solution. Consult your Wi-Fi vendor for specific guidance.|
9495

9596
## Operating systems and browsers (for JavaScript SDKs)
9697

@@ -99,8 +100,7 @@ Learn about the operating systems and browsers that the calling SDKs support in
99100

100101
## Next steps
101102

102-
The following articles might be of interest to you:
103-
104103
- Learn more about [calling libraries](./calling-sdk-features.md).
105104
- Learn about [client-server architecture](../client-and-server-architecture.md).
106105
- Learn about [call flow topologies](../call-flows.md).
106+
- Learn about [integrating Azure Communication Services with Azure ExpressRoute](../../tutorials/integrate-express-route.md).

articles/communication-services/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -463,6 +463,8 @@ items:
463463
href: concepts/call-flows.md
464464
- name: Call flow topologies
465465
href: concepts/detailed-call-flows.md
466+
- name: Integrate with Azure ExpressRoute
467+
href: tutorials/integrate-express-route.md
466468
- name: Advanced audio and video features
467469
items:
468470
- name: Music mode

articles/communication-services/tutorials/integrate-express-route.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Integrate Azure Communication Services with ExpressRoute
3-
titleSuffix: An Azure Communication Services tutorial
3+
titleSuffix: An Azure Communication Services article
44
description: Integrate Azure Communication Services with ExpressRoute to extend your local networks into the Microsoft cloud over a private connection.
55
author: hrazi
66
manager: mharbut
@@ -64,11 +64,13 @@ Route filters enable you to selectively consume services over ExpressRoute.
6464

6565
1.2. Provide a name, select your subscription and resource group.
6666

67-
2. Add Azure Communication Services to the route filter:
67+
2. Add Azure Communication Services to the route filter:
6868

6969
2.1. After creating the route filter, select **Rules** and click **+ Add**.
7070

71-
2.2. Choose Azure Communication Services from the list of services.
71+
2.2. Choose Azure Communication Services from the list of services.
72+
73+
2.3. If you use Microsoft PSTN, choose Azure SIP Trunking from the list of services.
7274

7375
3. Associate route filter with ExpressRoute Circuit:
7476

0 commit comments

Comments
 (0)