Skip to content

Commit 22a10e1

Browse files
authored
updated details to note how to best use SDK to see if connected to Microsoft infrastrucutre
1 parent b30925f commit 22a10e1

File tree

1 file changed

+1
-3
lines changed
  • articles/communication-services/how-tos/calling-sdk/includes/install-sdk

1 file changed

+1
-3
lines changed

articles/communication-services/how-tos/calling-sdk/includes/install-sdk/install-sdk-web.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,7 @@ const deviceManager = await callClient.getDeviceManager()
4646

4747
### How to best manage SDK connectivity to Microsoft infrastructure
4848

49-
The `Call Agent` instance lets you manage calls and join or start them. Your calling SDK needes to connect to Microsoft infrastructure to get notification of incoming calls and coordinate other call details. Sometimes the connection may fail be disconnected.
50-
51-
Your call `Call Agent` will be in 2 possible states:
49+
The `Call Agent` instance helps you manage calls (to join or start calls). In order to work your calling SDK needs to connect to Microsoft infrastructure to get notifications of incoming calls and coordinate other call details. Sometimes the connection may fail be disconnected. To give you signal what the current state of your call `Call Agent` will be in 2 possible states:
5250

5351
**Connected** - A `Call Agent` connectionStatue value of `Connected` means the client SDK is connected and capable of receiving notifications from Microsoft infrastructure.
5452

0 commit comments

Comments
 (0)