Hiding your Caller-ID in Lync 2013

An unintended feature for some...

There may be times (and it may be all the time) where you do not want you caller-id (CID) to be presented when making an outbound call. If you have moved to Lync 2013 or plan to move to Lync 2013 this featute may be available for you. The mayambiguity comes from your unknown - what SBC are you using and how is it configured. As of today, the IntelePeer SBC that is being used can make this happen...

To start, the Lync 2013 Server product introduced many new features including the ability to include P-Asserted-Identity history in the SIP signaling. This additional features is intended to allow the originator's ID to be masked with a new identity allowing forwarded calls to be 'authenticated' by the originating number but display to the receiving party as the forwarded user. This concept may be defined as follows (and may be found in RFC3325):

"Lync User" <sip:lyncuser@domain.com>
"Outside Caller" <sip:+14805551212@domain.com>
"My Cell" <sip:+16025551212@domain.com>

Outside caller calls Lync User who has call forwarding enabled on their phone. Ideally when the call is forwarded to the Lync user's cellular device it displays the caller ID of the Outside Caller, not the Lync User. This worked just fine in the past with SIP Trunk Providers and SBCs that supported Lync Server. However, if you have ever worked with a non-certified SIP trunk provider the call was typically denied as it appeared to be a call from the Outside Caller using the company’s SIP trunk (and that is not allowed). Using the P-Assert-Identity history these carriers would be able to recognize that the call was actually originating from the Lync User but the CID was simply being masked with the Outside Caller’s CID.

So how does this help us in hiding our CID you ask? Well, again, this depends on the SBC and how it interprets RFC3325. Currently IntelePeer and their SBCs interpret the RFC to mean mask ALL CID information. So, if this feature is enabled on the trunk, all CID is blocked and the recipient receives an incoming call that is shown as PRIVATE. This feature may or may not remain in effect but as of today it works. For your own SBCs, it may be an option to configure this as well.

Configuring Lync 2013 to block PRIVATE numbers is a simple task if you want it to be global. If you do not want it to be global, but perhaps for some users, additional voice policies, PSTN usages, and routes would need to be defined to create a one-off setup. To enable the option globally from the Lync Control Panel navigate to Voice Routing | Trunk Configuration.


What you display here will be different based off your configuration but the ideas and concepts are the same. If you only have a single trunk, the configuration may be in the Global Policy. If you have multiple trunks as shown then you would want to modify the policy(s) that apply to your trunk.

To modify the policies select it from the list and double-click (or select Edit | Show details…). Once in the policy you will see many new options; the one we are concerned with is Enable forward P-Assert-Identity data. Select the box to enable to feature and click OK to close the dialog.


You will need to commit the changes (Commit | Commit All) and then have a little patience. Once committed, the changes must be replicated to the Mediation Servers which may take a minute or two. If you want to see this change within the Event Viewer, search for Event ID 25091 which will look something like this:

Information       10/3/2012 5:32:27 AM    LS Mediation Server       25091   (1030)

Trunk configuration has changed
Trunk: 1-la01.intelepeer.com;trunk=1-la01.intelepeer.com
ByPass Enabled: False
Forward PAI Enabled: True
Forward Call History Enabled: True
Refer Supported: False
3pcc Refer Supported: False
SRTP Mode: NotSupported
Online Voice Enabled: False
RTP Latching Enabled: False

Once that Event Log has been logged, you may make an outbound call and check the results. If all the stars have aligned in your configuration, the recipient of the call will see the CID of the incoming call as PRIVATE and will probably not answer.

For further validation that the feature is enabled you may capture and inspect Lync Server Logs (IncomingAndOutgoingCall scenario). After you have captured the logs, open then in a text reader (such as notepad) and search for Privacy:id (not ms-privacy:id as that is always there). If you want to use Snooper to view the logs unfortunately this particular option is filtered and not shown so be aware – use a text viewer. Assuming the Privacy:id option is listed in the call setup things are configured as expected. If not, either the caller did not use the route you modified or the configuration has not replicated (Event ID 25091).

e911 for Lync now available from IntelePeer

IntelePeer has recently begun offering Enhanced 911 (e911) services which diretly integrate with Lync Server 2010. Enhanced 911 allows the Lync Location Information Service to query your on-prem database (LIS database) for known locations and publish that information to the 911 service. In addition, when the information has been entered manually the 911 service is aware the address has not been verified and an operator assists the process.

The e911 service is an optional service that incurs an additional fee per month. Contact your IntelePeer sales representative today and extend your Lync services to include emergency. For those that are not using IntelePeer for their voice services, consider trialing their 30-day free/no obligation service and see how you can use VoIP services for a fraction of the cost of traditional PSTN (tell them BriComp sent you!).


New Article Published on TechNet - Configuring IntelePeer with Lync Server 2010

Busy blog day! :)

Today on TechNet, Dr. Rez, another article was published written by myself around configuring IntelePeer SIP trunks with Lync Server 2010. The article is very similar to the OCS articles written last year but of course focuses on Lync Server.

Lync Server 2010 does a great job of connecting Internet SIP trunks directly especially if a Cisco ASA is involved (the 5505 is an amazing appliance). Check out the article from either my home web site or directly on TechNet here.

Exchange Connections

2011 Orlando, FL

Other than the rain in Orlando (who could have expected that, not me) Orlando is very nice this time of year. I am enjoying the location/hotel happy that my presentation went well yesterday, but a bit under-whelmed at the information presented this year. So much has happened at such a fast pace in 2010 and the beginning of 2011 yet nothing 'new' is being discussed. The cloud story is not new - in fact the idea is not new. Migrations and methods - definitely useful for those that are still on older systems (and there are a lot), but again nothing new. Rehashing the new features that have already been discussed in the products is the most relevant I suppose, in case you have not heard...but really, what we what needs to be shared is how to use the technology in an efficient manner and make sure you are already for the technology tomorrow.

Granted, I do have a slighted view but I do think the UC technology (on premise) is where the futures and cost savings of tomorrow are to be found. Reducing Telco costs using ITSP SIP trunking, enabling a remote  workforce, reducing travel expenses, all while improving time-to-market and customer/client satisfaction is exactly what Microsoft Lync has to offer.

If you are in Orlando for Exchange Connections make sure to stop at the EXC22: Enabling PSTN Communication Using the Internet and a SIP Trunk Provider with Lync Server (Tuesday, 10:15am in Tuscany B) where I will briefly discuss how to implement a SIP trunk using IntelePeer as an example.

BriComp Computers Chooses IntelePeer to Provide Next-Generation Voice Connections for Microsoft Unified Communications Platform

IntelePeer's High Quality and Rapidly Deployed SIP Trunking Services Now Enable Adoption of Microsoft's Latest UC Technology, Lync 2010

IntelePeer provides a comprehensive suite of on-demand communications and SIP trunking services that are backed by deep communications expertise and a proven Quick Start program to ensure partners' Microsoft Lync 2010 SIP trunk deployments are successful. Through its Cloud-based infrastructure, Voice Peering Network and SuperRegistry™ of more than 422 million directly peered telephone numbers, IntelePeer simplifies communications by delivering carrier-quality service over public or private Internet Protocol (IP) connections directly to Microsoft Lync. IntelePeer's patented platform provides real-time service availability that spares customers from the need to change their data service provider or existing communications equipment, eliminating the lengthy delays associated with typical service deployments.

As part of the Microsoft Technology Adoption Program (TAP) to beta test early releases, BriComp Computers, an independent IT consultant that designs and builds infrastructure for Microsoft products, has been using IntelePeer SIP trunking with the beta and now the current release candidate of Lync 2010.

"In addition to consulting, I write a blog on 'How-To' instructions for configuring Microsoft Lync 2010 for Microsoft's TechNet online resource center," said Brian Ricks, founder of BriComp Computers. "When I evaluated IntelePeer's SIP trunking solution ( www.IntelePeer.com), I was impressed by the speed of deployment, flexibility and connection quality. It's simply amazing that IntelePeer's SIP trunks work flawlessly right out-of-the-box with the beta and now the current release candidate of Microsoft Lync 2010."

"As a Microsoft Most Valuable Professional and expert in Microsoft Unified Communications, Brian Ricks' endorsement carries tremendous credibility," said Margaret Norton, general manager, enterprise for IntelePeer. "We are focused on providing the necessary tools and support to quickly and profitably roll out Microsoft Lync 2010 deployments. We tailor our approach to fit each customer's need. With minimal up-front cost and rapid turn-up, IntelePeer's SIP Trunking product delivers superior quality and reliability."

About IntelePeer
IntelePeer Inc., www.IntelePeer.com, is revolutionizing the delivery of communications, enabling carriers, service providers and enterprises to access communication services from the Cloud. Through the company's innovative, communications-as-a-service (CaaS) platform, IntelePeer AppworX™, SuperRegistry™ of more than 422 million telephone numbers and an extensive Voice Peering Network, IntelePeer provides the leading hosted platform to deliver high-quality interactive voice, video, SMS, data and other rich-media services to any wireline or wireless phone or IP connected device, worldwide. IntelePeer's solutions accelerate and simplify the transformation from legacy TDM to next-gen IP networks, enable new communications experiences that generate revenue and enhance productivity, and provide significant cost savings on telecommunication expenditures. Based in San Mateo, Calif., IntelePeer operates its own carrier-grade network, carrying more than 18 billion minutes annually, with worldwide coverage delivered through an IP and TDM peering grid with over 50 leading service provider peering partners. IntelePeer is privately held and is backed by venture capital firms VantagePoint Venture Partners, Kennet Venture Partners, NorthCap Partners and EDF Ventures.

IntelePeer, AppworX and SuperRegistry are trademarks of IntelePeer, Inc. All rights reserved worldwide. Other trademarks referenced are the property of their respective owners.

Original post copied from MSNBC.COM