Incidentally, you might have issues with the alternate caller ID not being sent.

I originally attempted this several years ago, and the Lync client (or server.can't recall), didn't deal with the *67 so well. Let me know if this doesn't work on an older platform. I've tested this using the latest Skype for Business server and client (as of August 2015), and the 5.4 firmware on a VVX 600 as well as a CX600 deskphone. First, you'll need a normalization rule in your dial plan that will accept the caller ID block code. Here's a simplified example using the North American dialplan. Also, when someone types *67 and a number, it normalizes without showing the parameter suffix, which looks nicer to the user. This method is much nicer as it conforms to the standard RFCs and is fully E.164 compliant.

So, after a bit of trial and error, I managed to make it work. Kevin Bingham from Cerium Networks suggested it might work by adding a custom parameter suffix, such as callerid=blocked (custom parameters are allowed by RFC3966). My earlier version of this blog post simply put the *67 in front of the number and sent it through the system, stripping the *67 just before sending off to the PSTN. Thankfully, things have improved recently so that the Skype for Business client will happily accept the * (or # if you want). It threw up the virtual equivalent of giving me the finger and refused to work, so I had to go about it differently. When I first tried this, I wanted to use *67 in my dialplan, but the Lync client didn't like the * so much. Since the caller ID block code you use on the PSTN should be unique, you can incorporate that into your dialplan, routes and trunk translation rules.

For calls to use that route, you will need some unique signifier that would not occur in normal day-to-day dialing. Since the caller ID blocking feature is done at the route level, you will need to have a separate route for calls with an alternate caller ID. In Lync/Skype for Business, you can replicate this functionality but it takes some work. So, a user could dial *6715552224444 and their caller ID would be blocked for that call. In most North American markets, this code is usually *67. Easy enough, right? But what if administrators want to give users the ability to selectively block caller ID at the individual call level? When on the traditional PSTN, users in most places can enter a code prior to dialing the number if they want to block their caller ID.

Skype for business block