Skip to content

Commit 26b7c2f

Browse files
Merge pull request #282387 from adamtuck-msft/main
#2536852: Update Transfer to Voicemail quickstart docs
2 parents 552987f + bf336e6 commit 26b7c2f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -99,22 +99,22 @@ transfer.on('stateChanged', () => {
9999

100100
### Transfer to voicemail:
101101

102-
1. There's already a connected call between the *transferor* and the *transferee*.
102+
1. There is a connected call between the *transferor* and the *transferee*.
103103
2. The Teams User Identifier of the *target participant voicemail* is known.
104-
3. The *transferor* decides to transfer the call with the *transferee* to the voicemail with *voicemail id*.
104+
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.
105105
4. The *transferor* calls the `transfer` API.
106-
6. The *transferee* receives the transfer request.
106+
5. The *transferee* receives the transfer request.
107107

108108
To transfer a current call, you can use the `transfer` API.
109109

110110
```js
111-
// transfer to the target call specifying the call id
112-
const id = { targetParticipantVoicemail: <TEAMS_USER_ID> };
111+
// transfer to the target participant voicemail specified by their Teams User Identifier
112+
const id: MicrosoftTeamsUserIdentifier = { microsoftTeamsUserId: userId}
113113
```
114114

115115
```js
116116
// call transfer API
117-
const transfer = callTransferApi.transfer({ target: id });
117+
const transfer = callTransferApi.transfer({ targetParticipantVoicemail: id });
118118
```
119119

120120
The `transfer` API allows you to subscribe to `stateChanged`. It also comes with a transfer `state` and `error` properties

0 commit comments

Comments
 (0)