Lync » History » Version 1
Adrian Georgescu, 10/20/2014 01:55 AM
| 1 | 1 | Adrian Georgescu | h1. Lync Gateway |
|---|---|---|---|
| 2 | |||
| 3 | h2. Goal |
||
| 4 | |||
| 5 | The goal of this project is to develop a software gateway that makes possible interoperability between Microsoft Lync, a proprietary solution based on modified IETF SIP standards and a domain using XMPP foundation standards. The solution would then be used for federating real time communication services using multiple media like audio, chat, presence, screen-sharing, video and file transfer between these Lync, SIP and XMPP protocols. |
||
| 6 | |||
| 7 | h3. Features |
||
| 8 | |||
| 9 | The gateway will provide translations for the following media: |
||
| 10 | |||
| 11 | * Audio calls |
||
| 12 | * Chat conversations |
||
| 13 | * Presence notifications |
||
| 14 | * Screen Sharing (using Remote Desktop Protocol) |
||
| 15 | |||
| 16 | h3. End-points |
||
| 17 | |||
| 18 | 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 | |||
| 20 | h3. |
||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | |||
| 25 | |||
| 26 | |||
| 27 | |||
| 28 | |||
| 29 | |||
| 30 |