If your contact center still rides Lumen, CenturyLink, or Level 3 for SIP, DIDs, or toll-free, the news is easy to misread. Nothing is supposed to go dark this week. That is exactly why operations teams delay, and why a clean cutover later gets harder.
Lumen has confirmed it is ending sales of voice products. Existing agreements stay in force. Net-new voice does not. When a term expires, there is no Lumen voice SKU waiting on the other side of a renewal. For a contact center, that is a carrier-project deadline hiding inside a contract date most people have not looked at since the last audit.
End of sale is not end of life
Lumen is concentrating capital on digital network services and AI-era connectivity. Voice no longer sits in that growth story. Channel Dive reported the company will honor current voice contracts and associated partner commissions, while helping customers move toward other solutions.
Treat that as end-of-sale, not a kill switch. Circuits keep carrying calls. Agents keep logging in. The change is commercial: no new logos, and no straightforward multi-year renewal once you hit term. After that, many customers drift to month-to-month, with less negotiating room and a lot more inbound from every SIP and UCaaS seller in the market.
If invoices still say CenturyLink, Qwest, Embarq, US West, or Level 3, you may already be in this population. The brand on the PDF is a poor filter. The products are the filter: SIP trunks, Voice Complete, PRI, leftover POTS, toll-free, and any hosted Teams or Zoom voice that was sold through Lumen.
The risk is operational, not theoretical
Contact center voice fails in public. A missed office DID is an inconvenience. A missed toll-free, a broken outbound campaign, or a 911 location that still points at last year’s floor plan is an incident. The work is less about picking a new logo and more about sequencing four dependencies that Lumen currently binds together:
- Numbers. Local DIDs, toll-free, and any overflow or department lines tied to IVRs and skills. Toll-free moves through RespOrg, which has its own lead times and data-quality problems.
- The SIP path into CCaaS. For Genesys Cloud CX that often means BYOC, Direct Connect options, and failover that does not drop the queue when one carrier blips.
- Emergency calling. Location databases and e911 have to follow the numbers. They do not magically survive a port.
- Dialers and AI audio. Outbound pacing, STIR/SHAKEN attestation, and any bot or transcription tap sit on the same trunks. A “simple SIP swap” that ignores them will show up as connect-rate and containment problems after go-live.
None of that requires ripping out Genesys Cloud CX, your WFM stack, or agent desktops. It does require a provider that treats those four as one migration, not four vendor tickets.
Two moves that look easy and age badly
Waiting for month-to-month. It feels like buying time. In practice you lose committed rates, freeze architecture decisions, and start porting under a deadline you no longer control. Number projects that should have been a scheduled weekend become a scramble across RespOrg, 911, and carrier FOCs.
Folding telecom into the CCaaS contract. One invoice is tempting after an ILEC exit. It also recreates the problem you just escaped: voice quality, redundancy, and numbering become features of a software vendor’s roadmap. We have made this case before in why buying telecom from your CCaaS provider is a weak default. Lumen’s exit is a reason to separate connectivity from the CX platform, not to glue them together again.
What good looks like on the new trunks
A contact center replacement for Lumen voice should be boring on go-live day. Callers keep the same numbers. Agents keep the same login. Supervisors keep the same Genesys views. The interesting work is underneath:
- Geo-redundant SIP with active-active, multi-carrier failover, not a single ILEC path with a backup that has never been exercised
- Per-call QoS and MOS you can tie back to Genesys interaction IDs, so a “the calls sound thin” ticket is evidence, not folklore
- Canadian and U.S. numbering on one plan, including toll-free RespOrg and scheduled ports
- Support that can join a cutover bridge, not a generic NOC queue that discovers you are a contact center after the fact
How Star Telecom runs this kind of move
Star Telecom builds SIP trunking for contact centers, especially Genesys Cloud CX BYOC. That is the job. We are not a long-haul network company deprioritizing voice to fund backbone growth, and we are not a CCaaS suite trying to own your PSTN as a bundle.
On a Lumen displacement we typically:
- Inventory trunks, numbers, 911 locations, and how those map into Genesys queues, IVRs, and dialers
- Design the SIP architecture (including private connectivity where it earns its keep) against your term dates, not against a sales quarter
- Scrub and port numbers with dedicated project management so FOC dates, RespOrg, and test calls happen in order
- Stand up quality monitoring before the marketing number flips, then stay on the bridge through hypercare
Partners who still own the customer relationship stay in that seat. We take the connectivity and the cutover mechanics. You keep the account.
A 30-day pass for ops and IT
You do not need a full migration this month. You do need a picture accurate enough to stop guessing:
- Export every Lumen / CenturyLink / Level 3 voice service and its term or circuit date.
- Match numbers to Genesys flows, campaigns, and 911 records. Note anything that has no owner.
- Flag anything that expires inside nine months. Those ports start now, not after the invoice language changes.
- Decide, in writing, that CCaaS stays and SIP changes, unless you already had a platform program underway.
- Book a design review with a voice specialist who can show redundancy, QoS, and a port plan against that inventory.
If you want that review to be with us, start here. Bring the contract dates and a number dump. We will tell you whether you have a quiet two-quarter project or a problem that is already late.