There is a lot of digging going on between Midland and Odessa: new construction, road work, and new utility lines on the edges of both towns. Buried fiber and copper get cut, and when your building sits downstream of the break, you are not waiting on a reboot. You are waiting on a splice crew, and that can take anywhere from a few hours to the better part of a day.
For an office running cloud phones, cloud accounting, and card processing, a single circuit is a single point of failure for the whole business. Failover is the fix, and it is not complicated. It just has to be set up before you need it, because nobody configures a backup circuit well while the phones are down.
What failover is
A dual-WAN router takes two internet connections. One is your primary, usually fiber or coax. The second is a backup, and out here that is usually cellular, either an LTE or 5G modem built into the router or a separate gateway feeding a WAN port.
The router watches the primary link. A good setup checks whether traffic reaches the internet, not just whether the port has a link light. Most units ping a few targets on a short interval and mark the circuit down after several failures in a row. When that happens, the default route moves to cellular. When the primary comes back and stays stable for a set period, traffic moves back.
Failover happens at the router, not at every device. Your workstations, phones, and terminals keep the same local addresses and the same gateway. Most of them never know anything changed.
Why VoIP and card terminals react differently
Card terminals are forgiving. A transaction is a short request and response. If the link flips mid-swipe, the terminal errors out and the clerk runs it again on the cellular path. Check the batch afterward so a retried sale did not go through twice. Some terminals also have their own cellular backup, which is worth knowing before you design the rest around them.
VoIP is harder. A call in progress is a live media stream tied to a session your provider expects from a specific public IP. Change the public IP under it and that call almost always drops. Phones re-register on the new path, usually within a minute or two depending on your registration timers, and new calls work normally. Calls that were up when the circuit died do not survive.
Two details catch people. If your phone provider or card processor only accepts traffic from your office's fixed IP, the backup path will be blocked until its address is allowed or the service is switched to login-based authentication. And many cellular plans sit behind carrier NAT with no fixed public IP at all, so ask for a static IP on the backup plan if anything depends on one.
Set expectations internally. Failover means you are answering the phone again in a minute or two. It does not mean nobody notices. If seamless voice matters, look at an SD-WAN or bonding service that keeps a fixed public IP across both circuits. It costs more than most offices want to spend.
Data caps and signal are the real limits
Cellular backup only helps if it works at your address and does not run out. Check two things before you buy.
Signal at the equipment location. Network gear usually lives in an interior closet, which is where carrier signal is worst. An external antenna on the roof or an outside wall, cabled back to the modem, is a normal part of these installs. Test signal in the closet itself, not with your phone in the parking lot.
The plan behind the modem. Backup data plans vary widely in what they allow and what happens past the limit. Some throttle hard enough that the backup is useless by hour 3 of an outage. Size the plan for a realistic worst case, not a 5 minute blip.
Decide what gets to use the backup
This is the part people skip. When you fail over, everything in the building tries to use one cellular connection, and cloud backups, video calls, and software updates will use all of it while the phones starve.
Use traffic shaping and policy routing on the failover path. Voice and card processing get priority. Business applications get what is left. Backup jobs, camera uploads to cloud storage, and large syncs get paused or throttled while the primary is down. Many business firewalls can apply rules based on which WAN is active, so you can set one behavior for normal operation and a leaner one for backup mode.
Then test it. Unplug the primary during a slow hour and watch what happens. Confirm the phones re-register, run a test transaction, and time the whole thing. A failover circuit nobody has tested is an assumption, not a plan.
Who we are
West Texas Wi-Fi & Networking is a veteran-owned contractor in Lubbock. We design and install commercial Wi-Fi, cameras, access control, and cabling across West Texas, and we hold a Texas Department of Public Safety security license (B31108601) for the camera and access control work. If you want a second set of eyes on your building, book a free site survey or call (806) 370-9434.