Jump to content

Live Communications Server 2005

Add links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 74.227.160.34 (talk) at 02:48, 29 February 2008. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Live Communications Server 2005 (LCS 2005) is a Microsoft instant messaging and presence server. 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 login. Once connected the clients can 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.

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

The product was released in two editions, Standard Edition and Enterprise Edition.

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.

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 would know what each user's Home Server name would be and be able to direct traffic to the appropriate home server.

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 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.

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Live_Communications_Server_2005&oldid=194813135"