DesignWebRTC

Version 16 (Adrian Georgescu, 08/14/2015 11:28 am)

1 1 Saúl Ibarra Corretgé
h1. SylkServer WebRTC Gateway (Moonshot)
2 1 Saúl Ibarra Corretgé
3 1 Saúl Ibarra Corretgé
h2. Goal
4 1 Saúl Ibarra Corretgé
5 13 Adrian Georgescu
Allow end-users that have access to a web-based application to communicate with the rest of the Internet without having to download and configure locally a SIP or XMPP client. Optionally, a temporary or permanent address can be created on the fly and assigned to the user for receiving incoming calls. A web page will be designed that can be customizable by third-party web developers where users will be able to enter an address and start an audio/video call or chat session.
6 1 Saúl Ibarra Corretgé
7 1 Saúl Ibarra Corretgé
h2. Background
8 1 Saúl Ibarra Corretgé
9 1 Saúl Ibarra Corretgé
WebRTC provides a media library that allows web developers to load a web page through which Java script runs code that can access the microphone, speakers and camera. The soon to emerge standard provides a media stream and its SDP (session description protocol) that can be used by a signaling protocol like SIP or XMPP to locate another users and negotiate a media session. ICE methodology is used to probe a media path.
10 1 Saúl Ibarra Corretgé
11 10 Adrian Georgescu
SylkServer allows transparent bridging of call flows for audio, chat, presence file transfer between SIP and XMPP protocols and supports ICE. All these call flows have an equivalent in WebRTC realm.
12 1 Saúl Ibarra Corretgé
13 1 Saúl Ibarra Corretgé
h2. Addressing
14 1 Saúl Ibarra Corretgé
15 1 Saúl Ibarra Corretgé
WebRTC is not a signaling protocol and does not introduce any new addressing scheme. To allow users to have a globally reachable address for receiving incoming calls we envisage a mechanism by which an external end-user controlled identity management system can be mapped to a SIP/XMPP address provided by the operator that runs SylkServer. For example we can link the webfinger profile of end-users with a user@domain addresses reachable through SylkServer.
16 1 Saúl Ibarra Corretgé
17 1 Saúl Ibarra Corretgé
h2. Implementation
18 1 Saúl Ibarra Corretgé
19 1 Saúl Ibarra Corretgé
To achieve the goal we propose to make SylkServer WebRTC enabled.  A web server with web sockets support will be added to SylkServer and an API will be created that allows the end-users that loaded the page to join a conference or start an outgoing session to any other client on the Internet that uses user@domain addressing. The server will be zero configuration for the protocol mechanics.
20 1 Saúl Ibarra Corretgé
21 1 Saúl Ibarra Corretgé
h2. Deliverables
22 1 Saúl Ibarra Corretgé
23 14 Adrian Georgescu
The outcome is an open source licensed software.
24 1 Saúl Ibarra Corretgé
25 15 Adrian Georgescu
# SIP SIMPLE client SDK support for WebRTC (written in C and Python)
26 1 Saúl Ibarra Corretgé
# Additions to "janus":https://github.com/meetecho/janus-gateway webrtc server component (written in C)
27 16 Adrian Georgescu
# Gateway application (part of SylkServer) (in Python)
28 15 Adrian Georgescu
# sylkRTC API server side implementation (Python)
29 15 Adrian Georgescu
# sylkRTC API client side implementation (JavaScript)
30 1 Saúl Ibarra Corretgé
# Web page front-end (HTML, CSS & JavaScript)
31 1 Saúl Ibarra Corretgé
# Debian / Ubuntu packaging
32 16 Adrian Georgescu
# sylkRTC API extensions for chat
33 16 Adrian Georgescu
# sylkRTC API extensions for presence
34 16 Adrian Georgescu
# sylkRTC API extensions for contacts
35 16 Adrian Georgescu
# Multiparty video conferencing
36 1 Saúl Ibarra Corretgé
37 12 Adrian Georgescu
The software will be freely available for download on GitHub public repositories, as Debian package and as a public service at http://sip2sip.info