บทบาทของเซิร์ฟเวอร์ส่งสัญญาณ

Web Real-Time Communication (WebRTC) is all about direct communication! It lets browsers and mobile apps talk to each other directly, peer-to-peer (P2P).

This means your video call data goes straight from your device to your friend's, without a central server in the middle for the actual media stream.

Sounds great, right? But how do two devices, often behind different networks and firewalls, even find each other to start that direct conversation?

They don't know each other's public IP addresses or what kind of media they want to exchange. This is where a crucial helper comes in!

Before peers can connect directly, they need an introduction. That's the job of a signaling server.

Think of it as a temporary matchmaker or a post office. It helps peers exchange vital setup information, but it doesn't handle the actual audio, video, or data once the connection is made.

The signaling server helps peers exchange two main types of metadata:

• Session Description Protocol (SDP): Details about the media (audio/video codecs, resolutions, etc.) and network capabilities.
• ICE Candidates: Information about potential network paths (IP addresses and ports) each peer can use to connect.

This "metadata" is key to establishing the direct link.

When one peer (let's call them Alice) wants to start a call, she creates an SDP offer. This offer describes what Alice wants to send and how she can receive media.

It's like Alice saying, "Hey, I want to talk! Here's how I can do it."

Alice then sends her SDP offer to the signaling server. The signaling server's job is to deliver this offer to the other peer (Bob).

It acts as a temporary messenger service. This communication often happens over a persistent connection like WebSockets.

When Bob receives Alice's SDP offer (via the signaling server), he processes it. He then creates an SDP answer, which describes his own media capabilities and confirms he's ready to connect.

It's Bob saying, "Got it! Here's how I can respond."

Just like the offer, Bob sends his SDP answer back to the signaling server, which then delivers it to Alice.

Once Alice receives the answer, both peers have exchanged their initial media descriptions and know what to expect from each other.

After exchanging SDP, peers also need to find the best network path. They do this by sharing ICE candidates.

These candidates are potential network addresses (like your home IP, or a relayed address) that each peer can use to connect. The signaling server relays these candidates too, until a direct path is found.

It's vital to remember: the signaling server's role is temporary! Once the SDP and ICE candidates are exchanged, and a direct peer-to-peer connection is established, the signaling server steps aside.

The actual audio, video, and data streams then flow directly between the peers, without touching the signaling server.

In this lesson, we explored the crucial role of the signaling server in WebRTC. We learned:

• WebRTC aims for direct peer-to-peer communication.
• Signaling servers act as temporary intermediaries to help peers find each other.
• They exchange vital metadata like SDP offers/answers and ICE candidates.
• Once the direct connection is established, signaling steps aside, and media flows P2P.

Next, we'll dive deeper into Session Description Protocol (SDP).