整合內部部署整合通訊和 Lync Server 2013 的指導方針Guidelines for integrating on-premises Unified Messaging and Lync Server 2013

 

主題上次修改日期: 2012-09-25Topic Last Modified: 2012-09-25

以下是部署企業語音時所需考慮的指導方針和最佳作法:The following are guidelines and best practices to consider when you deploy Enterprise Voice:

重要

只有在您同時使用 UCMA 4 時,Exchange 整合通訊 (UM) 才會支援 IPv6。Exchange Unified Messaging (UM) supports IPv6 only if you are also using UCMA 4.

  • 部署 Lync Server 2013 Standard Edition Server 或前端集區。Deploy a Lync Server 2013 Standard Edition server or a Front End pool. 如需安裝的詳細資訊,請參閱部署檔中的 部署 Lync Server 2013For details about installation, see Deploying Lync Server 2013 in the Deployment documentation.

  • 與 Exchange 系統管理員合作,確認每一個人將要執行的工作,以確保能夠順暢、成功地整合。Work with Exchange administrators to confirm which tasks each of you will perform to assure a smooth and successful integration.

  • 在您要為 Exchange UM 啟用使用者的每個 Exchange 整合通訊 (UM) 樹系中,部署 Exchange 信箱伺服器角色。Deploy the Exchange Mailbox server roles in each Exchange Unified Messaging (UM) forest where you want to enable users for Exchange UM. 如需安裝 Exchange 伺服器角色的詳細資訊,請參閱 Microsoft Exchange Server 2013 檔。For details about installing Exchange server roles, see the Microsoft Exchange Server 2013 documentation.

    重要

    安裝 Exchange 整合通訊 (UM) 時,會將其設定為使用自我簽署憑證。When Exchange Unified Messaging (UM) is installed, it is configured to use a self-signed certificate.
    不過,自我簽署憑證不會讓 Lync Server 2013 和 Exchange UM 彼此信任,這就是為何必須從兩部伺服器信任的憑證授權單位單位要求個別憑證。The self-signed certificate, however, does not enable Lync Server 2013 and Exchange UM to trust each other, which is why it is necessary to request a separate certificate from a certification authority that both servers trust.

  • 如果 Lync Server 2013 和 Exchange UM 安裝在不同的樹系中,請將每個 Exchange 樹系設定為信任 Lync Server 2013 樹系和 Lync Server 2013 樹系,以信任每個 Exchange 樹系。If Lync Server 2013 and Exchange UM are installed in different forests, configure each Exchange forest to trust the Lync Server 2013 forest and the Lync Server 2013 forest to trust each Exchange forest. 此外,您也可以在 Lync Server 2013 樹系中的使用者物件上設定使用者的 Exchange UM 設定,通常是使用腳本或跨樹系工具(例如身分識別生命週期管理員 (ILM) )。Also, set the users’ Exchange UM settings on the user objects in the Lync Server 2013 forest, typically by using a script or a cross-forest tool, such as Identity Lifecycle Manager (ILM).

  • 必要時,安裝 Exchange 管理主控台以便管理 Unified Messaging 伺服器。If necessary, install the Exchange Management Console to manage your Unified Messaging servers.

  • 取得 Outlook Voice Access 和自動語音應答的有效電話號碼。Obtain valid phone numbers for Outlook Voice Access and auto attendant.

  • 如果您使用的 Exchange UM 版本低於 Microsoft Exchange Server 2010 Service Pack 1 (SP1) ,則為 Exchange UM SIP URI 撥號對應表和 Enterprise Voice 撥號對應表的座標名稱。If you are using a version of Exchange UM earlier than Microsoft Exchange Server 2010 Service Pack 1 (SP1), coordinate names for Exchange UM SIP URI dial plans and Enterprise Voice dial plans.

部署重複的 Exchange UM 伺服器Deploying Redundant Exchange UM Servers

重要

建議您為組織設定的每個 Exchange UM SIP URI 撥號對應表,至少部署兩部執行 Exchange UM 服務的伺服器。We recommend that you deploy a minimum of two servers on which Exchange UM services is running for each Exchange UM SIP URI dial plan that you configure for your organization. 除了提供擴充的容量之外,部署冗余伺服器也可提供高可用性。In addition to providing expanded capacity, deploying redundant servers provides high availability. 當伺服器失敗時,Lync Server 2013 可以設定成容錯移轉至另一部伺服器。In the event of an server failure, Lync Server 2013 can be configured to fail over to another server.

以下範例設定可提供 Exchange UM 恢復能力。The following example configurations provide Exchange UM resiliency.

範例 1:Exchange UM 恢復能力Example 1: Exchange UM Resiliency

Exchange UM 範例1Exchange UM Example 1

在範例 1 中,Tukwila 資料中心內的 Exchange UM 伺服器 1 和伺服器 2 均已啟用;Dublin 資料中心內的 Exchange UM 伺服器 3 和伺服器 4 均已啟用。In Example 1, Exchange UM servers 1 and 2 are enabled in the Tukwila data center, and Exchange UM servers 3 and 4 are enabled in the Dublin data center. 在 Tukwila 中發生 Exchange UM 中斷的情況時,網域名稱系統 (DNS) 伺服器1和2的記錄應該設定為分別指向 servers 3 和4。In the event of an Exchange UM outage in Tukwila, the Domain Name System (DNS) A records for servers 1 and 2 should be configured to point to servers 3 and 4, respectively. 在都柏林中發生 Exchange UM 中斷的情況時,伺服器3和4的 DNS A 記錄應該設定為分別指向 servers 1 和2。In the event of an Exchange UM outage in Dublin, the DNS A records for servers 3 and 4 should be configured to point to servers 1 and 2, respectively.

注意

在範例 1 中,您還需要在每部 Exchange UM 伺服器上指派以下任一憑證:For Example 1, you should also assign one of following certificate on each Exchange UM server:

  • 在主體替代名稱 (SAN) 中使用含萬用字元的憑證。Use a certificate with a wildcard in the Subject Alternative Name (SAN).

  • 將 SAN 中每四個 Exchange UM 伺服器的完整功能變數名稱 (FQDN) 放入該功能變數名稱。Put the fully qualified domain name (FQDN) of each of the four Exchange UM servers in the SAN.

範例 2:Exchange UM 恢復能力Example 2: Exchange UM Resiliency

Exchange UM 範例2Exchange UM Example 2

在範例 2 中,於正常運作情況下,Tukwila 資料中心內的 Exchange UM 伺服器 1 和伺服器 2 均已啟用;Dublin 資料中心內的 Exchange UM 伺服器 3 和伺服器 4 均已啟用。這四部伺服器均包含在 Tukwila 使用者的 SIP URI 撥號對應表中,不過伺服器 3 和 4 均已停用。當 Tukwila 的 Exchange UM 伺服器發生如停止運作等的情況時,應停用 Exchange UM 伺服器 1 和 2 並啟用 Exchange UM 伺服器 3 和 4,以將 Tukwila Exchange UM 的流量路由傳送至 Dublin 的伺服器。In Example 2, under ordinary operating conditions Exchange UM servers 1 and 2 are enabled in the Tukwila data center, and Exchange UM servers 3 and 4 are enabled in the Dublin data center. All four servers are included in the Tukwila users' SIP URI dial plan; however, servers 3 and 4 are disabled. In the event of an Exchange UM outage in Tukwila, for example, Exchange UM servers 1 and 2 should be disabled and Exchange UM servers 3 and 4 should be enabled so the Tukwila Exchange UM traffic will be routed to the servers in Dublin.

如需如何啟用或停用 Exchange 2013 整合通訊的詳細資訊,請參閱「整合 Exchange 2013 UM 搭配 Lync Server」 https://go.microsoft.com/fwlink/p/?LinkId=265372For details about how to enable or disable Unified Messaging on Exchange 2013, see “Integrate Exchange 2013 UM with Lync Server” at https://go.microsoft.com/fwlink/p/?LinkId=265372.

如需如何在 Microsoft Exchange Server 2010 上啟用或停用整合通訊的詳細資訊,請參閱:For details about how to enable or disable Unified Messaging on Microsoft Exchange Server 2010, see: