Skip to content

Commit 3f44120

Browse files
authored
Update proxy-calling-support-tutorial.md
1 parent 6f1e8ff commit 3f44120

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

articles/communication-services/tutorials/proxy-calling-support-tutorial.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,19 +14,18 @@ ms.custom: mode-other
1414
---
1515
# How to force calling traffic to be proxied across your own servers
1616

17-
In certain situations, it might be useful to have all your client traffic proxied to a server that you can control. When the SDK is initializing, you can provide the details of your servers that you would like the traffic to route to. Once enabled all the media traffic (audio/video/screen sharing) travel through the provided TURN servers instead of the Azure Communication Services defaults. When you define that a TURN server should be used when initializing the `CallClient`, all the calls to and from this `CallClient` will be using the provided TURN servers. This tutorial will guide on how to have WebJS SDK calling traffic be proxied to servers that you control.
17+
In certain situations, it might be useful to have all your client traffic proxied to a server that you can control. When the SDK is initializing, you can provide the details of your servers that you would like the traffic to route to. Once enabled all the media traffic (audio/video/screen sharing) travel through the provided TURN servers instead of the Azure Communication Services defaults. When you define that a TURN server should be used when initializing the `CallClient`, all the calls to and from this `CallClient` will use the provided TURN servers. This tutorial guides on how to have WebJS SDK calling traffic be proxied to servers that you control.
1818

1919
>[!IMPORTANT]
2020
> The proxy feature is available starting in the public preview version [1.13.0-beta.4](https://www.npmjs.com/package/@azure/communication-calling/v/1.13.0-beta.4) of the Calling SDK. Please ensure that you use this or a newer SDK when trying to use this feature. This Quickstart uses the Azure Communication Services Calling SDK version greater than `1.13.0`.
2121
2222
[!INCLUDE [Public Preview](../includes/public-preview-include-document.md)]
2323

2424
## What is a TURN server?
25-
Many times, establishing a network connection between two peers is not straightforward. A direct connection will not work because of many reasons: firewalls with strict rules, peers sitting behind a private network, or computers are running in a NAT environment. To solve these network connection issues a common way to solve this is by using a TURN server. The term stands for Traversal Using Relays around NAT, and it is a protocol for relaying network traffic STUN and TURN servers are the relay servers here. See [Network Traversal Concepts](../concepts/network-traversal.md) for more details on how ACS mitigates network challenges with STUN and TURN.
26-
25+
Many times, establishing a network connection between two peers isn't straightforward. A direct connection might not work because of many reasons: firewalls with strict rules, peers sitting behind a private network, or computers are running in a NAT environment. To solve these network connection issue you can use a TURN server. The term stands for Traversal Using Relays around NAT, and it's a protocol for relaying network traffic STUN and TURN servers are the relay servers here. See [Network Traversal Concepts](../concepts/network-traversal.md) for more details on how ACS mitigates network challenges with STUN and TURN.
2726

2827
## Providing your TURN servers details to the SDK
29-
To provide the details of your TURN servers, you need to pass details of what TURN server to use as part of `CallClientOptions` while initializing the `CallClient`. For more details on on to setup a call see [Azure Communication Services Web SDK](../quickstarts/voice-video-calling/get-started-with-video-calling.md?pivots=platform-web)) Quickstart on how to setup Voice and Video.
28+
To provide the details of your TURN servers, you need to pass details of what TURN server to use as part of `CallClientOptions` while initializing the `CallClient`. For more details how to setup a call see [Azure Communication Services Web SDK](../quickstarts/voice-video-calling/get-started-with-video-calling.md?pivots=platform-web)) for the Quickstart on how to setup Voice and Video.
3029

3130
```js
3231
import { CallClient } from '@azure/communication-calling';
@@ -68,7 +67,7 @@ const callClient = new CallClient({
6867
```
6968

7069
> [!IMPORTANT]
71-
> Note that if you have provided your TURN server details while initializing the `CallClient`, all the media traffic will <i>exclusively</i> flow through these TURN servers. Any other ICE candidates that are normally generated when creating a call will not be considered while trying to establish connectivity between peers i.e. only 'relay' candidates will be considered. To learn more about different types of Ice candidates can be found [here](https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidate/type).
70+
> Note that if you have provided your TURN server details while initializing the `CallClient`, all the media traffic will <i>exclusively</i> flow through these TURN servers. Any other ICE candidates that are normally generated when creating a call won't be considered while trying to establish connectivity between peers i.e. only 'relay' candidates will be considered. To learn more about different types of Ice candidates can be found [here](https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidate/type).
7271
7372
> [!NOTE]
7473
> If the '?transport' query parameter is not present as part of the TURN url or is not one of these values - 'udp', 'tcp', 'tls', the default will behaviour will be UDP.
@@ -80,6 +79,5 @@ The API reference for the `CallClientOptions` object, and the `networkConfigurat
8079

8180
## Setting up a TURN server in Azure
8281
You can create a Linux virtual machine in the Azure portal using this guide - [Quickstart: Create a Linux virtual machine in the Azure portal](/azure/virtual-machines/linux/quick-create-portal?tabs=ubuntu), and deploy a TURN server using [coturn](https://github.com/coturn/coturn), a free and open source implementation of a TURN and STUN server for VoIP and WebRTC.
83-
Best spot to start from - [coturn turnserver README](https://github.com/coturn/coturn/blob/master/README.turnserver)
8482

85-
Once you've setup a TURN server, you can test it using the WebRTC Trickle ICE page - [Trickle ICE](https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/).
83+
Once you have setup a TURN server, you can test it using the WebRTC Trickle ICE page - [Trickle ICE](https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/).

0 commit comments

Comments
 (0)