v0.0.X

How to register your own signal in NextRTC

On GitHub I was asked how to implement own signal using NextRTC. In configuration file you have to autowire SignalResolver as shown below:

then you have to add bean which will add your handlers. Handler has to implement only one interface SignalHandler. That interface has only one method so you can write it just …

Continue Reading
v0.0.X

How to use nextrtc in java project

NextRTC is designed to be easy to integrate with existing solution. First step is to add to your maven project dependency to latest version of nextrtc-signaling-server.

Then you have to expose your websocket channel, to allow js client to connect to server. In NextRTC you can do it by creating class:

Here you can …

Continue Reading
v0.0.X

JS client description

If you want to use nextrtc js client you have to add to your code following js files: – adapter.js – nextRTC.js Both files are available in project nextrtc-signaling-server in directory resources. Adapter is taken from here, so if you want to use newest version you should take it direct from that project.   NextRTC js client …

Continue Reading
v0.0.X

Signal exchange with examples

S – Server C – Client CM – Client registered in server as potencial member of conversation   Connect to server via websocket:

(1) open websocket connection (2) C became CM   Send command to create conversation:

(1) send signal “create” with optional conversation name (2) receive “created” with unique conversation Id – …

Continue Reading
v0.0.X

NextRTC protocol phrases

Register yourself in server Registration to server is simple open websocket connection. When connection is established you are allowed to post signals via websocket channel. Details: In this phrase to websocket schannel is bound unique ID which is use to recognize exactly one member of communication. Execute command on server Exceptions, Timeouts When connection (websocket) breaks …

Continue Reading
v0.0.X

Json signal structure

Signal structure:

“from” – This field is filled by Server. Server attach here unique ID of client who trigger action “to” – This field is filled by Client or Server. Here you can check your ID (in incomming messages) or point to whom signal should be propagated (in outcomming messages) “signal” – name of …

Continue Reading
v0.0.X

Signals in NexRTC

NextRTC uses twelve signals all are presended below: offerRequest offerResponse answerRequest answerResponse finalize candidate ping left join create joined created

Continue Reading
v0.0.X

Signal types

There are three type of signals. Information signals (you can, but it is not mandatory to handle it). Those signals are always came from server, and are triggered by action of user, or by server to check if client is still running. This group includes: ping joined created left Commands (you will send it to …

Continue Reading