TopBanner

I think the value of both Microsoft Lync and Skype have been dramatically increased by allowing connectivity between the two. I suspect other enterprise UC vendors would love to have this capability. In many ways Microsoft is doing in the real world in substantial numbers, what webRTC advocates hope to do some time in the future.

Skype is becoming a kind of multi-protocol IM/Voice/Video Client (much Like Pidgin?)

It would appear that Skype to Lync federation could be powered behind the scenes by components of what used to be marketed as “Windows Live Messenger”

Microsoft Account requirement to federate/provide connectivity Skype to Lync will mean less than all Skyper users will likely be “ready to federate” by June 2013, so those planning solutions website Skype to Lync click-to-dial strategies will want take this into consideration

For those not Live Messenger PIC Enabled, you can configure it now, so you are ready-to-roll when Skype connectivity is released mid-year (June 2013)

We’ll go over these points in detail below.

Skype Is Becoming a Multi-Protocol Communication Client

Skype is becoming a multi-protocol IM/Voice/Video communication client that is providing connectivity to various back end solutions/accounts. Skype for Windows version 6.2 is providing connectivity to:

Skype

Live Messenger

Facebook Chat

Plus Microsoft Lync on Premise and Lync Online (June 2013)

ARS Technica notes: “the Skype client now connects to both Skype and Messenger networks (and Facebook too), the networks are at present still separate, and there's no bridging between the two.”

Below is the Skype 2.6 Profile screen showing the various accounts being used by this Skype client.

Below is the Account management page:

What needs to be understood about this multi-protocol method of connecting to various services (Skype, Microsoft Account/Live Messenger, Facebook) is that both endpoints need to have shared accounts in the service to chat. For example: a Skype user (with only a Skype account setup in/associated with Skype) will not be able to chat with a Facebook user. Likewise, a Skype user will not be able to communicate to Messenger users, unless they have a Microsoft/Live Messenger Account.

Will Skype to Lync Connectivity Be Powered By Components of What Used to Be “Windows Live Messenger”? (specifically MSNP)

[NOTE: I have no inside information and there are some guesses in this section, I will highlight them so guess-work is clear from documented work.]

In the previous section we noted that typically you need shared accounts to communicate together. (you have a Facebook account associated with Skype to communicate with Facebook users, a Live Messenger account to communicate to Live Messenger users, etc) But in the case of Microsoft Lync federation you need a Microsoft Account (or a Live Messenger account) associated with a Skype user. Because of the below items I have been guessing that components of Microsoft Live Messenger network are being used to federate Skype and Lync:

Existing Skype users need to merge their Live Messenger account before communicating to Lync users

New Skype users need to associate a MSA (Microsoft Account) with their new Skype account

New Skype/Lync connectivity functionality seems to be tied to new Skype client releases, indicating that much of the “magic” is in the client?

On the Lync Server side all that needs to be done have PIC to Live Messenger configured & working and this enables Lync <-> Skype federation. (How to Enable WLM PC)

At the moment communication coming from Skype to Lync indicates JUST as if it was coming from Live Messenger

Your Skype ID doesn’t show up anywhere in Lync, You cannot search for Skype ID’s, just Live Messenger/Microsoft Accounts

Lync Contact relationships established in WLM will pass to & live on in Skype client

Below is what a Skype to Lync Instant Message federation looks like at the moment. (from Lync perspective) Microsoft has noted they will change the current Live Messenger icon/indicator to Skype indicator when Skype <-> Lync connectivity is released/completed.

While we have been guessing for some time that components of WLM network were being used, the presenters at Lync Conference took away our doubt by noting that the Skype <-> Lync federation would use a MSNP gateways to handle IM/P traffic to Lync. (MSNP is the protocol that delivers IM/P for WLM) A separate audio gateway will deliver voice to Lync. Does this mean Skype is merely using a MSNP gateway? Or are Live Messenger users largely continuing life as usual inside Skype? (I would lean toward the latter by my observations <—Note: this is a guess. The way to test this theory is to see if WLM communication to Lync capability goes away when Skype <-> Lync is officially implemented.) UPDATE 5/29/2013: It is verified that WLM communication is indicated as Skype communication now the Skype <-> Lync is officially live, which appears to verify above hunch. Click Here for more details.

We might ask: but wasn’t “Windows Live Messenger” “going away? As brand yes, as infrastructure, not necessarily. How do we know this? ARS Technica article on November 6, 2012 notes very carefully “that the Windows Live Messenger brand and client will be retired”. The article also notes that China will retain “Live Messenger” naming. (Microsoft’s wording does not make clear if the WLM client itself will survive, or just the WLM brand. It would seem that if they are not continuing to use the WLM client they would move branding to Skype though.) The same ARS article notes that while the branding is moving to Skype “Behind the scenes, the migration has been underway for some time—in the opposite direction”. Mary Jo Foley notes: “the [Skype] instant messaging back-end now uses a mix of Messenger's infrastructure and Azure cloud services”

Below: Skype <-> Lync Modalities Supported

.

Microsoft Account Requirement to Federate Skype to Lync Means Less Than All Skype Users Will Likely Be Available for Federation When Connectivity Goes Live

While there are 280million connected skype users, all these users need to voluntarily associate either a Live Messenger or Microsoft Account to their Skype accoun before Skype <-> Lync will work. This means two things:

280Million Skype users will not likely be ready on day one of Skype <-> Lync Federation

Those planning Skype click-to-call scenarios into Lync Call Centers need to be aware that not all Skype users may be enabled to do this and will need to make this exception a part of their calling plan

Get Your Live Messenger/Skype PIC Enabled So You Are Ready for Lync <-> Skype Federation

Conclusion

As an early promoter of federation awareness, (via the ongoing Lync Federation Directory Project) I am hugely interested in this massive enabling of B2X (as Microsoft is calling it). This is the first time that federation between a massive consumer base and a widely deployed enterprise UC solution has be enabled with this little friction. With this new connectivity Lync Server 2013 now connects to Skype, Office365, Gmail and more solutions—Out of the box!

Many UC and related vendors are eager to see video as “the new voice”, but I have wondered aloud if video will actually get the traction because of several inhibitors:

The freedom of “not being seen” can actually be thought of as a feature?

many seem to be replacing Voice with text messaging, not video?

the high “social cost” of face to face video?

some note that they expand the content over the video for business meetings that are not of a “high-stakes” nature

even at UC shops, users seem need to need to be asked to start video: if people crave video, wouldn’t they naturally start it?

both sides need to decide to start it, and there seems to be a extra pause not present with a voice call.

This article is not a anti-video, but thinking aloud if possibly the largest amount of video in the future will not replace voice, but actually come from an untapped new type of scenario: Virtual Camaraderie. (a term coined, I think, by Scott Hanselman) Currently when we think of UC video we think of someone starring intently right at us (or up above us ;-) but could many more video minutes come from creating virtual camaraderie scenarios with separated teams?

Think about your actual in person interactions when you work with someone in person. You don’t see there starring at each other---you sit along side. In this model no one needs to be continuously talking or even think about being looked at. This is the kind of vantage point where camaraderie, brainstorming and mentoring can occur naturally during the course of the day. It’s interesting to hear stories of when IT pro’s started out, with their desk near a mentor—learning, overhearing great work on problems etc, learning by just being around. Could this be recreated virtually?

There is likely few people that are familiar with remote working and can communicate the challenges as Scott Hanselman. He has written a great article on the challenges and benefits of the remote worker that got me thinking once again about his interesting Microsoft Lync project that enables Lync (a concept that could work with any UC/video calling solution) to provide virtual camaraderie (virtual cube buddy?, VC2? Video Buddy? Video Mentor? Video Office Group?) by having a 2nd video camera from the vantage point of a desk nearby rather than staring into the camera. So your video call buddy is more like “with you in the next cube” providing casual, ambience like interaction instead “you have my full attention” expected in a normal video call.

Perhaps UC vendors need to build “Virtual camaraderie” (VC?) functionality into their products? Below are a couple components I would think about:

Perhaps a second USB monitor that can be place beside you along with that 2nd cam

audio for VC session set to “like 1 cube over”?

Users Ability to Call their VC camera (separate from calling them normally)

in lync this could be like calling their mobile? or private line? or another modality?

Control’s around who can call your VC

your VC would automatically answer authorized “buddies”

when in a VC “call” (session?) presence not set to busy

When you make a call it does not necessarily put the VC session on hold

and likely more pieces I didn’t think about

Indeed, perhaps BYOD will beat UC vendors to this? Just buy a $150USD Android tablet, install Lync 2013 Mobile, setup UserName_VirtualOffice in Lync and have people call that with their own VirtualOffice user?

NOTE: We are hearing feedback from users that if you have Lync Server 2013 with Live Messenger PIC enabled and the Skype user has Skype for PC Version 6.2 audio calls should work.

On November 19, 2011 it was noted (see blog/how-to) that Skype to Lync federation seemed to start working at the IM & presence level after users updated to latest version of the Skype application and merged their Live Messenger ID into Skype using the latest Skype client.

At Lync Conference it was announced that indeed, merging LiveMessenger/Microsoft Account and a new version of Skype will be the actions that enable Lync <-> Skype federation. (blogger Greig Sheridan has done a good job of listing the requirements to get Lync <-> Skype federation working here: Click Here) Also noted was that Lync <-> Skype federation IM, Presence & Voice would be here around June 2013 ETA/timeframe. It appears that while no announcements have been made, Lync <-> Skype Voice federation has started to work for some and at various levels for others. See @shawnharry note below.

@voipnorm has it working both ways with Lync 2013

@MichaelVerso Notes it works one-way for him:

At the moment my experience has been that I can make one audio call from Lync (Skype PC version 6.1.x) –> Skype (Skype Android 3.1.0.6458) and audio flows, but after hanging up I can’t make another call. Also, I’m noticing that the incoming call notification to Skype indicates “unknown caller”. It is interesting to note that in the Skype call history the call is listed as “undisclosed_pstn:xxx”. I don’t think this necessarily means Skype is using pstn to deliver the call: it may just be a generic message if caller ID is note received correctly?

So, to summarize: Microsoft has not announced Lync <-> Skype voice federation to be ready at this time, so don’t expect it to work. But it does look like it is working for some, so if it does for you: Enjoy. Also, it appears Microsoft is making progress towards their mid-year ETA release goal.

According to Brier Dudley of the Seattle Time, I-Mate is set to introduce a Windows 8 Pro power mobile device and MWC.

This interesting device brings the possibility that BYOD could actually be a PC. While at first blush glance this device might seem far fetched, it does bring some interesting benefits if the experience can be made to work.

I have been following Damaka for some time so was glad to meet Ragu and Sandeep and get to ask them some question about their Lync/OCS mobile client Xavy. Below is the video interview and my summary of our discussion.

The Lync/OCS Mobile Client Now Available for free on applicable mobile marketplaces. Damaka is moving Xavy to freemium model so you can get a copy for free on the marketplace and only pay if you want support and to roll it out in quantities to your corporate users.

Roy Kuntz noted in his Lync Conference 2013 “Deploying Voice” session today that Lync Server 2013 will get Group Call Pickup functionality as part of CU1 update. Since this is one of the top requested features on http://lync.ideascale.com this is very welcome news.

I caught up with Roy in the Lync Conference Lounge afterwards and we chatted about the details of how Group Call Pickup will work in more detail. Below are some of my notes: (note: I didn’t test or see the feature, so I’m going on what I’m told here)

Setup

Call Park Ranges will be used to define Group Call Pickup. Admins can check a flag when setting up a Call Park Range and then the range will be used for Group Call Pickup instead of a Call Park.

When a phone is ringing, dial the Park/Group Call Pickup number assigned to that extension to pick it up.

The original ringing user will get a missed call notification from Exchange UM. (source: MicrosoftUC Blog)

How Group Call Pickup (GCP) Works Behind the Scenes

An incoming call going to a user that is part of a GCP will ring the user and simultaneously be automatically placed in a Call Park.

Various Notes:

More than one Group Call Pickup per FE Pool can be defined

SEFAUTIL will be used to administrate the Group Call Pickup

If an extension is assigned to a Group Call Pickup, anyone will be able to pick it up as there is no authorization needed to pick it up.

All users need to be homed on a Lync Server 2013 with CU1 applied to use GCP feature. (source: MicrosoftUC Blog)

Feature noted to work with Lync 2010, Lync 2013 & Lync Phone Edition (really should work with any endpoint)

This feature is designed to work in scenarios where a user can *hear* the other phone ringing. The reason for this is that Lync has no concept of “Ringing” presence state that users can see. (I have argued for the need for such a state for dynamic/fluid/fast-paced voice scenarios, but at this time there Lync does not have one)

If you were not able to make it to Lync Conference 2013: I’m sorry to hear that! But I will try to do my job and bring you any announcements/cool new products/vendor product & interview videos via twitter so follow/watch https://twitter.com/matthewlandis or follow hashtag #lyncconf

Here are My Key Takeaways of Lync Conference 2013

Microsoft the first Enterprise communication vendor to have massive presence and connectivity from the Enterprise to Consumer: Living Room to Boardroom and B2X are terms Microsoft is using to talk about this developement

Microsoft has invested heavily to get a full featured Lync Mobile client, with feature parity, on all major mobile platforms: BYOD fully embraced and no fear that it will be Microsoft mobile centric

Microsoft is fully committed to Lync Server, demonstrated by announcing Lync Server 2014 in beginning of 2014. (no plans to rebrand it to Skype Server. Ent. and Consumer marketing will be intentionally preserved)

Now that Lync is in Skype division expect Faster Release Cycles: Already demonstrated by several things: iteration via apps stores, CU including much more than fixes, and next Lync Server version announced for 2014

Cisco and Avaya see Microsoft Lync + Skype as a major threat to their business as evidenced by blogs during conference (links below)

TakeAways: Monday 2/18

Audiocodes is planning to Lync Qualified there HD Series IP phones: Click Here

If you want to watch the Lync Conference Keynotes, please see the following URL: Click Here

If you are here at the Lync Conference, make SURE you give your biz card to any of the UCArchitects podcast guys with the black tee-shirts. They have 67 Lync goodies to give away (like IP phones, headsets and more)

Justin Morris has taken time out of his busy schedule to do an interview of me for his “Interview with a Lync Pro” Series on the Microsoft Lync team’s NexHop site. If you can’t get to the Lync Conference, this is a way to get a little peak into my life and background with Microsoft Lync. But even better, let’s chat at Lync Conference!

Enables users to receive buddy invites from untrusted networks.Note This option is available under Alerts in Lync Options.

Improves the support for high dots per inch (DPI) displays, for Microsoft Narrator, and for other accessibility features.

Fixes bugs that are related to Location sharing and settings.

Fixes bugs that are related to Tabbed Conversations.

Enables participants to join online meetings by dialing out to their telephone number if online meetings are scheduled by a non-audio-enabled Lync 2013 user.

Improves the handling of devices that have both a front-facing and rear-facing camera.

Improves the user experience when you join a Lync meeting in a Lync Room System-enabled room.

Enhancements and Bugs Not Listed in KB

When hovering over a Contact Group, there is a new Bullet that clearly highlights the group

The Conversation tab is now populated from Exchange!

The Phone tab VoiceMail now populated!

Show Offline, Away and Unknown Presence Contacts in a Separate Group (below)

New Group Hover Indicator

Conversation History Now Populated from Exchange

Why are there TWO files to update Lync?

There are 2 files involved in update 15.0.4454.1506 and you need to run both updates. The MSORES file contains icons/images and will not normally need to be updated. The LYNCLOC file is the actual Lync update.

Xavy has continued to release new versions of their Android/Ios VoIP Lync in what has become a litany of “upgrade & test if it works yet” for those hoping for a full-featured mobile VoIP client for Lync.

In this last version of Xavy, I went through my quick battery of tests (make a EV call, call a Lync contact, video call) and…surprise…the basic feature test actually succeeded on my low end Android device. This means Damaka is making progress and means we can get on to test real-life scenarios like

How will Xavy consume power?

Will Xavy continue to run in the background gracefully?

How will Xavy handle moving from different data networks? (wifi to 3G/4G for example)

How will audio devices work with Xavy? (built in phone mic/speaker, blue tooth devices, etc)

Some might ask: Why does Xavy even matter if Lync 2013 Mobile client with VoIP support will soon be out? Below are some reason Xavy is still relevant:

Lync 2010 and OCS are still without a VoIP client, since Lync 2013 depends on Lync Server 2013 components.

The nearest thing to having a full Lync client on a mobile device at this point

Now that basic functions work we can start looking at usability, what did we notice in this last version of Xavy (for Android in my tests)

NOTE: this has nothing to do with Lync and is just myself keeping my brain cells stimulated. An evening, extra curricular detour…

After reading & thinking about webRTC, my take away is that the most transformative aspect is new “federation” models that webRTC has the possibility of enabling. One of these pointed out by Phil Edholm is a federation method that could be called “point at URL federation”. To envision how this would work I have started to write an extremely simple point at URL communication server (lab/proof of concept/experimental) to test the ideas.

The basic idea is that this type of “federation” (or inter organization connectivity) depends on nothing other than one user “pointing at another user URL” to connect to someone in the other organization. But what challenges will pop up with this? After scribbling on various napkins, I decided to just do a quick mockup app to test the ideas.

Pillars of this experimental Server/Client

interconnectivity with as little connection “friction” is a foundational goal

absolutely as little “start a conversation” friction as possible

IM/P & note is foundational as well

Note could serve as foundation for decentralized twitter-like social

with media made possible by webRTC (or something like it)

Some of my initial goals:

build an extremely simple server

starting with IM/P and non-realtime modalities

p2p server and client combined in web interface

voluntary participating in directory connects many different p2p servers

see how much can be achieved with GET model

(This is all a hobby/evening project so might take considerable time.)

Below: screen home user sees when logged in:

Below: screen guest user sees

GuestName –or- usernamepassword

Next the “external user” will see a screen similar to above, with themselves and other user (the url they typed in) in the conversation.

Followers

About Me

Matthew M. Landis has various industry certifications: Microsoft Certified Systems Engineer, Microsoft Certified Database Administrator, Microsoft Office Certified Expert, Microsoft Certified Dynamics, Network+ and A+.
In 1995 Matt started Landis Computer which has been providing IT services to small businesses for 14 years and is now a 11 person Microsoft Gold Certified Partner. Matt has over 14 years of field experience implementing Windows Server, Microsoft & Dynamics ERP solutions in small business environments.
Matt is very active in the Windows based IP PBX community: He was a 3CX Valued Professional from 2008-2010 and has co-authored a book on Windows communication software "3CX IP PBX Tutorial". He is pbxnsip Certified, he has contributed thousands of posts to the 3CX community forum and he writes the monthly Windows PBX Report e-newsletter for VARS and administrators. His company, Landis Computer, was the first company in the USA to be designated a 3CX Premium Partner.
When not working and when a chance affords Matt likes to travel internationally with his wife Rosalyn and is very involved in his church.