Freeze one number, time window and unexpected result
Record UTC and local time, account and location, affected DID, expected trunk group and PBX destination, actual destination that rang, observed source address, SIP Call-ID, portal report or ticket reference and every enabled continuity target. Redact credentials and reusable authorization material.
Classify the symptom before changing anything: the number is absent or assigned differently; the provider selected another group; no request reached the customer edge; the correct request reached the PBX but its identity missed; the correct route selected a failing application destination; or a continuity control intentionally created another leg.
Confirm number inventory without inferring call execution
Use the Comcast number view to preserve the affected number under the correct account, location and service context. Compare that state with the current service order and any recent port, move, add or change. Inventory evidence establishes what the portal lists; it does not prove the source group, delivered SIP identity or destination of one call.
If the number is missing, stale or attached to another location or group, stop before changing the PBX. Preserve the provider change and its effective time, then run an authorized new call after the change window.
Correlate the provider leg with customer-edge receipt
For the failed attempt, preserve any provider-side record and the customer-edge capture. Compare timestamps, called and calling identities, source and destination addresses, Request-URI, To, Diversion or History-Info, first response, retransmissions and Call-ID. A report row or utilization peak does not establish edge receipt.
If no matching INVITE arrives, keep PBX routing out of the first correction. If it arrives, follow the exact delivered identity through PJSIP identify or trunk selection, context, normalization and the first loaded Asterisk or FreePBX route.
Name the continuity control that selected the alternate leg
Distinguish Failover/Overflow, Load Balancing, Bursting, Unreachable Destination and Call Forward Not Reachable. Preserve the enabled rule, source group or number, target group or ten-digit destination, capacity state, provider observation and subsequent leg. Do not label every alternate result failover.
The public pages do not publish one universal SIP-code matrix, timeout, retry count, precedence or restoration sequence. Describe only the configured control and observed new-call transition. An answered forwarded call does not prove that the primary SIP path, PBX, LAN, power or access circuit recovered.
Keep capacity, media and emergency evidence separate
A busy group, purchased channels, optional bursting and PBX or SBC limits are separate capacity boundaries. Preserve the report interval and the exact resource that rejected or redirected the call. After the intended route answers, prove SDP agreement, RTP endpoints, packets in both directions and decoded audio independently.
Do not use an ordinary DID call as emergency validation. Preserve the assigned emergency identity, zone or civic address, PBX station mapping, callback route and provider-approved procedure. Obtain emergency-centre approval before any live 911 test and keep an independent calling method available.
Correct one divergence and run bounded controls
Change only the first proven divergence: number assignment, trunk-group relationship, continuity rule, customer-edge source policy, digit normalization or exact inbound route. Keep rollback state. Retest the affected DID and one unaffected control DID, recording provider selection, edge receipt, PBX match, final destination, answer and media separately.
If continuity was involved, coordinate an approved new-call failure and restoration exercise without inferring established-call survival. No Comcast account, number, group, forward target, portal report, PBX, packet, continuity event, emergency call or media stream 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.
- Comcast Business SIP Trunks ↗
- Comcast Business Enterprise SIP Trunks ↗
- Comcast Business Trunks features ↗
- View Comcast Business SIP Trunks numbers ↗
- View Comcast Business Trunks utilization reports ↗
- Comcast Enterprise Trunk Service product-specific attachment ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.