开始使用
复制一个安装步骤和完整的Markdown指南的设置提示。
Set up this Capacitor plugin in the project.
Use the package manager already used by the project.
Install these package(s): `@capgo/capacitor-incoming-call-kit`
Run the required Capacitor sync/update step after installation.
Read this markdown guide for the full setup steps: https://raw.githubusercontent.com/Cap-go/website/refs/heads/main/apps/docs/src/content/docs/docs/plugins/incoming-call-kit/getting-started.mdx
Use that guide for platform-specific steps, native file edits, permissions, config changes, imports, and usage setup.
If that guide references other docs pages, read them too.
-
安装包
终端窗口 bun add @capgo/capacitor-incoming-call-kit -
同步本地项目
终端窗口 bunx cap sync -
选择您的环源 决定是否来自您的后端、一个像Twilio或Stream这样的SDK,还是一个本地推送路径,如FCM或PushKit。
整合的如何协同工作
标题:整合的如何协同工作此插件仅拥有本地来电显示。您的应用程序仍拥有传输、身份验证和实际媒体会话。
生产模式的共同模式是:
- 您的后端或调用 SDK 发出一个环事件。
- 您的应用程序调用
showIncomingCall(). - 插件呈现本机 incoming-call UI。
callAccepted告诉您的应用程序加入实际房间或 VoIP 会话。callDeclined,callEnded或callTimedOut告诉您的应用程序清理远程状态。
最小集成
标题:最小集成import { IncomingCallKit } from '@capgo/capacitor-incoming-call-kit';
await IncomingCallKit.requestPermissions();await IncomingCallKit.requestFullScreenIntentPermission();
await IncomingCallKit.addListener('callAccepted', async ({ call }) => { console.log('Accepted', call.callId, call.extra); // Start or join your real call session here.});
await IncomingCallKit.addListener('callDeclined', ({ call }) => { console.log('Declined', call.callId); // Tell your backend or SDK that the user declined.});
await IncomingCallKit.addListener('callTimedOut', ({ call }) => { console.log('Timed out', call.callId); // Clear ringing state in your backend or SDK.});
await IncomingCallKit.showIncomingCall({ callId: 'call-42', callerName: 'Ada Lovelace', handle: '+39 555 010 020', appName: 'Capgo Phone', hasVideo: true, timeoutMs: 45_000, extra: { roomId: 'room-42', callerUserId: 'user_ada', }, android: { channelId: 'calls', channelName: 'Incoming Calls', showFullScreen: true, }, ios: { handleType: 'phoneNumber', },});重要选项
标题:重要选项callId: 稳定标识符,后续重复使用endCall()timeoutMs: 最佳努力未回答超时extra: 监听器载荷中反射回任意 JSONandroid.channelId和android.channelName: Android 通知频道调节android.showFullScreen: 请求 Android 全屏 incoming-call 活动ios.handleType选择generic,phoneNumber, 或emailAddress用于 CallKit
管理活动呼叫
标题:管理活动呼叫const { calls } = await IncomingCallKit.getActiveCalls();
await IncomingCallKit.endCall({ callId: 'call-42', reason: 'remote-ended',});
await IncomingCallKit.endAllCalls({ reason: 'session-reset',});事件模型
事件模型incomingCallDisplayed: 本地 UI 已成功显示callAccepted: 用户从本地 UI 中接受callDeclined: 用户在加入之前拒绝callEnded: 您的应用或平台结束了跟踪的呼叫callTimedOut: 呼叫一直未被回答直到timeoutMs
每个事件都携带了标准化的 call 和您的原始 extra 对象。
- 阅读 iOS 指南 __CAPGO_KEEP_0__
- 阅读 Android 指南 __CAPGO_KEEP_0__
- Web 不支持