WBSO

Version 19 (Adrian Georgescu, 11/05/2012 10:21 am)

1 4 Adrian Georgescu
h1. WBSO status
2 1 Adrian Georgescu
3 18 Adrian Georgescu
h2. Performed activities 2012
4 7 Adrian Georgescu
5 17 Adrian Georgescu
!20121105-Progress-AgentschapNL.png!
6 17 Adrian Georgescu
7 12 Adrian Georgescu
h3. Presence
8 12 Adrian Georgescu
9 10 Adrian Georgescu
Implemented Presence in the middleware, the client side and server side. At over 15,000 lines of Python code, Presence is by far the most complex part of the SDK and the reason it took so long to produce. Presence functionality is now incorporated into an easy to use address book that can be used to develop contact-driven Real Time Communication clients without having to deal with the complexity of SIP signaling, XCAP storage and data replication among multiple devices.
10 7 Adrian Georgescu
11 5 Adrian Georgescu
http://sipsimpleclient.com/projects/sipsimpleclient/news
12 1 Adrian Georgescu
13 12 Adrian Georgescu
h3. Implemented XMMP translation for Chat and Presence
14 11 Adrian Georgescu
15 1 Adrian Georgescu
http://sylkserver.ag-projects.com/news/7
16 12 Adrian Georgescu
17 16 Adrian Georgescu
h3. MacOSX version completed (without Video yet)
18 11 Adrian Georgescu
19 11 Adrian Georgescu
 * The MacOSX version now has all Presence integrated
20 11 Adrian Georgescu
21 11 Adrian Georgescu
http://projects.ag-projects.com/news/15
22 13 Adrian Georgescu
23 13 Adrian Georgescu
h2. Roadmap
24 13 Adrian Georgescu
25 15 Adrian Georgescu
 * XMMP translation for audio calls
26 15 Adrian Georgescu
 * XMMP translation for file transfers
27 15 Adrian Georgescu
 * Multiparty support for MUC add/remove participants
28 14 Adrian Georgescu
 * Adding Chat for Linux and Windows client
29 1 Adrian Georgescu
 * Adding File Transfer for Linux and Windows client
30 1 Adrian Georgescu
 * Adding Screen sharing for Linux and Windows client
31 15 Adrian Georgescu
 * Adding Screen sharing for Linux and Windows client
32 15 Adrian Georgescu
 * Migration to PJSIP 2.0 that solves many of the outstanding issues
33 15 Adrian Georgescu
 * Add Video support in middleware
34 15 Adrian Georgescu
 * Add Video to MacOSX client
35 15 Adrian Georgescu
 * Add Video to Linux and Window client
36 19 Adrian Georgescu
37 19 Adrian Georgescu
38 19 Adrian Georgescu
h2. Current Issues (February 17th, 2012)
39 19 Adrian Georgescu
40 19 Adrian Georgescu
1. -Cannot correlate session with local and remote end-points state (busy, available, on the phone and type of media supported by the remote end-point) (Tickets 144, 118, 130)-
41 19 Adrian Georgescu
2. The approach to implement video did not worked as envisaged (Ticket 18, 135)
42 19 Adrian Georgescu
3. -The address book is unreliable, causing loss of contacts, duplicated contacts or broken synchronization among multiple instances (Ticket 143, 144)-
43 19 Adrian Georgescu
4. -Presence Chat and file transfer are perceived as being useless because of lack of interoperability with XMPP users (Gmail, Facebook) (no ticket)-
44 19 Adrian Georgescu
5. Session is unreliable when adding/removing streams and network has packet loss (Ticket 107, 135)
45 19 Adrian Georgescu
6. TLS transport is not working properly due to assumption that is a general setting (Ticket 120, 135)
46 19 Adrian Georgescu
47 19 Adrian Georgescu
h2. Solutions
48 19 Adrian Georgescu
49 19 Adrian Georgescu
1. -Integration and synchronization of Presence with different media streams (speech, IM, File transfer and video) in only one SIP session-
50 19 Adrian Georgescu
2. The libraries we relied upon were buggy and poorly supported. It was actually to early to start working on video and it was too complex of a task to approach with only one developer. PJSIP 2.0 has added basic video support in the mean time. We will migrate to PJSIP 2.0 that has support for video libraries that are already integrated into the media layer 
51 19 Adrian Georgescu
3. -The IETF model for contacts management seem to be broken as it allows non-atomic operations. For example when one contact is added, 3 XCAP documents must be saved over the network and if any one fails, there is no way to reliably rollback only parts of the operation. The solution is to use the OMA standards (Open Mobile Alliance) that defines the Presence and Address book together in a main document and the other documents use links to the entries in the main document. This way only one document can be written for a contact add update or delete and this operational can be done atomically-
52 19 Adrian Georgescu
4. -Presence and Chat must be refactored to support XMPP translation in order to interoperate with other users using other protocols-
53 19 Adrian Georgescu
5. All operations in the session must be serialized and applied when they can be performed. This requires refactoring of the session model
54 19 Adrian Georgescu
6. Each SIP account requires its own encrypted transport because TLS connections have per account settings, for example verify_peer and certificate validation depends on foreign domain