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 ポリシー
プライバシーポリシー
データ処理とセキュリティ契約
用語集
ドキュメントTencent Real-Time CommunicationCallServer APIsThird-Party CallbackCall Status CallbackCallback after Member Changed

Callback after Member Changed

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-04-14 15:05:10

Feature Description

The App backend can view call member status changes in real time through this callback.

Must-Knows

To enable the callback, you must configure the callback URL via the REST API and turn on the switch corresponding to this callback protocol. For the configuration method, see Callback Configuration Settings.
The direction of the callback is that the Call backend initiates an HTTP POST request to the App backend.
After receiving a callback request, the App backend needs to verify whether the value of the SDKAppID parameter in the request URL is its own SDKAppID.

Callback Triggering Scenarios

Status changes of members caused by operations such as connect, hang up, etc. performed by App users through the client will trigger this callback.

Callback Triggering Timing

After the call member status changes.

API Description

Sample Request URL

In the following example, the callback URL configured for the App is https://www.example.com.
Example:
https://www.example.com?SdkAppid=$SDKAppID&CallbackCommand=$CallbackCommand&contenttype=json&ClientIP=$ClientIP&OptPlatform=$OptPlatform

Request Parameters

Parameters
Overview
https
The request protocol is HTTPS, and the request method is POST.
www.example.com
Callback URL
SdkAppid
Assigned SDKAppID in the Chat console when creating an application
CallbackCommand
Fixed as Call.CallbackAfterMemberChanged
contenttype
The value is fixed as json
ClientIP
Client IP address, in the format of 127.0.0.1
OptPlatform
Client platform. For the parameter values, see the description of the OptPlatform parameter in the Third-Party Callback Overview: Callback Protocol

Sample Request Packet

{
    "CallbackCommand":"Call.CallbackAfterMemberChanged",
    "CallId":"055662e1-bc8a-469c-a334-1126c8c17d58",
    "UserList":[
        {
            "User_Account":"user1",
            "Status":"Calling"
        },
        {
            "User_Account":"user2",
            "Status":"Calling"
        }
    ],
    "ChangedUserList":[
        {
            "User_Account":"user2",
            "ActionType":"Answer"  // Answer: Answer; Reject: Reject; NotAnswer: Unanswered; Hangup: Hang up; Join: Proactively Join; Offline: Offline (heartbeat expiry); Invite: Invite; Cancel_Invite: Cancel invitation;
        }
    ]
    "EventTime":1740464128807
}

Request Packet Fields

Field
Type
Overview
CallbackCommand
String
Callback command
CallId
String
Call ID
UserList
Array
Call Member List
User_Account
String
Calling User ID
Status
String
Call status:
Calling : on a call
Waiting : waiting for connection
ChangedUserList
Array
Member list
ChangedUserList.User_Account
String
User ID of the member whose status has changed
ActionType
String
Change operation that causes changes
Accept: Answer
Reject: Deny
NotAnswer: Unanswered
Hang Up: Hang up
Join: Join in Call
Offline: Offline
Invited: Invite to join a call by caller
Canncel_Invite: Cancel Invite by caller
EventTime
Integer
Event-triggered timestamp in milliseconds

Sample Response Packet

The response packet is returned after the App backend synchronizes the data.
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 0 // Ignore callback result
}

Response Packet Fields

Field
Type
Required
Overview
ActionStatus
String
Required
Request processing result. OK: processing successful; FAIL: processing failed.
ErrorInfo
String
Required
Error message.
ErrorCode
Integer
Required
Error code. Enter 0 here to ignore the callback result.

References

Webhook Overview
REST API: Retrieve real-time call status
前の記事へ: Callback after Call Ends次の記事へ: Call Status Callback

ヘルプとサポート

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

フィードバック