It took me a little while to fully understand the in’s and out’s of a voice policy. Finally one day it clicked. Here’s a little post to recap how it works.
So what is a Voice Policy?
Well, a voice policy is really 2 different parts (some may say 3 but I see it as 2).
The first part is what you would think a Voice Policy is, that is, what features are you allowed to use.
The second part is where you allow (or disallow) a user to call (long distance, local, …..) and what route (gateway) do you use to make the call.
To do this you make a PSTN usage then add a route to the usage. Here’s how it looks blank.
We will start off by clicking “New”. I gave the usage a name of “Test Usage” (it should be a meaningful name but this is just an example).
After you give it a name you need to give the Usage a Route. Here’s where things for me got confusing until i ran through it a few time. As you can see in the below I gave the route a name of “Test Route” (again this should be a meaningful name but this is just a test)
In the section above called “Build a pattern to Match” i simply put +1703 and hit the add button (i’ll explain why i put in the +1703 below). The next section called “Associated trunks” i clicked Add and added a Trunk that has been published in topology. The next couple of slides will show you what happens when you keep clicking OK to save your work until you’re back at the first screen.
In the above print screen you will see a complete voice policy. So what did we just accomplish. Well, if a user would be assigned this policy, that user is enabled for Call forwarding, delegation, simultaneous ring, team call, and PSTN reroute. If they were to make a call to a +1703 phone number it would use the gateway at 10.140.143.230
What if the user assigned to this policy wants to call a number that doesn’t begin with +1703? The user can’t make that call, they are only permitted to call +1703 numbers. This is a way of controlling where your users can call (Local/Long/Distance….). It’s also a way to get around long distance charges should you have gateways in various geographical location.
Example: Lets say I want to call Washington state and i know i have a gateway in that state. Well i could make another PSTN usage (following the same steps as in the above) and where I put in the +1703 and told Lync to use the 10.140.143.230 gateway, I could says for the Washington State Area Code, use the IP of the gateway in Washington State, thus keeping the call internal to my companies network until it reaches Washington State.
Another question you may ask is, well, what if a user wants to forward calls to a +1301 phone number (if you recall in the Voice Feature section, the user is enabled for this feature)? The answer is, they will not be able to as they are only a permitted to call +1703 phone numbers.