Moonshot
Version 5 (Adrian Georgescu, 05/13/2015 02:42 am)
| 1 | 3 | Adrian Georgescu | h1. Project Moonshot (a.k.a. WebSylk) |
|---|---|---|---|
| 2 | 1 | Adrian Georgescu | |
| 3 | 4 | Adrian Georgescu | Adding WebRTC and video capability to SylkServer. This will allow anyone with basic computer knowledge to setup a zero-configuration meeting point that can be used to join a multi-party conference using standards-based clients like SIP, XMPP, IRC and and Web-browsers. |
| 4 | 1 | Adrian Georgescu | |
| 5 | 1 | Adrian Georgescu | (Items in this list are not necessarily in order) |
| 6 | 1 | Adrian Georgescu | |
| 7 | 1 | Adrian Georgescu | h2. Add VP8 support to SIP SIMPLE Client SDK |
| 8 | 1 | Adrian Georgescu | |
| 9 | 1 | Adrian Georgescu | WebRTC mandates implementing both VP8 and H264, but the H264 part is getting quite some resistance. The current state (as of 12th of May 2015) is: Chrome does not implement H264, and in Firefox it has to be manually enabled through the advanced configuration menu. |
| 10 | 1 | Adrian Georgescu | |
| 11 | 1 | Adrian Georgescu | We need to add support for it to the SDK so we can transparently interoperate with WebRTC endpoints without the need for transcoding. |
| 12 | 1 | Adrian Georgescu | |
| 13 | 1 | Adrian Georgescu | Apparently libvpx already has VP9 support, which is currently behind a flag in Chrome, it's probably a good idea to try to add it too. |
| 14 | 1 | Adrian Georgescu | |
| 15 | 5 | Adrian Georgescu | h2. Extend SylkServer with a web framework any application can tap into. |
| 16 | 5 | Adrian Georgescu | |
| 17 | 5 | Adrian Georgescu | Different applications might need to serve web content: screensharing images, conference web page, WebRTC endpoint, etc. There should be a single HTTP(S) endpoint where applications tap into and serve content. |
| 18 | 1 | Adrian Georgescu | |
| 19 | 1 | Adrian Georgescu | Example URLs: |
| 20 | 1 | Adrian Georgescu | |
| 21 | 1 | Adrian Georgescu | https://conference.sip2sip.info/sylk/conference/screen-sharing/ |
| 22 | 1 | Adrian Georgescu | https://conference.sip2sip.info/sylk/conference/ |
| 23 | 1 | Adrian Georgescu | https://conference.sip2sip.info/sylk/webrtcgateway/ |
| 24 | 1 | Adrian Georgescu | |
| 25 | 1 | Adrian Georgescu | |
| 26 | 1 | Adrian Georgescu | h2. Design SylkRTC |
| 27 | 1 | Adrian Georgescu | |
| 28 | 1 | Adrian Georgescu | The WebSocket API for gatewaying WebRTC endpoints to the SIP world. It needs to cover: |
| 29 | 1 | Adrian Georgescu | |
| 30 | 1 | Adrian Georgescu | h3. Phase 1 |
| 31 | 1 | Adrian Georgescu | |
| 32 | 1 | Adrian Georgescu | * Registration of multiple accounts |
| 33 | 1 | Adrian Georgescu | * Multiple sessions |
| 34 | 1 | Adrian Georgescu | * Audio / video sessions |
| 35 | 1 | Adrian Georgescu | |
| 36 | 1 | Adrian Georgescu | h3. Phase 2 |
| 37 | 1 | Adrian Georgescu | |
| 38 | 1 | Adrian Georgescu | * Chat |
| 39 | 1 | Adrian Georgescu | * Presence |
| 40 | 1 | Adrian Georgescu | * Contacts management |
| 41 | 1 | Adrian Georgescu | |
| 42 | 1 | Adrian Georgescu | h3. Phase 3 |
| 43 | 1 | Adrian Georgescu | |
| 44 | 1 | Adrian Georgescu | * File transfer |
| 45 | 1 | Adrian Georgescu | * Screen sharing |
| 46 | 1 | Adrian Georgescu | |
| 47 | 1 | Adrian Georgescu | |
| 48 | 1 | Adrian Georgescu | h2. Implement the gateway skeleton (first alpha release) |
| 49 | 1 | Adrian Georgescu | |
| 50 | 1 | Adrian Georgescu | It needs to cover: |
| 51 | 1 | Adrian Georgescu | |
| 52 | 1 | Adrian Georgescu | * Multiple accounts |
| 53 | 1 | Adrian Georgescu | * Single session per account |
| 54 | 1 | Adrian Georgescu | * Audio and video |
| 55 | 1 | Adrian Georgescu | |
| 56 | 1 | Adrian Georgescu | |
| 57 | 1 | Adrian Georgescu | h2. Gateway phase 2 |
| 58 | 1 | Adrian Georgescu | |
| 59 | 1 | Adrian Georgescu | * Chat |
| 60 | 1 | Adrian Georgescu | * Presence |
| 61 | 1 | Adrian Georgescu | * Contact management |
| 62 | 1 | Adrian Georgescu | |
| 63 | 1 | Adrian Georgescu | |
| 64 | 1 | Adrian Georgescu | h1. Other |
| 65 | 1 | Adrian Georgescu | |
| 66 | 1 | Adrian Georgescu | Random notes, thoughts, etc. |
| 67 | 1 | Adrian Georgescu | |
| 68 | 1 | Adrian Georgescu | |
| 69 | 1 | Adrian Georgescu | h2. Write our own Janus SIP plugin |
| 70 | 1 | Adrian Georgescu | |
| 71 | 1 | Adrian Georgescu | Based on the existing one, but using PJSIP instead. It will become clearer once we are further in the project. We'd use just the SIP signaling part, not any media capability, that's taken care of. |
| 72 | 1 | Adrian Georgescu | |
| 73 | 1 | Adrian Georgescu | The SylkRTC API would not change, but it should facilitate some features such as multiple sessions per account. |
| 74 | 1 | Adrian Georgescu | |
| 75 | 1 | Adrian Georgescu | h2. Multi-party video |
| 76 | 1 | Adrian Georgescu | |
| 77 | 1 | Adrian Georgescu | There is a Janus plugin for that, maybe we can leverage it. Adding support for this to our SDK is a no go, in it's current state. |
| 78 | 1 | Adrian Georgescu | |
| 79 | 1 | Adrian Georgescu | Adding support for "transparent streams" (and sessions) might be required. Basically we'd need a Session which doesn't really handle media, but it takes some SDP that got passed to it and deals with it. |
| 80 | 1 | Adrian Georgescu | |
| 81 | 1 | Adrian Georgescu | We'd use multiple Video streams in a single session, and some way to correlate them, probably piggibacking on what WebRTC already does with BUNDLE, for example. |
| 82 | 1 | Adrian Georgescu | |
| 83 | 1 | Adrian Georgescu | I'm not sure if Janus supports simulcast. (sending one big picture and the rest as thumbnails) |
| 84 | 1 | Adrian Georgescu | |
| 85 | 1 | Adrian Georgescu | |
| 86 | 1 | Adrian Georgescu | h2. Streaming |
| 87 | 1 | Adrian Georgescu | |
| 88 | 1 | Adrian Georgescu | This can probably be offloaded to Janus. |