Freeze one service, site and affected call window
Record UTC and local time, customer, site, order and activation reference, exact Lingo service and platform, access path, edge, PBX version, direction, calling and called values, expected route, first response, alert, answer, audio and hangup. Redact credentials and unnecessary subscriber data.
Preserve the last-known-good time and recent order, access, path, pool, burst, DID, port, failover, PBX, firewall or emergency-location change. Diagnose the first unexpected boundary before changing multiple systems.
Compare the implementation record with loaded edge state
Use the account implementation record and authorized support path for the exact platform, handoff, addressing, routing, authentication or identification, codecs and enabled features. Compare those records with the PBX or SBC objects actually loaded and the network path actually selected.
The public pages do not publish one universal registrar, proxy, username, password, source-address rule, port, transport, certificate or firewall range. Do not copy values from another customer or infer service state from a successful portal login.
Separate path allocation, pooling and burst evidence
Record ordered call paths, pool and site membership, burst entitlement and limit, active dialogs, local channel usage, new-attempt time, bandwidth context and the first provider or PBX response. A scalability or burst statement is not measured capacity or proof that one account can exceed its ordinary allocation.
Do not generate production load. Distinguish a local resource limit, exhausted pool, absent burst entitlement, provider rejection, destination busy response and timeout.
Trace number state, inbound delivery and outbound identity
For inbound failure, preserve DID order, port and activation state, provider attempt, delivered called value, PBX match, alert and answer. For outbound failure, retain selected route, presented identity, authorization, provider response and remote response.
A completed port, assigned DID, working outbound call or caller-ID row does not prove inbound delivery, callback, emergency identity or presentation at every destination.
Follow access, SIP, SDP and media through failover
At each authorized observation point, record selected access and route, firewall state, SIP requests and responses, SDP offer and answer, packet directions, decoding and listener result. If failover is expected, correlate the trigger, alternate target, access state and each new attempt.
Cloud redundancy and automatic-failover claims do not prove established-call survival, customer-access continuity, a completed alternate call or full restoration. A reachable gateway, accepted dialog, packets and usable two-way audio remain separate evidence.
Retest one correction and escalate a bounded case
Apply one authorized correction, repeat the affected ordinary call and an unaffected control, and retain order, edge, route, signaling, answer, both media directions and hangup evidence. Keep public status, support case, provider finding, action and verified restoration separate.
For emergency readiness, confirm the exact number, registered location, callback, PBX route, power and access dependencies through Lingo-approved non-live validation. No Lingo service, call, burst, failover event, emergency outcome 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.
- Lingo — Cloud SIP and PRI solutions ↗
- Lingo Knowledge Base — Cloud PRI and SIP Trunking ↗
- Lingo — Partner Product Guide 2024 ↗
- Lingo — E911 and California E911 Notice ↗
- Lingo — support resources ↗
- Lingo — service status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.