Skip to content

Commit c32cafa

Browse files
Merge pull request #290512 from ashwinder/patch-9
GA4 updates for CA signaling features
2 parents 982cf1f + f071fde commit c32cafa

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,6 @@ Communication Services offers the following types of logs that you can enable:
7676
| `ServerCallId` | A unique ID to identify a call. |
7777
| `SDKVersion` | The SDK version used for the request. |
7878
| `SDKType` | The SDK type used for the request. |
79-
| `ParticipantId` | The ID to identify the call participant that made the request. |
8079
| `SubOperationName` | The name that's used to identify the subtype of media operation (play or recognize). |
8180
|`operationID`| The ID that's used to correlate asynchronous events.|
8281

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The following features are currently available in the Azure Communication Servic
3939
| | Place new outbound call to one or more endpoints | ✔️ | ✔️ | ✔️ | ✔️ |
4040
| | Redirect* (forward) a call to one or more endpoints | ✔️ | ✔️ | ✔️ | ✔️ |
4141
| | Reject an incoming call | ✔️ | ✔️ | ✔️ | ✔️ |
42-
| | Connect to an ongoing call or Room (in preview) | ✔️ | ✔️ | ✔️ | ✔️ |
42+
| | Connect to an ongoing call or Room | ✔️ | ✔️ | ✔️ | ✔️ |
4343
| Mid-call scenarios | Add one or more endpoints to an existing call | ✔️ | ✔️ | ✔️ | ✔️ |
4444
| | Cancel adding an endpoint to an existing call | ✔️ | ✔️ | ✔️ | ✔️ |
4545
| | Play Audio from an audio file | ✔️ | ✔️ | ✔️ | ✔️ |
@@ -64,7 +64,7 @@ The following features are currently available in the Azure Communication Servic
6464
| | List all participants in a call | ✔️ | ✔️ | ✔️ | ✔️ |
6565
| Call Recording | Start/pause/resume/stop recording | ✔️ | ✔️ | ✔️ | ✔️ |
6666

67-
\* Transfer or redirect of a VoIP call to a phone number is currently not supported.
67+
\* Redirect of a VoIP call to a phone number is not supported.
6868

6969
## Architecture
7070

@@ -84,11 +84,11 @@ These actions are performed before the destination endpoint listed in the `Incom
8484

8585
**Reject** – To reject a call means your application can receive the `IncomingCall` event and prevent the call from being connected to the destination endpoint.
8686

87-
**Redirect** – Using the `IncomingCall` event from Event Grid, you can redirect a call to one or more endpoints creating a single or simultaneous ringing (sim-ring) scenario. Redirect action doesn't answer the call. The call is redirected or forwarded to another destination endpoint to be answered.
87+
**Redirect** – Using the `IncomingCall` event from Event Grid, you can redirect a call to another endpoint. Redirect action doesn't answer the call. The call is redirected or forwarded to another destination endpoint to be answered.
8888

8989
**Create Call** - Use the Create Call action to place outbound calls to phone numbers and to other communication users. Use cases include your application placing outbound calls to proactively inform users about an outage or notify about an order update.
9090

91-
**Connect Call** (in preview) - Use the Connect Call action to connect to an ongoing call and take call actions on it. You can also use this action to connect and [manage a Rooms call programmatically](./../../quickstarts/rooms/manage-rooms-call.md), like performing PSTN dial outs for Room using your service.
91+
**Connect Call** - Use the Connect Call action to connect to an ongoing call and take call actions on it. You can also use this action to connect and [manage a Rooms call programmatically](./../../quickstarts/rooms/manage-rooms-call.md), like performing PSTN dial outs for Room using your service.
9292

9393
### Mid-call actions
9494

@@ -153,6 +153,7 @@ The Call Automation events are sent to the web hook callback URI specified when
153153
| `CallConnected` | The call successfully started (when using `Answer` or `Create` action) or your application successfully connected to an ongoing call (when using `Connect` action). |
154154
| `CallDisconnected` | Your application has been disconnected from the call. |
155155
| `CreateCallFailed` | Your application has failed to create the call. |
156+
| `AnswerFailed` | Your application has failed to answer the call. |
156157
| `ConnectFailed` | Your application failed to connect to a call (for `Connect` call action only). |
157158
| `CallTransferAccepted` | Transfer action successfully completed and the transferee is connected to the target participant. |
158159
| `CallTransferFailed` | The transfer action failed. |

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,9 +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-
In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on Call Automation error codes).
169+
In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on error codes).
170170

171-
## Connect to a call (in preview)
171+
## Connect to a call
172172

173173
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.
174174

@@ -303,6 +303,8 @@ The response provides you with CallConnection object that you can use to take fu
303303

304304
![Sequence diagram for answering an incoming call.](media/answer-flow.png)
305305

306+
In the case where answer operation fails, you will receive a `AnswerFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on error codes).
307+
306308
## Reject a call
307309

308310
You can choose to reject an incoming call as shown below. You can provide a reject reason: none, busy or forbidden. If nothing is provided, none is chosen by default.

articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ services: azure-communication-services
1616

1717
# Add a Microsoft Teams user to an existing call using Call Automation
1818

19-
[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
20-
2119
In this quickstart, we use the Azure Communication Services Call Automation APIs to add, remove, and transfer call to a Teams user.
2220

2321
## Prerequisites

0 commit comments

Comments
 (0)