/

WebRTC Subscriber Events

The following events are specific to the RTCSubscriber implementation and accessible on the global red5prosdk object from the RTCSubscriberEventTypes attribute. These events are dispatched during the lifecycle of thre trickle ICE functionality required to start subscribing to a stream:

AccessNameMeaning
PEER_CONNECTION_AVAILABLE'WebRTC.PeerConnection.Available'When the negotation process has produced a valid PeerConnection.
OFFER_START'WebRTC.Offer.Start'When the subscriber requests to start an offer on the PeerConnection.
OFFER_END'WebRTC.Offer.End'When the subscriber has received a SessionDescription from a requested offer over the PeerConnection.
ANSWER_START'WebRTC.Answer.Start'When the subscriber requests to send an answer on the PeerConnection.
ANSWER_END'WebRTC.Answer.End'When the subscriber has received an answer (in form of a MediaStream) over the PeerConnection.
CANDIDATE_START'WebRTC.Candidate.Start'When the subscriber requests to send a candidate on the PeerConnection.
CANDIDATE_END'WebRTC.Candidate.End'When the subscriber has received a candidate over the PeerConnection.
ICE_TRICKLE_COMPLETE'WebRTC.IceTrickle.Complete'When the negotaiton process (a.k.a. trickle) has completed and the subscriber will attempt at consuming a stream.
DATA_CHANNEL_AVAILABLE'WebRTC.DataChannel.Available'the underlying RTCDataChannel is available when signalingSocketOnly configuration is used.
DATA_CHANNEL_OPEN'WebRTC.DataChannel.Open'When the underlying RTCDataChannel is opened when signalingSocketOnly configuration is used.
DATA_CHANNEL_CLOSE'WebRTC.DataChannel.Close'When the underlying RTCDataChannel is closed when signalingSocketOnly configuration is used.
DATA_CHANNEL_ERROR'WebRTC.DataChannel.Error'When an error has occurred within the underlying RTCDataChannel when signalingSocketOnly configuration is used.
DATA_CHANNEL_MESSAGE'WebRTC.DataChannel.Message'When a message has been delivered over the underlying RTCDataChannel when signalingSocketOnly configuration is used.