[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-08

As in previous versions, Communications Server requires all dial strings to be normalized to E.164 format for the purpose of performing reverse number lookup (RNL) as part of call routing. Downstream components such as gateways, PBXs, or SIP trunks, however, may require numbers in local dialing formats. As a result, in Office Communications Server 2007 R2, it was sometimes necessary to individually configure downstream components, or even reroute calls, in order to accept E.164 dial strings.

Communications Server 2010, however, enables you to create one or more rules that assist in manipulating the Request URI E.164 format prior to routing it to the gateway. For example, you could write a rule to remove +44 from the head of a dial string and replace it with 0144 before it is routed to a gateway.