Treat the current contract and service family as the interface boundary
Lumen documents SONUS-based and Broadsoft-based SIP Trunking as different service families with different management surfaces. For the SONUS-based service, Lumen Connect exposes service IDs, locations, trunks, telephone numbers, DID numbers and route plans; the Broadsoft-based service uses the VoIP portal. Do not move a screen, field or workflow from one family into the other without the account implementation record.
Lumen's 2026 FAQ says ordinary new sales have ended, while existing contracted service continues for now under applicable contractual and regulatory obligations. Adds, moves, changes, renewals and expansions require individual review. That is a transition constraint, not an immediate shutdown date or proof that a requested change will be accepted.
Documented service facts
Reviewed 2026-10-20. Compare SIP trunk services →
Authentication
Not verifiedLumen's public service and portal pages describe service IDs, locations, trunks and route plans, but the reviewed pages do not establish one universal customer-PBX authentication method. Preserve the exact SONUS- or Broadsoft-based service, provider interop profile, source addresses and any redacted credentials separately; do not infer source-IP, digest or certificate identity from the portal object alone.
SIP registration
Not verifiedThe reviewed public pages do not say that every customer trunk uses REGISTER or that registration is forbidden. A service ID, trunk group and CURRENT route-plan status are administrative states, not proof of a loaded PBX registration or completed call. Obtain the account-specific interop guide before selecting an Asterisk or FreePBX registration model.
Inbound delivery
DocumentedFor the documented SONUS-based service, a phone number can be assigned to a route plan that controls inbound delivery across one or more trunks. Preserve service family, service ID, number assignment, route-plan status, hunt type, selected trunk, customer-edge receipt and PBX route separately.
Inbound failover
DocumentedSequential hunting, percentage allocation, pooled sessions and the product sheet's built-in failover statement are different evidence. Preserve the configured plan, ordered trunks or percentages and each observed new-call leg without inventing one universal trigger, timer, SIP-code matrix, restoration sequence or established-call result.
Number and regional availability
Not verifiedLumen's 2026 FAQ says ordinary new sales have ended; additions, moves, changes, renewals and expansions require individual review, while existing contracted service continues for now and no universal decommissioning date is published. Exact availability and transition timing remain account-, product-, contract-, state- and regulation-specific.
Audio codecs and DTMF
DocumentedThe product sheet says Lumen transports voice using uncompressed G.711 and supports a wider codec set including G.729. The reviewed pages do not provide a complete DTMF, packetization, transcoding or per-route codec matrix. Treat these as provider capability statements, then capture the actual SDP, RTP endpoints and digit method on authorized representative calls.
T.38 fax
DocumentedThe product sheet lists T.38 support, but does not establish availability on every service implementation, number, direction, carrier route, PBX or gateway. Qualify fax independently with the account interop profile, initial audio codec, switchover behavior, redundancy, page count and fallback policy; ordinary voice completion is not fax acceptance evidence.
Signaling and media encryption
Not verifiedLumen describes a secure portal and secure network, but the reviewed public service, route-plan and data-sheet pages do not establish one customer-facing TLS identity, certificate-validation procedure, SRTP profile or downgrade policy. Private transport, portal authentication and provider-network controls are not proof that the PBX signaling or media leg is encrypted.
Concurrent calls and burst
Not verifiedThe product sheet describes pooled sessions across locations, but the reviewed pages do not publish one account's simultaneous-session, calls-per-second, burst, queueing or rejection limits. A route plan with multiple trunks and a pool of sessions do not establish the same measurement. Obtain contracted sessions and call-start controls before any authorized load test.
Emergency calling
DocumentedLumen documents number and physical-address management plus an eligible 933 readback service after prerequisites such as completed porting and correct portal address are satisfied. Preserve emergency assignment, civic address, caller identity, callback and provider-approved validation independently from ordinary route-plan evidence.
Pricing model
Not verifiedLumen distinguishes usage-based trunks from flat trunks and describes pooled sessions, but does not publish a complete current rate card for one account. The end-of-sale FAQ says out-of-term rates may change and Lumen cannot commit to holding them. Obtain dated contract terms for sessions, numbers, usage, toll-free service, changes, porting, emergency service, taxes, support and renewal.
Administration and support
DocumentedLumen Connect manages SONUS-based service IDs, trunks, numbers and route plans; Broadsoft-based service uses the VoIP portal. Route plans are normally CURRENT and change to UPDATE during processing. The 2026 transition FAQ requires individually reviewed changes and preservation of contract, network dependency, account-team and support evidence.
SMS and MMS
Not verifiedThe reviewed SIP Trunking support, route-plan, number-management and product-sheet pages do not establish SMS or MMS on a trunk number. Voice or toll-free capability does not prove messaging eligibility, sender registration, consent controls, API delivery, throughput, retention or fees. Verify the exact number and messaging product independently.
Keep service IDs, trunk types and call direction separate
For the documented SONUS-based service, a service ID is a container for provisioned locations, trunks and numbers. Lumen distinguishes usage-based trunks used for outbound long distance and toll-free service from flat trunks used for local or bidirectional calls. The tenth character of the documented trunk-group name distinguishes those types.
Administrative membership does not prove that one call used a given trunk. Preserve the service ID, location, phone number, route-plan assignment, trunk group, expected direction, provider timestamp, customer-edge source, delivered identity, first response and Call-ID as separate evidence.
Follow the phone number into its assigned route plan
Lumen Connect provides separate workflows for adding, updating and disconnecting numbers, assigning a route plan, and managing 911 information. A number listed in the service container is inventory evidence; it does not prove the active route-plan relationship, selected trunk, customer-edge receipt or PBX route.
Before changing Asterisk or FreePBX, preserve the number record, service ID, route-plan name, change timestamp and status. Then compare the actual Request-URI, To and asserted identities with the loaded PJSIP identification, context, normalization and first matching inbound route.
Interpret hunt type and change status precisely
A Lumen route plan can contain one or more trunks and controls inbound delivery. The documented hunt choices include sequential and percentage allocation. Route plans are normally CURRENT; while a change is being processed, Lumen Connect reports UPDATE. Those are different dimensions: CURRENT is an administrative status, while sequential or percentage describes selection policy.
Record the plan, ordered trunks or percentages, status before and after the change, and each observed provider leg. Do not infer a universal response-code matrix, timer, retry count, customer-access diversity, restoration sequence or established-call continuity from the hunt label or CURRENT status.
Separate pooled sessions, media and emergency evidence
The 2024 data sheet describes pooled sessions across locations, built-in failover protection, G.711 transport, broader codec support including G.729 and T.38 fax capability. These are portfolio statements, not proof of one account's session quantity, call-start rate, codec agreement, fax result or failover trigger. Preserve both SDP bodies, RTP endpoints and decoded media for authorized representative calls.
Lumen's 933 service can read back the registered phone number and address without dialing 911 after product prerequisites are met, including completed porting and the correct portal address. Keep route-plan selection, emergency-number assignment, civic address, callback path and the approved validation procedure independently evidenced.
Plan transition without inventing availability or dates
Lumen says there is no immediate change to existing contracted voice service and no universal decommissioning date; timing varies by product, state, contract and regulatory obligations. It also says out-of-term rates may change and that network services supporting voice should be reviewed with any migration. Do not represent the product as generally available for new purchase or predict an account migration date.
Correct only the first proven divergence: wrong service family, number assignment, route plan, hunt configuration, trunk relationship, edge policy or PBX route. Keep rollback state, retest one affected and one control number, and record transition dependencies separately. No account, route plan, call, emergency result, price, availability or compatibility was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Lumen SIP Trunking support ↗
- Lumen communication-services end-of-sale FAQ ↗
- Lumen SIP Trunking data sheet ↗
- Update a Lumen SIP Trunking route plan ↗
- Assign Lumen SIP Trunking numbers and manage 911 information ↗
- Lumen 933 emergency testing FAQ ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.