The Polycom CX700 phone ships with version 7577.4100 of the Lync Phone Edition operating system. It’s an older version, from OCS days.

You can still use this phone with Lync Server 2010 and 2013, by installing the latest version of Lync Phone Edition.

However, attempting to upgrade it via the direct route fails. Turns out there’s an error in its upgrade path.

We encountered this error, and after some online research plus talking to Microsoft, came to the solution. Here it is, for your future reference!

The Problem: CX700 Won’t Allow Upgrades OR Login

Like all Polycom phones, the CX700′s OS is upgradeable. We found out about the latest version of Lync Phone Edition, Cumulative Update 7 (CU7). Hey, new version! Let’s upgrade!

Except we couldn’t. We tried logging into the phone for upgrading…and failed. The phone stalled, eventually giving us a Certificate Authentication Error.

Why would the phone resist upgrading? Were we missing a setting? Did we have the wrong process?

Time to find out. To the Internet!

The Solution: CX700 Requires CU5 Before CU7

Thanks to a call to Microsoft and one of Jeff Schertz’s excellent blog posts, we discovered the problem. It’s an error between version upgrades of Lync Phone Edition. Microsoft has not listed this error on their websites, but they will confirm the error exists if asked.

In order to upgrade to CU7, you must first install a prior update, Cumulative Update (CU5). Once CU5 is installed, the CX700 will recognize CU7 as a valid upgrade path for its OS, and the install will go through.

Jeff Schertz, a Lync Server MVP and blogger at http://Blog.Schertz.Name, has posted an explanation and workaround for the CU5-to-CU7 upgrade issue:
Lync Phone Edition CU6 Upgrade Issues – Jeff Schertz’s Blog

(His post discusses upgrading to CU6. The same process can be used for CU7.)

You must manually install CU5 to the phone, and verify its certificate, before attempting to install CU7. The steps for doing are listed in “Workaround” on the above-linked blog post.

(Using this process, you can even skip upgrading to CU6 and use CU7 instead.)

CU5 Not Available for Download at Microsoft; Download the Update File Below

Lync Phone Edition CU7 is available from Microsoft Support. However, Microsoft does not have CU5 posted on their Downloads site anymore! If you search for it, you will find a CU5 KB page. But clicking Download will give you a copy of CU7 instead.

Unfortunately, this is standard Microsoft practice. But it leaves all of us in the lurch on these phones!

Jeff Schertz again came to the rescue. He posted the CU5 download file (in .cab format) on his blog. In order to continue the goodwill, we’re offering the same file for download here:
UCUpdates_tanjay_CU5.cab

So there you have it. Download Lync Phone Edition CU5, install it on your CX700s following the Schertz procedure, and THEN you can upgrade the phones to CU7. It’s a workaround, yes. But for now, it does accomplish the goal.

Have you upgraded your Lync-enabled phones? How’d it go?

Yesterday I spent the afternoon at the Cloud Connect event in Santa Clara. They hold an Expo for 2 days (basic registration is free), workshops & conferences.

Now wait a second. Why would a Lync expert go to a Cloud Computing expo?

• I like to learn about the latest cloud services. Since Lync can run entirely on virtualized servers, hosting it in the cloud is a great way for companies to start using Lync without paying for lots of on-site hardware. (We’re already doing this via our own Private Cloud Service!) So it makes sense to be aware of the major players (and the upstarts) in the cloud arena. What they’re offering now, and what’s coming.
• Networking. Always good to meet up with fellow IT pros. Hear some stories, discuss trends. Sometimes I meet good partners for us, or I can point people in a useful direction (like here!).
• Prizes! Last year I won an iPad 2 from the OpSource booth (now Dimension Data). I figure that increases my odds of winning something this year too!

Results of Wandering in the Cloud (Connect)

Expos like Cloud Connect are prime example of sharing information via ALL channels. Lot of people are on twitter while moving through the expo (hashtag #cloudconnect). Networking took place in the lobby & the halls as well as the expo hall. There’s printed datasheets and transferred files aplenty.

This year, they had more discussion about PaaS and IaaS. Cloud providers have solidified their offerings in replacing on-site servers. With just a few of the exhibitors’ solutions, you could build an entire business network from email to desktop.

I went in with two main questions to answer:
“Where is Cloud going?” and
“How is the Lync Server awareness among the cloud crowd?”

These are the answers I came away with.

Where is cloud going?
Cloud is expanding its presence like crazy. The number of major players – Rackspace, VMWare, Citrix, OnApp – is only growing. What’s more, cloud providers are sharpening their focus. No longer is it just, “We host a cloud.”

Now it’s, “This is how our clouds are built, with your chosen elements in place. These options are customizable, we can host software in a hybrid deployment, and here’s some examples of how it’s done.”

Some of the exhibits had very specific software: Racemi, for example, offered software to automate migrations of server software into the cloud.

How was the general Lync Server awareness?
Actually quite low. Many of the exhibitors offered solutions for higher (OS, network routing) or lower (data storage) IT systems. Many of the solutions will accommodate Lync Server nicely – smart infrastructure management hardware from OpenGear, carrier-neutral data centers run by TelecityGroup in Europe.

The biggest issue was that many of these cloud providers didn’t support the necessary Microsoft software to host Lync!

In a way, I like that. It means many of these big cloud players are catering to one area of demand – non-Microsoft systems. Less competition for us! And there’s still plenty of solid development for cloud overall.

Big thanks to all the exhibitors with whom I spoke, and to Cloud Connect for putting this event on! Hmmm, wonder what I’ll win this year…
That’s all for this week, folks! Check back next time for more Lync how-to. I have a few write-ups in the works on issues with VoIP phones and Web App Server.

Did you go to Cloud Connect? What did you want to see there?

My first reader email of 2013 contained a question about receiving Instant Messages. Specifically, he asked if he could use Lync IM on his iPhone and his laptop at the same time.

He was asking if multiple simultaneous logins are possible for Lync – signing in with your account on more than 1 computer. And receiving IMs to both locations.

I told him that Lync Server 2010 does not support multiple logins. But I would check to see if Lync Server 2013 can support this. Here’s what I found.

Why would you want multiple logins in Lync?

Unless you have a mysterious power to be in two places at once, multiple logins for communications software like Lync Server seems unnecessary. Lync treats your latest login as the ‘active’ one, whether that’s on your phone on your desktop. Since, presumably, that’s where you are!

However, I can think of one *good* reason to want multiple logins:  Conversation History. In case one client isn’t recording IM conversations properly, or you want multiple copies of a conversation.

(If one of your devices isn’t recording your IM conversations properly, this is a setup issue. Tell your systems administrator.)

Multiple Login Workarounds for Lync Server 2010

Sadly, I must repeat: Lync Server 2010 does NOT support multiple logins for one user. The reason is simple: each user can only have a single SIP address.

However, some workarounds DO exist to facilitate multiple connections.

While looking for reference links to show my reader, I came across this TechNet Forum thread: Lync Multiple & Simultaneous Account Login

Here we find a response from Matt Landis (if you’ve been reading Lync Insider, you know I’ve pointed Matt out as an excellent Lync specialist in the past!). He lists out some workaround solutions–and cautions that not all of them are supported by Microsoft!

What about multiple logins in Lync Server 2013?

We still have to wonder if Lync Server 2013 would support multiple logins. Many aspects of user management were updated in this version. Maybe an improvement to SIP addressing allows for multiple simultaneous logins?

After checking in TechNet and reviewing some fellow Microsoft bloggers, I have to say…no. Multiple logins is still a no-go for Lync 2013.

However, many of the workarounds Matt listed on the forum thread will work for 2013 as well. Personally, I think the best choice would be: Run a virtualized (second) copy of Lync on your desktop.
This would let you use a mobile client at the same time. And still be on Lync at your desktop. In terms of capabilities available, this seems the most promising.

Lync User QuickTip #4: Running Lync Twice on the Same PC – Matt Landis

PLEASE NOTE: This is NOT a supported solution by Microsoft! You take your chances. (And do a backup first!)

Lync knows where you are…in one spot

I always hate giving readers bad news…especially when they take the time to email in! But, “one login at a time” is just how Lync was made. It does make sense, considering Presence is intended to track where you are and what you’re doing.

We’ll just have to see what updates & modifications 2013 will bring.

Would you like to modify how Lync handles user access? In what way?

EDIT:  Please read the comments below if you’re confused.  I referred to simultaneous login activity with this post, not just signing in on more than one client!

Like many of you, I received an announcement from Microsoft yesterday. They’re shuttering Messenger and moving accounts to Skype by March 15.

A few people on Twitter this morning asked the same question I had: “Does this mean Skype will replace Lync?”

First off, no. I don’t think it does. Lync isn’t going anywhere – we have a brand-new version to play with right now! So don’t worry too much. Instead, let’s consider where this move leads.

Merging Messenger’s contacts & functions into Skype suggests finality. It suggests that that’s what they plan to use for consumer-level IM from now on. Which is an overall good thing – easier to support one app across platforms. Especially one like Skype, with its huge user base and wide feature set.

But where does that leave Lync users? Is their app under threat?

Again, not really. If Microsoft follows the streamlining pattern, there are 4 possible courses they could take with Lync and Skype:

1. Skype replaces Lync.

Dumb move. Microsoft won’t do this. It would ruin their Lync base among larger businesses.

2. Lync absorbs Skype.

Possible, but unlikely. And that’s because of the move from Messenger to Skype. It would mean users have to move apps twice!
Microsoft is already having trouble with migrating contacts on THIS move. The comments on this Engadget article testify to it: Microsoft retiring Messenger on March 15th, wants you to use Skype instead – Engadget

3. A new Lync-Skype hybrid app replaces both platforms.

Ideally, a hybrid app would adapt itself to the user (Lync or Skype) and the platform (desktop, mobile, tablet). Technically, this is possible…but in terms of user base, it’s only possible way down the line, around 2016 or later. Right now, the business of streamlining user bases and application platforms won’t allow it.

4. Lync and Skype stay separate, but interoperate.

The most likely course. MS has too much invested in building Lync Server as a business communications platform to abandon its desktop app. This approach also allows Skype to keep growing among consumer-level platforms.
I’m supported here by “Lync Bridge“, my name for the coming Lync app for Windows 8 and Windows RT.
It will federate with Skype…but it’s still Lync. And both will work on mobile.

Merging Messenger users into Skype makes more sense than the other way around. Plus it means that Skype will continue to evolve as part of the Microsoft software family.

In the meantime, Lync users have Lync 2013 to play with. And Lync Bridge (Lync for Windows 8/RT) to look forward to.  So let’s not worry ourselves.

Do any of our readers use Skype AND Lync? Please leave a comment or email me. I’d like to ask a couple questions.

2 weeks ago, I mentioned a training session I gave for a client. They had me back for another session late last week, this one focused on conferencing.

All went smoothly at first. People were able to join a Lync Online Meeting I set up, enable video, talk to each other…

…Except for one person.

When she tried to join the meeting via her Outlook invitation, she received a DNS lookup error. Each time. Naturally I went to her computer to see what the problem was.

Turns out the problem wasn’t with Lync.
It was with Google Chrome.

Chrome Browser And Lync Helper Don’t Speak to One Another

What had happened? Well, this particular person had Google Chrome set as her default browser. Now, that’s not a bad decision. I like Chrome myself; it’s great for testing, and works very fast.

However, the Lync Browser Helper is not configured to play nice with Chrome. And Chrome doesn’t like it anyway.

The Browser Helper add-in connects Lync Online Meeting commands with the Lync client on your computer. For example, when I joined the meeting (though I was only a federated partner & not part of their Lync Server network), my Lync Attendee client opened up. Lync 2010 or Lync Attendee opened for all the others. This is because the Browser Helper auto-loaded once the Outlook meeting link was clicked, and called up Lync.

But when the Chrome user clicked the meeting link in Outlook, Browser Helper didn’t recognize it. The command failed, and she ended up with a DNS lookup error.

At first I thought there was a missing DNS setting in the external certificates. But according to this Microsoft Support page:
External users can’t join Lync Online conferences anonymously or as guests – Microsoft Support

“The user is using Google Chrome as their default browser. The Lync Browser Helper add-in isn’t configured for Google Chrome when the Lync 2010 Attendee client is installed.”

And this discussion:
Starting Lync Meeting with Google Chrome as default browser – Office 364 Community

“Chrome does not like to interact with other programs. So when you attempt to join a meeting with the Join Meeting link, it loads an aspx which attempts to search for the client outside of the browser. Since the aspx runs into this roadblock it fails the search and falls back to the webapp.”
———
Clearly I’m not the only one who’s encountered the issue!

Want to Run Lync Online Meetings? Use IE

The solution to this little conundrum is simple. We switched the Chrome user’s default browser to Internet Explorer, clicked the Online Meeting link again…and she connected in a flash.

That’s all you need to do. Set Internet Explorer as your default browser before you run a meeting. (You can even switch it back afterward!)

To set IE 10 as default in Windows 8, go here: Make Internet Explorer you default browser – Microsoft Windows 8 Support

For IE 9, click the Settings icon at top right (the gear). Click “Internet Options.” In the Settings window, click the “Programs” tab. At the top you’ll see the “Default web browser” field. Click the Make Default button. Then click OK. You’re done.

And with that, The Lync Insider is off for the holidays. We at PlanetMagpie hope all of you enjoy your Christmas, and we’ll see you all in 2013!

Guest Post from RealPage

The other day, Craig at RealPage Inc. contacted me with an unusual question about Lync user identities.

In short: They have two users. They want both users to be able to open an Administrative profile in their local Outlook and set Online Meetings. While still logged into their own Lync accounts.

They had this working for one user, but not the other. What did they need to do?

We gave them some advice – probably a Lync/Outlook configuration issue. But Craig industriously figured the problem out on his own. He was even kind enough to share his documentation with us.

Below you’ll find Craig’s solution, in guest post format. Take it away Craig!

Multi-user Lync Steps – Instructions on configuring Lync and Outlook to properly use multiple user identities in the same desktop login session

Say you need to schedule meetings using the Lync “Online Meeting” plugin, but you need those meetings and their corresponding Calendar info to be on a different account’s Calendar (the “Secondary Account”), and not your personal Calendar (the “Primary Account”). The scenario requires the manipulation and testing of several pieces in Lync and Outlook. These are:

1. A new, separate Outlook profile complete with the credentials of the Secondary Account you wish to make the meeting under. Proper configuration of mailbox permissions is beyond the scope of this document; it’s assumed the user already has the necessary access to the mailbox.
2. A successful login to Lync using the same credentials in Step 1 above. Proper login of the Lync client is assuming that the account has been properly built out in Lync Server.
3. A successful Meeting creation within the Outlook profile created in Step 1, using the identical credentials logged into Lync in Step 2, using the “Online Meeting” button to confirm the connection information of the environment. *this is key, do not skip as it builds session credential cache info for later use*
4. Log out of Lync as the Secondary profile, and log back into Lync as the Primary user account.
5. Log out of Outlook, and back in as the Primary user and insure their “Online Meeting” button works as expected.

Configuration Instructions

1. Log onto the user’s computer with their login.
2. Build the new User profile on the Outlook client using the target Calendar user’s credentials. Configure the Profile management to “Prompt” so that you can choose which Outlook profile loads:
   
3. If the Lync account has already logged on, log off the Primary user from Lync.
4. Login on Lync using the Secondary Account’s proper SIP account login.
   
   If this is the first time you have logged in on Lync using the Secondary account, you should receive a re-prompt (as this credential will be in conflict with your Primary user profile that you have logged in on your desktop), enter the password for the Secondary account.
   **If you get an error here saying your credentials are incorrect, log in on the Lync Server and temporarily disable/re-enable the account in question. Then retry this step.
   3rd credential prompt, you will need to supply it the Secondary Account’s AD login info ([domain name]\[username]) in the username field, as well as the password:
   There will be a 4th credential challenge; it will re-prompt for credentials, requiring you to enter the password one more time.
   
5. At this point, Lync should be started with the Secondary Account as active, while the Primary Account is still logged in on their desktop.
6. Start Outlook and choose the new Secondary profile that you created in step 2, so you’re starting Outlook to use the same identity that is running in Lync.
7. Create a new meeting and click the Lync “Online Meeting” button:
   
8. The info that populates in the Meeting info window should contain linking to the Lync account that is running.
   
9. Once that is done, you can cancel the meeting request. Sign out of Lync and close Outlook.
10. Sign back into Lync using the Primary Account.
11. Start Outlook and log back into the Secondary email profile.
12. Your environment should now consist of
    • Primary account – logged in at the desktop.
    • Primary account – logged in on Lync.
    • Secondary account – active in the Outlook profile.
13. In Outlook, create a new meeting. Click the “Online Meeting” button as in step 7.
14. The results of that button press should be identical to your step 8 test. Functionality should be that the Lync “Online Meeting” button reflects the actively logged in profile *in Outlook*, and not who is logged in on Lync or logged in on the desktop.

And that’s it! Thanks Craig, for sharing your documentation with us. (And for the screenshots, they’re helpful.)

So now we know how to log into multiple Lync user identities from one desktop, and schedule Online Meetings.

How would you use this in your organization? Drop us a comment and let’s talk.

I was all set to expound on some reader feedback, when I saw what happened Tuesday.

Lync Server 2013 is now out on Preview.

That’s right folks, the next version of Lync Server has begun its journey into the IT world! Download it here.

Justin Morris has a “quick look at what’s new” here. I might be as excited as he is – or at least close.

His characterization of Conferencing’s new Gallery View is hilarious as well as accurate – Brady Bunch View! (Anyone feel old when they recognized that? I did…)

There’s a slew of changes to Lync Server in this preview. I encourage everyone to read the Preview Page to start out. Me, I went to the TechNet library pages and started digging.

And I found quite a few things!

The First 5 Lync Server 2013 Feature Changes to Take Note Of

The Lync Server 2013 Preview Planning Tool is 32-bit. So you can test it out without using a 64-bit server.

Lync Server 2013 Front End now incorporates Monitoring Server as an optional feature. Now, TechNet specifies that this is the case with 2013 Preview only. It may well be the case for full-version Lync Server 2013; nobody can make the claim 100%. Yet.

That said, I think this is a great evolution of Lync’s monitoring capability. It may be an ‘optional feature,’ but most smart organizations will surely take advantage of a minimal-overhead, no-additional-server-needed monitoring option.

DNS Load Balancing loses ground, in favor of hardware load balancers. On the DNS Load Balancing TechNet page for the 2013 Preview, several situations are discussed where DNS load balancing can be used, but with limitations. I noted this one:

Using DNS load balancing on your Edge Servers causes a loss of failover ability in the following scenarios:
* Federation with organizations that are running versions of Office Communications Server released prior to Lync Server 2010.
* Instant message exchange with users of public instant messaging (IM) services, such as Windows Live, AOL, and Yahoo!, in addition to XMPP-based providers and servers, such as Google Talk and Jabber.

These scenarios will work as long as all Edge Servers in the pool are up and running, but if one Edge Server is unavailable, any requests for these scenarios that are sent to it will fail, instead of routing to another Edge Server.

Much of the page’s content appears to frame DNS load balancing as a way to reduce impact on hardware load balancers. It’s only a subtle shift away from how it was referred to in Lync Server 2010. Given 2013′s increased service capacity, it even makes sense. I’m curious how this will shape up once we see the full version of 2013.

Multiple trunks between Mediation Servers and gateways are now supported. One given reason for this is interconnecting different telephony systems, such as hooking an IP-PBX into a PSTN gateway.

However, another use (and a potentially bigger one) is redundancy among voice routing. Will need to dig more into this later.

Lync 2013 is federated with Skype! Huge benefit to Lync Server AND to Skype users. The existing Skype network will connect with Lync Server-enabled organizations. Seamless voice, IM and presence sharing.
(My predictions are once again vindicated!)

There’s many more changes coming in 2013. I’ll blog about as many as I can (as well as test them!) in the coming weeks.

Now, if you’ll excuse me, I need to go pester my colleagues about installing the 2013 Preview…

NY Times posted an article on Skype on Memorial Day:
$8.5 Billion Deal for Calling Service Presents a Puzzle – NYTimes.com

It details the current status of Skype’s integration with Microsoft. They have more autonomy than other acquisitions, allowing Skype to keep improving its communications software on multiple platforms.

A while back I wrote several posts about Skype and Lync combing in in some fashion. In the last one, I agreed with Ars Technica’s speculation that a version of Skype would be released for Windows 8 soon.

According to the Times, that’s soon to come. In time, no doubt, to capitalize on the Windows 8 fervor building on the Web.

But I’m wondering if that’s just Phase 1.

The article points out that Skype is popular across platforms. Including mobile devices. And tablets. (Skype on my iPad is immensely handy.)

What if Skype on Windows 8 is the trial run?

Maybe Microsoft is checking the reception here, before fully realizing integration with other Microsoft systems…like, say, Lync Server.

Skype and Lync Co-Developed in the Future? Skype Pulling Ahead?

A check of Skype’s job postings reveals 5 positions addressing Lync. A Program Manager, two development engineers, a network architect and a “Lync Technology Solutions Professional.”

All discuss growing inter-operation between Lync and Skype.
And all were posted this month.

So far, I’ve done pretty well on speculations. My first Skype-related post gave 4 ideas on how Skype and Lync could integrate. One of those ideas was:

Three, they could use Skype as an entry-level VoIP & video chat client for Lync Server. This is just a hop skip & a jump above the current Lync 2010 client tools. Plus it gives businesses already using Skype a chance to connect with Lync users, and vice versa. Instant tools expansion.

Building Skype on Windows 8 is one way to foment entry-level VoIP & video, all right!

Plus, if it’s successful, Skype takes vanguard position. It’s the first big communications option on a new operating system.

What about Lync on Windows 8? I haven’t seen much on that. No new versions mentioned for the new OS. Hmmm.

Unified Communications Includes Skype AND Lync

Does this mean Lync Server could take a back burner, while Microsoft pushes Skype?

Hardly. There are 5 Skype/Lync jobs listed. Microsoft has 208 jobs available for Lync 15, Lync Server’s somewhat-mysterious next version. Lync 15 is roaring ahead. (I’ll try digging up some information on it for a future post.)

It looks like Microsoft is continuing its Unified Communications initiative. Letting Skype’s inroads among multiple platforms keep it strong. There’s time for further integration along the line.

And if Windows 8 does well, you know a Lync client will soon follow. Maybe it will piggyback on Skype. Maybe a fully-integrated composite app will appear for business use.

Informed speculation, yes. But I’ve been on-track so far!

Your thoughts? Where do you think Skype and Lync are headed?

That’s not a rhetorical question I wrote for today’s blog post. It’s part of a question a prospective client asked us:

“Why is there a Mediation Server in Lync if you have Media Bypass? Doesn’t that make it (the server) redundant?”

Media Bypass Lets You “Go Around” a Mediation Server

Media Bypass allows you to call non-Lync phones without transcoding the media stream through Mediation Server. This reduces the load on Mediation Server. And it can preserve audio quality.

Media Bypass has 2 modes:

• Always Bypass – Media Bypass will be attempted for every PSTN call.
• Use Site and Region Information – Media Bypass creates a Bypass ID for each network region. Sites with lower bandwidth are given their own IDs; otherwise, sites inherit the same regional ID. This mode uses those IDs to determine when to bypass. (You have control over when bypass happens, in this mode.)

(Note: You cannot use Call Admission Control if you’re in Always Bypass mode. Just an FYI.)

If media can be sent through without transcoding though, why DO we need a Mediation Server? What does the Mediation Server bring to the table?

What a Mediation Server Does (Beyond Bypass)

Without the Mediation Server Role, you would not have Enterprise Voice. Period.

Mediation Servers handle traffic between Front End servers and your chosen gateway (an IP-PBX, SIP trunk, or PSTN gateway). It’s responsible for all SIP traffic, and all PSTN calls through its connected gateway/gateways.

Except for when Media Bypass routes PSTN calls around it.

Did Microsoft hamstring their own Lync Server roles? What’s missing from the picture here?

The Reason Mediation Server is Necessary: Wi-Fi

Is Mediation Server necessary? Only if one condition applies.

Your office uses a wireless network.

Why does that make Mediation Server necessary? Because of this paragraph right here:

“Wi-Fi networks typically experience more packet loss than wired networks. Recovery from this packet loss is not typically something that can be accommodated by gateways. Thus, we recommend that you evaluate the quality of a Wi-Fi network before determining whether bypass should be enabled for a wireless subnet. There is a tradeoff in latency reduction versus recovery from packet loss to consider, as well. RTAudio, a codec which is available for calls that do not bypass the Mediation Server, is better suited for handling packet loss.”

–From Planning for Media Bypass – TechNet

Transcoding media (phone calls) is why Mediation Server exists. One server role has to identify which network your call’s going to, and which codec will work best.

The G711 codec gives callers a better-quality signal. But RTAudio works better on networks where packet loss is higher. RTAudio for calls made via wireless; G711 for internal calls on the LAN.

And what decides which codec to use when you make a call? That’s right…your Mediation Server.

Media Bypass is a very useful feature of Lync Server. It lightens the load, reducing the number of Mediation Servers necessary in your deployment. But make no mistake. If you want to use Enterprise Voice, you will have at least one Mediation Server.

(Oh, and you can collocate it with your Front End pool!)

How’s your Mediation Server set up?

The question of “what comes next” always looms over major software like Lync Server. Speculation’s already begun over what form Enterprise Voice & Conferencing will take in the next version.

Here’s a little speculation of my own. I think Lync Instant Messaging could grow into a replacement for texting.

I know that seems like a huge leap. But bear with me while I tease out some thoughts.

Consider the following:

• Texting is more popular than talking.
• Phones are primarily seen as data devices nowadays.
• Lync clients already exist for mobile devices.
• All Lync Mobile clients are capable of Instant Messaging.
• In terms of usability, IM is only 1 step away from texting. Both convey short written messages over whatever connection is available. The only major difference is that text messages can be sent via PSTN.
• Phones are geared more toward texting than voice now.
• Younger generations of businesspeople are already used to doing business over social media, email, IM–and yes, texting.

So, my speculation doesn’t look so implausible. Instant Messaging is very close to texting. Texting won’t do anything but grow in the future. Bridging the two, tweaking IM into a texting medium, is conceivable.

How would it work though?

The Method: Build an SMS Gateway into Lync Server

The simplest solution would be to build an SMS gateway into the next version of Lync Server.
(Maybe not EASY, but simple!)

An SMS gateway would allow Lync users to send texts the same way they do instant messages. The gateway pipes them out to the Internet (or the PSTN via Mediation Server).

We’re halfway there already.

A company called Geomant has developed SMS for Lync – an add-on which allows you to send & receive texts like they’re IMs.

It is not an SMS gateway; Geomant lists four gateway providers you can use with SMS for Lync. But it creates the functionality in Lync 2010. Seamless. Just like IM.

Which means if such a gateway were built into Lync Server, using it for texting IS achievable.

The Snag: Telecom via Satellites VS. Lync via Internet

SMS is not dependent on the PSTN to transmit text messages. Google Voice proves that.

But most text messages are sent through telecom carriers like AT&T and Verizon. Using, among other things, communications satellites.

Merging IM and texting in Lync Server would change the primary transmission medium to the Internet. (At least, that would make the most sense to me.)

This presents a snag in adoption. Telecoms won’t just give up the satellites. And increasing the amount of text messages sent via the Internet could strain existing channels (more than they are already!).

The saving grace might come in the “session” orientation of Instant Messaging. People in IM conversations tend to encapsulate those conversations into one period of time. One ‘session’ where they communicate what’s needed.

Text messages are less structured, more random. Combine the two, and you may introduce a little structure without damaging the “anytime” nature of texting.

What do you think? Would Microsoft be smart to integrate texting into a future Lync Server?