Skip to main content
0 means success; anything non-zero is an error. Every error code has the structure prefix + 3-digit specific code (001–999). Once you can read the prefix, you can immediately tell whether the error was returned by the server or produced by a client SDK, and which platform it came from—so you know where to start troubleshooting.

​
How to read an error code

There are three cases:

​
Platform types

The 3rd digit of a 6-digit error code indicates the platform: So 103002 reads as: SRTC layer + iOS + error number 002.

​
Using it when troubleshooting

Full error code tables for each platform: Web · Android · Windows (Chinese) · Swift · iOS (Chinese) · C (Chinese)
Read the C SDK at two levels. Its API return values are simple status values such as 0 / -1 / -2 / -3 / -4; they only express the result of the call and carry no reason. The actual reason is written to the log, which contains both the SDK’s own 180xxx codes and 1xxx codes passed through from the server. See C SDK error codes (Chinese).
Don’t branch on error messages—messages change between versions; error codes don’t.

​
Difference from SMeeting

Same rules, only a different product layer number: SRTC uses 1, SMeeting uses 2. If you use SMeeting, you see both kinds of error codes: 2xxxxx come from the meeting layer, and 1xxxxx come from the underlying SRTC (passed through unchanged by the meeting layer to help you locate the problem). See SMeeting error code format.