Export (0) Print
Expand All

[MS-OCSPROT]: Lync and Lync Server Protocols Overview

Office

Click here to view this version of the [MS-OCSPROT] PDF.

Click here to download a zip file with all of the PDF files.

This document provides a system overview for the protocols in the Communications Server system. It is intended for use in conjunction with the Microsoft protocol technical specifications, publicly available standard specifications, network programming art, and Microsoft Windows distributed systems concepts. It assumes that the reader is either familiar with the aforementioned material or has immediate access to it.

A protocol system document does not require the use of Microsoft programming tools or programming environments in order to implement the protocols in the system. Developers who have access to Microsoft programming tools and environments are free to take advantage of them.

Intellectual Property Rights Notice for Open Specifications Documentation

  • Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.

  • Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.

  • No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

  • Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@microsoft.com.

  • Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.

  • Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.

Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.

Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.

Abstract

Communications Server is a client-server product that is based on the Session Initiation Protocol (SIP) to facilitate real-time communications between users. Protocol clients, such as Office Communicator, are used to sign in to Communications Server. Users can initiate calls to one or more users who are also signed in to Communications Server by using different protocol clients such as IM, audio, video, VoIP, and applications-sharing. These clients are enabled via other protocols. Communications Server aggregates the user’s presence from all of the user’s protocol clients and publishes that presence information for other users authorized to view it.

This document describes the intended functionality of the Communications Server system and how the protocols in this system interact. It provides examples of some of the common user scenarios. It does not restate the processing rules and other details that are specific for each protocol. These details are described in the protocol specifications for each of the protocols and data structures that make up this system.

Date

Revision History

Revision Class

Comments

4/4/2008

0.1

Major

Initial Availability

4/25/2008

0.2

Major

Revised and edited the technical content

6/27/2008

1.0

Major

Revised and edited the technical content

8/15/2008

1.01

Major

Revised and edited the technical content

12/12/2008

2.0

Major

Revised and edited the technical content

2/13/2009

2.01

Major

Revised and edited the technical content

3/18/2009

2.02

Editorial

Revised and edited the technical content

7/13/2009

2.03

Major

Changes made for template compliance

8/28/2009

2.04

Editorial

Revised and edited the technical content

11/6/2009

2.05

Editorial

Revised and edited the technical content

2/19/2010

2.06

Editorial

Revised and edited the technical content

3/31/2010

2.07

Major

Updated and revised the technical content

4/30/2010

2.08

Editorial

Revised and edited the technical content

6/7/2010

2.09

Editorial

Revised and edited the technical content

6/29/2010

2.10

Editorial

Changed language and formatting in the technical content.

7/23/2010

2.10

No Change

No changes to the meaning, language, or formatting of the technical content.

9/27/2010

3.0

Major

Significantly changed the technical content.

11/15/2010

3.0

No Change

No changes to the meaning, language, or formatting of the technical content.

12/17/2010

3.0

No Change

No changes to the meaning, language, or formatting of the technical content.

3/18/2011

3.0

No Change

No changes to the meaning, language, or formatting of the technical content.

6/10/2011

3.0

No Change

No changes to the meaning, language, or formatting of the technical content.

1/20/2012

4.0

Major

Significantly changed the technical content.

4/11/2012

4.0

No Change

No changes to the meaning, language, or formatting of the technical content.

7/16/2012

4.0

No Change

No changes to the meaning, language, or formatting of the technical content.

10/8/2012

4.1

Minor

Clarified the meaning of the technical content.

2/11/2013

4.2

Minor

Clarified the meaning of the technical content.

7/30/2013

4.3

Minor

Clarified the meaning of the technical content.

11/18/2013

4.3

No Change

No changes to the meaning, language, or formatting of the technical content.

2/10/2014

4.3

No Change

No changes to the meaning, language, or formatting of the technical content.

4/30/2014

4.3

No Change

No changes to the meaning, language, or formatting of the technical content.

7/31/2014

4.4

Minor

Clarified the meaning of the technical content.

10/30/2014

4.4

No Change

No changes to the meaning, language, or formatting of the technical content.

3/30/2015

4.4

No Change

No changes to the meaning, language, or formatting of the technical content.

Show:
© 2015 Microsoft