-
Notifications
You must be signed in to change notification settings - Fork 344
Reasons of meeting terminating
Dipanshu Sharma edited this page Sep 8, 2022
·
10 revisions
if ((type === “CALL”) || (type === “SIP_BRIDGE”)) {}
1.1. DESCRIPTION: When both host and partner leaves the call
EVENT REASON THROWN: ‘CALL_INACTIVE’
if (state === LOCUS.STATE.INACTIVE) {}
1.2. DESCRIPTION: Partner leaves/rejects the call
EVENT REASON THROWN: ‘PARTNER_LEFT’
if (partner.state === MEETING_STATE.STATES.LEFT &&
(self.state === MEETING_STATE.STATES.DECLINED ||
self.state === MEETING_STATE.STATES.NOTIFIED ||
self.state === MEETING_STATE.STATES.JOINED)) {}
1.3. DESCRIPTION: host left/declined the call or user just joins and adds no Media
EVENT REASON THROWN: ‘SELF_LEFT’
if (self.state === MEETING_STATE.STATES.LEFT &&
(partner.state === MEETING_STATE.STATES.LEFT ||
partner.state === MEETING_STATE.STATES.DECLINED ||
partner.state === MEETING_STATE.STATES.NOTIFIED ||
partner.state === MEETING_STATE.STATES.IDLE)
) {}
if (type === “MEETING”) {}
2.1. DESCRIPTION: Meeting got ended or everyone left the meeting or user stops sending media due to:-
- poor network connection
- user gets an incoming call on device
- no activity from user for a long time, etc
EVENT REASON THROWN: ‘MEETING_INACTIVE_TERMINATING’
if (state === LOCUS.STATE.INACTIVE || state === LOCUS.STATE.TERMINATING) {}
2.2. DESCRIPTION: User has been dropped from a meeting or meeting got dropped
EVENT REASON THROWN: ‘FULLSTATE_REMOVED’
if (fullState.removed) {}
2.3. DESCRIPTION: Server or host removed you from the meeting
EVENT REASON THROWN: ‘SELF_REMOVED’
if (self.removed) {}
Caution
- Introducing the Webex Web Calling SDK
- Core Concepts
- Quickstart guide
- Authorization
- Basic Features
- Advanced Features
- Introduction
- Quickstart Guide
- Basic Features
- Advanced Features
- Multistream
- Migrating SDK version 1 or 2 to version 3