Greetings all. It's been a while since the last real blog update. This past summer was quite busy both work-wise and life-wise, so the blog posts fell by the wayside. Consider it a summer hiatus, like TV. As fall brings a new TV season, it also brings new blog posts, so read on....
If you've used trunk translation rules in Lync (and if you've followed my Enterprise Voice Best Practices series, you should be), you may have discovered a very annoying omission in the Voice Route Test Case window.
Once you've created all your normalization rules, its a good idea to validate your dial plan and voice policies by running some numbers through the Voice Routing Test Case window. The voice routing test case dialog box can be accessed from any of the tabs in the Voice Routing section of the Lync Control Panel. Just click the little downwards facing chevron to expand the window. The window will stay active no matter which tab you click on, which can be handy for testing changes as you go.
I usually find it best to select the checkbox beside Populate from user and selecting a valid Enterprise Voice-enabled user, so you can be sure you're testing the right dial plan and voice policy.
You'll notice that when I plug in a test 10-digit local phone number for a Vancouver based Lync deployment, it shows that it applies the correct normalization rule, picks the correct usage and the route. If you've used the http://almourasiloun2.blogspot.com /2011/05/major-upgrade-to-dialing-rule-optimizer.html">Dialing Rule Optimizer or followed my http://almourasiloun2.blogspot.com /2011/01/enterprise-voice-best-practices-in-lync_21.html">best practices for creating routes and trunk translation rules, a trunk translation rule should strip the +1 from the number before sending it to the PSTN. However, the test case results do not show the trunk translation rule that would be applied to the number.
The omission of the trunk translation rule from the results window can lead to the mistaken belief that the number isn't being sent out correctly. It can also lead to general confusion, heart palpitations, sweaty palms and mild to severe incontinence. I believe this is a serious omission that limits the usefulness of this otherwise great tool.
Normally, the only way to verify the number is being formatted correctly once it leaves Lync is to use the Lync Logging Tool or IP gateway logs (if you've got one) to sift through until you find the information. Either that or if the call completes successfully, that's a pretty good indication things are working as expected. However, if you happen to have a Polycom CX500/600/700/3000 series Lync phone or Aastra Lync phone, you can easily validate what number is sent to the PSTN.
When you dial a local number, the normalized number will be shown first (which will always start with +1), but the actual number sent to the PSTN will be shown in a smaller size below. The first screengrab shows what it looks like when you dial a local number that should have the +1 stripped out. The second shows a long distance number that should only strip the +.
 |
| Local Call |
 |
| Long Distance Call |
If you happen to have a Polycom or Aastra Lync deskphone, this is a great way to validate your trunk translation rules. Hopefully, Microsoft will update the Voice Test Case app to include trunk translation rules in the future.
Many thanks to Tim from Rolling Thunder, who pointed this out to me during a discussion about trunk translation rules this morning.
0 komentar:
Posting Komentar