Communications·production

IAM.Comm Meet

Enterprise video conferencing on the IAM.Comm media platform.

Key capabilities

  • WebRTC rooms and participant lifecycle
  • SFU/MFU media orchestration
  • Recording, observability and perimeter deployment

Step-by-step guides

Use cases

Start with the outcome: open a guide, prepare prerequisites, follow the steps and verify the success signals.

01 Join a meeting and manage audio, participants and AI notesParticipants control media, moderators see the roster and AI captures decisions.
Audience
Participant or moderator
Outcome
Participants control media, moderators see the roster and AI captures decisions.

Before you start

  • Room link
  • Browser camera/microphone permission
  • Display name

Steps

  1. Complete prejoinSelect devices, verify preview and mute before joining when appropriate.
  2. Control mediaThe bottom bar shows the actual microphone/camera/screen-share state.
  3. Open PeopleReview roles, guests and the waiting room; admit only expected participants.
  4. Review AI notesIn AI, review decisions and action items before copying notes.

Step screenshots

Video guide

The frames follow the sequence above; every screenshot caption names the state to verify.

Media provenance: Captured on 6 August 2026 in the official production demo room using synthetic participants and data.

Verify the result

Controls match media indicators; roster and AI panel work without reload.

If it does not work

If audio is missing, check the selected device and browser permission before network quality.

02 Run a moderated recorded meetingParticipants pass through the waiting room and recording starts with consent and ends cleanly.
Audience
Organizer
Outcome
Participants pass through the waiting room and recording starts with consent and ends cleanly.

Before you start

  • Organizer role
  • Recording policy
  • Participants notified about recording

Steps

  1. Create the roomSet title, time, access policy and waiting room.
  2. Admit participantsVerify display name/domain and reject unexpected guests.
  3. Request recordingWait for consent state; if declined, follow policy instead of bypassing it.
  4. End the meetingStop recording, end the room and verify artifact readiness.
Verify the result

Recording, transcript and attendance share one conference id.

If it does not work

If recording does not start, check consent and policy status before media diagnostics.

Application sections

Open detailed manual

Every application screen has a separate page with controls, safe example values, CLI/API alternatives and status-specific recovery steps.

Open detailed manual →

Role in the ecosystem

IAM.Comm Meet provides video conference rooms on top of a shared media platform IAM.Comm. The product is aimed at corporate and perimeter deployments where traffic control, predictable topology, and auditing are important.

Conference script

The organizer creates a room and access policy, participants go through the join flow and establish a WebRTC connection. Signalling manages membership and SFU/MFU routes media. Recording, screen sharing and AI functions are enabled as separate capabilities.

Network and quality

ICE/STUN/TURN are selected for the deployment loop. Important for every room join latency, packet loss, jitter, renegotiation, active speaker and status media nodes. Adaptive quality should not hide a complete break or error devices from the user.

Access control

Room tokens have a limited TTL and role. Host controls, waiting room and moderation are performed server-side. Records are isolated by tenant and deleted by retention policy; a public link does not automatically provide access to the archive.

Limit of responsibility

Meet owns the user-facing conference flow. Low-level signalling, the media gateway and operator integrations are documented in IAM.Comm.