Lync Server 2013 的遠端呼叫控制和電話號碼正規化Remote call control and phone number normalization in Lync Server 2013

 

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

Lync 用戶端會下載電話號碼正規化規則,作為通訊錄服務的一部分 (ABS) 檔案下載。Lync clients download phone number normalization rules as part of the Address Book Service (ABS) file download. 在遠端呼叫控制案例中,通訊錄服務電話號碼正規化規則會同時套用至撥入與撥出的遠端呼叫控制電話。In remote call control scenarios, Address Book Service phone number normalization rules are applied to both incoming and outgoing remote call control calls. 有來電撥打給已啟用遠端呼叫控制的使用者時,來電者的電話號碼會先由 SIP/CSTA 閘道或專用交換機 (PBX) 正規化為 E.164 格式。For incoming calls to a remote call control-enabled user, the phone number of the caller is first normalized to E.164 format by either the SIP/CSTA gateway or private branch exchange (PBX). 當 Lync Server 2013 接收來自閘道的呼叫時,會針對來電者的 Microsoft Office Outlook 連絡人清單中的標準化號碼,或在通訊錄服務中儲存的全域通訊清單 (GAL) ,對來電者的電話號碼執行反向號碼查閱 (RNL) 。When Lync Server 2013 receives the call from the gateway, it performs reverse number lookup (RNL) on the phone number of the caller against the normalized number in the callee’s Microsoft Office Outlook Contacts list or the global address list (GAL) that is stored in the Address Book Service. 如果反向號碼查閱順利找到相符項目,則會以來電通知中的名稱識別來電者。If reverse number lookup successfully finds a match, the caller is identified by name in the incoming call notification.

對於撥出的遠端呼叫控制通話,Lync 會在將通話路由傳送至 SIP/CSTA 閘道之前,先將通訊錄服務電話號碼正規化規則套用至撥號的號碼。For outgoing remote call control calls, Lync applies the Address Book Service phone number normalization rules to the dialed number before routing the call to the SIP/CSTA gateway.

如需建立遠端呼叫控制之電話號碼正規化規則的詳細資訊,請參閱規劃檔中的 Lync Server 2013 中的撥號對應表和正常化規則For details about creating phone number normalization rules for remote call control, see Dial plans and normalization rules in Lync Server 2013 in the Planning documentation.

移轉電話號碼正規化規則Migrating Phone Number Normalization Rules

如果您要移轉先前啟用遠端呼叫控制的使用者,請參閱移轉文件中的下列主題:If you are migrating users previously enabled for remote call control, see the following topics in the Migration documentation: