Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

242
Views
Assuming a user sends his IP and port to another, why does WebRTC need a signaling server for a data connection?

In all serverless (not including ICE/STUN) implementations of WebRTC, that create a data connection, I've always noticed that the flow is:

  • User 1 sends contact info to user 2.
  • User 2 processes contact info and sends reponse to user 1.
  • Users can now communicate.

What I don't understand is why do we need the second step? In desktop apps, the first step is enough, even if there's a NAT (due to STUN servers). Is this some WebRTC limitation? If so, why?

about 4 years ago · Juan Pablo Isaza
1 answers
Answer question

0

Besides ICE candidates, SDP contains information about codecs, tracks etc. Signaling server is needed as a channel to establish a connection between peers by exchanging such information.

about 4 years ago · Juan Pablo Isaza Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!