Dave Michels
Dave Michels is a Principal Analyst at TalkingPointz. His unique perspective on unified communications comes from a career involving telecommunications...
Read Full Bio >>

Dave Michels | December 07, 2015 |


A Proximity Equal

A Proximity Equal Tapping into Plantronics' proximity API, UC vendors facilitate seamless handoffs from wireless headsets to desktop phones, softphone clients, and mobile devices.

Tapping into Plantronics' proximity API, UC vendors facilitate seamless handoffs from wireless headsets to desktop phones, softphone clients, and mobile devices.

One frustration I used to have with my Bluetooth headset was forgetting when it was connected and answering the smartphone like a handset. Hello. Hello?

That problem is a memory because a few years ago I switched to a Plantronics Voyager Legend UC that detects when I'm wearing it. When I remove the headset, calls go through the handset. I don it, and the headset becomes active.

Sensors are all around us, and it's time to put them to work. Why, for instance, doesn't the smartphone provide this same functionality itself using the face detection sensors that come into play in turning off the display when the phone is in use as a handset? It's actually kind of odd that the smartphone doesn't do this.


That auto-sensing of headset use was a reasonably obvious problem to solve, but there's quite a bit more that can be done. Plantronics has been loading its headsets with sensors and providing direct access to them with APIs. UC vendors, and Plantronics itself, have been publishing some creative integrations.

Of the APIs Plantronics makes available, wear state and proximity are the most popular. The wear state API enables what I described above, where the headset knows if it's on a head or set on the table. Contact center solutions can automatically take agents out of service when they remove their headsets.

Proximity detection determines if a user is near his or her phone or computer. Last month Avaya announced an expanded partnership with Plantronics that includes a proximity-based integration with Voyager Legend headsets. I've seen other integrations that use Plantronics' proximity APIs, too, and had assumed they were all the same -- but it turns out proximity integrations are more like snowflakes.

Here are three examples showing how different UC vendors are using proximity detection:

  • Avaya - The newest integration from Avaya offers a mobile-to-desktop solution, and works with the Scopia video client. When a mobile user on an active Avaya system call approaches his or her desktop, the client detects the user's presence and 1) moves the call from mobile to the desktop client, and 2) upgrades the call from audio-only to video, if appropriate.

  • Cisco - The Cisco integration also supports a mobile-to-desktop handoff, but in this case it is to a desktop phone rather than PC client. The app runs on the DX series of Android-based desktop phones. The phone app detects when a mobile user approaches his or her office, and prompts the call manager to move the active call to the desktop endpoint.

  • Microsoft - Microsoft has previewed an integration with Plantronics that senses when a Skype for Business user in a conversation moves away from the desk. The software will prompt the user to move the call to the cell phone, and if selected transfers the call. In this example, the call manager transfers the call out of the Skype for Business system to the mobile phone via the PSTN.

In all three cases, Plantronics uses the strength of a Bluetooth signal to determine proximity. Bluetooth is fairly reliable and consistent across smartphones, but that's not the case on desktops. Plantronics offers a Bluetooth USB dongle for desktops.

Wear state and proximity are just the beginning. As we move toward a more connected workplace, we will find reasons to enable integrations that react to a wide variety of triggers. These could include conversation over talk and volume level, headset and background noise level, and workflow events such as calendar meetings, emails, or queue length. Avaya released its proximity integration as a Snap-in within its Engagement Environment, so it is available for modification.

APIs are part of our new customized and integrated world. Give a user an integration and they are happy for the moment. Give the user a catalog of APIs and they can take-up fishing.

Don't look now, really, because Plantronics even offers an API for head position.

Dave Michels is a contributing editor and analyst at TalkingPointz. Join him at Enterprise Connect 2016, coming March 7 to 10 in Orlando, Fla., where he'll be highlighting cutting-edge enterprise mobility solutions in the Innovation Showcase. Register now using the code NJPOST and receive $200 of the current conference price.

Follow Dave Michels on Twitter and Google+!
Dave Michels on Google+


October 26, 2016
Software-defined wide area networks (SD-WAN) will change the shape of real-time communications, ushering in a new way to access cloud applications from remote offices. SD-WAN promises significant cost...
October 12, 2016
As business and technology leaders launch digital transformation initiatives, they sometimes put the cart before the horse. Though brilliant ideas for digital transformation may emerge, they simply wi...
September 28, 2016
Enterprises migrating to Skype for Business have choices when selecting the right elements to form a complete Unified Communications system. One thing thats not optional is the need for seamless, feat...