Eternet Portal Documentation

Meetings and Calls

Meeting workflow

The workspace can create a room name, open the Jitsi meeting experience, copy a room link, select users, initiate calls, schedule invitations, and display incoming-call notices when the realtime connection is available.

Messaging and presence

Meeting messages use portal API routes. Incoming-call signaling uses an authenticated WebSocket connection and may remain unavailable without preventing basic page rendering.

Service boundary

Media conferencing is provided by the Jitsi integration; user lookup, invitations, chat, and realtime signaling are backed by the configured Eternet meeting services. Confirm each external service is reachable before claiming an end-to-end call is active.

Starting, joining, and inviting participants

The Meetings workspace combines room selection, the embedded Jitsi experience, participant discovery, invitations, and meeting-related chat. A user can enter a room name or start with a generated room identifier, then join the meeting interface. The portal can create a shareable link for the active room and select Eternet users from a contact drawer. Calls and scheduled invitations are submitted through the meeting API, which receives the room, invitee email addresses, and optional scheduled time. The UI can also show an incoming-call notice when the authenticated realtime connection receives a supported event.

Room naming is normalized before use to restrict characters and limit length. This reduces malformed room paths but does not establish who may access the room; that depends on the Jitsi deployment and its authorization configuration. A shared link should therefore be distributed according to the organization’s meeting policy. The portal’s WebSocket signaling and the Jitsi media session are separate connections: a user may join a room while notifications are unavailable, or receive an invitation event while the media service cannot establish a call.

Chat, scheduling, and realtime reliability

Meeting chat loads and sends messages through portal API routes and marks messages as read. The current UI normalizes message text from common body/text fields and can display the returned timestamp. Scheduling collects selected users and a date/time and submits an invitation request; a successful request should be confirmed using the returned meeting record or invitation state. The realtime connection retrieves the authenticated session and a client token before opening the WebSocket. If the endpoint or token is unavailable, the workspace remains usable for basic meeting actions but incoming-call notifications may not arrive.

For troubleshooting, test each layer separately: session and identity, user lookup, invitation API, meeting record, Jitsi room join, media/audio permissions, WebSocket signaling, and chat persistence. A copied URL proves only that the browser generated a link. It does not prove an invitation was delivered, a participant joined, or audio/video is flowing. Browser permissions, firewall rules, STUN/TURN, and external service availability can affect media even when the portal API succeeds.

Customer value and responsible use

Meetings can connect operational teams directly from the portal, making it easier to coordinate around a device incident, fleet issue, or analytics review. It brings collaboration closer to the systems being discussed without making the portal itself a conferencing server. Before presenting, confirm the Jitsi environment, invite flow, user directory, chat service, and realtime endpoint are all configured. Use test participants and avoid exposing room links in public channels. Explain which parts are hosted by Jitsi and which are provided by Eternet APIs. The result is a more useful workflow while preserving clear ownership of identity, media, invitations, and chat data.