Freeze one order, site and affected interval
Record UTC and local time, current legal provider, customer, site, service order, Dynamic IP product and access model, trunk-group identity, circuit or public-Internet path, PBX or SBC version, direction, calling and called values, DTO state, first response, alert, answer, audio and hangup. Redact credentials and unnecessary subscriber data.
Preserve the last-known-good time and recent order, access, number, port, DTO, capacity, QoS, PBX, firewall, portal or provider change. Diagnose the first unexpected boundary before editing multiple systems.
Compare the order with loaded edge and access state
Use the current order and provider implementation record for the exact site, trunk group, access, authentication or identification, signaling target, numbers, capacity and DTO option. Compare those facts with PBX or SBC objects actually loaded and the network path actually selected.
The reviewed public pages do not establish one universal registrar, proxy, realm, username, password, source-address rule, port, transport, certificate, codec or media range. Do not copy values from another account or infer a working trunk from a reachable circuit.
Separate capacity, access and the first SIP response
Record active dialogs, local channel use, offered attempts, call-start times, access bandwidth and utilization, the first PBX or provider response and the destination result. Compare the same interval with ordinary control calls without creating unapproved production load.
The 100 Kbps planning value is not a codec measurement, concurrency entitlement or guarantee. Distinguish local resource exhaustion, access impairment, provider policy, destination busy, timeout and completed call.
Verify DTO trigger, target and actual alternate answer
Confirm the ordered DTO option, affected number block, documented trigger, alternate trunk or number, current target and activation state. Preserve the primary-side impairment or exhaustion evidence, provider redirection evidence, alternate-edge receipt, PBX route, answer and media separately.
Do not use a normal manually forwarded call as proof of DTO. Do not treat inbound alternate delivery as evidence of outbound rerouting, established-call continuity or primary-path restoration.
Trace number, signaling, SDP and both media directions
For inbound failure, follow number order or port state, provider attempt, delivered called value, edge receipt, PBX match, alert and answer. For outbound failure, retain selected trunk group, calling identity, dialed value, request, response and destination result. Then align SDP, interface packets, NAT or firewall state, decoding and each listener result.
An accepted INVITE, configured QoS class or packets in one direction do not establish two-way audio. Change only the first demonstrated owner.
Correlate support and prove bounded restoration
Retain the U Connect service object, case, affected site and number, sanitized evidence, provider finding and action separately. Confirm the applicable emergency record and dependencies without placing an uncoordinated live 911 call. After one authorized correction, repeat the affected ordinary call, an unaffected control and DTO validation only when the provider-approved plan permits it.
A closed case, restored circuit, portal state, alternate answer or one successful call does not establish root cause or durable restoration. No Windstream Enterprise or Uniti Solutions service, DTO event, call, emergency result, incident or support finding was tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Windstream Enterprise — SIP Trunking with Dynamic IP ↗
- Windstream Enterprise — Voice & Communications ↗
- Windstream Enterprise — Direct Trunk Overflow fact sheet ↗
- Windstream — Standard Agreement for Service Terms and Conditions ↗
- Windstream Enterprise — Dynamic IP Standard Terms and Conditions ↗
- Windstream Enterprise — Customer Responsibilities Guide ↗
- Windstream Enterprise — Data Products SLA and QoS classes ↗
- Windstream Enterprise / Uniti Solutions — U Connect portal and support ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.