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
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/call-automation/actions-for-call-control.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,11 +168,9 @@ The response provides you with CallConnection object that you can use to take fu
168
168
169
169
## Connect to a call
170
170
171
-
You can create a connection to a call using CallLocator, then you can manage the call and perform actions in the call using Call Automation.
171
+
Connect action enables your service to join an ongoing call to manage it and perform actions. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator.
172
172
173
-
Currently, we support 3 different CallLocators:ServerCallLocator, GroupCallLocator, and RoomCallLocator
174
-
175
-
To connect to a call using ServerCallLocator, which take a serverCallId. You can use it to connect to regular P2P or multi-parties call.
173
+
ServerCallLocator takes the serverCallId and can be used to connect to any 1:1 or group call.
The response provides you with CallConnection object that you can use to take further actions on this call once it successfully connect to a call. Once it connects to the call, two events are published to the callback endpoint you provided earlier:
281
-
278
+
A successful response provides you with CallConnection object that you can use to take further actions on this call. Two events are published to the callback endpoint you provided earlier:
282
279
1.`CallConnected` event notifying that you successfully connect to the call.
283
280
2.`ParticipantsUpdated` event that contains the latest list of participants in the call.
284
281
285
-

282
+
Failure to connect to the call results in ConnectFailed event.
286
283
284
+

0 commit comments