Make sure that the two devices use different
UserIDs. With TRTC, you cannot use the same
UserID on two devices simultaneously unless the
SDKAppIDs are different.
Please set the
TRTCAppScene parameter in
enterRoom to *TRTCAppSceneLIVE.
VideoCall mode is optimized for video calls, so when there is only one user in a room, TRTC tends to maintain a low bitrate and frame rate to reduce traffic usage, which makes the video choppy and blurry.
This may be because advanced permission control is enabled. If you enable advanced permission control for an application (
SDKAppid), users must pass
PrivateMapKey in TRTCParams
to enter the rooms under the application. Therefore, if your online business is running, and you haven’t integrated into it theprivateMapKey` logic, please do not enable the feature. For more information, please see Enabling Advanced Permission Control.
TRTC logs are compressed and encrypted by default with the XLOG extension. You can set
setLogCompressEnabled to specify whether to encrypt logs. If a log filename contains
C (compressed), the log is compressed and encrypted; if it contains
R (raw), the log is in plaintext.
Documents/logof the application sandbox
- You need to download a decryption tool to view an XLOG file. Place the tool in the same directory of the XLOG file in Python 2.7 and run
- You can download the log decryption tool at
If the "Join room failed result: 10006 error: service is suspended, if charge is overdue,renew it" occurs, check whether your TRTC application service is available.
Log in to the TRTC console, click Application Management, find the application you created, and click Application Info to view the service status.
This error is a result of
UserSig verification failure, which may be caused by the following reasons:
SDKAppIDparameter passed in is incorrect. You can log in to the TRTC console and click Application Management to view the
UserSigpassed in, which should match the
UserID,is incorrect. To verify your
UserSig, log in to the TRTC console and click Development Assistance > UserSig Generation & Verification.
You can make a cross-room call using the
connectOtherRoom API. Anchor A calls
connectOtherRoom() to connect to anchor B and gets the result via the
onConnectOtherRoom callback. All users in anchor A’s room will be notified via the
onUserEnter callback that anchor B has entered the room, and all users in anchor B’s room will be notified via the
onUserEnter callback that anchor A has entered the room.
After you call
enterRoom, regardless of whether room entry succeeds, you must call
exitRoom before calling
enterRoom again; otherwise, an unexpected error will occur.
Recording files are generated in whatever format specified in the TRTC console.
You know when you receive the
onSendFirstLocalVideoFrame callback. After
startLocalPreview are called successfully, the SDK will capture video from the camera and encode the video captured. It will return this callback after sending the first video frame to the cloud.
You know when you receive the
onSendFirstLocalAudioFrame callback. After
startLocalAudio are called successfully, the SDK will capture audio from the mic and encode the audio captured. It will return this callback after sending the first audio frame to the cloud.
Currently, statistics of all
UserID values are not available. After user accounts are successfully signed up on the client, you can write all user information into SQL for management and query.
UserIDbe in the same room at the same time?
In TRTC, users with the same
userID cannot be in the same room at the same time as it will cause a conflict.
setAudioRouteAPI take effect?
You can switch between the receiver and speaker only in the call volume mode. That is to say, the API works only if two or more users are co-anchoring.
You can manually enable recording for a call in the following steps:
userid) enters a room, splice the user’s
streamidaccording to the stream ID generation rule.
UserSig? How do I troubleshoot the “-3319” or “-3320” error during room entry?
Log in to the TRTC console and select Development Assistance > UserSig Generation & Verification to verify your
You can find the information on the Usage Statistics page of the TRTC console.
If you have integrated IM into your project, you can use the IM group user counting API to calculate the number of users in a room. However, such calculation is not always accurate. You may use this method if you don’t have a high requirement on accuracy.
If you do have a high requirement on the accuracy of the calculation, we recommend you implement the following calculation logic:
This error indicates that the service is unavailable. Please check the following:
You can call startSystemAudioLoopback to enable system audio capturing.
You need to use another Tencent Cloud product, IM, to enable the feature.
This is how it works: A sends a custom message X (you can determine how the message is displayed) to B, and the calling page is triggered; B receives X and the called page is triggered; B uses enterRoom to enter the room and sends a custom message X1 to A; A receives X1 (you can determine whether to display the message) and uses
enterRoom to enter the room. The messages are sent via IM.
In live streaming scenarios, audience get the
userid of anchors in a room via the onUserVideoAvailable callback in
TRTCCloudDelegate (co-anchoring users enter the room via enterRoom and are also anchors for audience). They then call startRemoteView to play the videos of the anchors.
For more information, please see Live Streaming Mode > Windows.
The TRTC SDK for Linux is not commercially available yet. If you have questions about the SDK or want to use it, please contact us at firstname.lastname@example.org.