Identify the service platform before choosing a PBX template
Lumen's current support area separates SONUS-based and Broadsoft-based SIP Trunking services. For the SONUS path, a service ID contains locations, trunks, telephone numbers and DIDs. The reviewed public pages do not establish one universal customer-PBX authentication or registration model across those implementations. Record the exact service, assigned signaling profile, source addresses, redacted identity and PBX owner before using any Asterisk or FreePBX example.
Keep administrative objects and live evidence separate. A visible service ID, CURRENT route-plan state or portal telephone number does not prove that a PBX registration is required, that a request was authenticated or that a call completed. Obtain the account-specific interop profile, then verify loaded configuration, signaling and media in that order.
Documented service facts
Reviewed 2026-09-28. 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 route plan contains one or more trunks and controls inbound delivery. Sequential hunt and percentage allocation are available route-plan choices, while customer equipment separately controls how outbound traffic reaches Lumen. Preserve the service ID, telephone number, route plan, trunk group, hunt type, delivered identity and PBX context as separate evidence.
Inbound failover
DocumentedLumen documents sequential hunt and percentage allocation across trunks in an inbound route plan, and its product sheet describes built-in failover protection. Those statements do not define every account's response-code triggers, timers, access-path behavior or established-dialog survival. Record the configured hunt type and approved failure cases, then test new-call routing separately from active-call continuity.
Number and regional availability
Not verifiedThe product sheet describes local, national, global and toll-free services, but also says services are not available everywhere. Lumen's 2026 communication-services notice says voice requests are no longer handled in the ordinary sales course and additions, renewals or expansions require review. Exact number inventory, portability, geography, contract and change eligibility remain account-, location- and date-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 user and primary-place-of-use assignment plus a physical emergency address for a SIP Trunking telephone number. Address changes can require approval, and the 933 service can read back the registered telephone number and address without placing a 911 call. Confirm eligibility, current portal state, caller identity, callback, notifications and the provider-approved test procedure for every real location.
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 service IDs, trunks, route plans and telephone numbers, while route-plan changes move through UPDATE before returning to CURRENT. Lumen's 2026 notice says existing contracted service continues for now, but no exact decommissioning date is available and adds, moves, renewals or expansions are reviewed individually. Preserve portal evidence, contract notices, change status, provider identifiers and support cases together.
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.
Follow inbound calls through the route plan
Lumen documents a route plan as one or more trunks that control inbound delivery on the SONUS-based service. The plan can use sequential hunt or percentage allocation. Outbound traffic remains controlled by how customer equipment points to Lumen. Preserve the service ID, telephone number, route plan, trunk group, hunt type, delivered called-party identity and PBX context rather than treating a trunk name as the whole path.
A route-plan edit moves through UPDATE before returning to CURRENT. Record that propagation state and the actual provider call identifiers during a bounded inbound test. Sequential and percentage routing are new-call controls; neither alone proves the response codes, timers, access-path behavior or survival of an established call. Test authorized failure cases independently and retain a rollback and separate calling path.
Qualify sessions, codecs, fax and protected transport separately
The product sheet describes pooled sessions, G.711 transport, support for G.729 and T.38. These are capability statements, not the active limits or negotiated result for one account and route. Obtain contracted simultaneous sessions, call-start or burst controls, rejection behavior and upgrade timing before any authorized load test. Capture SDP, RTP endpoints, packetization and DTMF method on representative calls, and qualify fax by number, direction, gateway, document set and fallback.
Lumen also describes a secure portal and network, but the reviewed pages do not publish one customer-facing TLS identity, certificate-validation procedure, SRTP profile or downgrade policy. Private connectivity, portal login and provider-network controls do not prove encrypted PBX signaling or media. Preserve each negotiated leg and trust owner separately.
Bind emergency service to the exact telephone number and address
Lumen's number-management guide assigns a telephone number to a user and primary place of use, then makes that user's physical address the emergency-service location. A move can require Lumen approval because service is not available at every address. Verify the eligible number, approved location, outbound caller identity, callback, notification path and current provider procedure for every operating site; a portal address that is not linked to the presented number is incomplete evidence.
Lumen's 933 service can read back the telephone number and address without placing a 911 call, subject to the product's prerequisites. Document the date, time, timezone, calling number and returned information as its FAQ requests. Do not treat a 933 result as a notification test or place a live emergency test outside the provider's current authorization and local procedure. Retain an independent fallback.
Treat the 2026 end-of-sale direction as a lifecycle control
Lumen's current communication-services FAQ says it is moving toward the end of sale for its non-Mass-Markets voice and communications portfolio. Existing contracted service has no immediate change, but Lumen says it is no longer proactively selling voice in the ordinary course; additions, moves, renewals and expansions require individual review. The FAQ does not provide an exact decommissioning date because timing depends on product, state, contract and regulation.
Do not convert that notice into either an immediate shutdown claim or an assumption of indefinite availability. Preserve the exact product, contract term, account-team response, regulatory notices, network dependencies, porting lead time and fallback plan. Review emergency-service continuity and number ownership before changing any supporting access service.
Use portal and commercial evidence without inventing a current offer
Lumen distinguishes usage-based trunks from flat trunks and exposes service, route-plan, number, reporting and billing controls through its portals. Those objects can support diagnosis, but they do not define one account's pricing, retention, support response or change eligibility. Preserve redacted portal state, provider call identifiers, change timestamps, contract notices and support cases together.
Obtain dated terms for sessions, numbers, usage, toll-free service, changes, porting, E911, taxes, support, renewal and exit. The end-of-sale FAQ says out-of-term rates may change and Lumen cannot commit to holding them. The reviewed SIP Trunking pages also do not establish SMS or MMS on a trunk number. No account, PBX, trunk, number, call, codec, DTMF, fax, encryption, failover, capacity, emergency call, message, price, availability, contract or support response 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 route-plan update guide ↗
- Lumen phone-number and 911 management ↗
- Lumen 933 emergency testing FAQ ↗
- Lumen SIP Trunking data sheet ↗
- Lumen communication-services end-of-sale FAQ ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.