Freeze one number, service ID and unexpected destination
Record UTC and local time, account, service family, service ID, location, affected phone number, expected route plan and trunk, actual destination that rang, route-plan status, observed source address, SIP Call-ID, portal change or support reference and recent port, add, move or change activity. Redact credentials and reusable authorization material.
Classify the failure before editing: wrong service family or portal; stale number assignment; route plan still in UPDATE; wrong sequential order or percentage allocation; provider selected the expected trunk but no packet reached the edge; or the correct request reached the PBX but matched the wrong identity or route.
Confirm SONUS or Broadsoft ownership first
The public documentation separates SONUS-based service managed in Lumen Connect from Broadsoft-based service managed in the VoIP portal. Preserve the account implementation record and the service object that owns the number. Do not diagnose a Lumen Connect route-plan field on a Broadsoft-based service or infer a Broadsoft workflow from a SONUS screen.
If the service family or owning service ID is uncertain, stop before changing the PBX. Obtain the current provider record and preserve any transition, contract or support restriction affecting a requested change.
Prove number assignment and route-plan status
In the correct service container, preserve the phone number, assigned route plan, route-plan status and the effective time of the last accepted change. CURRENT and UPDATE are administrative states; neither proves the trunk selected for one call. A number present in inventory also does not prove that the active relationship matches the intended route plan.
If the plan remains in UPDATE, preserve the submission and provider status rather than repeatedly editing it. If it is CURRENT but the assignment is wrong, correct only that relationship through the approved workflow and wait for a recorded terminal state before a bounded retest.
Correlate hunt selection with customer-edge receipt
For sequential hunting, preserve the ordered trunk list and each observed attempt. For percentage allocation, preserve the configured percentages and a bounded series of provider observations; one call cannot prove a distribution. Then align provider timestamps and identifiers with the customer-edge capture.
If no matching INVITE arrives, keep PBX routing out of the first correction. If it arrives, follow the actual source, Request-URI, To and asserted identity through PJSIP identify or trunk selection, context, normalization and the first loaded Asterisk or FreePBX route.
Keep capacity, media, emergency and transition evidence separate
Pooled sessions, route-plan membership, active calls, call-start controls, PBX channels and access bandwidth are different capacity boundaries. G.711, G.729 and T.38 capability statements do not prove the negotiated SDP, RTP path, decoded audio or fax pages for this call.
Do not use an ordinary DID call as emergency validation. Where eligible, preserve the assigned emergency phone number and address and use Lumen's provider-approved 933 workflow after its prerequisites are satisfied. The end-of-sale direction also does not prove an immediate service cutoff or acceptance of an add, move, change or renewal.
Correct one divergence and retest with transition controls
Change only the first proven divergence: service ownership, number-to-route-plan assignment, incomplete portal change, sequential order, percentage allocation, customer-edge source policy, digit normalization or exact inbound route. Keep rollback state. Retest the affected number and one unaffected control, recording provider plan and trunk selection, edge receipt, PBX match, answer and media separately.
If the correction requires a provider-reviewed change, preserve the account-team or support decision and do not promise availability or timing. No Lumen account, route plan, portal update, PBX, packet, media stream, emergency result, transition date or support response was inspected or tested for this diagnostic.
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 ↗
- 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.