Boris,
sorry for asking so many questions. But I'm new with this piece of the
architecture of webRTC and I could not get the pieces together
I need to do a post to the video bridge, something like this:
{
"contents" :
[
{
"name" : "audio",
"channels" : [ { "expire" : 60 } ]
},
{
"name" : "video",
"channels" : [ { "expire" : 60 } ]
}
]
}
then I will get an conference ID. After that, what should I do?
Intercept the SDP in the signalling server? And based on that, what I
need to change?
The following assumes that the signalling server will be generating the offer. If that's not the case, the procedure will need to be different. Also, it is not the only way to go, but just an example (based on Jitsi Meet and jicofo).
1. The signalling server allocates a conference on the bridge. What you have above. Apart from the conference ID, the bridge will include a "transport" for each channel, which will have ICE candidates and a DTLS fingerprint.
2. The signalling server creates an SDP offer, and substitutes the ICE candidates and DTLS fingerprint with the ones obtained in step 1. It then sends the offer to the client.
3. The signalling server receives the client's answer. It takes the transport information, and the payload-type description, converts them to the COLIBRI/JSON format and sends it to the videobridge with a PATCH request.
Now the client and videobridge have each other's ICE candidates and will start ICE.
If you think it is valuable, after understanding how it works I could
write a tutorial about this.
Sure, I think that more documentation would be welcome. Thanks!
Regards,
Boris
···
On 15/01/15 15:45, Renan Reis wrote: