Freeze the exact product, order and failed attempt
Record UTC and local time, contracting entity, exact product, service identifier, region, site, access, PBX or SBC owner, number inventory, ordered channels, support scope, direction, calling and called numbers, expected route, first response, answer and audio result. Redact secrets while retaining field names and retrieval time.
Classify the first unexpected boundary: order, provisioning, access, addressing, DNS, certificate, PBX object, outbound request, provider response, inbound attempt, number delivery, route, channel admission, dialog or media. Do not substitute Connect, call-termination, Teams, Webex or another customer settings.
Prove the delivered access and SIP handoff
Compare the loaded PBX or SBC values with the current provider handoff: targets, authentication identity, secret owner, source-address rule, registration requirement, transport, port, certificate validation, number format and media contract. Preserve the first request and response at an authorized observation point.
A reachable Symbio address or working Internet path does not establish that the selected source, identity, certificate, trunk or called number is accepted. Determine whether traffic is absent, rejected, misrouted or attached to the wrong object before changing firewall, NAT, credentials or transport.
Trace number state and PBX route separately
For inbound failure, establish reservation or lease, port state, provider attempt, delivered Request-URI and called-number headers, PBX receipt and route match. For outbound failure, preserve selected trunk, Request-URI, caller identity, Call-ID, response sequence and any provider restriction. Inventory presence or port completion is not proof of delivery or call completion.
The Connect Portal and APIs are documented management surfaces for relevant customers, but a portal or API result does not replace the enterprise order, provider-side trace or PBX evidence. Preserve the exact system of record and observation time.
Keep TLS, SRTP, signaling and audio distinct
If protection is ordered, verify TLS negotiation, certificate names and chain, transport selection and SRTP offer, selection and packet evidence independently. The optional-feature article applies to voice termination in named regions; do not infer enterprise entitlement or fallback from the general announcement.
After answer, preserve both SDP bodies, selected codec and DTMF method, RTP endpoints, packet directions, decoding and audible result for the same call. A SIP response, TLS session or connected timer does not establish two-way protected media.
Prove the selected dual-network behavior
Confirm that dual-network service is present in the order, then record primary and alternate networks, route policy, health signal, trigger, attempted call, selected path, result and restoration. Provider marketing or a public incident notice is not proof that one account changed path.
A new call routed on an alternate network does not establish survival of an existing dialog. Keep PBX failover, access redundancy, Symbio dual-network routing, number diversion and disaster-recovery destinations as distinct mechanisms.
Retest one correction and close with bounded evidence
Apply one authorized correction and repeat the affected ordinary call plus an unaffected control. Preserve access, SIP exchange, route match, channel count, answer, both media directions and hangup. If a number or network change is involved, keep the former path until the approved cutover and rollback conditions are met.
Use the outage register only as timestamped context. Preserve the account-specific incident, provider observations, restoration claim and customer retest. Confirm emergency address, presented identity, callback, route, power and independent access under an approved non-live process; do not use an emergency number as an uncoordinated test. No trunk, route, call, failover, media or emergency result was tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Symbio — Enterprise SIP Trunking ↗
- Symbio — Australia voice network and carrier services ↗
- Symbio — phone numbers and porting ↗
- Symbio — SIP TLS and SRTP announcement, 24 January 2024 ↗
- Symbio — dual-carrier voice redundancy, 11 November 2025 ↗
- Symbio — security and trust ↗
- Symbio — Major Outage Register ↗
- Symbio — 24x7 Global Service Assurance, 19 December 2023 ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.