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
+4-40Lines changed: 4 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,10 +167,9 @@ The response provides you with CallConnection object that you can use to take fu
167
167

168
168
169
169
## Connect to a call
170
+
Connect action enables your service to establish a connection with an ongoing call and take actions on it. This is useful to manage a Rooms call or when client applications started a 1:1 or group call that Call automation isn't part of. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator. These IDs can be found when the call is originally established or a Room is created, and also published as part of [CallStarted](./../../../event-grid/communication-services-voice-video-events.md#microsoftcommunicationcallstarted) event.
170
171
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
-
173
-
ServerCallLocator takes the serverCallId and can be used to connect to any 1:1 or group call.
172
+
To connect to any 1:1 or group call, use the ServerCallLocator. If you started a call using GroupCallId, you can also use the GroupCallLocator.
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:
279
243
1.`CallConnected` event notifying that you successfully connect to the call.
280
244
2.`ParticipantsUpdated` event that contains the latest list of participants in the call.
281
-
282
-
Failure to connect to the call results in ConnectFailed event.
245
+
246
+
At any point after a successful connection, if your service is disconnected from this call you will be notified via a CallDisconected event. Failure to connect to the call in the first place results in ConnectFailed event.
283
247
284
248

0 commit comments