Skip to content

Commit d26788a

Browse files
Merge pull request #212909 from chriswhilar/patch-45
Update manage-calls-web.md
2 parents 72560ff + c46fd42 commit d26788a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -197,12 +197,14 @@ The state can be:
197197
- `Disconnected`: Final state. The participant is disconnected from the call. If the remote participant loses their network connectivity, their state changes to `Disconnected` after two minutes.
198198
199199
- `callEndReason`: To learn why a participant left the call, check the `callEndReason` property:
200-
201200
```js
202201
const callEndReason = remoteParticipant.callEndReason;
203202
const callEndReasonCode = callEndReason.code // (number) code associated with the reason
204203
const callEndReasonSubCode = callEndReason.subCode // (number) subCode associated with the reason
205204
```
205+
Note:
206+
- This property is only set when adding a remote participant via the Call.addParticipant() API, and the remote participant declines for example.
207+
- In the scenario where for example, UserB kicks UserC, from UserA's perspective, UserA will not see this flag get set for UserC. In other words UserA will not see UserC's callEndReason property get set at all.
206208
207209
- `isMuted` status: To find out if a remote participant is muted, check the `isMuted` property. It returns `Boolean`.
208210

0 commit comments

Comments
 (0)