You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Manage ACS SDK connectivity for incoming calls
48
+
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.
50
+
51
+
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`.
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.
0 commit comments