signalingState property on the
RTCPeerConnection interface returns one of the string values specified by
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 Signaling in Lifetime of a WebRTC session for more details about the signaling process.
Because the signaling process is a state machine, being able to verify that your code
is in the expected state when messages arrive can help avoid unexpected and avoidable
failures. For example, if you receive an answer while the
"have-local-offer", you know that something is wrong, since you
should only receive answers after creating an offer but before an answer has been
received and passed into
code will be more reliable if you watch for mismatched states like this and handle them
This value may also be useful during debugging, for example.
var state = RTCPeerConnection.signalingState;
The allowed values are those included in the enum
RTCSignalingState enum specifies the possible values of
RTCPeerConnection.signalingState, which indicates where in the process of signaling the exchange of offer and answer the connection currently is.
||There is no ongoing exchange of offer and answer underway. This may mean that the
||The local peer has called
||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
||The offer sent by the remote peer has been applied and an answer has been created (usually by calling
||A provisional answer has been received and successfully applied in response to an offer previously sent and established by calling
The connection is closed.
var pc = new RTCPeerConnection(configuration); var state = pc.signalingState;
|WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'RTCPeerConnection.signalingState' in that specification.
|Candidate Recommendation||Initial specification.|
BCD tables only load in the browser