Reported when local user's authentication with the network has failed. This can happen when user-supplied credentials do not match the credentials the server expects to receive from the end user.
Reported when a request by the client to start, accept or unhold a call results in an automatic hold of another currently active call and that hold operation fails.
Reported when the request is rejected by the server due to resource being busy. For example, a point-to-point call may fail if the called party returns a busy indication, or if there are no local line appearances available on the server side to initiate the call.
Call is not found.
Reported when the request cannot be supported at the moment due to the current state of the call. For example, a hold request while the call is being transferred, is not allowed.
Camera didn't initialize until allowedCameraInitDelay milliseconds after the call was established.
Camera is not accessible.
Camera is not found.
Camera permission denied
Current operation is cancelled.
Operation is not allowed currently.
Reported when a VoIP session cannot be established due to incompatibility of codecs between the local and remote parties.
Collaboration only call is not supported.
Media devices are not found.
Call is ended.
Operation has failed. The failure reason was not specified.
Reported when no ice candidates are found after ice gathering time elapsed
Operation has failed because another call operation is in progress.
Operation has failed due to an internal error. For example, if the network connection is lost after the API call is made by the application but before the API call can be processed, this error code is returned.
Invalid events to subscribe.
Reported when an invalid parameter is used for the request. For example, if the application tries to add a participant but provides an empty participant address, this error is reported.
Reported when a line reservation attempt is failed by the server. It should be noted that the line appearance id and the line appearance owner are required to reserve a line appearance when the call is initiated on a bridged line appearance. If, for some reason, the line reservation request fails, this error code is reported. This error code is only applicable to communication system environments where bridging and bridged line appearances are supported.
Reported when local audio and/or video resources cannot be initialized successfully.
Reported when audio and/or video resources connection failed.
Signaling path for the call has failed but media is preserved.
Media service is unavailable.
Reported when local audio and/or video resources cannot be started successfully.
Microphone is not accessible.
Microphone is not found.
Microphone permission denied
Reported when the call server doesn't support multiple simultaneous calls.
Multiple video channels are not supported.
Mute state mismatch.
Network events subscriptions request failed
Network events url to subscriptions is undefined
Reported when the local user call initiation attempt fails because the Avaya Communication Manager has no idle line appearance available for the call.
Reported when add or remove operations of the participant cannot be supported because the local user does not have moderator privileges to perform these actions.
Reported when the called party address is not known to the server. For example, if the user dials an invalid telephone number, this error code is reported.
Reported when an operation is denied because the user does not have the license to perform the operation. For example, a video add request may be denied using this error code when the user account is not licensed to support video calls.
Reported when an operation fails because the server assumes that the user is not registered.
Reported when no acceptable device constraint is found.
Operation was redirected to another destination.
Reported when an attempt to register call services is rejected most likely due to maximum device limits has reached.
Reported when an attempt to answer an incoming call locally at a remote extension (e.g., at a bridged line appearance extension) has failed because the call was already answered remotely.
Reported when the application tries to accept an incoming call, but this attempt fails because the remote audio and/or video information could not be applied to local audio/video resources.
Reported when a network message could not be sent due to a network connection error.
Reported when the request has failed due to an internal server error.
Reported when service is temporarily unavailable.
Reported when service is unavailable.
Reported when the same sessionId is used for two MPaaS calls at the same time.
Reported when an invalid or expired sessionId is used for an MPaaS call.
Speakers are not found.
Statistics information is unavailable.
Operation completed successfully. This return code is not used.
Edge Turn TLS/TCP error.
Reported when local time-out occurs while sending a network message or a response to the message was not received from the server in time.
Reported when the request could not be sent to the network server.
Unhandled video direction.
Reported when the called party address is not known to the server. For example, if the user dials an invalid telephone number, this error code is reported.
Reported when the called party has no device registered on his/her behalf, thus, making call setup not possible at this point in time.
VDI service is unavailable
Reported when browser does not support video deescalation from a remote endpoint/gateway.
Reported when a mid-call video add request was denied by the remote party.
Video only call is not supported.
Video was rejected by far-end and the browser does not support reverting to audio only.
WEBRTC is not supported by the browser.
AxpCallError reasons