Official Microsoft Lync Clients for WP7, Android, iPhone and iPad are here!


As of today, all of the official Microsoft Lync Mobile clients are now available.  Now what?  Well, unfortunately unless you are running Lync on Office 365 you can not just load them and login.  First, you need to install the latest update for Lync Server, Cumulative Update 4 (CU4), which you can download here.

Second, you need to install and configure the mobility and autodiscover service, which will also entail getting a new SAN for your Lync public certificate and external DNS changes for outside access.  Jeff Schertz has a very comprehensive and easy to follow installation guide here.

After that is complete, you are ready to get the clients:

Windows Phone 7:

Android :



At the next Dallas / Fort Worth Unified Communications User Group meeting in January, we will discuss the mobility service installation and have all versions of the new mobile client available to play with.  I hope to see you there.  

Thanks, Tom


Publishing a recording from another PC in Lync Recording Manager

Occasionally, someone else may record a Lync Meeting for you, or you may need to move meetings from one PC to another and you later want to publish the file as .WMV file (and don’t have the original one that was made automatically) or you need to change the options in what is included in the .WMV.

However, just moving the file to the “Lync Recordings” folder on your PC doesn’t cause it to automatically show up in Lync Recording Manager, and there is no intuitive way to “import” it into your recordings.

Fortunately, there is a way to get it to show up.  For this to work:

  1. Lync Recording Manager *must* be closed
  2. You must copy the recording folder to your “Lync Recordings” folder (if doesn’t work if the folder is in any other location)

Now do the following:

  1. Browse in Explorer to your recording the Lync Recordings folder ( in Windows 7 “x:\Users\userID\Lync Recordings\RecordingName”, in Windows XP “x:\Documents and Setttings\userID\Lync Recordings\RecordingName” )
  2. Doubleclick “RecordingData.frd”
  3. Windows won’t have an application associated with .frd extension and won’t know how to open it.  Pick  “Select the program from a list” ,  and then browse for “x:\Program Files\Microsoft Lync\ocpubmgr.exe”
  4. Lync Recording Manager will open.  Click on the “Lync Recordings” Tab and your recording will now be in the list.

You can now publish the recording (and change the options for publishing).



Lync 2010 HTML URL Protocols for HREF tags

As a follow up to my previous post about the syntax to initiate an IM or phone call from web page using standard HTML, I’ve gotten some questions on how to do other things in Lync via HTML like video and PC to PC calls.  Not seeing any documentation on it, I used a utility called URLProtocolView to see what other commands besides tel: , sip:, and im: that were available to Lync (and Live Meeting) in a web browser –

callto Enabled URL:CallTo Protocol Microsoft Lync 2010
conf Enabled URL:Conf Protocol Microsoft Lync 2010
im Enabled URL:IM Protocol Microsoft Lync 2010
sip Enabled URL:Sip Protocol Microsoft Lync 2010
sips Enabled URL:Sips Protocol Microsoft Lync 2010
tel Enabled URL:Tel Protocol Microsoft Lync 2010
meet Enabled URL:Meet Protocol Microsoft Office Live Meeting 2007

Aside from the ones that I knew about, there is also callto: and conf:

What I also figured out from URLProtocolView is that when these are invoked in a HREF tag in a web browser, the web browser launches communicator.exe with a command line argument of what is contained in the tag.  Searching for the communicator.exe command line arguments got me this for Lync 2010 on TechNet  :

Lync 2010 Command-Line Parameters

Extension Format of Data Action
tel: tel URI Opens the Conversation window for an audio call but does not dial the specified number.
callto: tel:, sip:, or typeable tel URI Opens the Conversation window for an audio call but does not dial the specified number.
sip: SIP URI Opens the Conversation window with the specified SIP Uniform Resource Identifier (URI) in the participant list.
Sips: SIP URI If Lync 2010 is configured to use the Transport Layer Security (TLS) protocol, functions exactly like sip:. If TLS is not being used, displays a dialog box informing the user that a higher level of security is required.
conf: SIP URI of conference to join If URI is self, instantiates the focus and brings up roster-only view. Otherwise, brings up roster view but does not send INVITE.
im: SIP URI Displays an instant messaging (IM)-only Conversation window with the SIP URI. Accepts multiple SIP URIs specified inside angle brackets (<>) without any separator.

The following table provides examples of these command-line parameters.

Command-Line Parameter Examples

Instance Results
Tel:+14255550101 Opens a phone-only view with +14255550101.
Callto:tel:+ 14255550101 Opens a phone-only view with +14255550101. Opens a phone-only view with Opens a Conversation window with


Hey, that looks the same as our list of protocols available, and they give examples to boot!

 For example the behavior of callto: in this example:

<a href=””>Click Here to Call</a>

Results in the contact to be pulled up like this:

 but the call isn’t made, you still need to click to call or open the IM panel, which is not exactly what we were looking for but still useful.

So, given the information we have here it doesn’t look possible to do an automatic video call using this method, put putting in a SIP URI and then another click to pick the modality is possible.



ACE for Lync and CUCILync vs SIP Trunking : Don’t use a typewriter as your keyboard

Chris Norman has posted what should be regarded as the definitive blog post and discussion on Avaya ACE.  I’ve talked about this and CuciLync in user group discussions and I always advise against it.

I wanted to highlight a  couple of comments I made in the thread.  Joe Schurman from Avaya contends multiple times that companies cannot throw away their investments in their Avaya infrastructure and, not should, but *have to* use ACE, to which I respond:

“Let’s go back a few years to the 80s. Let’s trade “UC” for “PC”.

I have a large amount of expensive typewriters. Best of breed. I’m putting in new computers, but my typewriter company tells me instead of wasting money on buying keyboards, I should buy a special cable to connect my typewriter to my computer to protect my investment in Typewriters. But, the typewriter doesn’t have all the keys that a computer keyboard does, so I lose the ability to do everything I could with the computer.

This is the logic here.

Instead of putting the computer and typewriter side by side for those pesky triplicate forms and labels and stuff that there were no solutions or replacement for yet (and trim down the number of typewriters to only people who needed them for those tasks) – you go with the “better together” approach?

P.S. My typewriter company is working as hard as it can to get into the PC business. “


“First, I didn’t mean to make my analogy seem hardware centric. Only that the computer (Lync) can do many many things and well (IM/Presence/Voice/Video/Conferencing/Collaboration/Etc.) and the Typewriter (Avaya) could do one (Voice).

Even though you have dismissed it several times, one strategy of co-existence is SIP trunking, like putting the computer next to the typewriter. When you eliminate the need for the typewriter, you take it away. ROI in part comes from all of the additional features the computer gave you that you didn’t have before or paid for in other higher ways (plus not having to pay annual maintenance and upgrades on the typewriter when it’s gone).”

While Joe makes a very passionate plea to try to fully leverage your Avaya investment, what he completely disregards is fully leveraging your investment in Lync, which ACE kills as noted by Chris Norman:

“Greyed out icons adding to end user confusion

Escalation to a voice call requires the use of add on to the bottom of the window.

No escalation path to video or desktop sharing from the conversation window since Avaya recommended configuration is to only license STD Cal and they have been removed through policy settings.

You can only accept or decline an inbound call there is no way to redirect to another phone or voicemail

You cannot use Lync audio conferencing using ACE with Lync AVMUC. This experience is totally broken.

No conference controls when in an Avaya Audio conference from Lync with ACE

No contact card integration or broader Office integration for click to call, your limited to the ACE plugin for Outlook and what it offers.

No way to launch directly into a video or sharing session from right clicking the client.

No visual voicemail and no seamless integration into Exchange UM or even Avaya MM platform

No remote access capability

Scheduled conferencing, I saw no click to conference capability only very basic and rudimentary telephony capabilities so I do not understand where you think this advanced voice features are in the ACE integration to Lync.”

There is a point in an asset’s life where it has completely depreciated in value.  Then you look around, you find a replacement for that asset that provides 10x more functionality, is less expensive, and has a lower on-going costs.  If you instead decide to put more money into the depreciated asset, there is a technical name for that, it’s called “throwing good money after bad”.

Avaya Voice is not more magical than Lync Voice.  If there is some telephony feature as a business need, then keep those phones until there is a Lync solution.  However, Lync gives you far more features as a unified communications platform and it’s Voice features are suitable for most businesses.

My advice to everyone is this: SIP trunk the systems together.  It is possible through dial plan manipulation to give the Lync phone numbers the same as the desk phones – use access code plus the real number in the PBX to point to Lync, then you can forward the phone (or sim ring) to the Lync station (or the reverse, point everything to Lync and allow sim ring to the desk phone).  Downside -this doesn’t give you the “in a call” presence indication if you are talking on the PBX phone.  Then you can start eliminating legacy desk phones or replacing them with native Lync phones, until your down to the people who absolutely need them – like the last people who had a typewriter in the office.

November 3rd DFW IT Professionals Meeting – Lync Overview

I’ll be presenting at 6:00 PM Nov. 3rd at Microsoft in Las Colinas for the DFW IT Professionals Users Group.  Here is a description of the session:

Come see how Lync can improve communications in your organization and give new tools for interacting with your peers, partners and customers including instant messaging, desktop sharing, voice, video and collaboration all from a single client that is integrated with the rest of the Microsoft Office suite. We’ll demonstrate Lync including communicating with Federated partners and show it’s native integration with other Microsoft products such as SharePoint and Outlook.

Click here to RSVP:


Thanks to everyone for coming out.  Here is the slide deck from last night:

 Lync 2010 DFW IT Pro

For those who want to test drive Lync in their lab (or at home), here are a couple of resources.  First, you can download all the software that you need here: 

For a good video tutorial of how to install, check out this site:



DFW Unified Communications User Group October Meeting

Join us for our October Meeting on October 27th at the Microsoft Campus in
Las Colinas at 6:00 PM.This month meeting will topic will be on the Lync
Edge Server with guest speaker Microsoft Lync MVP Randy Wintle.

7000 North Highway
Las Colinas Campus
Irving, TX 75039

Update – Video of the Presentation is here:

Please join our LinkedIn Group as well to get the latest information and interact with other


This month’s meeting is graciously being sponsored by NETSCOUT.

Lync *is* Enterprise Ready

Join the DFW Unified Communications User Group tonight (September 22nd) for the our September monthly 4th Thursday meeting.  Our topic this month is “Lync Integration and Interoperability”.  For those interested, I’ll also be happy to give my personal debunking of the Network World article point by point.

Click here to Register Today!



%d bloggers like this: