This document describes how to quickly run the TRTC-API-Example for Android.
TestTRTC. If you have already created an application, click Select Existing Application.
- 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.
LiteAVSDK_TRTC_Android version number/TRTC-API-Example/Debug/src/main/java/com/tencent/trtc/debug/GenerateTestUserSig.java.
- The method for generating
UserSigdescribed in this document involves configuring
SECRETKEYin client code. In this method,
SECRETKEYmay be easily decompiled and reversed, and if your key is disclosed, attackers can steal your Tencent Cloud traffic. Therefore, this method is suitable only for the local execution and debugging of TRTC-API-Example.
- The correct
UserSigdistribution method 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 the business server for a dynamic
UserSig. For more information, please see How do I calculate UserSig on the server?.
TRTC-API-Example project with Android Studio (3.5 or above) and click Run.
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 mobile phones use different UserIDs. With TRTC, you cannot use the same UserID on two devices simultaneously unless the SDKAppIDs are 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, please see How to Deal with Firewall Restrictions to troubleshoot the issue.