Anecdotal use of Voice Enterprise with iPhone/Android?

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Hey everyone,

The last specific post about this topic was about a year ago, so I'm wondering if anyone has anecdotal updates regarding using Voice Enterprise features with iPhones and Android devices.

I have a deployment coming up that will most likely feature a VOIP system using the employees smartphones as the main handset, with some normal VOIP handsets sprinkled through as conference phones/backups. It's possible they may use computers with soft phones as well. We're going full BYOD here.

Specifically I'm wondering:

  1. Whether 802.11r works well or poorly overall currently
  2. Whether the client support issues mentioned previously have continued
  3. Whether it's a good idea to start implementing it into a prod environment, and how the architecture would look (separate SSID still? other considerations?)
  4. Opinions on whether I should look at an 802.11n AP330 with Voice Enterprise as opposed to an 802.11ac AP230 without it for this particular application
Any general anecdotal reports about using VoWiFi via smartphones would also be appreciated. RF Design and QoS are well-established in my mind already, so I'm more interested in potential issues specific to "soft" handsets.

Thanks!
Photo of Steven Bateman

Steven Bateman

  • 65 Posts
  • 12 Reply Likes

Posted 4 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Steve, did you read:

http://www.revolutionwifi.net/2013/05/apple-ios-fast-roaming-with-aerohive-wi.html

I am certainly curious if-and-when we will see feature parity here in the AP230 and AP350/AP370,

Part of the reason for the slow uptake is the compatibility issues and therefore the need to run with an additional, often dedicated, SSID for capable clients.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Typo: I meant AP370/AP390 here...
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
  1. Yes, works well when the clients support it.
  2. The compatibility issues still exist but this just means that you usually need to run with an additional SSID unless you can vet clients to check for the driver bug that exists parsing the updated RSN IE.
  3. Seems to work well, yes. Caveat usually being the need for that additional SSID.
  4. If you need it today, go with AP330s, otherwise I guess pester Aerohive nicely to see if they will disclose additional information to you, perhaps on an 'NDA basis' if they feel that this is needed.
(Edited)
Photo of Steven Bateman

Steven Bateman

  • 65 Posts
  • 12 Reply Likes
Thanks Nick.

I did read Andrew's post. That and the Apple support document spurred me into thinking that Voice Ent. might actually be a decent option for this deployment.

Well... it might be a decent option for iPhones specifically. I'll have to rigorously qualify devices before giving access, but the majority are Apple ecosystem and presumably newer than a 4S. 

The deployment is scheduled to go live by EOY, so it would seem to me that unless Aerohive has plans for feature parity this quarter or a 2nd wave 802.11ac platform coming out now, the AP330/350 would be the choice. I see the Voice Ent. features as a bigger draw than the 802.11ac features which would seem to show very limited benefit (no benefit to phones, and I'm using 20 MHz channels).
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
Well... it might be a decent option for iPhones specifically
Good luck with Android devices.  Some of the latest models support some of the Voice Enterprise standards but from my experience a larger number of models don't.

I see the Voice Ent. features as a bigger draw than the 802.11ac features which would seem to show very limited benefit (no benefit to phones, and I'm using 20 MHz channels)
Getting your layer one and two environment right is, IMHO, much more important in a voice deployment than the new 802.11ac functionality.  If you don't have a good layer one and two then your voice users will never get a good experience.
(Edited)