Freeze the product, country, profile and failed attempt
Record UTC and local time, legal product, contracting country, order, site, access, number range, channel quantity, PBX and version, provider profile, registrar or proxy, transport, direction, calling and called values, first response, answer and media result. Redact secrets while retaining field names and retrieval time.
Classify the first unexpected boundary: order, access, profile, registration, route, number, request, response, dialog, media, continuity or restoration. Do not substitute a reseller, platform or other-country profile.
Compare portal and profile evidence with loaded state
For Enreach Trunk (DE), compare the operator-portal channel identity, user ID, authentication name and selected Enreach Trunk or Enreach Trunk TLS profile with generated and loaded Swyx state. Retain the exact software version because earlier versions use the former Swyx Trunk name.
For another Enreach offer, obtain its own implementation record. A profile appearing in a list, a successful download or an accepted registration is not proof that the intended number and media path work.
Trace number and route selection independently
Preserve number allocation, port or activation state, configured number range and SIP URI, inbound provider attempt, delivered called value, PBX receipt and destination match. For outbound calls, retain canonical number construction, routing-record priority and time condition, selected trunk, presented identity and response sequence.
A number shown in a portal, a matching wildcard or a selected trunk group is not proof of a completed inbound or outbound call.
Correlate signaling, codec, DTMF, fax and media
Map the current provider contract to registrar, proxy, realm, source trust, transport, ports, codecs, DTMF and media. Correlate request, response, SDP and packets by the same Call-ID. After answer, prove sent media, received media, decoding and audibility separately.
Apply the Enreach Trunk (DE) codec, RFC2833 and T.38 notes only to that named profile and current evidence. A TLS profile name is not proof of certificate validation or protected media.
Prove the continuity control and trigger
Identify whether the account uses Enreach rerouting, redundant service, a secondary access, IP whitelisting or PBX routing. Record control scope, trigger, owner, destination, provider action, PBX route, call result, number presentation, media, restoration and rollback.
A saved target, secondary path or marketing redundancy statement is not proof of automatic trigger, physical diversity, completed calls or preserved features.
Retest one correction and close with bounded evidence
Apply one authorised correction and repeat the affected ordinary call plus an unaffected control with the same evidence set. Preserve profile and loaded state, registration or source trust, selected route, SIP exchange, number match, answer, each media direction and hangup.
Validate location and emergency readiness only through the organization’s approved non-live process. Do not place an uncoordinated emergency call. No Enreach service, PBX, call, media path, continuity control 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.
- Enreach — SIP Trunks for businesses ↗
- Enreach — SIP Trunks for resellers ↗
- Enreach — PBX Trunks platform for service providers ↗
- Enreach Service Center — Enreach Trunk (DE), updated 9 April 2026 ↗
- Enreach Swyx 15 — creating a SIP trunk group ↗
- Enreach Swyx 15 — creating a SIP trunk ↗
- Enreach Control Center 15 — forwarding and number substitution ↗
- Enreach Swyx 15 — emergency call detection ↗
- Enreach Service Center — Enreach Trunk FAQ and nomadic-use boundary ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.