Skip to content

(708) 273-3111

Internet access and SD-WAN, designed so the phones stay up

XCLUTEL is carrier neutral. It designs the access for each site, sources the circuit that fits from whichever carrier serves the address, steers traffic around failures with Fortinet SD-WAN, and supports the whole thing from one desk on one invoice.

Talk to an engineer How SD-WAN keeps calls up

Internet access

The circuit that fits each site, from whoever has the best one

XCLUTEL is carrier neutral. Rather than resell a single provider, it designs the access layer per site and sources the circuit that actually fits: dedicated fiber, broadband, fixed wireless or private transport. Interconnection at Equinix gives XCLUTEL direct reach into the major carriers and cloud on ramps, so traffic does not take an unnecessary trip through the public internet to reach Azure or AWS.

Dedicated fiber

Symmetrical, guaranteed bandwidth with a service level agreement, for the sites that carry the phones and the applications.

Business broadband

Cable and DSL where fiber is not built or not justified, sized for the site and paired with a second path where it matters.

Fixed wireless

A diverse path that does not share the street conduit with the fiber, so a backhoe cannot take both down at once.

Private transport

Point to point circuits, MPLS and Ethernet between sites and into data centers, for traffic that should never touch the public internet.

Equinix interconnection

Direct reach into the major carriers and the cloud on ramps, so traffic to Azure or AWS takes the short road.

Voice access

SIP trunks, PRI circuits and analog POTS lines for the sites and the equipment that still need them.

SD-WAN and security

Two paths into every site, and a call that does not drop when one fails

A single circuit failing should not take a location offline, and a saturated link should not turn a customer call into garbage. XCLUTEL deploys Fortinet SD-WAN so each site can run two or more diverse links, steer voice onto whichever path is healthy right now, and fail over without dropping the call. The same appliance carries the security stack, so branch firewalling, segmentation and inspection are part of the network rather than a separate project.

A site with desk phones, CloudX Phone and computers connects to a FortiGate SD-WAN edge. The edge holds two diverse circuits from two carriers. Voice travels on the healthy path to CloudX and the cloud; the second path stands by and takes over in under a second. Your site Desk phones CloudX Phone Computers and apps FortiGate SD-WAN and firewall one appliance per site Carrier A, dedicated fiber voice steered here while it is healthy Carrier B, fixed wireless or broadband diverse path, takes over in under a second sub second failover CloudX calls, CCAI, Teams via Equinix interconnection Internet and cloud Microsoft 365, Azure, AWS, everything else the site uses Every circuit and every edge watched 24x7 by the XCLU-Care desk
One site, two carriers, one edge. Voice rides the healthy path and the other stands by.
  • Two or more diverse links per site, any mix of carriers and media
  • Application aware path selection with sub second failover
  • Voice steered onto the healthy path during congestion and brownouts, usually without dropping the call
  • Bandwidth aggregation across the links you already pay for
  • Next generation firewall, segmentation and inspection at every branch, on the same appliance
  • Central policy across all sites, not box by box

When a circuit goes down

What happens to the phones?

Sites are built with diverse access paths and Fortinet SD-WAN, which detects a failing or congested link and steers active voice traffic onto a healthy path, usually without dropping calls. If a location loses connectivity entirely, pre staged disaster recovery routing sends inbound calls to mobile numbers, another site or an auto attendant. The support desk sees the failure before you call, and the carrier ticket is already open.

How a site is built

Four steps from floor plan to live circuit

The same engineer who designs the site is the one the support desk escalates to. Nothing is handed to a tier one script.

  1. Design the access layer per site

    An engineer looks at what each location runs, how many people work there and what happens to the business if it goes dark, then picks the access that fits. Not the one carrier XCLUTEL happens to resell, because XCLUTEL does not own a network and has no reason to sell you the wrong one.

  2. Source the circuits

    XCLUTEL orders from whichever carriers actually serve the address, manages the install and the carrier on your behalf, and puts every circuit on one invoice and one support number.

  3. Stage the failover before the first outage

    Diverse paths, SD-WAN steering and pre staged disaster recovery call routing are part of the design, not an add on sold after the first time the phones go down.

  4. Watch it around the clock

    XCLU-Care monitors every circuit and every SD-WAN edge 24x7, opens and drives carrier tickets, and escalates to engineers who know the account.

Cisco

Networking

Fortinet

SD-WAN and security

Equinix

Interconnection

ADTRAN

Access equipment

Get started

Tell us where the sites are

Send the addresses and what runs at each one, and an XCLUTEL engineer will come back with the access options, the failover design and one price for all of it. Or call (855) 925-8835.

Talk to an engineer