The release candidate for Microsoft Lync Server 2010 (formerly known as Office Communications Server and/or Speech Server) was just made available for download. From the site:
Microsoft Lync Server 2010 now delivers complete presence, instant messaging, conferencing and enterprise voice capabilities through a single, easy-to-use interface that is consistent across PC, browser, and mobile device. Administrators benefit from a single, consistent management infrastructure, new capabilities to increase availability, and interoperability with existing systems.
In coordination with this release, also available for download is the Microsoft Unified Communications Managed API 3.0 SDK (UCMA 3.0). This is the client-side .NET managed API enabling integration and extension of Lync experiences.
This is all very exciting because I would like to start building rich voice and instant messaging application with tight integration to the Microsoft technology stack and with fewer third-party dependencies (e.g. Voxeo, Nuance, IMified, etc).
However, what I am still unclear on is this: Is Microsoft Lync Server 2010 a good fit for public-facing Web sites and applications? Or is really intended for use primarily within the corporate firewall, for mostly internal applications?
I guess what I need to know is this: Can Microsoft Lync Server 2010 serve as both an internal and public-facing hosting provider for VoiceXML and IM-based applications, and scale to meet the needs of a large public-facing site with thousands or even millions of users?
Am I totally misunderstanding what Lync can/cannot, and should/should not do?