EventHandlers

Handler	Event	Dispatch by
AuthResult	Events.AuthResult	Client.login Client.loginWithOneTimeKey Client.loginWithToken
AuthTokenResult	Events.RefreshTokenResult	Client.tokenRefresh
ConnectionFailed	Events.ConnectionFailed	Client.connect
IncomingCall	Events.IncomingCall	None
MicAccessResult	Events.MicAccessResult	Client.init Client.attachRecordingDevice Client.setVideoSettings
NetStatsReceived	Events.NetStatsReceived	None
SDKReady	Events.SDKReady	Client.init
CallEvent	CallEvents.ICECompleted CallEvents.ICETimeout CallEvents.ProgressToneStart CallEvents.ProgressToneStop CallEvents.TransferComplete CallEvents.TransferFailed	Client.connect Client.call Call.answer Client.transferCall
CallEventWithHeaders	CallEvents.Connected	Client.call Call.answer
Disconnected	CallEvents.Disconnected	Call.reject Call.hangup Call disconnected from another side
Failed	CallEvents.Failed	Client.call
InfoReceived	CallEvents.InfoReceived	Call.sendInfo
MessageReceived	CallEvents.CallEvents	Call.sendMessage
MediaElementCreated	CallEvents.MediaElementCreated	New remote media stream received.
Updated	CallEvents.Updated	Call.sendVideo Call.setActive Call.setVideoSettings Call.shareScreen Call.stopSharingScreen Call.useAudioOutput
StateUpdated	CallEvent.StateUpdated
ActiveUpdated	CallEvent.ActiveUpdated

IncomingCall
AuthResult
CallEvent
CallEventWithHeaders
ConnectionFailed
Disconnected
EndpointHandler
EndpointMediaHandler
Failed
AuthTokenResult
InfoReceived
MediaElementCreated
MessageReceived
MicAccessResult
NetStatsReceived
SDKReady
SIPRegistrationResult
Updated
ICEDisconnectedIssue
Reported in a handler function for CallEvents.QualityIssueICEDisconnected. The issue level is always QualityIssueLevel.Critical as there is no media in the call until the issue is resolved or QualityIssueLevel.None when the issue has been resolved. Event may be triggered intermittently and resolved just as spontaneously on less reliable networks, or during temporary disconnections. Possible reasons:
- Network issues.
ActiveUpdated
CodecMismatchIssue
Reported in a handler function for CallEvents.QualityIssueCodecMismatch. The issue level is QualityIssueLevel.Critical if a stream is not sent or QualityIssueLevel.Major in case of codec mismatch. Possible reasons:
- The device does not support a selected codec. For example, if H264first is specified and the device does not support this hardware codec, the issue will be triggered.
- The stream is not being sent for some reasons. In this case sendCodec will be undefined.
- Different codecs are specified in the call endpoints. Only in Chrome
HighMediaLatencyIssue
Reported in a handler function for CallEvents.QualityIssueHighMediaLatency. Latency is calculated based on rtt (round trip time) and jitter buffer delay. Latency refers to the time it takes a voice/video packet to reach its destination plus the time it waits in a jitter buffer. Sufficient latency causes call participants to speak over the top of each other. The issue level may vary during the call. Possible reasons:
- Network congestion/delays.
- Lack of bandwidth. Only in Chrome
LocalVideoDegradationIssue
Reported in a handler function for CallEvents.QualityIssueLocalVideoDegradation. Reports that a video resolution being sent to an endpoint is lower than a captured video resolution, so it affects the quality of remote video or screen sharing on a remote participant side, but do not affect the quality of a local video preview. The issue level may vary during the call. Possible reasons:
- High CPU load during the video call.
- Network issues such as poor internet connection or low bandwidth. Only in Chrome for video Only in Firefox for sharing
PacketLossIssue
Reported in a handler function for CallEvents.QualityIssuePacketLoss. 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:
- Network congestion.
- Bad hardware (parts of the network infrastructure).
StateUpdated