Skip to content

Commit f30a2de

Browse files
committed
Update per comments
1 parent eeb5716 commit f30a2de

File tree

1 file changed

+12
-13
lines changed

1 file changed

+12
-13
lines changed

articles/communication-services/quickstarts/rooms/manage-rooms-call.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -11,25 +11,24 @@ ms.date: 07/10/2024
1111
ms.topic: quickstart
1212
ms.service: azure-communication-services
1313
ms.custom: mode-other
14-
zone_pivot_groups: acs-js-csharp-java-python
1514
---
1615

1716
# Quickstart: Manage a room call
1817

1918
## Introduction
20-
Once Azure Communication Services (ACS) room call has been successfully started, the call can be managed using Calling SDKs, Call Automation SDKs or both. In a room call, the mid-call actions are controlled by either the roles assigned to participants and properties configured in the room.
19+
Azure Communication Services (ACS) room call is started, the call can be managed using Calling SDKs, Call Automation SDKs or both. In a room call, the mid-call actions are controlled by either the roles assigned to participants and properties configured in the room.
2120

2221
## Calling SDKs
2322
Calling SDK is a client side calling libraries enabling participants in a room call to perform several mid-call operations (e.g. screen share, turn on/off video, mute/unmute, etc. ). Full list of capabilities offered in Calling SDK is listed in the [Calling SDK Overview](../../concepts/voice-video-calling/calling-sdk-features.md#detailed-capabilities)
2423

25-
The capabilities are controlled based on roles assigned participants in the call (e.g. Only presenter can screen share). Please refer to this [Rooms Concepts](../../concepts/rooms/room-concept#predefined-participant-roles-and-permissions) for participant roles and permissions.
24+
The capabilities are controlled based on roles assigned participants in the call (e.g. Only presenter can screen share). Please refer to [Rooms concepts](../../concepts/rooms/room-concept#predefined-participant-roles-and-permissions) for participant roles and permissions.
2625

2726
## Call Automation SDKs
2827
Call Automation SDK is a sever side libraries enabling administrator to manage an ongoing room call in a central and controlled environment. Unlike Calling SDK, Call Automation SDK operations are roles agnostic. Therefore, a call administrator may perform several mid-call operations on behalf of the room call participants.
2928

30-
The following lists common mid-call actions available for Room call.
29+
The following lists common mid-call actions available in a room call.
3130

32-
### Connect to Rooms call
31+
### Connect to a room call
3332
Call Automation must connect to an existing room call prior to performing any mid-call operations. CallConnected or ConnectFailed events are notified using callback mechanism to indicate a connect operation is successful or failed respectively.
3433

3534
### [csharp](#tab/csharp)
@@ -65,11 +64,11 @@ call_connection_properties = client.connect_call(call_locator=room_call_locator,
6564
```
6665
-----
6766

68-
Once connect action succeeds, a CallConnect event is notified via Callback URI. The ```callConnectionId``` is available such that it can be used to retrieve a call connection object on the room call that it has just successfully connected. ```callConnectionId``` will be used to retrieve a callConnection object in the following mid-call actions.
67+
Once successfully connected to a room call, a CallConnect event is notified via Callback URI. The ```callConnectionId``` is available such that it can be used to retrieve a call connection on the room call as needed. ```callConnectionId``` will be used in the following sample code snippets.
6968

7069

7170
### Add PSTN Participant
72-
Call Automation can dial out to a PSTN number and add the participant into a room call. A room, however, must be set up to enable PSTN dial-out option (EnabledPSTNDialout is set to true) and Azure Communication Services (ACS) resource must have a valid phone number. Please refer to Rooms [Quickstart](get-started-rooms?tabs=windows&pivots=platform-azcli#enable-pstn-dial-out-capability-for-a-room) for detail.
71+
Call Automation can dial out to a PSTN number and add the participant into a room call. A room, however, must be set up to enable PSTN dial-out option (EnabledPSTNDialout is set to true) and Azure Communication Services (ACS) resource must have a valid phone number. Please refer to [Rooms quickstart](get-started-rooms?tabs=windows&pivots=platform-azcli#enable-pstn-dial-out-capability-for-a-room) for detail.
7372

7473
### [csharp](#tab/csharp)
7574

@@ -165,7 +164,7 @@ result = call_connection_client.remove_participant(remove_this_user, opration_co
165164
```
166165
-----
167166

168-
### Send STMF
167+
### Send DTMF
169168
Send a list of DTMF tones to an external participant.
170169

171170
### [csharp](#tab/csharp)
@@ -217,7 +216,7 @@ result = call_connection_client.send_dtmf_tones(
217216
-----
218217

219218
### Terminate a Call
220-
Call Automation SDKs provides Hang Up action which can be used to terminate a call. CallDisconnected event is published once the hangUp action has completed successfully.
219+
Call Automation SDKs provides Hang Up action which can be used to terminate a call. CallDisconnected event is published once the Hang Up action has completed successfully.
221220

222221
### [csharp](#tab/csharp)
223222

@@ -248,8 +247,8 @@ call_connection_client.hang_up(is_for_everyone=True)
248247
```
249248
-----
250249

251-
## Other Operations
252-
The following mid-call operations are also supported in a room call.
250+
## Other Actions
251+
The following mid-call actions are also supported in a room call.
253252
1. Add Participant (ACS identifier)
254253
1. Remove Participant (ACS identifier)
255254
1. Cancel Add Participant (ACS identifier and PSTN number)
@@ -259,9 +258,9 @@ The following mid-call operations are also supported in a room call.
259258
1. Play both audio files and text
260259
1. Play All both audio files and text
261260
1. Recognize both DTMF and speech
262-
1. RecogniseContinuousDTMF
261+
1. Recognize continuous DTMF
263262

264-
Please see [call actions](../../how-tos/call-automation/actions-for-call-control?branch=pr-en-us-280574&tabs=csharp) and [media actions](../../how-tos/call-automation/control-mid-call-media-actions?branch=pr-en-us-280574&tabs=csharp) for detail on the actions.
263+
Please see [call actions](../../how-tos/call-automation/actions-for-call-control?branch=pr-en-us-280574&tabs=csharp) and [media actions](../../how-tos/call-automation/control-mid-call-media-actions?branch=pr-en-us-280574&tabs=csharp) for detail.
265264

266265
## Next steps
267266

0 commit comments

Comments
 (0)