TRTCCalling is an RTC solution based on TRTC and TIM. It supports one-to-one and group audio/video calls and allows quick integration.
Does TRTCCalling support string-type roomID?
roomID can be a string, but it must be a numeric string.
Environment
What browsers does the TRTC Web SDK support?
For details about browser support, please see Browsers Supported.
If your browser is not listed in the above document, you can open the TRTC compatibility check page with the browser to test whether it fully supports WebRTC.
I can run the Chat H5 demo successfully locally, but when it is deployed to the server and accessed via an IP address, I can’t make audio/video calls. What should I do?
Background: After running the Chat H5 demo locally, the user can send messages and make audio/video calls using localhost. When the project is deployed to the server and accessed via an IP address, text messages can be sent and received, the server responds to console requests properly, and the console reports no errors, but the user fails to make audio/video calls and cannot obtain video.
Cause: Chat uses the TRTCCalling SDK for audio/video calls, but the user uses HTTP for access.
Solution: Make sure the TRTCCalling SDK is accessed via HTTPS or localhost.
Integration
Why can’t I receive the NO_RESP event in the online demo of TRTCCalling?
Cause: The NO_RESP event is triggered only when two conditions are met at the same time: the call invitation times out and the callee is not online.
Solution: You will receive the event when both conditions are met.
What should I do if I can’t hear the audio of remote users when accessing TRTCCalling using WeChat’s built-in browser on iOS?
Cause: This problem is caused by the browser’s autoplay policy.
Solution: We have addressed this problem in v1.0.0. Please update TRTCCalling to v1.0.0 or a later version.
What should I do if the error “uncaught (in promise) TypeError: cannot read property 'stop' of null” occurs when I call hangup() of TRTCCalling?
Cause: The user calls hangup() multiple times in a callback, which causes the API to be triggered again before it is executed.
Solution: You only need to call hangup() once. The subsequent operations are performed within TRTCCalling. You only need to pay attention to operations related to your business.
On Chrome 90, trtccalling.js prompts “Unsupported TRTCClient. Your browser is not compatible with the application”. What should I do?
Cause: Your Chat version is too old. It does not have a compatibility check mechanism.
Solution: Update Chat to the latest version.
What should I do if the error “TypeError: Cannot read property 'getVideoTracks' of null” occurs when I make a call?
Cause: The error occurs because the callee has not granted the camera/mic access when answering the call.
Solution: Call device-related APIs (such as startRemoteView and startLocalView) asynchronously, or update TRTCCalling to v1.0.0.
What should I do if the error “TSignaling._onMessageReceived unknown bussinessID=undefined” occurs in an application (SDKAppID) that imports TRTCCalling via script?
Details: If the same application (SDKAppID) imports TRTCCalling both via script on two clients, the two clients can communicate with each other. However, if the application imports TRTCCalling via script on one client and npm on the other, or if the other client’s application imports the TRTC SDK for Android/iOS, the two clients cannot communicate with each other.
Cause: bussinessId=undefined indicates that the TSignaling version is too old. The signaling feature in old TSignaling versions is flawed.
Solution: Update TSignaling and make sure that the file name of TSignaling is tsignaling-js during import.
What should I do if the error “Uncaught (in promise) Error: You can call createCustomMessage only when the SDK is ready” occurs?
Cause: The SDK is not initialized as required.
Solution: Update TRTCCalling to v1.0.0 and call the API after receiving the SDK_READY callback.
What should I do if the error “Uncaught (in promise) RTCError: duplicated play() call observed, please stop() firstly <INVALID_OPERATION 0x1001>” occurs?
Cause: This error occurs if you call the startRemoteView API during an audio call.
Solution: Do not call startRemoteView during an audio call.
What should I do if the error “Uncaught (in promise) Error: inviteID is invalid or invitation has been processed” occurs?
Details: Client A, which uses TRTCCalling for web, calls client B, which uses a native application. Client B answers the call, and client A hangs up before the local camera is started and local preview is displayed. Client B remains on the call page, and the error Uncaught (in promise) Error: inviteID is invalid or invitation has been processed is prompted.
Cause: A user can enter a TRTC room without granting access to audio/video devices, but if the user hangs up, a user in a native application will not be notified.
Solution: TRTCCalling 1.0.0 requests camera/mic access beforehand and does not allow users to enter a room before they grant the access. We recommend you update TRTCCalling to v1.0.0 or a later version.
After a call is made, log is printed at the callee side (which indicates that the call invitation is received), but why is the handleNewInvitationReceived callback not received?
Cause: The TRTCCalling version is v0.6.0 or earlier, or the TSignaling version is v0.3.0 or earlier.
Solution: Update TRTCCalling and TSignaling to the latest version.
What should I do if I fail to make another call after a call is rejected?
Cause: The calling status is not reset after the call is rejected.
Solution: Update TRTCCalling to v1.0.3 or a later version.
What should I do if the error “Error: TRTCCalling.call - failed to access the user’s device” occurs?
Cause: TRTCCalling has no access to the camera/mic or the camera/mic does not exist.
Yes
No
Was this page helpful?