Single PeerConnection Documentation

sreichman · November 7, 2018, 4:45pm

Looking for information on how to setup rooms with a single peer connection - so far this is the only thing I’ve found:

lynckia/licode/blob/master/feature-review/single-peer-connection.md

# Single Peer Connection - Feature Review
Single Peer Connection means that we can send/receive all streams in the same PeerConnection, sharing UDP ports, ICE credentials, DTLS certificates, etc. It usually means that publishers/subscribers use a single UDP "connection", with some benefits: reduce the number of ports used by the clients and server and shorter times to publish/subscribe new streams.

![comparison](https://docs.google.com/drawings/d/1EMW43_6BX0mDJ2v4kLWrzDobz6dRjjqhctSkLM869io/pub?w=960&h=721)

## Architecture
Single Peer Connection involves changes in both client and server sides.

This new feature will be optional because we'd like to keep backwards compatibility with older systems and be sure we can disable it if some browser does not support it.

## API Changes
Client: All changes will be hidden inside code.

Server: The feature will be activated/deactivated via `licode_config.js`. The policies that control ecCloudHandler will be modified to allow more fine-grained control over the ErizoJS chosen for any given connection or client.

## Details
This features involves changes in:

- SDP: Full SDP will only be used in the Clients. We will transition to an asynchronous exchange of JSON messages between ErizoClient and ErizoJS. ErizoClient will be in charge of assembling the SDP and passing it to the PeerConnection. There will be a single SDP per connection, with information about all the streams that take part of it.

This file has been truncated. show original

I’ve found the config.erizoController.allowSinglePC and set it to true, and also passed the options singlePC = True when calling room.connect(), and on the client side, all replies from the server / all places where the singlePC value is checked show true, however in webrtc internals, I still see multiple peer connections. (Using Chrome 70 - so singlePC is supported)

Is there something else needed, or something else that is preventing a single PeerConnection being used?

EDIT: Also, I should mention that I am using licode v6

Javier · November 8, 2018, 4:03pm

You may also need to set config.erizoController.maxErizosUsedByRoom to 1 in order to see just one Peer Connection. Actually, you should see as many Peer Connection as the number you set in that config file.

Also please take into account that Peer Connection is still a work in progress feature. We use it already in production with Chrome browsers but we don’t support it in Firefox (or other browsers) yet.

sreichman · November 8, 2018, 4:08pm

Thanks for your reply I will try setting set config.erizoController.maxErizosUsedByRoom to 1 - but when you say 'you should see as many Peer Connection as the number you set ’ are you referring to the number set to config.erizoController.maxErizosUsedByRoom?

Javier · November 8, 2018, 4:10pm

yes, that’s exactly what I mean. Please let me know if it works for you

sreichman · November 8, 2018, 4:14pm

Just did - it works. Thanks again for your help.

Topic		Replies	Views
Stream Data is not sent peer to peer and uses erizoController instead? Support	1	826	June 12, 2017
Using ErizoAPI without erizo controller, status 500 after sending SDP answer	0	587	January 5, 2015
How many p2p rooms can be served by erizoController? Support	1	729	May 29, 2017
Switching the type of connection on the fly	0	387	March 13, 2014
What exactly happens when a call is set up?	1	412	May 17, 2013

Single PeerConnection Documentation

Related Topics