- Release Notes and Announcements
- Release Notes
- TRTC Conference Official Editions Launched
- The commercial version of Conference is coming soon
- Terms and Conditions Applicable to $9.9 Starter Package
- Rules for the "First Subscription $100 Discount" Promotion
- Announcement on the Start of Beta Testing for Multi-person Audio and Video Conference
- TRTC Call Official Editions Launched
- License Required for Video Playback in New Version of LiteAV SDK
- TRTC to Offer Monthly Packages
- Product Introduction
- Purchase Guide
- Billing Overview
- RTC-Engine Packages
- TRTC Call Monthly Packages
- TRTC Conference Monthly Packages
- Pay-As-You-Go
- Billing Explanation for Subscription Package Duration
- Billing of On-Cloud Recording
- Billing of MixTranscoding and Relay to CDN
- Free Minutes
- FAQs
- Billing of Monitoring Dashboard
- Billing of Recording Delivery
- Overdue and Suspension Policy
- Refund Policies
- User Tutorial
- Free Demo
- Video Calling (Including UI)
- Overview (TUICallKit)
- Activate the Service（TUICallKit）
- Integration (TUICallKit)
- UI Customization (TUICallKit)
- Offline Call Push (TUICallKit)
- On-Cloud Recording (TUICallKit)
- Additional Features（TUICallKit）
- Server APIs (TUICallKit)
- Client APIs (TUICallKit)
- ErrorCode
- Release Notes (TUICallKit)
- FAQs(TUICallKit)
- Multi-Participant Conference (with UI)
- Live Streaming (Including UI)
- Voice Chat Room (with UI)
- Integration (No UI)
- SDK Download
- API Examples
- Integration Guide
- Client APIs
- Advanced Features
- Relay to CDN
- Enabling Advanced Permission Control
- RTMP Streaming with TRTC
- Utilizing Beautification Effects
- Testing Hardware Devices
- Testing Network Quality
- On-Cloud Recording
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Sending and Receiving Messages
- Event Callbacks
- Access Management
- How to push stream to TRTC room with OBS WHIP
- Server APIs
- Console Guide
- Solution
- FAQs
- Legacy Documentation
- Protocols and Policies
- TRTC Policy
- Glossary
- Release Notes and Announcements
- Release Notes
- TRTC Conference Official Editions Launched
- The commercial version of Conference is coming soon
- Terms and Conditions Applicable to $9.9 Starter Package
- Rules for the "First Subscription $100 Discount" Promotion
- Announcement on the Start of Beta Testing for Multi-person Audio and Video Conference
- TRTC Call Official Editions Launched
- License Required for Video Playback in New Version of LiteAV SDK
- TRTC to Offer Monthly Packages
- Product Introduction
- Purchase Guide
- Billing Overview
- RTC-Engine Packages
- TRTC Call Monthly Packages
- TRTC Conference Monthly Packages
- Pay-As-You-Go
- Billing Explanation for Subscription Package Duration
- Billing of On-Cloud Recording
- Billing of MixTranscoding and Relay to CDN
- Free Minutes
- FAQs
- Billing of Monitoring Dashboard
- Billing of Recording Delivery
- Overdue and Suspension Policy
- Refund Policies
- User Tutorial
- Free Demo
- Video Calling (Including UI)
- Overview (TUICallKit)
- Activate the Service（TUICallKit）
- Integration (TUICallKit)
- UI Customization (TUICallKit)
- Offline Call Push (TUICallKit)
- On-Cloud Recording (TUICallKit)
- Additional Features（TUICallKit）
- Server APIs (TUICallKit)
- Client APIs (TUICallKit)
- ErrorCode
- Release Notes (TUICallKit)
- FAQs(TUICallKit)
- Multi-Participant Conference (with UI)
- Live Streaming (Including UI)
- Voice Chat Room (with UI)
- Integration (No UI)
- SDK Download
- API Examples
- Integration Guide
- Client APIs
- Advanced Features
- Relay to CDN
- Enabling Advanced Permission Control
- RTMP Streaming with TRTC
- Utilizing Beautification Effects
- Testing Hardware Devices
- Testing Network Quality
- On-Cloud Recording
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Sending and Receiving Messages
- Event Callbacks
- Access Management
- How to push stream to TRTC room with OBS WHIP
- Server APIs
- Console Guide
- Solution
- FAQs
- Legacy Documentation
- Protocols and Policies
- TRTC Policy
- Glossary
AccountType
AccountType is the account type used to log in to a TRTC application in TRTC v1. It is automatically assigned for user authentication after the TRTC application is created and is no longer required in v2.Room
A room is an audio/video space where users can receive each other's real-time audio/video streams.
In TRTC, room is a virtual concept used to separate a group of users from another group.
A user's audio/video streams can be received only by other users in the same room.
A user can be in only one room at any time point and can enter another room only after exiting the current room.
notice
The user who creates a room will be the room owner, but this user cannot close the room actively.
The server will close the room as soon as all users actively exit the room.
If a user is disconnected exceptionally, the server will remove this user from the room after 30 seconds. If all users are disconnected exceptionally, the server will automatically close the room after 30 seconds.
When a user attempts to enter a room that does not exist, the TRTC backend will create the room first and then add the user to the room.
Role name
After you create a role parameter set for a specified device platform integrated with TRTC v1 in the TRTC Console, you can name this set of parameters, and this name is referred to as a role name. After a user enables the camera or mic and upstreams the audio/video streams in a room, the role to be used during room entry can be specified by the role name, which confirms the parameters for data streaming. This concept is no longer required in v2.
notice
During room entry, if a user uses a role name that has not been configured in the console, the user can still enter the room, but the default role will be used.
After room entry, the user can change the role by calling the role switching API.
Switching to a non-existent role with the API will throw back a failure callback.
After the role configuration is modified, logging in to the client again is required to make the new configuration take effect (the SDK will pull the configuration from the backend when login is successful. If the pull fails, the role will not be found).
Relayed live streaming
Relayed live streaming is a live broadcasting mode that is usually used for data forwarding between audio/video systems with different protocols. In this mode, the TRTC server pushes the audio/video data in a chat room to the LVB service through RTMP push, thereby implementing the features of relayed live streaming, relayed push, On-Cloud MixTranscoding, and On-Cloud Recording.
PrivateMapKey
PrivateMapKey (room ticket) is a credential used for permission verification when a user attempts to enter a room, which is equivalent to the key to a specified room (RoomID). It is usually used to authenticate room entry and implement room entry restrictions and is issued by your business server. For more information on its generation method, please see Room Entry Permission Protection.Group
The group system in TRTC v1 uses the group feature of the Tencent Cloud Instant Messaging (IM) service.
notice
Group and room are two different concepts completely independent of each other.
RoomID
RoomID (room number) is used in TRTC to uniquely identify a room. It is a number in the uint32 range that is maintained and assigned on your own.SDKAPPID
SDKAPPID (application ID) is a unique ID used by the Tencent Cloud backend to differentiate between different TRTC applications. It is automatically generated when an application is created in the TRTC Console. The data under different SDKAPPID is not interconnected.Tencent Real-Time Communication
Developed by Tencent Cloud based on Tencent's over a decade of expertise in QQ audio/video chat technologies, Tencent Real-Time Communication (TRTC) provides cross-platform, high-quality, and customizable real-time communication services by leveraging the WebRTC capabilities of Tencent Browsing Service (TBS) and TRTC SDKs. It enables you to build an audio/video communication platform from scratch quickly through Mobile QQ, WeChat Mini Program, WeChat Official Account, QQ Browser, and over 20,000 TBS-enabled apps with no knowledge of audio/video technologies required.
TRTC
UserID
UserID (user ID) is used to uniquely identify a user in a TRTC application.UserID maps a user account in your business system to Tencent Cloud. Usually, you can directly use a username as the UserID.The recommended length of
UserID is below 32 bytes. It can be a combination of letters, digits, and underscores but cannot only contain digits. It is case insensitive.UserSig
UserSig (user signature) is used for user login authentication to make sure that the user's identity is authentic. For more information on its generation method, please see Signature Generation.
Yes
No
Was this page helpful?