Lync Enterprise Voice ; Voice Policies, Route and PSTN Usage

In the blog post about Lync Enterprise Voice ; Dial Plans and normalization we started to discuss about dial plans, how to use them and what normalization does in all this. Today we going to extend all the fun with covering Polices, routes and PSTN usage. First we dig in the topics and later we continue on the example we used in the other post.


Voice Policy
To plan the voice policies you will need for your Enterprise Voice deployment:

Customize Lync Presence Status

Within the Lync client we can set a number of default states we can use to show our presence to the audience. As you can see below:

Lync Mobile Push notifications

Lync mobile push notification are not enabled by default. I heard some doubts about how to activate it. Let me state from the implementation guide:

Push notifications, in the form of badges, icons, or alerts, can be sent to a mobile device even when the mobile application is inactive. Push notifications notify a user of events such as a new or missed IM invitation, missed calls, and voice mail. The Microsoft Lync Server 2010 Mobility Service sends the notifications to the cloud-based Microsoft Lync Server 2010 Push Notification Service, which then sends the notifications to the Apple Push Notification Service (APNS) or the Microsoft Push Notification Service (MPNS).

To configure for push notifications with Lync Server 2010 Edge Server

Lync Enterprise Voice ; Dial Plans and normalization

Dial plans and normalization. I believe this is a hot topic in Lync Enterprise voice. What is best practice? how can I configure it? What about inbound normalization?  and so on and so on…
So lets create some! We will bounce to the questions while getting along with the post.
Lets first look at what options we have when we create a dial plan.

Lync Enterprise Voice Configuration

Today I would like to discuss Lync Enterprise Voice and its configuration objects. I want to summarize the functionality of these features and will go into detail in later posts.
The subjects we need to cover with enterprise voice are the following:

• Dial Plans

User dial plan: Can be assigned to individual users, groups, or Contact objects. Voice applications can look up and use a per-user dial plan when a phone-context value of user-default is received. For the purpose of assigning a dial plan, a Contact object is treated as an individual user.
Pool dial plan: Can be created at the service level for any PSTN gateway or Registrar in your topology. To define a pool dial plan, you must specify the particular service (PSTN gateway or Registrar pool) to which the dial plan applies.

Lync Technical Requirements for Mobility

 
I was looking at the document on the web about Planning for Mobility in Lync. I want to point out the technical requirements in this documents as there need to be some changes in your environment to be done before it might work as you espect it to work.
Mobile users encounter various mobile application scenarios that require special planning. For example, a user might start using a mobile application while away from work by connecting through the 3G network, then switch to the corporate Wi-Fi network when arriving at work, and then switch back to 3G when leaving the building. You need to plan your environment to support such network transitions and guarantee a consistent user experience. This section describes the infrastructure requirements you need to meet to support mobile applications and automatic discovery of mobility resources.

Lync Dialing Rule Optimizer

I found on the world wide web a interesting tool to create dialing rules in Lync.
http://www.lyncoptimizer.com/

Originally, the Optimizer created a simple text file that you would copy and paste into Lync Powershell. It would create the phone usage, route and trunk translation rules necessary for least cost routing for a given site. If you input the name or IP address of your PSTN gateway, it would set it in the route, but if not, then the route would not be associated with a gateway. The process was not very tolerant of errors either. If you mistyped the name of the PSTN gateway, much of the script would fail. The original output got you started, but you were still left to your own devices for pretty much everything else.
With this latest release, the Optimizer will provide you with a ready-made Powershell .PS1 script that will do the following:

Deploying BitLocker / MBAM (TPM+PIN) with SCCM 2007 OSD

I was reading on technet about bitlocker and possibilities to manage this central and deploying it centrally. I was looking for possibilities to deploy it with SCCM and found on technet nice article I would like to share with you.
This blog post will give a high level overview on how to deploy BitLocker TPM+PIN with MBAM within OSD in a SCCM07 environment. This guide will also detail how to start encryption as soon as MBAM talks with the service endpoint (while still deploying the OS). The benefits of this are encryption will finish sooner and it does not wait to start encryption until the user has selected a pin. Also added is integrating Dart 7 into the process.