question

I've been testing RC voice for 6 months or so and have had zero issues with running the handsets on the same VLAN as my client systems. I have plenty of headroom available in client and aggregation network layer. Whether you used VLANS or not, I would make sure you have a handle on the link utilization of your uplinks to your firewall and your link out to the Interwebs. Voice uses very little bandwidth, but is latency sensitive so enabling QOS and ensuring proper configuration of all infrastructure along the way is highly recommended as well. While VLANS are nice for ease of management and segregation of traffic, having them in place won't solve anything if your links are saturated.

Thanks for the reply. How many phones are you testing with? Most of our branches have < 10 phones with a few having 20 phones. We do have SonicWalls at all of our sites and will plan on implementing the RC recommendations for QoS.

NP Chris. I'm only testing with 3 handsets in my environment. These 3 handsets are running in a vlan with close to 150 endpoints. I already have a production VOIP phone system (Mitel) running in my office for about 23 users. Those sets are running on a separate VLAN. Our primary driver for having the other VLAN was due to IP exhaustion since we have quite a few hosts running on the subnet. I

We run over 2000 handsets and use VLANs on the Ring Central system and are also primarily voice users with only about 10% also using video for daily/weekly video Conferencing via Ring Central Meetings. In our former iteration of VOIP phone system via another provider, we did not use VLANs to segregate traffic, and had horrible QOS issues.  Since switching to Ring Central and deploying the VLANs organization-wide - we have had stellar performance using the setups exactly as recommended by RC.  In a small office environment with not many handsets and not much call volume - you can probably get away without using them. For a larger installation, I would strongly urge you to go with using VLANs.