Token导航 LogoToken导航TokenDH.com
开发操作浏览器github未标认证来源可访问许可证需确认审计提醒

sinch-in-app-calling应用程序调用中的 sinch

Agent Skill

sinch-in-app-calling 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,444

周安装

59

GitHub Stars

7

下载量

467
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sinch-in-app-calling(应用程序调用中的 sinch)
来源仓库:https://github.com/sinch/skills
仓库路径:skills/sinch-in-app-calling
安装命令:
npx skills add https://github.com/sinch/skills --skill sinch-in-app-calling
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sinch/skills --skill sinch-in-app-calling

简介

sinch-in-app-calling 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 当前无原始 SKILL.md 内容可参考,实际功能以来源仓库为准。

SKILL.md

Sinch In-App Calling

Overview

Real-time voice and video SDK for Android, iOS, and JavaScript (Web). Connects to Sinch's cloud for signaling and routing.

Supported call types

  • App-to-App (VoIP/WebRTC between users)
  • App-to-Phone (call PSTN numbers)
  • App-to-SIP (connect to PBXs, contact centers)
  • App-to-Conference (multi-party calls)
  • Phone-to-App / SIP-to-App (inbound calls)

Agent Instructions

Prerequisites

The user needs a Sinch account with an application key and secret from the Sinch Build Dashboard. See sinch-authentication for credential setup — In-App Calling uses application-scoped auth (Application Key + Application Secret).

Integration workflow

  1. Detect the platform from the user's project (language, build system, framework):

- Android (Kotlin/Java, Gradle) → Read references/android.md - iOS (Swift/ObjC, Xcode) → Read references/ios.md - JavaScript/Web (npm, browser) → Read references/js.md - If unclear, ask the user.

  1. Walk through the integration steps in the platform reference. Go step by step — confirm each step is in place before moving to the next.
  2. Ask about auth approach: Can the Application Secret be embedded (prototyping only) or must JWTs come from a backend (production)?
  3. Ask about call types: Which types does the user need? This determines which sections to cover.
  4. For Phone-to-App / SIP-to-App: The user needs a backend ICE callback handler. See the "Phone-to-App / SIP-to-App backend" section below.

SDK Init References

For detailed SDK initialization code per platform:

Phone-to-App / SIP-to-App backend

Receiving inbound PSTN or SIP calls requires:

  1. A Sinch voice number from the Build Dashboard assigned to the app (or SIP origination configured).
  2. A callback URL in the app's Voice settings.
  3. A backend ICE handler that routes calls via connectMxp:
{
  "action": {
    "name": "connectMxp",
    "destination": {
      "type": "username",
      "endpoint": "target-user-id"
    }
  }
}

Key Concepts

  • SinchClient — The core SDK object. Must be initialized with Application Key and started before any calls can be made or received.
  • User Identity — A string identifier (e.g., user ID) that uniquely identifies a user in the Sinch system. Set during SinchClient initialization.
  • Call Types — App-to-App (VoIP), App-to-Phone (PSTN), App-to-SIP, App-to-Conference, and inbound (Phone-to-App, SIP-to-App).
  • Managed Push — Sinch-managed push notifications for incoming calls when the app is backgrounded. Required on all platforms.
  • JWT Authentication — Production apps must use backend-generated JWTs (not embedded secrets) for SDK authentication.
  • ICE Callback — Incoming Call Event. A backend webhook handler required for Phone-to-App and SIP-to-App calls that routes calls via connectMxp.
  • Environment Host — Regional endpoint for the SDK connection (e.g., ocra.api.sinch.com for global routing).

Common Patterns

  • App-to-App voice call — Initialize SinchClient with user identity, call callUser("recipient-id"). Both users must have active SinchClient instances.
  • App-to-Phone (PSTN) — Call callPhoneNumber("+15551234567") with a CLI (caller ID) set to a Sinch number.
  • Receive incoming calls — Register push notifications, implement call listener/delegate, handle onIncomingCall event.
  • Phone-to-App routing — Assign a Sinch number to the app, set up backend ICE callback that returns connectMxp action targeting the user.
  • Video calling — Use callUserVideo("recipient-id") (or platform equivalent). Requires camera permissions.

Troubleshooting

SymptomLikely causeFix
onClientFailed / clientDidFailJWT issue — token missing, expired, wrong secret, or malformedVerify JWT generation: correct app key + secret, kid matches key ID, token not expired. See auth section in platform reference
onClientFailed / clientDidFailInvalid app key or wrong environment hostVerify key in Dashboard; check environmentHost matches your region
No incoming calls (JS)Managed push not enabledCall sinchClient.setSupportManagedPush() before starting — required even for the caller side
No incoming calls (Android)FCM misconfigurationVerify FCM credentials in Dashboard ("In-app Voice & Video SDKs" → "Google FCM Identification"); check that the device receives FCM tokens
No incoming calls (iOS)APNs push not configured or token staleVerify push certificate/key in Dashboard; ensure registerPushNotificationData is called with a fresh device token
No incoming calls (general)SinchClient not running on the receiver's deviceThe receiver's app must have an active, started SinchClient to receive calls. Verify start() completed successfully
App-to-Phone fails immediatelyMissing CLI (caller ID)Set callerIdentifier / cli with a Sinch number
Audio only in foreground (iOS)CallKit not reporting callsReport outgoing calls to CallKit for background audio

If the above steps don't resolve the issue, instruct the user to contact Sinch Support with their app key, platform, and a description of the problem.

Public endpoints

Set environmentHost when creating the Sinch client:

EndpointRegion
ocra.api.sinch.comGlobal (auto-routed)
ocra-euc1.api.sinch.comEurope
ocra-use1.api.sinch.comNorth America
ocra-sae1.api.sinch.comSouth America
ocra-apse1.api.sinch.comSouth East Asia 1
ocra-apse2.api.sinch.comSouth East Asia 2

Links

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.35%
按下载量换算165

Claude

30%
按下载量换算140

Cursor

20.23%
按下载量换算94

Gemini CLI

9.26%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills