This document describes how to quickly run the demo for the TRTC Windows C++/Qt SDK.
SDK/CPlusPlus/Win64/lib(for 64-bit Windows) to the
releasefolder of the project directory.
debug/releaseis auto-generated after environment configuration in Visual Studio. For 32-bit Windows, copy all the DLL files in
debug/releasefolder of the project directory.
TestTRTC. If you have already created an application, select Existing.
- An application name can contain up to 15 characters. Only digits, letters, Chinese characters, and underscores are allowed.
- Tags are used to identify and organize your Tencent Cloud resources. For example, an enterprise may have multiple business units, each of which has one or more TRTC applications. In this case, the enterprise can tag TRTC applications to mark out the unit information. Tags are optional and can be added or edited according to your actual business needs.
SDKAppIDand secret key are defined.
|Platform||Relative Path to File|
- In this document, the method to obtain
UserSigis to configure the secret key in the client code. In this method, the secret key is vulnerable to decompilation and reverse engineering. Once your secret key is leaked, attackers can steal your Tencent Cloud traffic. Therefore, this method is only suitable for locally running a demo project and debugging.
- The best practice is to integrate the calculation code of
UserSiginto your server and provide an application-oriented API. When
UserSigis needed, your application can send a request to your server for a dynamic
UserSig. For more information, see How do I calculate
QTDemo\QTDemo.profile in the source code directory with Qt Creator. Compile and run the
QTDemo\QTDemo.profile in the source code directory. Compile and run the
TRTC SDK 6.6 (August 2019) and later versions use the new signature algorithm HMAC-SHA256. If your application was created before August 2019, you need to upgrade the signature algorithm to get a new key. Without upgrading, you can continue to use the old algorithm ECDSA-SHA256. After upgrading, you can switch between the new and old algorithms as needed.
Make sure that the two devices use different
UserID. With TRTC, you cannot use the same
UserID on two devices simultaneously unless the
SDKAppID is different.
The SDK uses the UDP protocol for audio/video transmission and therefore cannot be used in office networks that block UDP. If you encounter such a problem, see How to Deal with Firewall Restrictions.