A Thought Provoking VoWiFi Talk
As a quick recap in terms of design, the take away messages are:
- Coverage, make sure you meet the vendor RSSI requirements.
- Data Rates, If you set a high mandatory data rate, set some of the lower as supported.
- Channel Widths, 20MHz is best for voice.
- Larger Cells, don´t keep the cells to small to avoid excessive roaming.
- Channel Plan, try and minimise your channel plan to absolute maximum 8 channels.
To minimise the amount of time a client spends off channel probing for other access points, it was recommended to minimise the amount of channels used in your deployment. Also avoid DFS channels for voice networks to further reduce the time a client is off channel.
Two design scenarios
This in consideration, two scenarios come to mind when using seperate voice clients (eg. not skype running on a PC).
Voice is important, very important, but it´s not mission critical. The other applications running on the network are not high bandwidth applications. For the company I work for, this could be a factory with VoWiFi clients and RF guns. RF guns are more important than the voice clients.
In this scenario it would make sense to have access points grouped. UNII1 APs have the voice SSID, and the data SSID. The other APs have only the data SSID.
The second scenario is when voice is mission critical, and there are high bandwidth applications in use. An example might be a customer call center that has gone all-wireless (hopefully not to be seen anytime soon..).
Here it might make sense to use access points which have dual 5GHz radios. UNII1 Channels are for 5GHz Radio A, and only voice SSID is available. UNII2 & 3 Channels are for 5GHz Radio B, and only data SSID is available.
This would mean that the clients on the data SSID are able to consume as much airtime as they´d like, without impacting the voice SSID which exists only within UNII1.
I don´t know of a vendor who can assign SSID by radio, maybe there´s somebody already doing this?