CallEvents

Event is triggered after remote peer answered the call or set the call into the Call.startEarlyMedia state. Note that event is not triggered in P2P mode.

Event is triggered when blind transfers are enabled by Call.handleBlindTransfer.

Event is triggered after an incoming/outgoing call is connected. For incoming call, it happens after the Call.answer was called. For outgoing call, it happens when a remote peer answers the call.

Event is triggered when a call is terminated. Most frequent status codes (returned when a call is terminated before being answered):

Note that this event doesn't mean the end of the JavaScript session. The session without calls and/or ACD requests will be automatically terminated after some time (see the session limits for details). It's a good idea to explicitly terminate the session with VoxEngine.terminate after it's no longer needed.

Event is triggered when an outgoing call is terminated before connection. Most frequent status codes:

Event is triggered when the first video packet was received

Event is triggered when INFO message is received

Event is triggered when a text message is received

Event is triggered each time when microphone status changes. There is the method for enabling status analyzing - Call.handleMicStatus.

Event is triggered when call is taken off hold

Event is triggered when call is put on hold

Event is triggered when the audio/voice playback is completed. Note that the Call.stopPlayback method finishes any media, so the PlaybackFinished event will be not triggered. The playback may be started by the Call.say or Call.startPlayback methods.

Event is triggered by the Call.startPlayback and Call.say methods when 1) the audio file download to the Voximpant cache is finished;
2) the audio file is found in the cache (i.e., it was in the cache before).

Event is triggered by the Call.startPlayback and Call.say methods when audio/voice playback is started.

Event is triggered when the Voximplant cloud receives the ReInviteAccepted message. This message means that a call received video from the other participant.

Event is triggered when the Voximplant cloud receives the ReInviteReceived message. This message means that a caller:
1) started to send video;
2) started/stopped screensharing;
3) put a call on hold / took a call off hold.

Event is triggered when the Voximplant cloud receives the ReInviteRejected message. This message means that a call didn't receive video from the other participant.

Event is triggered in case of problems during the recording process

Event is triggered when call recording is started as a result of the Call.record method call.

Event is triggered when call recording is stopped. This happens after the CallEvents.Disconnected event was triggered.

Event is triggered after outgoing call receives progress signal from a remote peer.

Event is triggered when call statistic changed.

Event is triggered when a call progress tone is detected (either dial tone or busy tone). There is the method for enabling tone detection - [Call.detectProgressTone]. Note that:
1) the event is triggered only if the CallEvents.Connected event was triggered;
2) the event is only triggered once in a call session.

Event is triggered when a DTMF signal is received. Note that by default DTMF signals will not trigger this event, this behavior needs to be set explicitly by using the Call.handleTones method.

Event is triggered when a call transfer is complete

Event is triggered when a call transfer is failed.

The event is triggered after the video track created. This could happen only if the Call.record method with {video: true} params was called.

Event is triggered each time when voicemail tone is detected. The detection is possible if the Call.detectVoicemailTone method was called in the scenario. Note that detection is ended after timeout specified in the method (default value is 20 seconds).

Event is triggered when voicemail tone is not detected. The event can be triggered only if the Call.detectVoicemailTone method was called in the scenario. Note that event is triggered strictly after timeout specified in the method (default value is 20 seconds). Possible causes of detection's failure: interferences or dividing of the signal; complex signal (more than one frequency); the signal is out of the supported range (500 - 2000 Hz)