Skip to content

Commit 1362da1

Browse files
committed
Reconcile article titles with TOC (9)
1 parent 54d7f75 commit 1362da1

File tree

7 files changed

+45
-36
lines changed

7 files changed

+45
-36
lines changed

articles/communication-services/how-tos/calling-sdk/capabilities.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,29 @@
11
---
22
title: Get local capabilities
3-
titleSuffix: An Azure Communication Services how-to guide
3+
titleSuffix: An Azure Communication Services article
44
description: Use Azure Communication Services SDK to get capabilities of the local user in a call.
55
author: elavarasid
66
ms.author: elavarasid
77
ms.service: azure-communication-services
88
ms.subservice: calling
99
ms.topic: how-to
10-
ms.date: 03/24/2023
10+
ms.date: 06/20/2025
1111
ms.custom: template-how-to
1212
zone_pivot_groups: acs-plat-web-ios-android-windows
1313
---
1414

1515
# Get local capabilities
1616

17-
Do I have permission to turn on video, do I have permission to turn on mic, do I have permission to share screen? Those permissions are examples of participant capabilities that you can learn from the capabilities API. Learning the capabilities can help build a user interface that only shows the buttons related to the actions the local user has permissions to.
17+
During a call, does a participant have permission to turn on video, turn on mic, or share screen?
18+
19+
These permissions are examples of participant capabilities that you can learn from the capabilities API operation. You can use capabilities to build a user interface that only shows the buttons related to the actions the local user can perform.
1820

1921
## Prerequisites
2022

2123
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
2224
- A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
2325
- A user access token to enable the calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
24-
- Optional: Complete the quick start to [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md)
26+
- Optional: Complete the quick start to [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md).
2527

2628
::: zone pivot="platform-web"
2729
[!INCLUDE [Capabilities JavaScript](./includes/capabilities/capabilities-web.md)]

articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-android.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: DaybreakQuip
33
ms.service: azure-communication-services
44
ms.topic: include
5-
ms.date: 05/21/2024
5+
ms.date: 06/20/2025
66
ms.author: zehangzheng
77
---
88
[!INCLUDE [Install SDK](../install-sdk/install-sdk-android.md)]
@@ -11,7 +11,7 @@ The ability to view capabilities is an extended feature of the core `Call` API.
1111

1212
The feature enables you to register for an event listener to listen for capability changes.
1313

14-
In order to use the Capabilities call feature for Windows, the first step is to obtain the Capabilities feature API object:
14+
To use the capabilities call feature for Windows, the first step is to obtain the capabilities feature API object:
1515

1616
## Get the capabilities feature
1717

@@ -22,7 +22,7 @@ capabilitiesCallFeature = call.feature(Features.CAPABILITIES);
2222

2323
## Get the capabilities of the local participant
2424

25-
Capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of Capabilities include:
25+
The capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of capabilities include:
2626

2727
- *isAllowed* indicates if a capability can be used.
2828
- *reason* indicates capability resolution reason.

articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-ios.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: DaybreakQuip
33
ms.service: azure-communication-services
44
ms.topic: include
5-
ms.date: 05/21/2024
5+
ms.date: 06/20/2025
66
ms.author: zehangzheng
77
---
88
[!INCLUDE [Install SDK](../install-sdk/install-sdk-ios.md)]
@@ -11,7 +11,7 @@ The ability to view capabilities is an extended feature of the core `Call` API.
1111

1212
The feature enables you to register for an event listener to listen for capability changes.
1313

14-
To use the Capabilities call feature for Windows, the first step is to obtain the Capabilities feature API object:
14+
To use the capabilities call feature for Windows, the first step is to obtain the capabilities feature API object:
1515

1616
## Get the capabilities feature
1717

@@ -21,7 +21,7 @@ let capabilitiesCallFeature =call.feature(Features.capabilities)
2121

2222
## Get the capabilities of the local participant
2323

24-
Capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of Capabilities include:
24+
The capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of capabilities include:
2525

2626
- *isAllowed* indicates if a capability can be used.
2727
- *reason* indicates capability resolution reason.

articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-web.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: elavarasidc
33
ms.service: azure-communication-services
44
ms.topic: include
5-
ms.date: 03/24/2023
5+
ms.date: 06/20/2025
66
ms.author: elavarasid
77
---
88
[!INCLUDE [Install SDK](../install-sdk/install-sdk-web.md)]
@@ -19,7 +19,7 @@ The feature enables you to register for an event listener to listen for capabili
1919
2020
## Get the capabilities of the local participant
2121
22-
Capabilities object has the capabilities of the local participants and is of type `ParticipantCapabilities`. Properties of Capabilities include:
22+
The capabilities object has the capabilities of the local participants and is of type `ParticipantCapabilities`. Properties of capabilities include:
2323
2424
- *isPresent* indicates if a capability is present.
2525
- *reason* indicates capability resolution reason.

articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-windows.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22
author: DaybreakQuip
33
ms.service: azure-communication-services
44
ms.topic: include
5-
ms.date: 05/21/2024
5+
ms.date: 06/20/2025
66
ms.author: zehangzheng
77
---
8+
89
[!INCLUDE [Install SDK](../install-sdk/install-sdk-windows.md)]
910

1011
The ability to view capabilities is an extended feature of the core `Call` API. It enables you to obtain the capabilities of the local participant in the current call.
@@ -22,7 +23,7 @@ capabilitiesCallFeature = call.Features.Capabilities;
2223

2324
## Get the capabilities of the local participant
2425

25-
Capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of Capabilities include:
26+
The capabilities object has the capabilities of the local participants and is of type `ParticipantCapability`. Properties of capabilities include:
2627

2728
- *isAllowed* indicates if a capability can be used.
2829
- *reason* indicates capability resolution reason.

articles/communication-services/how-tos/calling-sdk/includes/transfer-calls/transfer-calls-web.md

Lines changed: 25 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: probableprime
33
ms.service: azure-communication-services
44
ms.topic: include
5-
ms.date: 2/13/2024
5+
ms.date: 6/20/2025
66
ms.author: cnwankwo
77
---
88
[!INCLUDE [Install SDK](../install-sdk/install-sdk-web.md)]
@@ -22,17 +22,17 @@ const callTransferApi = call.feature(Features.Transfer);
2222

2323
Call transfers involve three parties:
2424

25-
- *Transferor*: The person who initiates the transfer request.
26-
- *Transferee*: The person who is being transferred.
27-
- *Transfer target*: The person who is being transferred to.
25+
- *Transferor*: The person initiating the transfer request.
26+
- *Transferee*: The person being transferred.
27+
- *Transfer target*: The person the call is being transferred to.
2828

2929
### Transfer to participant:
3030

3131
1. There's already a connected call between the *transferor* and the *transferee*. The *transferor* decides to transfer the call from the *transferee* to the *transfer target*.
32-
1. The *transferor* calls the `transfer` API.
32+
1. The *transferor* calls the `transfer` operation.
3333
1. The *transfer target* receives an incoming call.
3434

35-
To transfer a current call, you can use the `transfer` API. `transfer` takes the optional `transferCallOptions`, which allows you to set a `disableForwardingAndUnanswered` flag:
35+
To transfer a current call, you can use the `transfer` operation. The `transfer` operation takes the optional `transferCallOptions`, enabling you to set a `disableForwardingAndUnanswered` flag:
3636

3737
- `disableForwardingAndUnanswered = false`: If the *transfer target* doesn't answer the transfer call, the transfer follows the *transfer target* forwarding and unanswered settings.
3838
- `disableForwardingAndUnanswered = true`: If the *transfer target* doesn't answer the transfer call, the transfer attempt ends.
@@ -52,10 +52,10 @@ const transfer = callTransferApi.transfer({targetParticipant: id});
5252
1. There's already a connected call between the *transferor* and the *transferee*.
5353
2. There's already a connected call between the *transferor* and the *transfer target*.
5454
3. The *transferor* decides to transfer the call with the *transferee* to the call with *transfer target*.
55-
4. The *transferor* calls the `transfer` API.
55+
4. The *transferor* calls the `transfer` operation.
5656
6. The *transfer target* receives an incoming call.
5757

58-
To transfer a current call, you can use the `transfer` API.
58+
To transfer a current call, use `transfer`.
5959

6060
```js
6161
// transfer to the target call specifying the call id
@@ -67,7 +67,7 @@ const id = { targetCallId: <CALL_ID> };
6767
const transfer = callTransferApi.transfer({ targetCallId: <CALL_ID> });
6868
```
6969

70-
The `transfer` API allows you to subscribe to `stateChanged`. It also comes with a transfer `state` and `error` properties
70+
The `transfer` Aobject enables you to subscribe to `stateChanged`. It also comes with a transfer `state` and `error` properties
7171

7272
```js
7373
// transfer state
@@ -77,7 +77,7 @@ const transferState = transfer.state; // None | Transferring | Transferred | Fai
7777
const transferError = transfer.error; // transfer error code that describes the failure if a transfer request failed
7878
```
7979

80-
The *transferee* can listen to a `transferAccepted` event. The listener for this event has a `TransferEventArgs` which contains the call object of the new transfer call
80+
The *transferee* can listen to a `transferAccepted` event. The listener for this event has a `TransferEventArgs`, which contains the call object of the new transfer call
8181
between the *transferee* and the *transfer target*.
8282

8383
```js
@@ -99,13 +99,13 @@ transfer.on('stateChanged', () => {
9999

100100
### Transfer to voicemail:
101101

102-
1. There is a connected call between the *transferor* and the *transferee*.
102+
1. There's a connected call between the *transferor* and the *transferee*.
103103
2. The Teams User Identifier of the *target participant voicemail* is known.
104104
3. The *transferor* decides to transfer the call with the *transferee* to the *target participant's voicemail* using the target participant's Teams User Identifier.
105-
4. The *transferor* calls the `transfer` API.
105+
4. The *transferor* calls `transfer`.
106106
5. The *transferee* receives the transfer request.
107107

108-
To transfer a current call, you can use the `transfer` API.
108+
To transfer a current call, you can use `transfer`.
109109

110110
```js
111111
// transfer to the target participant voicemail specified by their Teams User Identifier
@@ -117,7 +117,7 @@ const id: MicrosoftTeamsUserIdentifier = { microsoftTeamsUserId: userId}
117117
const transfer = callTransferApi.transfer({ targetParticipantVoicemail: id });
118118
```
119119

120-
The `transfer` API allows you to subscribe to `stateChanged`. It also comes with a transfer `state` and `error` properties
120+
The `transfer` operation enables you to subscribe to `stateChanged`. It also comes with a transfer `state` and `error` properties
121121

122122
```js
123123
// transfer state
@@ -127,8 +127,8 @@ const transferState = transfer.state; // None | Transferring | Transferred | Fai
127127
const transferError = transfer.error; // transfer error code that describes the failure if a transfer request failed
128128
```
129129

130-
The *transferee* can listen to a `transferAccepted` event. The listener for this event has a `TransferEventArgs` which contains the call object of the new transfer call
131-
between the *transferee* and the *target participant voicemail*.
130+
The *transferee* can listen to a `transferAccepted` event. The listener for this event has a `TransferEventArgs`, which contains the call object of the new transfer call
131+
between the *transferee* and the *target participant voicemail*.
132132

133133
```js
134134
// Transferee can subscribe to the transferAccepted event
@@ -137,7 +137,7 @@ callTransferApi.on('transferAccepted', args => {
137137
});
138138
```
139139

140-
The *transferor* can subscribe to events for change of the state of the transfer. If the call to the *transferee* was successfully connected with *target participant voicemail*, *transferor* can hang up the original call with *transferee*.
140+
The *transferor* can subscribe to events for change of the state of the transfer. If the call to the *transferee* successfully connected with *target participant voicemail*, *transferor* can hang up the original call with *transferee*.
141141

142142
```js
143143
transfer.on('stateChanged', () => {
@@ -148,7 +148,13 @@ transfer.on('stateChanged', () => {
148148
```
149149

150150
### Initial Caller and Transferor information
151-
When forwarding or transferring a call, `transferInfo` is populated with information about the prior call state. This includes `callerInfo` which describes the initial caller and `transferorInfo` which describes the entity transferring or forwarding the call. For example, if an ACS user places a call to a Teams call queue which then distributes the call to a M365 user, the `callerInfo` would specify the ACS user and the `transferorInfo` would specify the Teams call queue. Callers and transferors have the ability to update their displayName, and if this occurs the callerInfoChanged or transferorInfoChanged events will fire. For more information on change events see [Event: callerInfoChanged](../../events.md?pivots=platform-web#event-callerinfochanged) and [Event: transferorInfoChanged](../../events.md?pivots=platform-web#event-transferorinfochanged). This applies to all calls and for any identity (BYOI or M365).
151+
152+
When a participant forwards or transfers a call, `transferInfo` is populated with information about the prior call state. This information includes `callerInfo`, which describes the initial caller and `transferorInfo`, which describes the entity transferring or forwarding the call.
153+
154+
For example, if an Azure Communication Services user places a call to a Teams call queue, which then distributes the call to a Microsoft 365 user, the `callerInfo` would specify the Azure Communication Services user and the `transferorInfo` would specify the Teams call queue. Callers and transferors have the ability to update their `displayName`. If they do, the change triggers the `callerInfoChanged` or `transferorInfoChanged` events.
155+
156+
For more information about change events, see [Event: callerInfoChanged](../../events.md?pivots=platform-web#event-callerinfochanged) and [Event: transferorInfoChanged](../../events.md?pivots=platform-web#event-transferorinfochanged). Change events apply to all calls and for any identity, including bring your own identity (BYOI) or Microsoft 365.
157+
152158
```js
153159
const incomingCallHandler = async (args: { incomingCall: IncomingCall }) => {
154160
const incomingCall = args.incomingCall;
@@ -157,4 +163,4 @@ const incomingCallHandler = async (args: { incomingCall: IncomingCall }) => {
157163
// Get information about initial caller
158164
const transferorInfo = incomingCall.transferorInfo
159165
};
160-
```
166+
```

articles/communication-services/how-tos/calling-sdk/transfer-calls.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,22 +7,22 @@ ms.author: chpalm
77
ms.service: azure-communication-services
88
ms.subservice: calling
99
ms.topic: how-to
10-
ms.date: 08/10/2021
10+
ms.date: 06/20/2025
1111
ms.custom: template-how-to
1212

1313
#Customer intent: As a developer, I want to learn how to transfer calls so that users have the option to transfer calls.
1414
---
1515

1616
# Transfer calls
1717

18-
During an active call, you may want to transfer the call to another person, number, or to voicemail. Let's learn how.
18+
During an active call, you can want to transfer the call to another person, number, or to voicemail. Let's learn how.
1919

2020
## Prerequisites
2121

2222
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
2323
- A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
2424
- A user access token to enable the calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
25-
- Optional: Complete the quickstart to [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md)
25+
- Optional: Complete [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md).
2626

2727
[!INCLUDE [Transfer calls Client-side JavaScript](./includes/transfer-calls/transfer-calls-web.md)]
2828

0 commit comments

Comments
 (0)