Lync
Version 7 (Adrian Georgescu, 10/20/2014 02:06 am)
1 | 6 | Adrian Georgescu | h1. SylkServer Lync Gateway |
---|---|---|---|
2 | 1 | Adrian Georgescu | |
3 | 1 | Adrian Georgescu | h2. Goal |
4 | 1 | Adrian Georgescu | |
5 | 7 | Adrian Georgescu | The goal of this project is to develop a software gateway that makes possible end-to-end interoperability between Microsoft Lync, a proprietary solution based on modified IETF SIP standards and foreign domains using XMPP foundation standards. The solution would then be used for federating real time communication services using multiple media like audio, chat, presence and screen-sharing between these Lync, SIP and XMPP protocols. This would allow parts of an organisation to migrate away from using a proprietary solution while maintaining interoperability with other parts of the organisation that still make use of it. |
6 | 1 | Adrian Georgescu | |
7 | 1 | Adrian Georgescu | h3. Features |
8 | 1 | Adrian Georgescu | |
9 | 1 | Adrian Georgescu | The gateway will provide translations for the following media: |
10 | 1 | Adrian Georgescu | |
11 | 1 | Adrian Georgescu | * Audio calls |
12 | 1 | Adrian Georgescu | * Chat conversations |
13 | 1 | Adrian Georgescu | * Presence notifications |
14 | 1 | Adrian Georgescu | * Screen Sharing (using Remote Desktop Protocol) |
15 | 1 | Adrian Georgescu | |
16 | 1 | Adrian Georgescu | h3. End-points |
17 | 1 | Adrian Georgescu | |
18 | 1 | Adrian Georgescu | The gateway will be inserted between two foreign domains, allowing each domain to use its own client to interoperate with the client in the remote domain. A Lync based domain will use a Lync client and an XMPP domain will use a modified XMPP client that is able to support audio calls using Jingle and screen sharing using RDP protocol. It is the responsibility of the customer to develop its client to support these standards. |
19 | 1 | Adrian Georgescu | |
20 | 3 | Adrian Georgescu | h3. Testbed |
21 | 3 | Adrian Georgescu | |
22 | 3 | Adrian Georgescu | The customer will provide a functional Microsoft Lync implementation both clients and servers and support for troubleshooting issues related to native Microsoft implementation. |
23 | 3 | Adrian Georgescu | |
24 | 3 | Adrian Georgescu | h3. Delivery schedule |
25 | 3 | Adrian Georgescu | |
26 | 6 | Adrian Georgescu | The delivery of the above mentioned features will be done over a twelve month period. After six month, a functional skeleton of the application will be available and two media types will be implemented. Other media types will be subsequently added. |
27 | 1 | Adrian Georgescu | |
28 | 1 | Adrian Georgescu | h3 Costs |
29 | 6 | Adrian Georgescu | |
30 | 6 | Adrian Georgescu | Costs consists of one time development fees and subsequent recurrent support fees. 1st year support period is mandatory, support may be cancelled after 12 months. |
31 | 6 | Adrian Georgescu | |
32 | 6 | Adrian Georgescu | * The development costs are 7000 Euro/month. The total costs of the project amounts to 84000 Euro. |
33 | 6 | Adrian Georgescu | * Support fees covers software upgrades and troubleshooting for problems reported by customer. The support fees amount to 18% of project value for the first year and 12% for subsequent years. |
34 | 6 | Adrian Georgescu | |
35 | 6 | Adrian Georgescu | |
36 | 6 | Adrian Georgescu | |
37 | 6 | Adrian Georgescu | |
38 | 3 | Adrian Georgescu | |
39 | 3 | Adrian Georgescu | |
40 | 3 | Adrian Georgescu | |
41 | 3 | Adrian Georgescu | |
42 | 1 | Adrian Georgescu | |
43 | 1 | Adrian Georgescu | |
44 | 1 | Adrian Georgescu | |
45 | 1 | Adrian Georgescu | |
46 | 1 | Adrian Georgescu | |
47 | 1 | Adrian Georgescu | |
48 | 1 | Adrian Georgescu | |
49 | 1 | Adrian Georgescu | |
50 | 1 | Adrian Georgescu | |
51 | 1 | Adrian Georgescu |