Status codes

-1

UNKNOWN

Unknown error.

Troubleshooting:

1. Record the API name, callId, user ID, and the time when the issue occurred.
2. If the issue persists, review the SDK logs for further investigation.

0

SUCCESS

Call succeeded.

No action is required.

80001

PARAMETER_ERROR

Invalid method parameters.

Troubleshooting:

1. Check whether any required parameter is empty.
2. Check whether parameter types and the call order are correct.

80002

ON_CALLING

The current user is already in a call and cannot start or join another call.

Troubleshooting:

1. Call endCall() or endCall(callId) to end the current call first.
2. Check whether getCurrentCallSession() still returns an active session.

80003

NOT_IN_CALL

There is no active call to operate on.

Troubleshooting:

1. Call in-call APIs only when you have a valid callId or an active session.
2. Check the current session state through getCurrentCallSession() first.

80004

MEDIA_TYPE_INVALID

The current call does not allow media type switching.

Troubleshooting:

1. Media type switching is supported only in 1-to-1 calls.
2. Check whether the target media type is already the current type.
3. Make sure INCCallAPIResultListener is set so you can receive the asynchronous result.

80006

RTC_SERVICE_UNAVAILABLE

The audio and video service is unavailable or disabled.

Troubleshooting:

1. Confirm that the audio and video service is enabled for the app in the console.
2. If you just enabled the service, wait for the configuration to take effect and try again.

80007

USER_LIST_INVALID

The user list is empty.

Troubleshooting:

1. Check whether the user list passed to startCall(...) or inviteToCall(...) is empty.
2. In a 1-to-1 call, the list must contain exactly one user.

80008

CALL_ID_INVALID

`callId` is empty or invalid.

Troubleshooting:

1. Use INCCallSession#getCallId() to get the current valid callId.
2. Do not reuse an old callId after the session ends.

80009

TRANSACTION_ID_INVALID

The media type change transaction ID is invalid.

Troubleshooting:

1. Use only the transactionId returned by the callback.
2. Do not cache expired transaction IDs.

80010

USER_ID_INVALID

The user ID is invalid.

Troubleshooting:

1. Check whether the remote user ID is an empty string.
2. Check whether the user IDs in the participant list belong to valid app users.

80011

SINGLE_CALL_NOT_SUPPORT_MULTI_PERSON

More than one user was passed to a 1-to-1 call.

Troubleshooting:

1. In NCCallType.SINGLE, pass only one remote user ID.
2. If you need a group call, use NCCallType.MULTI instead.

80200

SDK_NOT_INITIALIZED

The SDK is not initialized.

Troubleshooting:

1. Confirm that NCCallEngine.install() has been called.
2. Call initialize(...) only after IM is connected.
3. Check the return value of initialize(...) before calling business APIs.

80201

EXECUTION_METHOD_INTERRUPTED

The current method was interrupted by another action during an internal retry.

Troubleshooting:

1. Wait for the current asynchronous call to return before starting another operation.
2. Avoid calling mutually exclusive call control APIs in quick succession.

80202

CALL_ABRUPT_HANGUP

The outgoing call was ended proactively.

Troubleshooting:

1. Check whether endCall(...) was called before startCall(...) finished.
2. Make sure the app is not ending the same call session multiple times from different entry points.

80203

INTERNAL_ERROR

Internal SDK error.

Troubleshooting:

1. Collect logs, the App Key, user ID, callId, and the time when the issue occurred.
2. Contact technical support for further investigation.

80204

CAMERA_SWITCH_ERROR

Failed to switch the camera.

Troubleshooting:

1. Confirm that the device has both front and back cameras.
2. Confirm that the camera has been turned on with enableCamera(true).