tencent cloud

Tencent Real-Time Communication

お知らせ・リリースノート
製品アップデート情報
Tencent Cloudオーディオビデオ端末SDKの再生アップグレードおよび承認チェック追加に関するお知らせ
TRTCアプリケーションのサブスクリプションパッケージサービスのリリースに関する説明について
製品の説明
製品概要
基礎概念
製品の機能
製品の強み
ユースケース
性能データ
購入ガイド
Billing Overview
無料時間の説明
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
課金に関するよくあるご質問
Refund Instructions
初心者ガイド
Demo体験
Call
コンポーネントの説明(TUICallKit)
Activate the Service
Run Demo
クイック導入
オフライン通知
Conversational Chat
クラウドレコーディング(TUICallKit)
AI Noise Reduction
インターフェースのカスタマイズ
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
公開ログ
よくある質問
ライブ配信
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Demo のクイックスタート
No UI Integration
UI Customization
Live Broadcast Monitoring
Video Live Streaming
Voice Chat Room
Advanced Features
Client APIs
Server APIs
Error Codes
Release Notes
FAQs
RTC Engine
Activate Service
SDKのダウンロード
APIコードサンプル
Usage Guidelines
クライアント側 API
高度な機能
RTC RESTFUL API
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
コンソールガイド
アプリケーション管理
使用統計
監視ダッシュボード
開発支援
Solution
Real-Time Chorus
よくあるご質問
課金関連問題
機能関連
UserSig関連
ファイアウォールの制限の対応関連
インストールパッケージの圧縮に関するご質問
AndriodおよびiOS関連
Web端末関連
Flutter関連
Electron関連
TRTCCalling Web関連
オーディオビデオ品質関連
その他のご質問
旧バージョンのドキュメント
TUIRoom(Web)の統合
TUIRoom (Android)の統合
TUIRoom (iOS)の統合
TUIRoom (Flutter)の統合
TUIRoom (Electron)の統合
TUIRoom APIのクエリー
クラウドレコーディングと再生の実現(旧)
Protocols and Policies
セキュリティコンプライアンス認証
セキュリティホワイトペーパー
情報セキュリティの説明
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC ポリシー
プライバシーポリシー
データ処理とセキュリティ契約
用語集

Multi-Device Login

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-30 15:09:12

Feature Introduction

By default, each user ID (UserID) can only receive incoming calls on one device at a time. For example, if a user first logs in on a PC client and then logs in on a mobile client, only the mobile device will receive subsequent incoming call notifications.

Typically, a user ID (UserID) is restricted to a single device login at any given time. However, in environments like offices or healthcare facilities, users often need to switch between phones and computers to chat or make calls without interruption. To address this need, TUICallKit provides a multi-device login feature. When enabled, users can log in to multiple clients simultaneously using the same UserID—for example, an iPhone, an iPad, and a Windows PC. When an incoming call arrives, all logged-in devices will receive the call invitation and ring at the same time. Once the user answers the call on any device, the incoming call screen will automatically disappear from the other devices, and the call will connect on the device that answered.
Note:
Multi-device login is a premium feature. To use it, you must purchase or claim a group call edition package for TUICallKit's audio and video call capability. Alternatively, you can activate the trial edition for free. For details on editions and activation instructions, see Audio and Video Call Capability Editions.

Getting Started

1. Complete the steps in the Quick Access guide to integrate TUICallKit into your project. You should be able to initiate and answer basic audio and video calls.
2. To enable multi-device login, call the enableMultiDeviceAbility API after successfully logging in to TUICallKit. See the following examples:
Android
iOS
Flutter
Web
uni-app (Mini Program)
native mini program
// Take Kotlin as an example
// true: enable multi-device login false: disable multi-device login (default)
TUICallEngine.createInstance(context).enableMultiDeviceAbility(true, null)
// Take Swift as an example
// true: enable multi-device login false: disable multi-device login (default)
TUICallEngine.createInstance().enableMultiDeviceAbility(enable: true) {
} fail: { code, message in
}
// true: enable multi-device login false: disable multi-device login (default)
final result = await TUICallEngine.instance.enableMultiDeviceAbility(true);
// true: enable multi-device login false: disable multi-device login (default)
TUICallKitServer?.getTUICallEngineInstance()?.enableMultiDeviceAbility(true);
// true: enable multi-device login false: disable multi-device login (default)
TUICallKitServer?.getTUICallEngineInstance()?.enableMultiDeviceAbility(true);
// true: enable multi-device login false: disable multi-device login (default)
TUICallKitServer?.getTUICallEngineInstance()?.enableMultiDeviceAbility(true);
3. After completing these steps, your application will support multi-device login. No additional configuration is required.

Key Logic

To help you better understand the feature and troubleshoot potential issues, here is a brief overview of the signaling interaction logic behind the scenes.


FAQs

Default Behavior Without Calling enableMultiDeviceAbility

Multi-device login is disabled by default in TUICallKit. In this mode, only the most recently logged-in device with the same UserID will receive incoming calls. For example, if a user logs in on a PC client first and then on a mobile client, only the mobile device will receive calls.

Handling Unstable Network Conditions

No. TUICallKit’s signaling backend uses atomic processing to accept only the first "answer" request received. Once a device answers, TUICallKit immediately sends a "cancel" instruction to all other devices, ensuring that only one device connects to the call.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック