CallEvents

Triggered when the call statistics are received. The collection interval is specified in Config.rtcStatsCollectionInterval (defaults to 10 seconds).

See: Config.rtcStatsCollectionInterval

Trigerred after the call is connected from the signaling perspective. Depending on network conditions there can be a 2-3 seconds delay between first audio data and this event.

Triggered when a call has been disconnected

Triggered when a new Endpoint is created. Endpoint represents another participant in the call or conference.

Triggered when an Endpoint is removed. E.g. when a participant leaves the conference or player is removed.

Triggered due to a call failure Most frequent status codes:

Triggered when an ICE connection is complete

Triggered when connection has not been established due to a network connection problem between 2 peers

Triggered when the INFO message is received

Triggered when a text message is received.

Triggered when the Call.ring method is called on the scenario side. Usually, this event is triggered when the call is arrived to its destination. After receiving this event, the application should start playing progress tones.

Triggered when the Call.answer or Call.startEarlyMedia method is called on the scenario side. After receiving this event, the application should stop playing progress tones if they have been playing after the ProgressToneStart event.

Triggered every 10 seconds when the call is CONNECTED. Handler function receives RTCStatsReport dictionary as it is returned by a browser RTCPeerConnection.getStats() method as an argument. RTCStatsReport provides statistics about the specified Call and may differ from one vendor to another.

Triggered when screen sharing is stopped

Triggered when a call has been transferred successfully.

Triggered when a call transfer failed

Triggered when a call has been updated. For example, video has been added/removed. Handler function receives the EventHandlers.Updated object as an argument.