CODEWITHSUNDEEP
androidwebrtcp2psignaling
Sofia Clover
Sofia Clover

Reputation: 679

WebRTC local signaling server

I am trying to figure out a solution for a signaling server for an Android WebRTC based project. Both clients will be Android and both located close to each other, i.e. - within 100 yards or less. I would like the solution to work without the use of a public signaling server. I would rather just have one of the clients also act as the server.

So, my question is : 1. How can I achieve it so that one is the server? i.e. - Can I set one as a hotspot or use wifi direct? 2. If I can achieve #1, then what is a good solution for a signaling server running on android ? Can I run one of the nodejs servers on android ?

Upvotes: 6

Views: 2341

Answers (2)

Khoa Tran
Khoa Tran

Reputation: 528

With WebRTC, signaling server is just the way to help you transfer your message, exchange your information (SDP package(createOffer/answer), exchange candidates etc).

Example : You can use GCM (Free) as a signaling server, or using Nodejs with socket.io, websocket, XMPP etc. Only thing you need is transfer your message between two peers.

You can refer to this tutorial : http://www.html5rocks.com/en/tutorials/webrtc/basics/

Upvotes: 3

Adrian Ber
Adrian Ber

Reputation: 21360

A signaling server is simply a way to exchange messages between two parties. In the WebRTC case these messages are the offer/answer and ICE candidates.

You can use whatever type of server you want to do this, you can even do it manually :).

You can use one of the clients as the server too, but then you will have to communicate the IP to the other somehow. Maybe use Wi-Fi direct and get it programatically.

Upvotes: 4

Related Questions