Live Communications Server 2005: Difference between revisions
| Line 51: | Line 51: | ||
The contact list is the list of users the end user has added to client software in order to facilitate the sending of [[instant messages|IM]]'s and for the monitoring the presence. |
The contact list is the list of users the end user has added to client software in order to facilitate the sending of [[instant messages|IM]]'s and for the monitoring the presence. |
||
The watcher list is the list of other users that have added this user to their contact list. |
The watcher list is the list of other users that have added this user to their contact list. |
||
mahdi raeesi |
mahdi raeesi 00989153119754 |
||
==Director== |
==Director== |
||
Revision as of 12:51, 10 March 2008
Live Communications Server 2005 (LCS 2005) is the second version of a SIP based instant messaging and presence server after Live Communications Server 2003. LCS 2005 was first released in 2005, and was updated with new features with Service Pack 1 in 2006. LCS 2005 has been superseded by Microsoft Office Communications Server 2007.
Overview
This product allows SIP clients to exchange IM's and presence using the SIMPLE protocol. The client also allows two clients to setup audio/video sessions, application sharing, and file transfer sessions.
The product was released in two editions, Standard Edition and Enterprise Edition. The Standard Edition uses a Microsoft SQL Server Desktop Engine (MSDE) (included with the product) to store configuration and user data. Enterprise Edition uses a full version of Microsoft SQL Server (purchased seperately).
New features to this version compared to the 2003 release is the ability to leverage SQL and remote user access.
Presence? Presence is conveyed as levels of availability to communicate.
Levels of presence support by LCS:
- Online
- Busy
- Do not disturb
- Be right back
- Away
These presence levels are controlled manually and automatically. Automatic presence changes can be triggered by the following events:
- Locking the workstation -> Away
- Screen save launches -> Away
- User does not touch keyboard or mouse for a configured time -> Away
Dependencies
- Microsoft Active Directory
- PKI
- Microsoft SQL Server
- Storage of server configuration data
- User contact list
- User watcher list
Client Software
Server Roles
Both editions of the server software can be installed into several disctict roles:
- Home Server
- Director
- Access Proxy
- Branch Office Proxy
- Application Proxy
Home Server
This server role is designed to host data for the users. The user's data is stored in SQL. The server stores each user's list of contacts and watchers. The contact list is the list of users the end user has added to client software in order to facilitate the sending of IM's and for the monitoring the presence. The watcher list is the list of other users that have added this user to their contact list. mahdi raeesi 00989153119754
Director
This optional server role is designed to be a kind of traffic cop when you have more than one Home Server role deployed or when you are setting up for remote users to connect to the Home Server. This server does not host any of the user's data, but knows which server each user is homed on, and can therefore redirect or proxy the request.
Access Proxy
This server role is required to allow remote SIP clients to connect from the internet. This server role would be traditionally deployed in a DMZ network. The server's job would be to scan the SIP traffic and only allow communication that the server had been configured to allow to traverse to the internal network. The traffic would be sent either directly to the internal Home Server or to a Director that would send the traffic to the appropriate home server, based on the user the message was destined to.
Branch Office Proxy
This role is used to aggregate connection from a branch office across a single Transport Layer Security (TLS) encrypted link, allowing many remote clients to share a single communication channel.
Application Proxy
This server role is designed to allow 3rd party developers to leverage the Live Communications Server SIP stack with a custom code running on top of it. This allows 3rd parties to make a gateway server that could be used to communicate with a PBX or other internal telephoney infrastructure without having to create a fully functioning SIP stack.