“Lync Server 2010 SDK”和“Lync Server 2010 SDK”之间有什么区别？ /“UCMA 3.0 SDK” / 和 UCC API？
我正在寻找Lync 2010的客户端和服务器端API。但我发现很多可以开发的API。 有人知道它们之间有什么区别吗？请帮忙
Microsoft Lync Server 2010 SDK http://www.microsoft.com/downloads/en/details.aspx?FamilyID=58ccf6fd-31db-4f15-bafb-c5ef28afc5fc
微软统一通信托管 API 3.0 软件开发 套件 http://www.microsoft.com/downloads/en/详细信息.aspx?FamilyID=4493BAAB-6214-4770-8CF9-69C813E8A9FA
Microsoft 统一通信客户端 API SDK
http://www.microsoft.com/downloads /en/details.aspx?FamilyID=82c468da-3294-4ca9-bbcc-d455cfd06af2
I'm looking for the client side and server side API for Lync 2010. But I found many API that can be able to develop. Anyone what are difference between all of them? Please help
Microsoft Lync Server 2010 SDK http://www.microsoft.com/downloads/en/details.aspx?FamilyID=58ccf6fd-31db-4f15-bafb-c5ef28afc5fc
Microsoft Unified Communications Managed API 3.0 Software Development
Kit
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=4493BAAB-6214-4770-8CF9-69C813E8A9FAMicrosoft Unified Communications Client API SDK
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=82c468da-3294-4ca9-bbcc-d455cfd06af2
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Lync 2010 SDK 是Lync 2010 的最新客户端 SDK（不适用于以前的版本）。它是一个完全托管（即.Net）API，允许您构建自动运行 Lync 实例来执行任务的应用程序，例如显示状态并从 LoB 应用程序启动对话（自动化模式）。它还允许您构建自己的自定义客户端以完全替换 Lync UI（UI 抑制模式）。
统一通信托管 API 3.0 (UCMA) 是 Lync 2010 的最新服务器端 SDK（不适用于以前的版本） - 它也是一个完全托管的 API，允许您构建作为端点注册到 Lync 的应用程序。这对于构建机器人非常有用，例如，当股票价格超过特定阈值时向人们发送即时消息的股票行情机器人。您还可以用它构建呼叫路由和 IVR（交互式语音应答）应用程序，并且它可以使用 Windows Workflow Foundation 来减少您必须编写的代码量。
Lync Server 2010 SDK是另一个服务器端 SDK，但它不是按照 UCMA 创建端点，而是允许您编写插入前端服务器的过滤器。过滤器允许您在 SIP 流量通过服务器时对其进行检查，因此它对于构建归档解决方案等非常有用。
统一通信客户端 API (UCCA) 是一个客户端 API，允许您构建自定义端点 - 例如 Lync 客户端替代品。最好避免这种情况，因为它是基于 COM 的，因此您需要编写更多代码，并且需要非常小心内存泄漏。建议在 UI 抑制模式下使用 Lync SDK，而不是此 API。不过，它确实有一个好处，那就是它可以与 Communicator 2007、Communicator 2007 R2 和 Lync 配合使用。
如果您正在针对 Lync 进行开发且没有以前的版本，则 Lync SDK（客户端）和 UCMA 3.0（服务器）应该能够满足您的需求。否则，这篇文章此处更详细地讨论了以前的 SDK
编辑：我在博客文章
Lync 2010 SDK is the latest Client-side SDK for Lync 2010 (doesn't work against previous versions). Its a fully managed (i.e. .Net) API, and allows you to build apps that automate the running instance of Lync to perform tasks, e.g. display presence and start a conversation from your LoB app (Automation mode). It also allows you to build your own custom clients to completely replace the Lync UI (UI Supression mode).
Unified Communications Managed API 3.0 (UCMA) is the latest server-side SDK for Lync 2010 (doesn't work against previous versions) - its also a fully managed API, and allows you to build applications that register to Lync as endpoints. This is useful for building bots, for example, a stock ticker bot that IMs people when a stock price goes over a certain threshold. You can also build call routing and IVR (interactive voice response) apps with this, and it can use Windows Workflow Foundation to reduce the amount of code you have to write.
Lync Server 2010 SDK is another server-side SDK, but rather than creating endpoints as per UCMA, this allows you to write filters that plug in to a Front End server. A filter allows you to inspect SIP traffic as it passes through the server, so its useful for building e.g. archiving solutions.
Unified Communications Client API (UCCA) is a client side API that allows you to build custom endpoints - e.g. Lync client replacements. This is best avoided, as it is COM based, so you have a lot more code to write, and need to be very careful about memory leaks. Its recommended to use Lync SDK in UI Supression mode, instead of this API. One benefit it does have though, is it works against Communicator 2007, Communicator 2007 R2 and Lync.
If you're developing against Lync and no previous versions, then Lync SDK (client) and UCMA 3.0 (server) should give you what you need. Otherwise, this article here talks about the previous SDKs in a bit more detail
Edit: I've expanded on this in a blog post
对我来说，统一通信客户端 API 和 UCMA 之间的主要区别在于 UCC 支持摘要身份验证，这就是为什么可以为基于 asterisk 的 Linux 构建 sip/rtp 客户端。
The main difference for me between Unified Communications Client API and UCMA was that UCC supports digest auth and that's why it is possible to build sip/rtp client for linux based asterisk.