Freeze the exact service and failed attempt
Record UTC and local time, legal product, order or service identifier, site, feature pack, eligible access, accredited voice system and version, supplied equipment, channel quantity, number inventory, optional continuity products, direction, calling and called numbers, first response, answer and audio result. Redact secrets while preserving field names and retrieval time.
Classify the first unexpected boundary: order, access, routing, CPE, PBX object, number, capacity, request, response, dialog, media, diversion or restoration. Do not substitute Business SIP, TBS SIP Connect, SIP Complete, a lab template or another customer's settings.
Prove access and the accredited CPE boundary
Compare the order, confidential design and current accredited-CPE record with the installed model, software, interfaces and loaded configuration. Establish access state, addressing, route, quality policy and Telstra demarcation before changing firewall, NAT, SIP ALG, credentials or PBX objects.
A reachable Telstra address, active WAN, accredited model or registered-looking PBX object does not prove the selected trunk, source, identity, number or route is accepted. Preserve the first request and response at an authorized observation point and keep customer, access-provider and Telstra ownership explicit.
Trace channel and number state independently
For inbound failure, preserve number allocation or port state, provider attempt, delivered Request-URI and called-number headers, PBX receipt and route match. For outbound failure, preserve selected trunk, source identity, Request-URI, Call-ID, response sequence and restriction. Number presence, port completion and an accepted SIP transaction are not proof of a completed call.
Compare ordered simultaneous-call channels, current active dialogs, rejected attempts and any PBX or access ceiling. The documented minimum and increment rules do not reveal the account's purchased capacity or the cause of a specific rejection.
Keep signaling, Internet encryption and audio distinct
Use the current SIP Connect design to identify the approved signaling targets, transport, ports, identity model, number format, codecs, DTMF and media ranges. Do not import Business SIP NTU values or generic router instructions. Preserve the request, response, SDP and packet evidence for the same call.
The customer terms state that voice packets traversing Internet Access Services are unencrypted. That contract statement is not packet evidence and does not describe every access type or segment. After answer, prove both packet directions, selected codec, decoding and audible result independently.
Prove the selected continuity mechanism and restoration
Confirm the exact optional package in the order. For BRS+, preserve authorized user, plan revision, affected number set, activation time, success and failure history, provider route, destination result and rollback. For Shared Capacity, access redundancy or PBX failover, use that mechanism's own policy, trigger and observations.
Portal acceptance or history is control-plane evidence, not proof that every number diverted, a destination alerted, a call completed or the primary path recovered. Keep established-call behavior separate from new-call routing.
Retest one correction and close with bounded evidence
Apply one authorized correction and repeat the affected ordinary call plus an unaffected control. Preserve access, CPE and PBX state, SIP exchange, route match, channel count, answer, both media directions and hangup. If a port or diversion is involved, keep rollback criteria and the former path until the approved cutover is complete.
Attach the account-specific case and provider observations; a 24x7 help desk does not prove impact or restoration. Confirm emergency address, identity, callback, routing, power and access through an approved non-live process. Do not use 000 as an uncoordinated diagnostic. No SIP Connect service, call, diversion, 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.
- Telstra Enterprise — SIP Connect ↗
- Telstra — Our Customer Terms, SIP Connect section, changed 3 June 2024 ↗
- Telstra — SIP Connect Customer Integration Guide ↗
- Telstra Enterprise — SIP Connect support and accredited CPE ↗
- Telstra Enterprise — Business Resumption Service + ↗
- Telstra — Business SIP Critical Information Summary ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.