RTC Engine

Overview

Web
- Demo Quick Run
- SDK Quick Start
- Basic Features
  - Screen Sharing
  - Live Streaming
  - Media Device
  - Audio Volume
  - Set Encoding Profile
  - Detect Network Quality
  - Detect Capabilities
- Advance Features
  - Enable AI Denoiser
  - Enable Audio Mixer
  - Enable Watermark
  - Enable Beauty and Effects
  - SEI Message
  - Custom Capturing and Rendering
- Best Practices
  - Optimize Multi-Person Video Calls
  - Handle Autoplay Restriction
  - Handle Firewall Restriction
- API List
- Released Notes
- Supported Platforms
- Web FAQs
Android
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Setting Video Quality
  - 10.Rotating Videos
- Testing Newwork Quality
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Client APIs
  - Overview
  - TRTCCloud
  - TRTCStatistics
  - TRTCCloudListener
  - TXAudioEffectManager
  - TXBeautyManager
  - TXDeviceManager
  - Type Definition
  - Deprecated Interface
  - Error Codes
- Release Notes
iOS
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Setting Video Quality
  - 10.Rotating Videos
- Testing Network Quality
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Client APIs
  - Overview
  - TRTCCloud
  - TRTCCloudDelegate
  - TRTCStatistics
  - TXAudioEffectManager
  - TXBeautyManager
  - TXDeviceManager
  - Type Definition
  - Deprecated Interface
  - ErrorCode
- Release Notes
macOS
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Sharing Computer Audio
  - 10.Setting Video Quality
  - 11.Rotating Videos
- Testing Hardware Devices
- Testing Network Quality
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Client APIs
  - Overview
  - TRTCCloud
  - TRTCCloudDelegate
  - TRTCStatistics
  - TXAudioEffectManager
  - TXBeautyManager
  - TXDeviceManager
  - Type Definition
  - Deprecated Interface
  - ErrorCode
  - Release Notes
- Release Notes
Windows C++
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Setting Video Quality
  - 10.Rotating Videos
- Testing Hardware Devices
- Testing Network Quality
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Client APIs
  - Overview
  - ITRTCCloud
  - ITRTCStatistics
  - TRTCCloudCallback
  - ITXAudioEffectManager
  - ITXDeviceManager
  - Type Definition
  - Deprecated Interface
  - Error Codes
- Release Notes
Electron
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Sharing Computer Audio
  - 10.Setting Video Quality
  - 11.Rotating Videos
- Client APIs
  - Overview
  - Error Codes
Flutter
- Integration
  - 1.API Examples
  - 2.Importing the SDK
  - 3.Entering a Room
  - 4.Subscribing to Audio/Video Streams
  - 5.Publish Audio/Video Streams
  - 6.Exiting a Room
  - 7.Sensing Network Quality
  - 8.Enabling Screen Sharing
  - 9.Sharing Computer Audio
  - 10.Setting Video Quality
  - 11.Rotating Videos
- Client APIs
  - Overview
  - Error Codes
Unity
- Integration
  - 1.API Examples
  - 2Importing the SDK
- Client APIs
  - Overview
  - Error Codes
Qt
- Integration
  - 1.Importing the SDK
Overview
- Overview
- Features
- Performance Statistics

RTC Engine

Firewall Restrictions

What ports and domain names should I add to the allowlist of my firewall for a native SDK?
Add the following ports to the allowlist:
TRTC SDK (Native)
Ports
TCP
443, 20166, 10443, 10444, 10445, 10446, 10447, 10448, 10449, 10450, 10451, 13275, 23275, 33000, 37528
UDP
8000, 8080, 8001, 8002, 8003, 8004, 8005, 8006, 8007, 8008, 8009, 16285, 9000
Add the following domain names to the allowlist:
intl-query.trtc.tencent-cloud.com
intl-accelerate.trtc.tencent-cloud.com
trtc-client-log-overseas-1258344699.cos.ap-singapore.myqcloud.com
intl-sdklog.trtc.tencent-cloud.com
sdkdc.live.qcloud.com
speedtestint.trtc.tencent-cloud.com
intl-query.trtc.tencent-cloud.com
hwapi.im.qcloud.com
videoapi-sgp.im.qcloud.com
trtc-sdk-config-1258344699.file.myqcloud.com        
Note:
 As the Tencent Cloud service-side IP address/domain is dynamic, and not fixed to a certain batch of IP addresses/domains, we are unable to provide you with a fixed list.
What ports and domain names should I add to the allowlist of my firewall for WebRTC?
Add the following ports to the allowlist:
WebRTC (H5)
Ports
TCP
443
UDP
8000, 8080, 8800, 843, 443, 16285
Add the following domain names to the allowlist:
signailing.rtc.tencentcloud.com
schedule.rtc.tencentcloud.com
*.rtc.tencentcloud.com
*.rtc-web.com
*.rtc-web.io
How do I configure proxies for clients to access the TRTC SDK for web from a private network?
You can use the Nginx + Coturn scheme. For detailed directions, see Handle Firewall Restriction.
Solution
Application Scenario
Network Requirements
Solution 1
Allow clients to access specific proxy servers in the public network
Allow clients to access the proxy servers configured in the public network
Solution 2
Allow clients to access the public network via proxy servers configured in the private network
Allow the proxy servers to access the public network

TRTC SDK (Native)	Ports
TCP	443, 20166, 10443, 10444, 10445, 10446, 10447, 10448, 10449, 10450, 10451, 13275, 23275, 33000, 37528
UDP	8000, 8080, 8001, 8002, 8003, 8004, 8005, 8006, 8007, 8008, 8009, 16285, 9000

Solution	Application Scenario	Network Requirements
Solution 1	Allow clients to access specific proxy servers in the public network	Allow clients to access the proxy servers configured in the public network
Solution 2	Allow clients to access the public network via proxy servers configured in the private network	Allow the proxy servers to access the public network