DesignWebRTC
Version 11 (Adrian Georgescu, 07/31/2015 04:44 pm) → Version 12/17 (Adrian Georgescu, 08/03/2015 10:29 am)
h1. SylkServer WebRTC Gateway (Moonshot)
h2. Goal
Allow end-users that have access to a web-based tablet 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.
h2. Background
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.
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.
h2. Addressing
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.
h2. Implementation
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.
h2. Deliverables
The outcome is a software with an open source license that can be packaged either as a server or a client running on end-user computers.
* SIP SIMPLE client SDK support for WebRTC (written in C and Python)
* Gateway application (part of SylkServer) (in Python)
* Additions to "janus":https://github.com/meetecho/janus-gateway webrtc server component (written in C)
* sylkRTC API server side implementation (Python)
* sylkRTC API client side implementation (JavaScript)
* sylkRTC API extensions for chat, presence and contacts
* Web page front-end (HTML, CSS & JavaScript)
* Multiparty video conferencing (t.b.d.)
* Debian / Ubuntu packaging
The software will be freely available for download on GitHub public repositories, as Debian package and as a a public service at http://sip2sip.info
h2. Goal
Allow end-users that have access to a web-based tablet 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.
h2. Background
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.
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.
h2. Addressing
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.
h2. Implementation
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.
h2. Deliverables
The outcome is a software with an open source license that can be packaged either as a server or a client running on end-user computers.
* SIP SIMPLE client SDK support for WebRTC (written in C and Python)
* Gateway application (part of SylkServer) (in Python)
* Additions to "janus":https://github.com/meetecho/janus-gateway webrtc server component (written in C)
* sylkRTC API server side implementation (Python)
* sylkRTC API client side implementation (JavaScript)
* sylkRTC API extensions for chat, presence and contacts
* Web page front-end (HTML, CSS & JavaScript)
* Multiparty video conferencing (t.b.d.)
* Debian / Ubuntu packaging
The software will be freely available for download on GitHub public repositories, as Debian package and as a a public service at http://sip2sip.info