Skip to content

Commit 6f0833b

Browse files
Update install-sdk-web.md
Fixed the score issue.
1 parent e500678 commit 6f0833b

File tree

1 file changed

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

1 file changed

+5
-5
lines changed

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

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

4747
### Manage ACS SDK connectivity for incoming calls
4848

49-
A `Call Agent` instance lets you start/join and manage incoming calls. Your `Call Agent` instance needs to be connected to ACS infrastructure to receive incoming calls. This connection is usually established when a `Call Agent` instance is created, but sometimes, for example when the network is unstable, the connection may not be set up, or it may break during the lifecycle of `Call Agent`. ACS SDK will always try to stay connected and it will retry to reconnect continuously.
49+
A `Call Agent` instance lets you start/join and manage incoming calls. Your `Call Agent` instance needs to be connected to ACS infrastructure to receive incoming calls. This connection is established when a `Call Agent` instance is created, but sometimes, for example when the network is unstable, the connection may not be set up, or it may break during the lifecycle of `Call Agent`. ACS SDK always tries to stay connected with ACS infrastructure. It keeps retrying to connect when the connection is lost.
5050

5151
You can check if `Call Agent` is connected to ACS infra by looking at the current value of `connectionState` property and listening to `connectionStateChanged` event from `Call Agent`.
5252

@@ -62,7 +62,7 @@ callAgentInstance.on('connectionStateChanged', connectionStateCallback);
6262
```
6363

6464
The above example illustrates how to manage connection state, whenever connection state is:
65-
- `Connected` - `Call Agent` instance is connected and capable of receiving notification from ACS infra, e.g. receiving incoming call notifications.
66-
- `Disconnected` - `Call Agent` instance is disconnected, this is a terminal state, `Call Agent` should be re-created, user should make sure it has no network problems.
67-
-- reason `invalidToken` - if token ACS token expired or is invalid and application failed to provide new valid token, `Call Agent` instance will disconnect with this reason.
68-
-- reason `connectionIssue` - if network is permanently down, and after many retries `Call Agent` fails to re-connect, it will permanently disconnect with this reason.
65+
- `Connected` - `Call Agent` instance is connected and capable of receiving notification from ACS infra. For example, receiving incoming call notifications.
66+
- `Disconnected` - `Call Agent` instance is disconnected. It is a terminal state. `Call Agent` should be re-created. Users should make sure it has no network problems.
67+
-- reason `invalidToken` - if ACS token expired or it's invalid and application failed to provide new valid token. `Call Agent` instance will disconnect with this reason.
68+
-- reason `connectionIssue` - if the network is down, and after many retries `Call Agent` fails to re-connect, it will disconnect with this reason. It usually indicates client network issues and can be re-stored as soon as the connectivity issue is resolved.

0 commit comments

Comments
 (0)