Skip to main content

Overview

Out-of-meeting messages (IM) are a notification path independent of the meeting. They solve problems like “how does a user get notified before entering a meeting”:
  • Someone in a meeting is calling you
  • A scheduled meeting is about to start
  • You’ve been admitted from the waiting room
  • A sub-meeting you’re responsible for is asking for help
In-meeting chat messages don’t go through this path—those are In-meeting messages, which work only during the meeting.

Enable and disable

Key points:
  • You must call login(token:) first; calling it before logging in throws SMeetingError.notLoggedIn
  • logout() disables this path internally, so you don’t need to call it again in your logout flow
  • Once set up, the path stays up regardless of whether you’re in a meeting
The typical place to enable it is right after a successful login:

Events

Every out-of-meeting message event carries a base (ImBaseEventData) and a content:

Someone is calling you

Meeting reminders

Admitted from the waiting room

A sub-meeting asks for help


Connection state

This path has its own connection state events; don’t confuse them with the meeting’s reconnection events: The corresponding connection events for the meeting itself are meetingIsReconnecting(_:) / meetingDidReconnect(_:) / meeting(_:didDisconnect:).