Freeze one direction, number and transaction
Record local and UTC time, direction, account, redacted trunk ID, authentication mode, regional proxy, source address, registration state when applicable, number, saved destination, caller identity, E.164 target, Call-ID, first response or timeout, SDP and media result. Redact credentials, API keys and personal numbers before sharing evidence.
Classify the first divergence: wrong authentication model, missing registration, unapproved address, wrong proxy, inactive number, wrong destination, invalid identity or digits, limit rejection, missing provider attempt, PBX mismatch or media-only failure.
Confirm the selected authentication model first
For Digest, correlate the configured trunk ID, secret owner, regional proxy, REGISTER request, challenge, authenticated retry and accepted binding. For IP Authentication, correlate the approved dedicated address, actual egress address and first INVITE response without inventing a registration requirement.
A green registration indicator does not prove the provider used the expected number destination or accepted an outbound call. An approved source address does not prove caller identity, routing, answer or media.
Trace the number record and destination before the PBX
Retrieve the exact number record and preserve status, destination array, number-level channels and redacted target. For an inbound failure, correlate the provider attempt, customer-edge receipt, Request-URI and first PBX route match for the same Call-ID.
Do not treat multiple destinations or product-page failover language as proof of one applied sequence. Preserve the actual priority or policy supplied for the account and the observed response at each attempted destination.
Check digits, caller identity and every applicable limit
For outbound calling, preserve the selected trunk, E.164 destination, From and asserted identity, first Wavix response and any later network result. Confirm that the caller identity is active or verified for the account and that passthrough, if used, was approved.
Compare the symptom separately with global account limits, trunk simultaneous-call, duration and cost controls, number inbound channels, PBX capacity and call-start rate. A configured maximum is not measured capacity, and a single rejection does not identify its owner without the response and records.
Correlate signaling, CDR and media without flattening them
Preserve the full SIP exchange, SDP, selected transport, codec, DTMF method, responding address, firewall decision and packets in both media directions. Then correlate the provider CDR by time, direction, numbers, trunk and destination when available.
A CDR row can document provider-side accounting or disposition without proving the PBX matched the intended route or that audio was decoded. TLS or SRTP availability does not prove the observed call negotiated protection.
Correct one owner and retest the original symptom
Change only the demonstrated authentication method, approved address, credential, proxy, registration setting, number destination, caller identity, digit format, limit, PBX route or media boundary. Record prior and new values, approval, effective time and rollback, then repeat the same authorized call.
Test emergency calling, messaging, porting, recording, automated dialing and failover only with the exact provisioned feature and approved procedure. One successful call does not establish pricing, availability, compatibility, capacity or support performance.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Wavix business SIP trunk ↗
- Wavix SIP trunk FAQ ↗
- Wavix create-a-SIP-trunk guide ↗
- Wavix SIP Trunks API overview ↗
- Wavix 3CX configuration guide ↗
- Wavix Numbers API overview ↗
- Wavix phone-number record reference ↗
- Wavix call-detail-record guide ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.