IQualityIssueListener

Triggered if the local video is encoded by a codec different from the one specified in ClientConfig.preferredVideoCodec or CallSettings.preferredVideoCodec

Issue level is QualityIssueLevel.CRITICAL if video is not sent, QualityIssueLevel.MAJOR in case of codec mismatch or QualityIssueLevel.NONE if the issue is not detected.

Possible reasons:

1. The device does not support a selected codec. For example, if H264 is specified and the device does not support this hardware codec, the issue is triggered
2. The video is not sending for some reasons. In this case sendCodec is null
3. Different codecs are specified in the call endpoints

Triggered if a network-based media latency is detected in a call. The network-based media latency is calculated based on rtt (round trip time) and jitter buffer. The latency refers to the time it takes a voice/video packet to reach its destination. A sufficient latency causes call participants to speak over the top of each other.

Issue level may vary during the call.

Possible reasons:

1. Network congestion/delays
2. Lack of bandwidth

Triggered if ICE connection is switched to the "disconnected" state during a call.

Issue level is always QualityIssueLevel.CRITICAL, because there is no media in the call until the issue is resolved.

Event may be triggered intermittently and be resolved just as spontaneously on less reliable networks, or during temporary disconnections.

Possible reasons:

1. Network issues

Triggered if the video resolution sent to an endpoint is lower than a captured video resolution. As a result it affects the remote video quality on the remote participant side, but does not affect the quality of the local video preview on the android application.

The issue level may vary during the call.

Possible reasons:

1. High CPU load during the video call
2. Network issues such as poor internet connection or low bandwidth

DEPRECATED

Triggered if the current bitrate is insufficient for sending video with the current resolution.

Issue level may vary during the call. SDK may report QualityIssueLevel.MAJOR or QualityIssueLevel.MINOR while detecting network capabilities right after the call start.

Target bitrate depends on the sent video frame resolution. If the resolution of video frames sent is changed, target bitrate can also be changed (increased or degraded).

It is not recommended to change the resolution or other video call parameters once the issue is detected; in such case, SDK tries to adapt to the current congestion automatically. Only if the issue level is constantly QualityIssueLevel.MAJOR or QualityIssueLevel.CRITICAL, you can change the video call parameters.

Issue may be triggered and constantly report QualityIssueLevel.MAJOR or QualityIssueLevel.CRITICAL if the application is running in the background.

Possible reasons:

1. Network issues
2. Background state of an application

Triggered if no audio is received on a remote audio stream.

Issue level can be only QualityIssueLevel.CRITICAL if the issue is detected or QualityIssueLevel.NONE if the issue is not detected or resolved.

If no audio receiving is detected on several remote audio streams, the event is triggered for each of the remote audio streams with the issue.

If the issue level is QualityIssueLevel.CRITICAL, the event is not triggered with the level QualityIssueLevel.NONE in cases:

1. A (conference) call ended
2. The endpoint left a conference call - - IEndpointListener.onEndpointRemoved(IEndpoint) is triggered

The issue is not detected for the following cases:

1. The endpoint put the call on hold via ICall.hold(boolean, ICallCompletionHandler)
2. The endpoint stopped sending audio during a call via ICall.sendAudio(boolean)

Possible reasons:

1. Poor internet connection on the client or the endpoint
2. Connection lost on the endpoint

Triggered if no audio is captured by the microphone.

Issue level can be only QualityIssueLevel.CRITICAL if the issue is detected or QualityIssueLevel.NONE if the issue is not detected or resolved.

Depending on the device manufacturer, the issue may be occasionally reported in case of pause in the conversation.

Possible reasons:

1. Application or other library mutes the microphone via the setMicrophoneMute android sdk API
2. Application is running in the background for more than 1 minute and foreground service has not been started. Only Android 9+ applications are sensitive.

Triggered if no video is received on a remote video stream.

Issue level can be only QualityIssueLevel.CRITICAL if the issue is detected or QualityIssueLevel.NONE if the issue is not detected or resolved.

If no video receiving is detected on several remote video streams, the event is triggered for each of the remote video streams with the issue.

If the issue level is QualityIssueLevel.CRITICAL, the event is not triggered with the level QualityIssueLevel.NONE in cases:

1. A (conference) call ended
2. The remote video stream has been removed - IEndpointListener.onRemoteVideoStreamRemoved(IEndpoint, IRemoteVideoStream) is triggered.
3. The endpoint left the conference call - IEndpointListener.onEndpointRemoved(IEndpoint) is triggered

The issue is not detected for the following cases:

1. The endpoint put the call on hold via ICall.hold(boolean, ICallCompletionHandler)
2. The endpoint stopped sending video during the call via ICall.sendVideo(boolean, ICallCompletionHandler)
3. Video receiving has been stopped on the remote video stream via IRemoteVideoStream.stopReceiving(ICallCompletionHandler).

Possible reasons:

1. Poor internet connection on the client or the endpoint
2. Connection lost on the endpoint
3. The endpoint's application has been moved to the background state on an iOS device

Triggered on packet loss detection. Packet loss can lead to missing of entire sentences, pauses in the middle of a conversation or robotic voice during a call.

Issue level may vary during the call.

Possible reasons:

1. Network congestion
2. Bad hardware (parts of the network infrastructure)