VIQualityIssueDelegate

Invoked if local video is encoded by a codec different from specified in [VICallSettings preferredVideoCodec].

Issue level is VIQualityIssueLevelCritical if video is not sent, VIQualityIssueLevelMajor in case of codec mismatch or VIQualityIssueLevelNone if the issue is not detected.

Possible reasons:

1. The video is not sent for some reasons. In this case codec will be nil
2. Different codecs are specified in the call endpoints

Invoked if network-based media latency is detected in the call. Network-based media latency is calculated based on rtt (round trip time) and jitter buffer. Latency refers to the time it takes a voice/video packet to reach its destination. 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

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

Issue level is always VIQualityIssueLevelCritical, 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

Invoked if the video resolution sent to the endpoint is lower than a captured video resolution. As a result it affects remote video quality on the remote participant side, but do not affect the quality of 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

Invoked if current bitrate is insufficient for sending video with current resolution.

Issue level may vary during the call. SDK may report VIQualityIssueLevelMajor or VIQualityIssueLevelMinor 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 VIQualityIssueLevelMajor or VIQualityIssueLevelCritical, you can change the video call parameters.

Issue may be triggered and constantly report VIQualityIssueLevelMajor or VIQualityIssueLevelCritical if the application is running in the background.

Possible reasons:

1. Network issues
2. Background state of an application

Invoked if no audio is received on the remote audio stream.

Issue level can be only VIQualityIssueLevelCritical if the issue is detected or VIQualityIssueLevelNone if the issue is not detected or resolved.

If no audio receive is detected on several remote audio streams, the event will be invoked for each of the remote audio streams with the issue.

If the issue level is VIQualityIssueLevelCritical, the event will not be invoked with the level VIQualityIssueLevelNone in cases:

1. The (conference) call ended
2. The endpoint left the conference call - [VIEndpointDelegate endpointDidRemove:] is invoked

The issue is not detected for the following cases:

1. The endpoint put the call on hold via [VICall setHold:completion:]
2. The endpoint stopped sending audio during a call via [VICall sendAudio]

Possible reasons:

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

Invoked if no audio is captured by the microphone.

Issue level can be only VIQualityIssueLevelCritical if the issue is detected or VIQualityIssueLevelNone if the issue is not detected or resolved.

Possible reasons:

1. Access to microphone is denied
2. Category of AVAudioSession is not AVAudioSessionCategoryPlayAndRecord

Invoked if no video is received on the remote video stream.

Issue level can be only VIQualityIssueLevelCritical if the issue is detected or VIQualityIssueLevelNone if the issue is not detected or resolved.

If no video receive is detected on several remote video streams, the event will be invoked for each of the remote video streams with the issue.

If the issue level is VIQualityIssueLevelCritical, the event will not be invoked with the level VIQualityIssueLevelNone in cases:

1. The (conference) call ended
2. The remote video stream was removed - [VIEndpointDelegate endpoint:didRemoveRemoteVideoStream:] is invoked
3. The endpoint left the conference call - [VIEndpointDelegate endpointDidRemove:] is invoked

The issue is not detected for the following cases:

1. The endpoint put the call on hold via [VICall setHold:completion:]
2. The endpoint stopped sending video during a call via [VICall setSendVideo:completion:]
3. Video receiving was stopped on the remote video stream via [VIRemoteVideoStream stopReceivingWithCompletion:]

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 (camera usage is prohibited while in the background on iOS)

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

Issue level may vary during the call.

Possible reasons:

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