Skip to content

Commit fc85181

Browse files
authored
Update manage-calls-web.md
1 parent 2a52a6d commit fc85181

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -197,12 +197,15 @@ 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
201+
call.on('remote')
202202
const callEndReason = remoteParticipant.callEndReason;
203203
const callEndReasonCode = callEndReason.code // (number) code associated with the reason
204204
const callEndReasonSubCode = callEndReason.subCode // (number) subCode associated with the reason
205205
```
206+
Note:
207+
- This property is only set when adding a remote participant via the Call.addParticipant() API, and the remote participant declines for example.
208+
- 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.
206209
207210
- `isMuted` status: To find out if a remote participant is muted, check the `isMuted` property. It returns `Boolean`.
208211

0 commit comments

Comments
 (0)