Voice Routing: Normalization Rule vs. Route

Question

We're just testing some Enterprise Voice stuff within our Lync Environment but there's still one Thing not clear to me: On the specific user tab, we're able to assign a "Dial plan policy" and a "Voice policy"
In the Dial plan policy we're able to enter the normalization rules for Digit Manipulation.
In the Voice policy we can assign routes the call will take (e.g trunk).
But for example if there is a normalization rule which translates [phone] to 1111 and on the route there are just numbers allowed starting with 1, why the call will fail? In my opinion the number should be translated to 1111 right after dialing and
this should match the proper route.
Can someone describe how the callflow is working in Detail. Will it maybe check for the specific route before there is any Digit Manipulation process?
Thanks in advance

Answer 1

Typically you'd do it the other way around, you'd translate 1111 to [phone] so that it's in proper E.164 format, and you'd have your routes match that. 
What you described should work though, at a very high non-mechanical level:
A number is typed into Lync
The number is normalized by the users dial plan (typically to a standard such as E.165)
The normalized number is compared against the voice policy, which will match if it finds a route that matches that's tied to the policy through a PSTN usage.
An INVITE is sent through the trunk using the path determined. 
What kind of errors are you getting and do you get a "pass" in the Lync Control Panel -> Voice Routing -> Test Voice Routing when you enter the information?  If not, you've got a typo or misconfiguration somewhere and giving more detail
will help.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.