#1, I would recommend MS Office "Communicator" as a client to Live Communications Server 2005 SP1.
We have deployed this, following participation in its BETA.
Among all of the features that one would expect to be supported, is very tight "Advanced Presence" it reads public free/busy; provides for integration to virtual PBX Systems - as with a VOIP solution, and above all - it's encrypted. We use our own CA and place all communications in a wrapper that is securely published. Automatic settings detection for external systems is provided for by these means - the host being tls.<domainname.com>:443
//Read, protocoal, domain, port//
Finally, native integration of the SIP client's Advanced Presence awareness and Windows Sharepoint Technologies are also supported - you can create some very powerful operating environments in this way - using XML and some of the simplest dev tools I've seen to accomplish some very powerful solutions.
*The old NM collab stack is still use, so be sure to have a fully UPnP compliant NAT solution at the edge to support remote T.120 dependent features like applications and desktop sharing.
**Be prepared to support NM video, voice and data stack in similar ways - 1720, 1721, etc... to whatever gateway you will use, or individual clients [yeah, I know, that part bites...]
***The entire BETA community I saw was livid over that one....favoring instead the connection methods used in Live Meeting and MSN Messenger over NetMeeting's old stack. We built a stack rule around this and added client sets and also our MTU/MCU's by bolting it to an old implementation of Exchange Conferencing Server - it works, but it wasn't pretty...
****If you have ISA Server 2000/2004 this is a non-issue as it is a breeze to support a gateway for any MCU/MTU, or individual clients.
|