Skip to content

Commit bd64d98

Browse files
authored
Update actions-for-call-control.md
added CreateCallFailed and CallDisconnected events to making an outbound call
1 parent 67fe8de commit bd64d98

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,8 @@ 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+
In the case where the call fails, you will receive a `CreateCallFailed` and `CallDisconnected` event.
170+
169171
## Connect to a call (in preview)
170172

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

0 commit comments

Comments
 (0)