Skip to content

Commit 22604a4

Browse files
authored
Update actions-for-call-control.md
add preview label
1 parent 8f15055 commit 22604a4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/communication-services/how-tos/call-automation/actions-for-call-control.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,9 @@ The response provides you with CallConnection object that you can use to take fu
166166
2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
167167
![Sequence diagram for placing an outbound call.](media/make-call-flow.png)
168168

169-
## Connect to a call
169+
## Connect to a call (in preview)
170+
[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
171+
170172
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.
171173

172174
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.

0 commit comments

Comments
 (0)