RTCPeerConnection

L'interface RTCPeerConnection représente une connection WebRTC entre un ordinateur local et un homologue distant.

Il fournit des méthodes pour se connecter à un homologue distant, entretenir et surveiller la connexion et fermer la connexion dès qu'elle n'est plus nécessaire.

BCD tables only load in the browser

RTCPeerConnection() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection() constructor returns a newly-created RTCPeerConnection, which represents a connection between the local device and a remote peer.

Also inherits propriétés from: EventTarget

canTrickleIceCandidates (en-US)
The read-only RTCPeerConnection property canTrickleIceCandidates returns a Boolean which indicates whether or not the remote peer can accept trickled ICE candidates.
connectionState (en-US) This is an experimental API that should not be used in production code.
The read-only connectionState property of the RTCPeerConnection interface indicates the current state of the peer connection by returning one of the string values specified by the enum RTCPeerConnectionState.
currentLocalDescription (en-US) undefined
The read-only property RTCPeerConnection.currentLocalDescription returns an RTCSessionDescription object describing the local end of the connection as it was most recently successfully negotiated since the last time the  RTCPeerConnection finished negotiating and connecting to a remote peer. Also included is a list of any ICE candidates that may already have been generated by the ICE agent since the offer or answer represented by the description was first instantiated.
currentRemoteDescription (en-US) undefined
The read-only property RTCPeerConnection.currentRemoteDescription returns an RTCSessionDescription object describing the remote end of the connection as it was most recently successfully negotiated since the last time the RTCPeerConnection finished negotiating and connecting to a remote peer. Also included is a list of any ICE candidates that may already have been generated by the ICE agent since the offer or answer represented by the description was first instantiated.
getDefaultIceServers() (en-US) This is an experimental API that should not be used in production code.
The getDefaultIceServers() method of the RTCPeerConnection interface returns an array of objects based on the RTCIceServer dictionary, which indicates what, if any, ICE servers the browser will use by default if none are provided to the RTCPeerConnection in its RTCConfiguration. However, browsers are not required to provide any default ICE servers at all.
iceConnectionState (en-US) undefined
The read-only property RTCPeerConnection.iceConnectionState returns an enum of type RTCIceConnectionState which state of the ICE agent associated with the RTCPeerConnection.
iceGatheringState (en-US) This is an experimental API that should not be used in production code. undefined
The read-only property RTCPeerConnection.iceGatheringState returns an enum of type RTCIceGatheringState that describes connection's ICE gathering state. This lets you detect, for example, when collection of ICE candidates has finished.
localDescription (en-US) This is an experimental API that should not be used in production code. undefined
The read-only property RTCPeerConnection.localDescription returns an RTCSessionDescription describing the session for the local end of the connection. If it has not yet been set, this is null.
peerIdentity (en-US) undefined
The read-only RTCPeerConnection property peerIdentity returns a JavaScript Promise that resolves to an RTCIdentityAssertion which contains a DOMString identifying the remote peer.
pendingLocalDescription (en-US) undefined
The read-only property RTCPeerConnection.pendingLocalDescription returns an RTCSessionDescription object describing a pending configuration change for the local end of the connection. This does not describe the connection as it currently stands, but as it may exist in the near future. Use RTCPeerConnection.currentLocalDescription or RTCPeerConnection.localDescription to get the current state of the endpoint. For details on the difference, see /en-US/docs/Web/API/WebRTC_API/Connectivity.
pendingRemoteDescription (en-US) undefined
The read-only property RTCPeerConnection.pendingRemoteDescription returns an RTCSessionDescription object describing a pending configuration change for the remote end of the connection. This does not describe the connection as it currently stands, but as it may exist in the near future. Use RTCPeerConnection.currentRemoteDescription or RTCPeerConnection.remoteDescription to get the current session description for the remote endpoint. For details on the difference, see /en-US/docs/Web/API/WebRTC_API/Connectivity.
remoteDescription (en-US) This is an experimental API that should not be used in production code. undefined
The read-only property RTCPeerConnection.remoteDescription returns a RTCSessionDescription describing the session (which includes configuration and media information) for the remote end of the connection. If this hasn't been set yet, this is null.
sctp (en-US) This is an experimental API that should not be used in production code.
The read-only sctp property on the RTCPeerConnection interface returns an RTCSctpTransport describing the SCTP transport over which SCTP data is being sent and received. If SCTP hasn't been negotiated, this value is null.
signalingState (en-US) undefined
The read-only signalingState property on the RTCPeerConnection interface returns one of the string values specified by the RTCSignalingState enum; these values describe the state of the signaling process on the local end of the connection while connecting or reconnecting to another peer. See /en-US/docs/Web/API/WebRTC_API/Session_lifetime for more details about the signaling process.

Also inherits gestionnaires d'évènements from: EventTarget

onaddstream (en-US) Cette API obsolète ne doit plus être utilisée, mais elle peut continuer à fonctionner.
The RTCPeerConnection.onaddstream event handler is a property containing the code to execute when the addstream event, of type MediaStreamEvent, is received by this RTCPeerConnection. Such an event is sent when a MediaStream is added to this connection by the remote peer. The event is sent immediately after the call RTCPeerConnection.setRemoteDescription and doesn't wait for the result of the SDP negotiation.
onconnectionstatechange (en-US)
The RTCPeerConnection.onconnectionstatechange property specifies an EventHandler which is called to handle the connectionstatechange event when it occurs on an instance of RTCPeerConnection. This happens whenever the aggregate state of the connection changes.
ondatachannel (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.ondatachannel property is an EventHandler which specifies a function which is called when the datachannel event occurs on an RTCPeerConnection. This event, of type RTCDataChannelEvent, is sent when an RTCDataChannel is added to the connection by the remote peer calling RTCPeerConnection.createDataChannel.
onicecandidate (en-US)
The RTCPeerConnection property RTCPeerConnection.onicecandidate property is an EventHandler which specifies a function to be called when the icecandidate event occurs on an RTCPeerConnection instance. This happens whenever the local ICE agent needs to deliver a message to the other peer through the signaling server.
oniceconnectionstatechange (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.oniceconnectionstatechange property is an event handler which specifies a function to be called when the iceconnectionstatechange event is fired on an RTCPeerConnection instance. This happens when the state of the connection's ICE agent, as represented by the RTCPeerConnection.iceConnectionState property, changes.
onicegatheringstatechange (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.onicegatheringstatechange property is an EventHandler which specifies a function to be called when the icegatheringstatechange event is sent to an RTCPeerConnection instance. This happens when the ICE gathering state—that is, whether or not the ICE agent is actively gathering candidates—changes.
onidentityresult (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.onidentityresult event handler is a property containing the code to execute when the identityresult event, of type RTCIdentityEvent, is received by this RTCPeerConnection. Such an event is sent when an identity assertion is generated, via RTCPeerConnection.getIdentityAssertion() or during the creation of an offer or an answer.
onidpassertionerror (en-US) This is an obsolete API and is no longer guaranteed to work.
The RTCPeerConnection.onidpassertionerror event handler is a property containing the code to execute whent the idpassertionerror event, of type RTCIdentityErrorEvent, is received by this RTCPeerConnection. Such an event is sent when the associated identity provider (IdP) encounters an error while generating an identity assertion.
onidpvalidationerror (en-US) This is an obsolete API and is no longer guaranteed to work.
The RTCPeerConnection.onidpvalidationerror event handler is a property containing the code to execute whent the idpvalidationerror event, of type RTCIdentityErrorEvent, is received by this RTCPeerConnection. Such an event is sent when the associated identity provider (IdP) encounters an error while validating an identity assertion.
onnegotiationneeded (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection interface's onnegotiationneeded property is an EventListener which specifies a function which is called to handle the negotiationneeded event when it occurs on an RTCPeerConnection instance. This event is fired when a change has occurred which requires session negotiation. This negotiation should be carried out as the offerer, because some session changes cannot be negotiated as the answerer.
onpeeridentity (en-US) This is an obsolete API and is no longer guaranteed to work.
The RTCPeerConnection.onpeeridentity event handler is a property containing the code to execute whent the peeridentity event, of type Event, is received by this RTCPeerConnection. Such an event is sent when an identity assertion, received from a peer, has been successfully validated.
onremovestream (en-US) This is an experimental API that should not be used in production code.
The removestream event has been removed from the WebRTC specification in favor of the existing removetrack event on the remote MediaStream and the corresponding MediaStream.onremovetrack event handler property of the remote MediaStream. The RTCPeerConnection API is now track-based, so having zero tracks in the remote stream is equivalent to the remote stream being removed and the old removestream event.
onsignalingstatechange (en-US)
The onsignalingstatechange event handler property of the RTCPeerConnection interface specifies a function to be called when the signalingstatechange event occurs on an RTCPeerConnection interface.
ontrack (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection property ontrack is an EventHandler which specifies a function to be called when the track event occurs, indicating that a track has been added to the RTCPeerConnection.

Also inherits méthodes from: EventTarget

addIceCandidate() (en-US)
When a web site or app using RTCPeerConnection receives a new ICE candidate from the remote peer over its signaling channel, it delivers the newly-received candidate to the browser's ICE agent by calling RTCPeerConnection.addIceCandidate().
addStream() (en-US) This is an experimental API that should not be used in production code. Cette API obsolète ne doit plus être utilisée, mais elle peut continuer à fonctionner.
The obsolete RTCPeerConnection method addStream() adds a MediaStream as a local source of audio or video. Instead of using this obsolete method, you should instead use RTCPeerConnection.addTrack once for each track you wish to send to the remote peer.
addTrack() (en-US)
The RTCPeerConnection method addTrack() adds a new media track to the set of tracks which will be transmitted to the other peer.
close() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.close() method closes the current peer connection.
createAnswer() (en-US) This is an experimental API that should not be used in production code.
The createAnswer() method on the RTCPeerConnection interface creates an SDP answer to an offer received from a remote peer during the offer/answer negotiation of a WebRTC connection. The answer contains information about any media already attached to the session, codecs and options supported by the browser, and any ICE candidates already gathered. The answer is delivered to the returned Promise, and should then be sent to the source of the offer to continue the negotiation process.
createDataChannel() (en-US) This is an experimental API that should not be used in production code.
The createDataChannel() method on the RTCPeerConnection interface creates a new channel linked with the remote peer, over which any kind of data may be transmitted.
createOffer() (en-US)
The createOffer() method of the RTCPeerConnection interface initiates the creation of an SDP offer for the purpose of starting a new WebRTC connection to a remote peer.
generateCertificate() static function (en-US)
The static  RTCPeerConnection.generateCertificate() function creates an X.509 certificate and corresponding private key, returning a promise that resolves with the new RTCCertificate once it's generated.
getConfiguration() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.getConfiguration() method returns an RTCConfiguration object which indicates the current configuration of the RTCPeerConnection on which the method is called.
getIdentityAssertion() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.getIdentityAssertion() method initiates the gathering of an identity assertion. This has an effect only if the RTCPeerConnection.signalingState is not "closed".
getReceivers() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.getReceivers() method returns an array of RTCRtpReceiver objects, each of which represents one RTP receiver. Each RTP receiver manages the reception and decoding of data for a MediaStreamTrack on an RTCPeerConnection
getSenders() (en-US)
The RTCPeerConnection method getSenders() returns an array of RTCRtpSender objects, each of which represents the RTP sender responsible for transmitting one track's data.
getStats() (en-US)
The RTCPeerConnection method getStats() returns a promise which resolves with data providing statistics about either the overall connection or about the specified MediaStreamTrack.
getStreamById() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.getStreamById() method returns the MediaStream with the given id that is associated with local or remote end of the connection. If no stream matches, it returns null.
getTransceivers() (en-US)
The RTCPeerConnection interface's getTransceivers() method returns a list of the RTCRtpTransceiver objects being used to send and receive data on the connection.
removeStream() (en-US) This is an experimental API that should not be used in production code. Cette API obsolète ne doit plus être utilisée, mais elle peut continuer à fonctionner.
The RTCPeerConnection.removeStream() method removes a MediaStream as a local source of audio or video. If the negotiation already happened, a new one will be needed for the remote peer to be able to use it. Because this method has been deprecated, you should instead use RTCPeerConnection.removeTrack if your target browser versions have implemented it.
removeTrack() (en-US)
The RTCPeerConnection.removeTrack() method tells the local end of the connection to stop sending media from the specified track, without actually removing the corresponding RTCRtpSender from the list of senders as reported by RTCPeerConnection.getSenders().
restartIce() (en-US)
The WebRTC API's RTCPeerConnection interface offers the restartIce() method to allow a web application to easily request that ICE candidate gathering be redone on both ends of the connection.
setConfiguration() This is an experimental API that should not be used in production code.
The RTCPeerConnection.setConfiguration() method sets the current configuration of the RTCPeerConnection based on the values included in the specified RTCConfiguration object. This lets you change the ICE servers used by the connection and which transport policies to use.
setIdentityProvider() (en-US) This is an experimental API that should not be used in production code.
The RTCPeerConnection.setIdentityProvider() method sets the Identity Provider (IdP) to the triplet given in parameter: its name, the protocol used to communicate with it (optional) and an optional username. The IdP will be used only when an assertion is needed.
setLocalDescription() (en-US)
The RTCPeerConnection method RTCPeerConnection.setLocalDescription changes the local description associated with the connection. This description specifies the properties of the local end of the connection, including the media format.
setRemoteDescription() (en-US)
The RTCPeerConnection method setRemoteDescription() sets the specified session description as the remote peer's current offer or answer. The description specifies the properties of the remote end of the connection, including the media format.

La méthode suivante a été rendue obsolète il y a longtemps et n'a jamais été implémentée dans les principaux navigateurs.

RTCPeerConnection.createDTMFSender() This is an obsolete API and is no longer guaranteed to work.
Crées un nouveau RTCDTMFSender (en-US), associé à un MediaStreamTrack (en-US) spécifique, qui pourra envoyer un signal téléphonique DTMF sur la connection.

Écoutez ces événements en utilisant addEventListener() ou en assignant un récepteur d'événements à la propriété oneventname de cette interface.

connectionstatechange (en-US)
Envoyé à l'objet RTCPeerConnection lorsque le statut de connectivité globale de RTCPeerConnection change.
Aussi disponible au travers de la propriété de gestionnaire d'événements onconnectionstatechange (en-US).
datachannel (en-US)
Envoyé à l'objet RTCPeerConnection lorsque le pair distant ajoute un canal RTCDataChannel (en-US) à la connection.
Aussi disponible au travers de la propriété de gestionnaire d'événements ondatachannel (en-US).
icecandidate (en-US)
Sent to the peer connection to request that the specified candidate be transmitted to the remote peer.
Also available through the onicecandidate (en-US) event handler property.
icecandidateerror (en-US)
An error of type RTCPeerConnectionIceErrorEvent (en-US) which is sent to the connection if an error occurred during ICE candidate gathering. The event's properties describe the error.
Also available through the onicecandidateerror (en-US) event handler property.
iceconnectionstatechange (en-US)
Sent to the RTCPeerConnection when the state of the ICE connection changes, such as when it disconnects.
Also available using the oniceconnectionstatechange (en-US) event handler property.
icegatheringstatechange (en-US)
Sent to the RTCPeerConnection when the ICE layer's gathering state, reflected by iceGatheringState (en-US), changes. This indicates whether ICE negotiation has not yet begun (new), has begun gathering candidates (gathering), or has completed (complete).
Also available using the onicegatheringstatechange (en-US) event handler property.
isolationchange
Sent to the RTCPeerConnection when the isolated property on one of the MediaStreamTrack (en-US) objects associated with the connection changes value. A track is isolated if its content cannot be accessed by the owning document due to lack of authentication or if the track comes from a cross-origin source.
Also available through the onisolationchange event handler property.
negotiationneeded (en-US)
Sent to the RTCPeerConnection when negotiation or renegotiation of the ICE connection needs to be performed; this can happen both when first opening a connection as well as when it's neccessary to adapt to changing network conditions. The receiver should respond by creating an offer and sending it to the other peer.
Also available as the onnegotiationneeded (en-US) event handler property.
signalingstatechange (en-US)
The signalingstatechange event is sent to the RTCPeerConnection when the connection's ICE signaling state changes.
Also available through the onsignalingstatechange (en-US) event handler property.
statsended
The statsended event is sent when a statistics object being monitored is deleted. The RTCStatsEvent includes the final report on the deleted object (or objects, if multiple objects have been deleted since the last report was delivered). A statistics object is deleted, for example, when the connection is closed and deleted.
Available as the onstatsended event handler property.
track (en-US)
The track event is sent after a new track has been added to one of the RTCRtpReceiver (en-US) instances which comprise the connection.
Available as the ontrack (en-US) event handler property.
addstream (en-US) This is an obsolete API and is no longer guaranteed to work.
Sent when a new MediaStream has been added to the connection. Instead of watching for this obsolete event, you should watch each for track (en-US) events; one is sent for each MediaStreamTrack (en-US) added to the connection.
Available as the onaddstream (en-US) event handler property.
identityresult (en-US) This is an obsolete API and is no longer guaranteed to work.
In old versions of the WebRTC specification, this event was used to indicate that an identity assertion is available. Now, you should instead wait for a the promise returned by peerIdentity (en-US) to resolve with an identity.
Also available using the onidentityresult (en-US) event handler property.
idpassertionerror (en-US) This is an obsolete API and is no longer guaranteed to work.
In old versions of the WebRTC specification, this event was used to indicate that an error occurred while attempting to generate an identity assertion. Now, you should instead wait for a the promise returned by peerIdentity (en-US) to be rejected with an error.
Also available as the onidpinsertionerror (en-US) event handler property.
idpvalidationerror (en-US) This is an obsolete API and is no longer guaranteed to work.
In old versions of the WebRTC specification, this event was used to indicate that an error occurred while attempting to validate an identity assertion. Now, you should instead wait for a the promise returned by peerIdentity (en-US) to be rejected with an error.
Also available using the onpeerdentity (en-US) event handler property.
peeridentity (en-US) This is an obsolete API and is no longer guaranteed to work.
In old versions of the WebRTC specification, this event was used to deliver a received identity. Now, you should instead wait for a the promise returned by peerIdentity (en-US) to resolve with an identity.
removestream (en-US) This is an obsolete API and is no longer guaranteed to work.
Sent to the RTCPeerConnection when a MediaStream is removed from the connection. Instead of watching for this obsolete event, you should watch each stream for removetrack (en-US) events on each stream within the RTCPeerConnection.
Also available as the onaddstream (en-US) event handler property.

The RTCBundlePolicy enum defines string constants which are used to request a specific policy for gathering ICE candidates if the remote peer isn't compatible with the SDP BUNDLE standard for bundling multiple media streams on a single transport link.

Note: In technical terms, a BUNDLE lets all media flow between two peers flow across a single 5-tuple; that is, from the same IP and port on one peer to the same IP and port on the other peer, using the same transport protocol.

Constante Description
"balanced" On BUNDLE-aware connections, the ICE agent should gather candidates for all of the media types in use (audio, video, and data). Otherwise, the ICE agent should only negotiate one audio and video track on separate transports.
"max-compat" The ICE agent should gather candidates for each track, using separate transports to negotiate all media tracks for connections which aren't BUNDLE-compatible.
"max-bundle" The ICE agent should gather candidates for just one track. If the connection isn't BUNDLE-compatible, then the ICE agent should negotiate just one media track.

The RTCIceConnectionState enum defines the string constants used to describe the current state of the ICE agent and its connection to the ICE server (that is, the STUN or TURN server).

Constante Description
"new" The ICE agent is gathering addresses or is waiting to be given remote candidates through calls to RTCPeerConnection.addIceCandidate() (en-US) (or both).
"checking" The ICE agent has been given one or more remote candidates and is checking pairs of local and remote candidates against one another to try to find a compatible match, but has not yet found a pair which will allow the peer connection to be made. It's possible that gathering of candidates is also still underway.
"connected" A usable pairing of local and remote candidates has been found for all components of the connection, and the connection has been established. It's possible that gathering is still underway, and it's also possible that the ICE agent is still checking candidates against one another looking for a better connection to use.
"completed" The ICE agent has finished gathering candidates, has checked all pairs against one another, and has found a connection for all components.
"failed" The ICE candidate has checked all candidates pairs against one another and has failed to find compatible matches for all components of the connection. It is, however, possible that the ICE agent did find compatible connections for some components.
"disconnected" Checks to ensure that components are still connected failed for at least one component of the RTCPeerConnection. This is a less stringent test than "failed" and may trigger intermittently and resolve just as spontaneously on less reliable networks, or during temporary disconnections. When the problem resolves, the connection may return to the "connected" state.
"closed" The ICE agent for this RTCPeerConnection has shut down and is no longer handling requests.

The RTCIceGatheringState enum defines string constants which reflect the current status of ICE gathering, as returned using the RTCPeerConnection.iceGatheringState (en-US) property. You can detect when this value changes by watching for an event of type icegatheringstatechange.

Constante Description
"new" The peer connection was just created and hasn't done any networking yet.
"gathering" The ICE agent is in the process of gathering candidates for the connection.
"complete" The ICE agent has finished gathering candidates. If something happens that requires collecting new candidates, such as a new interface being added or the addition of a new ICE server, the state will revert to "gathering" to gather those candidates.

The RTCIceTransportPolicy enum defines string constants which can be used to limit the transport policies of the ICE candidates to be considered during the connection process.

Constante Description
"all" All ICE candidates will be considered.
"public" This is an obsolete API and is no longer guaranteed to work. Only ICE candidates with public IP addresses will be considered. Removed from the specification's May 13, 2016 working draft.
"relay" Only ICE candidates whose IP addresses are being relayed, such as those being passed through a TURN server, will be considered.

The RTCPeerConnectionState enum defines string constants which describe states in which the RTCPeerConnection may be. These values are returned by the connectionState (en-US) property. This state essentially represents the aggregate state of all ICE transports (which are of type RTCIceTransport (en-US) or RTCDtlsTransport (en-US)) being used by the connection.

Constante Description
"new" At least one of the connection's ICE transports (RTCIceTransport (en-US)s or RTCDtlsTransport (en-US)s) are in the "new" state, and none of them are in one of the following states: "connecting", "checking", "failed", or "disconnected", or all of the connection's transports are in the "closed" state.
"connecting" One or more of the ICE transports are currently in the process of establishing a connection; that is, their RTCIceConnectionState is either "checking" or "connected", and no transports are in the "failed" state. <<< Make this a link once I know where that will be documented
"connected" Every ICE transport used by the connection is either in use (state "connected" or "completed") or is closed (state "closed"); in addition, at least one transport is either "connected" or "completed".
"disconnected" At least one of the ICE transports for the connection is in the "disconnected" state and none of the other transports are in the state "failed", "connecting", or "checking".
"failed" One or more of the ICE transports on the connection is in the "failed" state.
"closed"

The RTCPeerConnection is closed.

This value was in the RTCSignalingState enum (and therefore found by reading the value of the signalingState (en-US)) property until the May 13, 2016 draft of the specification.

The RTCRtcpMuxPolicy enum defines string constants which specify what ICE candidates are gathered to support non-multiplexed RTCP. <<<add a link to info about multiplexed RTCP.

Constante Description
"negotiate" Instructs the ICE agent to gather both RTP and RTCP (en-US) candidates. If the remote peer can multiplex RTCP, then RTCP candidates are multiplexed atop the corresponding RTP candidates. Otherwise, both the RTP and RTCP candidates are returned, separately.
"require" Tells the ICE agent to gather ICE candidates for only RTP, and to multiplex RTCP atop them. If the remote peer doesn't support RTCP multiplexing, then session negotiation fails.

The RTCSignalingState enum specifies the possible values of RTCPeerConnection.signalingState (en-US), which indicates where in the process of signaling the exchange of offer and answer the connection currently is.

Constante Description
"stable" There is no ongoing exchange of offer and answer underway. This may mean that the RTCPeerConnection object is new, in which case both the localDescription (en-US) and remoteDescription (en-US) are null; it may also mean that negotiation is complete and a connection has been established.
"have-local-offer" The local peer has called RTCPeerConnection.setLocalDescription() (en-US), passing in SDP representing an offer (usually created by calling RTCPeerConnection.createOffer() (en-US)), and the offer has been applied successfully.
"have-remote-offer" The remote peer has created an offer and used the signaling server to deliver it to the local peer, which has set the offer as the remote description by calling RTCPeerConnection.setRemoteDescription() (en-US).
"have-local-pranswer" The offer sent by the remote peer has been applied and an answer has been created (usually by calling RTCPeerConnection.createAnswer() (en-US)) and applied by calling RTCPeerConnection.setLocalDescription() (en-US). This provisional answer describes the supported media formats and so forth, but may not have a complete set of ICE candidates included. Further candidates will be delivered separately later.
"have-remote-pranswer" A provisional answer has been received and successfully applied in response to an offer previously sent and established by calling setLocalDescription().
"closed" This is an obsolete API and is no longer guaranteed to work.

La connection est fermée.

Note : Cette valeur a été déplacée dans le RTCPeerConnectionState enum dans le brouillon de cette spécification du 13 mai 2016, pour qu'il reflète l'état de RTCPeerConnection, et non la connection de signalisation. Vous pouvez maintenant détecter une connection fermée en vérifiant à la place que l'état de la connection connectionState (en-US) est indiquée "closed".

Spécification Statut Commentaire
WebRTC 1.0: Real-time Communication Between Browsers
La définition de 'RTCPeerConnection' dans cette spécification.
Candidat au statut de recommandation Définition initiale.