Lync Server 2013 中的转换规则Translation rules in Lync Server 2013

 

上次修改的主题: 2012-10-05Topic Last Modified: 2012-10-05

Lync Server 2013 企业语音要求将所有拨号字符串正常化为 e.164 格式,以执行反向号码查找 (RNL) 。Lync Server 2013 Enterprise Voice requires that all dial strings be normalized to E.164 format for the purpose of performing reverse number lookup (RNL). 在 Microsoft Lync Server 2010 中,仅对被呼叫的号码支持转换规则。In Microsoft Lync Server 2010, translation rules are supported only for called numbers. 新增在 Microsoft Lync Server 2013 中,呼叫号码也支持转换规则。New in Microsoft Lync Server 2013, translation rules are also supported for calling numbers. “中继对等方”**(即,关联网关、专用交换机 (PBX) 或 SIP 中继)可能要求号码采用本地拨号格式。The trunk peer (that is, the associated gateway, private branch exchange (PBX), or SIP trunk) may require that numbers be in a local dialing format. 要将 E.164 格式的号码转换为本地拨号格式,可以在将其路由至中继对等方之前,定义一个或多个转换规则以处理请求 URI。To translate numbers from E.164 format to a local dialing format, you can define one or more translation rules to manipulate the request URI before you route it to the trunk peer. 例如,可以编写用于删除拨号串开头的 +44 并将其替换为 0144 的转换规则。For example, you could write a translation rule to remove +44 from the beginning of a dial string and replace it with 0144.

通过在服务器上执行出站路由转换,可以降低每个单独中继对等方上的配置要求,以便将电话号码转换为本地拨号格式。By performing outbound route translation on the server, you can reduce the configuration requirements on each individual trunk peer in order to translate phone numbers into a local dialing format. 在规划与特定中介服务器群集相关联的网关和多个网关时,使用类似的本地拨号要求对中继对等方进行分组可能非常有用。When you plan which gateways, and how many gateways, to associate with a specific Mediation Server cluster, it may be useful to group trunk peers with similar local dialing requirements. 这可减少所需的转换规则数和编写转换规则所需的时间。This can reduce the number of required translation rules and the time it takes to write them.

重要

将一个或多个转换规则与企业语音中继配置关联应用作在中继对等方上配置转换规则的替代方法。Associating one or more translation rules with an Enterprise Voice trunk configuration should be used as an alternative to configuring translation rules on the trunk peer. 如果已在中继对等方上配置转换规则,则不要将转换规则与企业语音中继配置相关联,因为这两个规则可能会发生冲突。Do not associate translation rules with an Enterprise Voice trunk configuration if you have configured translation rules on the trunk peer, because the two rules might conflict.

示例转换规则Example Translation Rules

以下示例转换规则说明了如何在服务器上开发将号码由 E.164 格式转换为适用于中继对等方的本地格式的规则。The following examples of translation rules show how you can develop rules on the server to translate numbers from E.164 format to a local format for the trunk peer.

有关如何实施转换规则的详细信息,请参阅部署文档中的 在 Lync Server 2013 中定义转换规则For details about how to implement translation rules, see Defining translation rules in Lync Server 2013 in the Deployment documentation.

说明Description 起始数字Starting Digits LengthLength 要删除的数字Digits to Remove 要添加的数字Digits to Add 匹配模式Matching Pattern TranslationTranslation 示例Example

美国常规长途拨号Conventional long-distance dialing in U.S.

(去掉“+”)(strip out the ‘+’)

+ 1+1

正好 12 位Exactly 12

11

00

^\+ (1 \ d {10}) $^\+(1\d{10})$

$1$1

+14255551010 变为 14255551010+14255551010 becomes 14255551010

美国国际长途拨号U.S. international long-distance dialing

(去掉“+”并添加 011)(strip out ‘+’ and add 011)

+

至少 11 位At least 11

11

011011

^\+ ( \d {9} \d +) $^\+(\d{9}\d+)$

011 $ 1011$1

+441235551010 变为 011441235551010+441235551010 becomes 011441235551010