cometchat-calls

• The top-level

  cometchat

  dispatcher's Step 3.0 routes here because

  product === "voice-video"

  or

  chat-messaging+voice-video

• The user explicitly asks for calling: "add calls", "add video calling", "add voice calls", "set up call screen", "integrate calls SDK", "add CallKit"
• The user is iterating on an existing chat integration and picks "Add calling" from the iteration menu (Step 7 of

  cometchat

  )

cometchat-{family}-calls

cometchat-react-calls

@cometchat/calls-sdk-javascript

cometchat-native-calls

@cometchat/calls-sdk-react-native

cometchat-angular-calls

@cometchat/calls-sdk-javascript

cometchat-android-v5-calls

com.cometchat:calls-sdk-android:5.x

cometchat-android-v6-calls

chatuikit-{compose,kotlin}-android:6.x

cometchat-ios-calls

CometChatCallsSDK

cometchat-flutter-v5-calls

cometchat_calls_sdk

cometchat-flutter-v6-calls

cometchat_chat_uikit:^6.0.0-beta2

Status: This dispatcher is the v4.1 entry point. Per-family skill stubs are scaffolded and being filled in. Flutter v5/v6 calls skills already exist from v4.0.0 and will be audited and brought into the same shape; the other six are being authored against

~/Downloads/calls-sdk/calls-sdk-{android,ios,javascript,react-native}-5/

as ground truth (Android ships 17 pre-authored sub-skills folded into

cometchat-android-v5-calls/references/

).

"Got it — setting up Ringing (1:1 / group calls with an incoming-call screen). If you wanted meeting-room URLs instead, say so and I'll switch."

• question: "What kind of calling experience are you building?"
• header: "Calling mode"
• multiSelect: false
• options (display in this exact order — Session FIRST, Ringing SECOND):
  1. label: "Session — meeting / conference room", description: "Multiple users join the same session by ID or link. No ringing. Like Google Meet, Zoom, or a Slack huddle. Examples: scheduled meetings, webinars, team huddles, classroom calls."
  2. label: "Ringing — 1:1 or group calls", description: "One user calls another (or a small group). Recipient's device rings; they accept or decline. Like a phone call. Examples: WhatsApp, FaceTime, in-app voice/video calls between contacts."

Strict-order rule: render option 1 above option 2. Do not reorder. Session-first is standardized across CometChat product surfaces.

• "Ringing" →

  mode === "ringing"

• "Session" →

  mode === "session"

ringing

cometchat-{family}-calls/references/ringing-integration.md

cometchat-android-v5-calls/references/ringing-integration.md

session

cometchat-{family}-calls/references/call-session.md

cometchat-android-v5-calls/references/join-session.md

Note on the kit's prebuilt UI ("Standard" mode in earlier docs): the UI Kit's

<CometChatCallButtons />

+

<CometChatIncomingCall />

+

<CometChatOngoingCall />

are a kit-provided implementation of Ringing, not a third mode. If the user picks Ringing AND wants the kit's prebuilt UI (most common), the per-family scaffold uses kit components and treats the ringing reference as the architectural ground-truth. If they want custom UI on top of the chat-SDK signaling, the ringing reference is the implementation guide.

⚠️ Group calls do NOT use the Ringing channel (validated 2026-05-15, applies to all kits). The kit's

<CometChatCallButtons group={g}>

sends a custom meeting message to the group via

CometChat.sendCustomMessage

with

type: "meeting"

, NOT

CometChat.initiateCall

. Other group members receive the meeting card in

<CometChatMessageList />

(kit-based receivers) OR a

MessageListener.onCustomMessageReceived

with

category: CATEGORY_CUSTOM

+

type: "meeting"

(custom-UI receivers). The

CallListener.onIncomingCallReceived

channel only fires for 1:1 user calls. If the user wants group calls, load

references/group-calls.md

IN ADDITION TO ringing-integration.md — group has its own architecture even though customers think of it as "ringing for groups."

question

header

multiSelect

options[].label

options[].description

• question: "How should users start a call in your app?"
• header: "Call trigger"
• multiSelect: false
• options (the option set differs by mode — show only the rows matching

  mode

  from Step 3.0):
  If

  mode === "ringing"

  — show these:
  1. label: "Call button on user/contact profile", description: "Voice + video buttons next to a user's name. Best for marketplaces, social, dating, healthcare."
  2. label: "Always-on '/calls' route", description: "Dedicated calls page with a 'Start a call' picker and call history. Best for telehealth, virtual events, contact centers."
  3. label: "Embedded in chat surface", description: "Call buttons in the chat header — voice + video next to message threads. Best for apps that already have chat. (Additive mode only.)"
  4. label: "Floating widget", description: "Always-visible call bubble — like Zoom's floating window. Best for support / sales tools."
  If

  mode === "session"

  — show these instead:
  1. label: "Meeting link route ('/meet/:sessionId')", description: "Shareable URLs that anyone with the link can join. Best for scheduled meetings, webinars, classrooms."
  2. label: "Channel-bound huddle", description: "Session keyed to a chat channel/group ID — anyone in the channel can join the active huddle. Best for team collab apps."
  3. label: "Lobby / waiting-room route", description: "User lands on a waiting screen, host admits. Best for telehealth, customer support."
  4. label: "Custom — I'll wire it myself", description: "Just give me the SDK glue. I'll decide the surface."

-calls

• question: "Where should call history live?"
• header: "Call logs"
• options:
  1. label: "Dedicated /calls route (or screen)", description: "Recommended — full call history, filterable, jump to caller's profile."
  2. label: "Inside the call trigger surface", description: "Compact list under the call button. Best when call volume is low."
  3. label: "Don't show call history", description: "Skip — calls just happen, no log surface."

android

ios

expo

react-native

flutter

-calls

• Firebase Cloud Messaging — look for

  google-services.json

  in

  app/

  and

  id("com.google.gms.google-services")

  in

  app/build.gradle{.kts}

• Service registration — look for

  <service android:name=".YourFirebaseMessagingService" ...>

  in

  AndroidManifest.xml

• ConnectionService — look for

  android.permission.MANAGE_OWN_CALLS

  and

  BIND_TELECOM_CONNECTION_SERVICE

  in

  AndroidManifest.xml

• Foreground service type — look for

  <service android:foregroundServiceType="phoneCall|microphone|camera">

  (Android 14+ silently crashes without

  phoneCall

  )

• CallKit — look for

  import CallKit

  and a

  CXProvider

  configured somewhere in source
• PushKit — look for

  import PushKit

  and a

  PKPushRegistry

  listener (VoIP push token registration)
• Capabilities — look for

  Background Modes

  with

  voip

  +

  audio

  +

  remote-notification

  in

  Info.plist

  and

  entitlements

• Microphone + camera Info.plist usage strings

• react-native-callkeep

  (CallKit + ConnectionService bridge) in

  package.json

• @react-native-firebase/messaging

  (Android) and a

  PushNotificationIOS

  setup

• react-native-voip-push-notification

  for iOS VoIP push tokens

• flutter_callkit_incoming

  in

  pubspec.yaml

  , OR a platform-channel bridge to native CallKit/ConnectionService

• firebase_messaging

  for FCM
• Native

  Info.plist

  and

  AndroidManifest.xml

  entries (Flutter doesn't auto-add these)

-calls

• Which packages will be installed
• Which files will be created vs modified vs left alone
• Where the call trigger will land (with the file path)
• Where call logs will land (or "skipped" if option 3 above)
• For mobile: what VoIP push artifacts will be added (FCM service, CallKit provider, foreground service registration, manifest permissions, Info.plist entries)
• What the user must do manually that the skill can't (Android: enable FCM in Firebase console; iOS: add VoIP Services certificate to App Store Connect; Flutter: bump

  minSdkVersion

  if below platform floor)

-calls

reactjs

nextjs

react-router

astro

cometchat-react-calls

expo

react-native

cometchat-native-calls

angular

cometchat-angular-calls

android

android_version === "v5"

cometchat-android-v5-calls

android

android_version === "v6"

cometchat-android-v6-calls

flutter

flutter_version === "v5"

cometchat-flutter-v5-calls

flutter

flutter_version === "v6"

cometchat-flutter-v6-calls

ios

cometchat-ios-calls

mode

ringing

session

mode

ringing

references/ringing-integration.md

session

references/call-session.md

references/join-session.md

groupCalls === true

group

references/group-calls.md

"meeting"

CometChat.initiateCall

ringing-integration.md

group-calls.md

@cometchat/skills

npx @cometchat/skills add --family <family>

"I just installed the {family} calls skill into your workspace. Please re-run

/cometchat-calls

to continue — your config is saved in

.cometchat/config.json

, so the next run picks up at code generation without re-asking the placement questions."

npx @cometchat/skills-cli verify --calls --json

--calls

• Add a feature (recording, screen sharing, PiP, in-call chat, custom UI)
• Customize call screen / participant list / control panel
• Set up production auth (server-minted tokens, no Auth Key in calls flow)
• Run diagnostics

1. Dual-SDK contract. Chat SDK does

   initiateCall

   (sends a

   MessageType.CALL

   ); Calls SDK does

   joinSession

   . They are NOT interchangeable. The Android skill leads with this — agents trained on multi-platform CometChat data will conflate

   com.cometchat.chat.core.Call

   with

   com.cometchat.chat.models.Call

   and write code that compiles but silently breaks.
2. VoIP push wired in standalone mode, not documented. CallKit + PushKit (iOS), ConnectionService + FCM high-priority (Android),

   react-native-callkeep

   (RN),

   flutter_callkit_incoming

   (Flutter). Documentation isn't enough — without working push, missed calls don't ring.
3. Foreground / background lifecycle correct. Android 14+ silently crashes on wrong

   foregroundServiceType

   for ongoing calls; iOS requires CallKit reporting for background audio. Belongs in the

   -calls

   skill body, not a "see also" reference.
4. Server-minted auth tokens for the calls path. Production calls flows must use auth tokens, never Auth Key. The skill detects existing token endpoints (same way the chat dispatcher does) and uses

   loginWithAuthToken()

   .
5. Cleanup on hangup. Camera-light-stays-on / mic-stays-hot is the canonical "looks fine in dev, fails review" bug. Every per-family skill includes the explicit teardown checklist.
6. Permissions with rationale. Microphone, camera, screen-record (where supported), notifications. All four, all with usage strings.

7. IncomingCall

   mounted at app root in standalone mode. Not at the chat surface — calls is the whole product, the listener has to be alive everywhere.

1. Don't try to add

   apply-feature calls

   from this dispatcher. That CLI command is the v4 chat-flow path — it returns the npm install command and that's it. This dispatcher does the actual integration end-to-end. If the user is in

   chat-messaging+voice-video

   mode, the chat flow already ran; just enter additive mode here. Never call

   apply-feature calls

   from inside this skill.
2. Don't load

   cometchat-components

   or

   cometchat-placement

   (the chat catalogs). Those are chat-shaped. The per-family

   -calls

   skill has its own component list (CallButtons, IncomingCall, OutgoingCall, OngoingCall, CallLogs) and its own placement vocabulary (call trigger, log surface, root listener). Loading the chat catalogs leaks chat assumptions into calls code.
3. Don't ask the chat archetype question ("Messaging app / Marketplace / SaaS / …"). That taxonomy is for where chat lives. Calls placement is where the call trigger lives + where logs live + whether VoIP push is mandatory. Different vocabulary, different recommendations.
4. Don't skip VoIP push in standalone mode even if the user says "I'll add it later." Calls without ringing isn't a product. The dispatcher refuses standalone-mode scaffold without VoIP push wired (or at minimum scaffolded with a clear TODO and red-banner warning in the call screen).
5. Don't mix V5 and V6 cohorts (Android, Flutter). The Calls SDK coordinates differ — V5 Android ships

   calls-sdk-android

   as a separate Cloudsmith dep; V6 folds calls into the unified

   chatuikit-{compose,kotlin}-android

   package. Same for Flutter. Read

   android_version

   /

   flutter_version

   from

   .cometchat/config.json

   and route to the matching cohort skill.

-calls

• Android V5:

  ~/Downloads/calls-sdk/calls-sdk-android-5/

  — pre-authored 17-skill pack at

  skills/

  , dispatcher at

  AGENTS.md

  . Folded into

  cometchat-android-v5-calls/references/{recording,screen-sharing,picture-in-picture,background-handling,voip-calling,audio-controls,video-controls,participant-management,custom-ui,in-call-chat,call-logs,session-settings,event-listeners,join-session,ringing-integration,setup}.md

  .
• iOS V5:

  ~/Downloads/calls-sdk/calls-sdk-ios-5/sample-apps/

  — sample-app code as ground truth (no pre-authored skill pack).
• JavaScript (web):

  ~/Downloads/calls-sdk/calls-sdk-javascript-5/sample-apps/

  — sample-app code as ground truth.
• React Native:

  ~/Downloads/calls-sdk/calls-sdk-react-native-5/sample-apps/

  — sample-app code as ground truth.
• Flutter:

  ~/Downloads/calls-sdk/calls-sdk-flutter-5/sample-apps/

  + existing

  cometchat-flutter-v5-calls

  and

  cometchat-flutter-v6-calls

  skills (audited against the SDK).
• Angular: Same JS Calls SDK (

  @cometchat/calls-sdk-javascript

  ) wrapped in Angular Inputs/Outputs. Sample-app code from

  ~/Downloads/calls-sdk/calls-sdk-javascript-5/

  plus existing

  cometchat-angular-features

  calls section.

• Telehealth / virtual visits →

  references/use-case-telehealth.md

  — provider/patient flow, two-party consent recording, waiting room, HIPAA notes
• Marketplace (buyer ↔ seller) →

  references/use-case-marketplace.md

  — opaque UIDs, time-bounded access, anti-fraud heuristics
• Customer support / help desk →

  references/use-case-support.md

  — agent queue, auto-record for QA, post-call CSAT
• Broadcast / webinar / town hall →

  references/use-case-broadcast.md

  — locked SIDEBAR, mute-by-default attendees, raise-hand Q&A, RTMP bridge for 100+
• Team huddle / standup / collab →

  references/use-case-team.md

  — TILE layout, opt-in join, recording auto-posted to channel

CallSettings

-calls

• references/migration-v4-to-v5.md

  — Calls SDK v4 → v5 (drop-in replacement; v5 APIs unlock granular event listeners + simpler init)

• references/add-calls-to-existing-chat.md

  — additive integration on top of an existing chat surface (init order, login order, IncomingCall mounting, server push setup)

cometchat-react-calls

references/

• iOS APNs PushKit (.p8 token auth) —

  cometchat-ios-calls/references/server-apns-pushkit.md

• Android FCM HTTP v1 (data-only, priority HIGH) —

  cometchat-android-v5-calls/references/server-fcm-voip.md

  (V6 sister with Compose IncomingCallActivity)
• Web Push VAPID (best-effort browser ringing) —

  cometchat-react-calls/references/server-web-push-vapid.md

  (Angular sister)

references/server-push-bridge.md

Platform.OS

Platform.is{iOS,Android}

• The actual code. Per-family

  -calls

  skills write the integration. This dispatcher routes.
• AI-Agent or BYO-Agent flows. Different surface entirely; out of scope. The top-level

  cometchat

  dispatcher's Step 3.0 routes those to docs.
• Moderation features for calls (recording-with-consent prompts, profanity filter on in-call chat, etc.). Same status as the chat dispatcher — moderation is dashboard-only.
• Call analytics dashboards — the CometChat dashboard surfaces these, no integration work needed.

/cometchat-calls

.cometchat/config.json

"Looks like you don't have CometChat integrated yet. For a calling-first app, that's fine — I'll run the standalone calls flow now. If you want chat alongside, run

/cometchat

first to set up chat, then come back to add calls."

cometchat/SKILL.md