cometchat-angular-v5-calls

Ground truth: calling UI ships INSIDE @cometchat/chat-uikit-angular@5 — there is no separate calls-UI package — but the WebRTC engine is a SEPARATE, NOT-bundled peer: @cometchat/calls-sdk-javascript@^5.0.3 (major 5, distinct from the chat SDK's v4). Every CometChat* symbol below exists in the angular-v5 catalog. Exhaustive inputs/outputs and advanced call surfaces are FETCHED, not baked — {DOCS_BASE}/ui-kit/angular/call-features.md, the per-component pages (/components/cometchat-incoming-call, -call-buttons, -call-logs, -outgoing-call), and /guides/call-log-details; base + paths in cometchat-angular-v5-core/references/docs-map.md. APPEND to the user's app — additive wiring only (RULES.md).

Companion skills (read first)

• cometchat-angular-v5-core — install, credentials, init→login→render. Assumed.
• cometchat-angular-v5-placement — where the incoming-call listener mounts.

Use this skill when

Adding voice/video calling, or diagnosing calls that never ring.

Prerequisites & install — calls needs a second package

npm install @cometchat/calls-sdk-javascript@^5

It is an optional peer of the UI Kit (^5.0.3), so it is not installed by default. Without it the call components are inert and CometChatUIKit.isCallingEnabled() returns false.

Calling must also be enabled for the app in the dashboard. Code alone is not enough.

⚠️ Installing the package is NOT what turns calling on

core inits with initFromSettings, and on that path the kit derives calling from the settings object:

// verified in the shipped 5.1.0 bundle
const callingEnabled = !!settings.uiKit?.['callsSDK'];
if (callingEnabled) builder.setCallingEnabled(true);

So you must declare a uiKit.callsSDK block or calling stays off no matter what you installed:

CometChatUIKit.initFromSettings({
  appId, region,
  credentials: { authKey },
  chatSDK: { presenceSubscription: { type: 'ALL_USERS' } },
  uiKit: { callsSDK: {} },          // ← REQUIRED for calling on the initFromSettings path
});