RTCIceCandidate: candidate property

A string describing the properties of the candidate, taken directly from the SDP attribute "candidate". The candidate string specifies the network connectivity information for the candidate. If the candidate is an empty string (""), the end of the candidate list has been reached; this candidate is known as the "end-of-candidates" marker.

The syntax of the candidate string is described in RFC 5245, section 15.1. For an a-line (attribute line) that looks like this:

a=candidate:4234997325 1 udp 2043278322 192.0.2.172 44323 typ host

the corresponding candidate string's value will be: "candidate:4234997325 1 udp 2043278322 192.0.2.172 44323 typ host".

The user agent always prefers candidates with the highest priority, all else being equal. In the example above, the priority is 2043278322. The attributes are all separated by a single space character, and are in a specific order. The complete list of attributes for this example candidate is:

• foundation = 4234997325
• component = "rtp" (the number 1 is encoded to this string; 2 becomes "rtcp")
• protocol = "udp"
• priority = 2043278322
• ip = "192.0.2.172"
• port = 44323
• type = "host"

In this example, we see a function which receives as input an SDP string containing an ICE candidate received from the remote peer during the signaling process.

function handleNewIceCandidate(candidateSDP) {
  const candidateObj = new RTCIceCandidate(candidateSDP);

  myPeerConnection.addIceCandidate(candidateObj).catch({
    /* handle the error thrown by addIceCandidate() */
  });
}

The handleNewIceCandidate() function shown here passes the received candidate's SDP text into RTCIceCandidate() to receive an RTCIceCandidate object in return, which represents the candidate.

The new candidate is then passed into RTCPeerConnection.addIceCandidate() to add the candidate to the list of candidates for WebRTC to consider using for the connection being established.