Local Business VoIP is a service of Carolina Digital Phone. This guide is for offices, schools, and agencies getting ready to move voice onto the same network that already carries email, cameras, and video meetings.
Quick answer. To prepare a network for cloud calling, do not start with the speed printed on the internet bill. Count simultaneous calls at the busy hour, measure latency, jitter, and packet loss at more than one time of day, put desk phones on Ethernet where you can, separate guest Wi-Fi, review firewall and DNS against the provider's requirements, and write down what happens when power or the last-mile circuit dies. Carolina Digital Phone can host the platform. Your building still owns the last mile.
A new cloud phone system can be configured quickly. The harder question is whether your connection, local network, Wi-Fi, and power plan will support clear calls when the office gets busy. Start with the conditions your staff actually work under, not a quiet Saturday speed test.
For a five-person shop, that may mean putting a few desk phones on the same network that already runs video meetings. For a school, a county department, or a company with more than one building, it means walking each site: front office, classrooms or exam rooms, paging gear, and the closet that holds the firewall. A decent assessment keeps a phone migration from turning into a three-week network hunt.
Start with the calls you actually make
Cloud calling uses your data network to carry voice. Each active call needs a small, steady amount of bandwidth both ways. The codec matters, but consistency matters more. A circuit that bursts to 400 Mbps at 7 a.m. and chokes at 3 p.m. will make phones sound worse than a smaller, stable circuit.
Ask how many conversations can happen at once during your worst fifteen minutes. Include reception, queues, conference rooms, and people on softphones. A 20-person office rarely needs 20 simultaneous calls. A medical front desk with several inbound lines, or a school office during an emergency, often needs more headroom than a typical Tuesday suggests.
Then add everything else on the same pipe: video conferencing, cloud backups, cameras, file sync, guest Wi-Fi, and after-hours updates. The FCC broadband speed guide is a starting point for whether the circuit can carry voice at all. It is not a substitute for a busy-hour test.
If you want the product side of this conversation, start with what hosted VoIP is and how it differs from a closet PBX.
Check more than internet speed
Call quality lives or dies on three measurements:
- Latency — how long packets take to reach the platform and return. Some delay is normal. High or uneven delay makes people talk over each other.
- Jitter — variation in that delay. Phones hate jitter more than they hate a modest average delay.
- Packet loss — missing pieces of the call. That is the clipped word, the chop, the brief hole in the sentence.
Run those tests at different times of day, and from each location that will use the service. One branch with a tired cable modem will not match the main office. Remote staff bring their own variables: home internet, a crowded Wi-Fi channel, and a headset that looked fine in the box.
When calls already drop, read why calls drop and what to check first. That article is the field version of this one.
Prepare the local network, not just the circuit
Routers, firewalls, switches, and cabling matter as much as the internet provider. Old gear can still pass email and still ruin voice. A desk phone hanging off an unmanaged switch in a dusty closet is not fixed by buying a faster plan.
Walk the closet. Confirm the firewall is supported, firmware is current, and someone still has the admin password. Look for daisy-chained switches, consumer Wi-Fi extenders, and cabling that was “temporary” in 2014. Write down what you find. That list is more useful than a diagram nobody updates.
Quality of service is a tool, not a miracle
Quality of service, or QoS, tells the network that voice is time-sensitive and a backup job is not. It does not create bandwidth. Poorly set QoS can cause its own one-way audio. Test it. Do not treat it as a checkbox.
Larger offices, schools, and government sites often put phones on a separate voice VLAN. That can keep guest traffic and cameras from sitting in the same broadcast domain as the reception console. A five-person office with a clean, current firewall may not need that extra layer.
Wi-Fi and softphones
Desk phones belong on Ethernet when you can run a drop. Wired is boring and predictable. Softphones and mobile apps are useful the moment someone leaves that desk. Test them where people actually stand: reception, a classroom, a warehouse aisle, a conference room in the corner of the building.
Keep guest Wi-Fi off the same network as business phones. If you need a wireless handset, read how a VoIP Wi-Fi phone fits a hosted system. For staff who live on laptops, see Digital Voice Plus.
Firewall, SIP ALG, security, and DNS
Phones have to reach the provider. Firewalls that block the wrong ports, inspect SIP the wrong way, or leave SIP ALG turned on are a common reason for one-way audio and registrations that die at 2 a.m. Do not punch holes “until it works.” Use the provider's published requirements, change only what is required, and write the change down.
DNS is the quiet dependency. If name resolution is slow or filtered oddly, phones fail even when the circuit looks fine. Check it during the same window you test calls.
CISA's guidance on layering network security is a useful reminder that voice gear is still a networked device. Unused admin accounts, default passwords, and skipped firmware updates belong on the same punch list as QoS.
Plan power and internet continuity before cutover
Cloud calling does not make a building independent of power or the last mile. If both go away, the desk phone, the switch, the access point, and the firewall go with them. Decide, in writing, what happens next.
A small UPS may carry the firewall and a core switch through a flicker. A longer outage may need a second circuit, cellular backup, a generator, or a standing rule that inbound calls forward to mobile apps. The right answer depends on the cost of silence. A design firm may be fine routing to cell phones. A school or a public-facing department should treat failover as a procedure, not a hope.
Carolina Digital Phone runs the platform across geographically separate facilities. That does not replace a local outage plan or power and internet backup. Ready.gov's business continuity page is a plain place to start the paperwork.
Treat E911 as location work, not a feature toggle
Enhanced 911 only helps if the location attached to the call is true. That matters more once phones can move, staff work from home, or one system covers two buildings. Before go-live, list the address and, where it applies, a dispatchable location: building, floor, suite, classroom.
The FCC summarizes multi-line telephone system 911 rules, including Kari's Law and RAY BAUM'S Act. Schools should also look at how we approach district phone systems and the dedicated resource at HostedVoIPforSchools.com. Test your administrative process. Do not test by calling 911.
Test the real workflow, then name who owns what
A useful test is not “I got dial tone.” Place inbound and outbound calls. Transfer. Hold. Leave voicemail and confirm it hit email. Walk the auto attendant. Open the mobile app. If you have paging, door controllers, analog adapters, or alarm lines, handle each one on its own. Some integrate. Some need a replacement plan.
Test during ordinary business, when the network is busy. Ask testers for a time, a place, a device, and what they heard. “It sounded weird” is not a ticket.
After install, write down who owns the platform, who owns the firewall, who owns the circuit, and who gets the 2 a.m. call. Keep an inventory of phones, extensions, sites, and backup steps. Network readiness is not a ribbon-cutting. It is how you stay reachable when a customer, a parent, or a resident calls.
If you want a second set of eyes. Carolina Digital Phone has designed and supported hosted systems from Greensboro since 2000. Call (336) 544-4000 or request a callback. We will talk through the network you have, not a brochure network.
Questions we hear before a cutover
How much bandwidth does cloud calling need?
Each call uses a modest, steady stream, not a huge download. Plan for simultaneous calls at the busy hour, then leave room for video, backups, and growth. Measure latency, jitter, and loss. A raw megabit number without those three is incomplete.
Should every desk phone be wired?
Where you can run Ethernet, do it. Use Wi-Fi and softphones for people who move. Test coverage in the rooms they actually use, and keep guest wireless off the voice network.
Will the phones work if the office loses power or internet?
Desk phones at that site will not, unless you have backup power and a backup path. Calls can still ring mobile apps or another location if you set that up before the outage. The hosted platform staying up is not the same as the closet staying up.
Who is responsible for the network versus the phone system?
The provider runs the calling platform. Your IT team, managed provider, or internet carrier owns the circuit, firewall, Wi-Fi, and power. Put that split in writing before go-live.