I’ve been working with some customers recently who are migrating to LCS 2005 and, in the process, I’ve had to do quite a bit of research to answer their various challenges about migration, provisioning, connecting to the client, and deploying the SIP to PSTN gateway.
So here are some of the resources and tools that I’ve been working with to help you if you come across any of the same challenges when you migrate:
LCS 2005 Planning guide:
Exchange IM customers can directly migrate to LCS 2005. The scripts were released recently as part of the LCS 2005 resource kit – “LCS 2005 and ISA 2000 and as Communicator supports most of the same interfaces as Messenger, so iyou can expose the API’s. look here:
LCS Capacity Planning Toolkit to help with the question of what will be the additional overhead on the network as a result of additional presence info once you migrate to Office 2003
If you’re planning on implrementing LCS with ISA server, you can have a look at Live Communications Server 2005 Access Proxy and Director document, or if you intend to use ISA 2004 for firewalls in conjunction with VPN there is the Configuring Microsoft Office Live Communications Server 2003 Standard Edition with ISA Server 2000. This document was actually written for Live Communications Server 2003, many of the concepts apply to Live Communications Server 2005.”
Other documentation for LCS 2005 : which steps through decommissioning and deployment steps that must be taken in order to preserve LCS functionality for users homed on Standard Edition server before upgrading to Enterprise Edition.
And finally, something that we’ve been playing around with in the Office: Live Communications Server 2005 Deploying a SIP/PSTN Gateway This document describes how to deploy a SIP/PSTN gateway for Live Communications Server 2005 and how the SIP address is generated. It works like this:
Windows Messenger will generate a sip address of sip:<phonenumber>@<yourdomain>,uri=phone
<phonenumber> is whatever you enter in the phone dialer
<yourdomain> is whatever is the domain element of your logged in SIP address e.g. if you sign in as email@example.com then it will be abc.com. We’re having a bit of fun with these different scenarios playing with Communicator and seeing just how much it will do!