Skip to content

Commit 8abeb1c

Browse files
authored
Merge pull request #259721 from richardcho-msft/call-automation/ga2
Call automation GA2 release
2 parents a265b90 + c360746 commit 8abeb1c

File tree

2 files changed

+363
-21
lines changed

2 files changed

+363
-21
lines changed

articles/communication-services/concepts/call-automation/call-automation.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ The following list presents the set of features that are currently available in
4343
| | Redirect* (forward) a call to one or more endpoints | ✔️ | ✔️ | ✔️ | ✔️ |
4444
| | Reject an incoming call | ✔️ | ✔️ | ✔️ | ✔️ |
4545
| Mid-call scenarios | Add one or more endpoints to an existing call | ✔️ | ✔️ | ✔️ | ✔️ |
46+
| | Cancel adding an endpoint to an existing call | ✔️ | ✔️ | ✔️ | ✔️ |
4647
| | Play Audio from an audio file | ✔️ | ✔️ | ✔️ | ✔️ |
4748
| | Play Audio using Text-to-Speech | ✔️ | ✔️ | ✔️ | ✔️ |
4849
| | Recognize user input through DTMF | ✔️ | ✔️ | ✔️ | ✔️ |
@@ -53,6 +54,7 @@ The following list presents the set of features that are currently available in
5354
| | Mute participant | ✔️ | ✔️ | ✔️ | ✔️ |
5455
| | Remove one or more endpoints from an existing call| ✔️ | ✔️ | ✔️ | ✔️ |
5556
| | Blind Transfer* a 1:1 call to another endpoint | ✔️ | ✔️ | ✔️ | ✔️ |
57+
| | Blind Transfer* a participant from group call to another endpoint | ✔️ | ✔️ | ✔️ | ✔️ |
5658
| | Hang up a call (remove the call leg) | ✔️ | ✔️ | ✔️ | ✔️ |
5759
| | Terminate a call (remove all participants and end call)| ✔️ | ✔️ | ✔️ | ✔️ |
5860
| | Cancel media operations | ✔️ | ✔️ | ✔️ | ✔️ |
@@ -162,6 +164,8 @@ The Call Automation events are sent to the web hook callback URI specified when
162164
| CallTransferFailed | The transfer of your application’s call leg failed |
163165
| AddParticipantSucceeded| Your application added a participant |
164166
| AddParticipantFailed | Your application was unable to add a participant |
167+
| CancelAddParticipantSucceeded| Your application canceled adding a participant |
168+
| CancelAddParticipantFailed | Your application was unable to cancel adding a participant |
165169
| RemoveParticipantSucceeded| Your application has successfully removed a participant from the call. |
166170
| RemoveParticipantFailed | Your application was unable to remove a participant from the call. |
167171
| ParticipantsUpdated | The status of a participant changed while your application’s call leg was connected to a call |
@@ -182,6 +186,22 @@ To understand which events are published for different actions, refer to [this g
182186

183187
To learn how to secure the callback event delivery, refer to [this guide](../../how-tos/call-automation/secure-webhook-endpoint.md).
184188

189+
### Operation Callback Uri
190+
191+
It is an optional parameter in some mid-call APIs that use events as their async responses. By default, all events are sent to the default callback Uri set by CreateCall / AnswerCall API when the user establishes a call. With the usage of Operation Callback Uri, corresponding events of this individual (one-time only) request will be sent to the new Uri.
192+
193+
| Supported API | Corresponding event |
194+
| ----------------- | ------------ |
195+
| AddParticipant | AddParticipantSucceed / AddParticipantFailed |
196+
| RemoveParticipant | RemoveParticipantSucceed / RemoveParticipantFailed |
197+
| TransferCall | CallTransferAccepted / CallTransferFailed |
198+
| CancelAddParticipant | CancelAddParticipantSucceeded / CancelAddParticipantFailed |
199+
| Play | PlayCompleted / PlayFailed / PlayCanceled |
200+
| PlayToAll | PlayCompleted / PlayFailed / PlayCanceled |
201+
| Recognize | RecognizeCompleted / RecognizeFailed / RecognizeCanceled |
202+
| StopContinuousDTMFRecognition | ContinuousDtmfRecognitionStopped |
203+
| SendDTMF | ContinuousDtmfRecognitionToneReceived / ContinuousDtmfRecognitionToneFailed |
204+
185205
## Next steps
186206

187207
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)