The biggest change in Skype for Business 2015 from Lync Server 2013 is the new user interface. Familiar to Skype users; minor learning curve for Lync users.
However, thatâ€™s not the only thing that’s new. We’ve already talked about integration with the Skype Directory…and there’s more.
This post is the first in a new post series on Skype for Business’ new features. We’re starting with a big one – Call Via Work.
What Call Via Work Is
Call Via Work replaces Lync’s Remote Call Control (RCC). I didn’t do too much with RCC, but Call Via Work intrigues me.
Essentially, Call Via Work enables integration between Skype for Business and a PBX phone system. Calls begun in Skype for Business ring a PBX phone – yours and the other party’s.
Why would you want to do that? A very good question. We’ll see what we can determine for an answer. But first, let’s talk about how Call Via Work, er, works.
How it Works
Call Via Work is part of Skype for Business’ Enterprise Voice role. It works by “bridging” two calls together into one.
- Let’s say Bob wants to call Sharon, one of his customers. He has her added as a contact in Skype for Business. Sharon uses a PBX phone system at her office. Bob also has a PBX phone available.
- He clicks her contact & selects the phone icon. The client initiates a call request to the Skype for Business Server.
- The server’s Mediation Server role sends a call to Bob’s phone. Caller ID shows a special number, called a “Global Phone Number”, so Bob knows this is not someone else calling. He picks up the phone.
- Sharon receives the call on her PBX phone. Skype for Business “bridges” the two calls.
- Bob and Sharon start talking normally. Aside from Bob having to pick up the phone *after* initiating the call, everything proceeds like a normal phone call.
Uses of Call Via Work
Obviously, a legacy PBX system is involved when using Call Via Work. In fact, not only does Call Via Work enable calls to PBX phones, but it also gives PBX users:
- Click-to-call (Audio going through the PBX phone)
- IM integration, Presence & user search. A TechNet piece cites as example, adding audio to an IM session, with the audio coming through PBX phones.
- The ability to add IM, application sharing, and file transfer to a Call Via Work call.
- One-click Meeting join (which I’d say is the most valuable capability, after voice calls)
It isn’t quite the full Lync/Skype4B experience. But it’s more than an old PBX has by default.
So what’s the best use of Call Via Work? I can think of two.
- Easier communication with customers/partners who still use a PBX.
- Transition Aid from an on-site PBX to Skype for Business. More on this later.
However, there’s a lot users need to know before you implement Call Via Work. Much of which involves its limitations.
What Users Need to Know
Call Via Work is a stealth function. It’s meant to do a job quietly, without messages or warnings. But users will need to know some things about it–otherwise it might cause confusion and disrupt calls.
What Call Via Work does. While the process is intended as transparent, users should still know what’s going on with their PBX calls. I wrote this post to help with exactly that. (Don’t forget to share it around!)
The Global Number. When you initiate a call using Call Via Work, Skype for Business shows the person called a certain number, which the administrator sets.
(The process for setting a Global Number is documented under “Deploy Call Via Work” here.)
This means a user’s direct number WILL NOT DISPLAY. Users must know the number, and that it will display in place of their own, so nobody’s left confused after a Call Via Work call.
Finally, Limitations. Yes, Call Via Work has limitations. Many of them in fact:
- If a Call Via Work user has set up Call Forwarding to the Global Number, and someone tries to invite them to a Meeting by phone number, the invitation won’t reach them. The forwarding blocks it. Solution: Tell users to invite Meeting participants by name.
- E-911 and malicious call tracing are NOT available during Call Via Work calls.
- Call Via Work users can’t use Delegation, Team Call, or Response Groups. (Serious drawback in my book.)
- Call Via Work users can’t record a Meeting, mute a call, hold or transfer the call, or use Call Park. (Ouch.)
- Users can’t access PBX voicemail through Call Via Work.
- Call Via Work users can’t escalate a voice call to a Meeting with video/whiteboards/PowerPoint.
- You can’t add more people to a call when using Call Via Work. It’s just you two.
- No support for deskphone pairing or VDI plugin pairing.
- If you make or answer a call using your PBX phone (not the Skype for Business window), you won’t have a log of the call.
- And finally – if your PBX system does not support “REFER with Replaces”, you’ll see this happen. While on a Call Via Work call, if you transfer the call from the PBX Phone, the call window will remain on your Skype for Business window. If you close the call window, the call between the transfer target and the transferee ends.
Lot of limitations users need to be aware of.
- Deploy a Mediation Server and an IP-PBX gateway.
- Ensure any user enabled for Call Via Work has Direct Inward Dialing (DID) on their phone.
- Enable Call Via Work users for Enterprise Voice.
- Configure their Skype for Business DID number to match their PBX phone’s DID number.
- Select “Automatic Configuration” in the users’ Skype for Business client’s Advanced Connections options. This is under the Personal menu in Options, by clicking the “Advanced” button.
- Enable Call Forwarding and Simultaneous Ring for every Call Via Work user.
- Enable Dial-In Conferencing and Conferencing Dial-Out for every Call Via Work user.
- Disable Delegation, Team Call and Response Groups for every Call Via Work user.
So why WOULD you want to use Call Via Work?
I think Call Via Work is very useful in a transition environment: Going from PBX to Skype for Business Enterprise Voice.
–It allows you to continue using existing hardware.
–It slows the training schedule.
–You have time to notify any customers or partners who might be affected. Without ruining your ability to call them!
However, for the long-term, I suggest enabling Call via Work only for those people who need it. Such people include sales staff calling businesses you know use PBX phone systems, legacy hardware/software testers, etc.
Because of its limitations on the user’s Skype4B call capabilities, Call via Work can hinder some communications. It’s useful, definitely. But it comes at a price.
If you’d like to read more about Call Via Work, the Mastering Lync Blog has a good rundown too: Call Via Work – Mastering Lync.
Do you use Call Via Work in the office? Planning to? What’s your experience with it? Please comment or email. And join us again next week!