Status codes

0

NCCallCodeSuccess

Call succeeded.

No action is required.

41000

NCCallCodeUnknownError

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.

41001

NCCallCodeDatabaseError

Database error.

Troubleshooting:

1. Check whether the local storage environment is healthy.
2. If the issue persists, investigate the underlying database error with logs.

41002

NCCallCodeJsonError

JSON parsing or serialization failed.

Troubleshooting:

1. Check whether business passthrough fields and extension fields are valid JSON.
2. Check whether the server response structure matches the current SDK expectation.

41003

NCCallCodeInvalidJsonFormat

Invalid JSON format.

Troubleshooting: Check whether the incoming or returned JSON fields contain formatting errors.

41004

NCCallCodeMissParameters

Missing parameters.

Troubleshooting: Check whether all required API parameters were passed.

41005

NCCallCodeParamIsRequied

Required parameter is missing.

Troubleshooting: Add the required parameter and try again.

41006

NCCallCodeDataTypeError

Invalid parameter type.

Troubleshooting: Check whether field types, enum values, and object types match the API definition.

41007

NCCallCodeNotImplemented

The current operation is not implemented.

Troubleshooting: Confirm that the SDK version you use supports this capability.

41008

NCCallCodeNotRegisteredUser

The user is not registered.

Troubleshooting: Confirm that the target user is allowed to receive calls and has completed business registration.

41009

NCCallCodeNotSupportVersion

The current version does not support this operation.

Troubleshooting: Confirm that the client and server capability versions match.

41010

NCCallCodeCallNotExist

The call does not exist.

Troubleshooting:

1. Confirm that callId is correct.
2. Do not reuse an old callId after the call ends.

41011

NCCallCodeSingleExceed

Too many participants were provided for a 1-to-1 call.

Troubleshooting: In NCCallSingleType, pass only one remote user.

41012

NCCallCodeMultipleExceed

Too many participants were provided for a group call.

Troubleshooting: Limit the number of participants so it stays within the server-side limit.

41013

NCCallCodeOperationExpired

The current operation has expired.

Troubleshooting: Retry the operation with the latest transaction ID or session state.

41014

NCCallCodeAlreadyCalling

The current user is already in a call.

Troubleshooting: End the current call before starting or joining another one.

41015

NCCallCodeNotCallUser

The current user is not a participant in this call.

Troubleshooting: Confirm that the current signed-in user belongs to this call session.

41016

NCCallCodeDataExpiration

The data has expired.

Troubleshooting: Fetch the latest call state again or send the request again.

41017

NCCallCodeUserInOtherCall

The target user is in another call.

Troubleshooting: Retry later, or show a busy state in your app.

41018

NCCallCodeReadyTimeInvalid

The ready time is invalid.

Troubleshooting: Check whether the passthrough time parameter from the app layer is valid.

41019

NCCallCodeCannotCallSelf

Calling yourself is not allowed.

Troubleshooting: Check the callee list and make sure it does not include the current signed-in user.

41020

NCCallCodeSessionNotExist

The session does not exist.

Troubleshooting: Confirm that the current session is still valid. If needed, re-create or rejoin it.

41021

NCCallCodeHangupNotAllow

Hang up is not allowed in the current state.

Troubleshooting: Check the call state before you call an endCall API.

41022

NCCallCodeAcceptNotAllow

Accept is not allowed in the current state.

Troubleshooting: Confirm that the current session is still in an acceptable state.

41025

NCCallCodeOperationNotAllow

The current operation is not allowed.

Troubleshooting: Check the current call type, session state, and API call timing.

41100

NCCallCodeTransactionIdErr

The transaction ID is invalid.

Troubleshooting: Use only the transactionId returned by the callback. Do not reuse old values.

41101

NCCallCodeUpgradeExist

A media type upgrade request already exists.

Troubleshooting: Wait until the current upgrade request finishes before sending another one.

41150

NCCallCodeUpgradeCancelled

The media upgrade request was canceled.

Troubleshooting: If you still need to change the media type, send a new request.

41151

NCCallCodeAlreadyAudioCall

The current call is already an audio call.

Troubleshooting: Do not switch an audio call to the same media type again.

41152

NCCallCodeAlreadyVideoCall

The current call is already an audio-video call.

Troubleshooting: Do not switch a video call to the same media type again.

41200

NCCallCodecSeqIdNotSupport

The current codec sequence is not supported.

Troubleshooting: Confirm that the client version matches the underlying media capability.

80001

NCCallCodeParamError

Invalid method parameters.

Troubleshooting: Check whether required parameters are empty and whether parameter types are correct.

80002

NCCallCodeOnCalling

The current user is already in a call.

Troubleshooting: End the current call before starting or joining another one.

80003

NCCallCodeNotInCall

There is no active call to operate on.

Troubleshooting: Check the current session state and avoid calling in-call APIs when there is no active session.

80004

NCCallCodeMediaTypeInvalid

Media type switching is not allowed in the current state.

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.

80301

NCCallCodeSignalTimeOut

Signaling timed out.

Troubleshooting: Check whether the network and signaling path are stable.

80302

NCCallCodeIMDisconnect

IM is not connected.

Troubleshooting:

1. Confirm that the Chat SDK has signed in successfully.
2. Call the Call SDK APIs only after IM is connected.