Map the Wavix objects before interpreting a call
A Wavix account, SIP trunk, authentication mode, regional proxy, caller identity, phone number and number destination are separate objects. Record each identifier in redacted form and the effective time before following one inbound or outbound transaction.
A created trunk or active number is management state. It does not by itself prove registration, source admission, route selection, provider acceptance, PBX matching, answer, media or release.
Documented service facts
Reviewed 2026-10-24. Compare SIP trunk services →
Authentication
DocumentedWavix documents Digest authentication using the generated trunk ID and password, and IP Authentication using a dedicated static address after manual approval. Preserve the selected method and its current owner.
SIP registration
DocumentedThe 3CX digest workflow uses a regional proxy and registration, while the IP Authentication workflow uses an approved source address. Registration state is relevant only to the configured model and does not prove call routing.
Inbound delivery
DocumentedA phone-number record includes status and inbound destinations; Wavix also documents routing to a SIP-capable PBX or forwarding externally. Preserve the exact destination type, redacted target and observed attempt.
Inbound failover
Not verifiedProduct material advertises redundant trunking and multiple fail-over options, but the reviewed sources do not establish one universal destination order, response matrix, timer, restoration rule or established-call survival result.
Number and regional availability
Not verifiedThe Numbers API describes inventory in more than 140 countries. Current stock, required documents, locality, portability, activation and feature eligibility remain number-, account- and date-specific.
Audio codecs
Not verifiedThe 3CX guide recommends PCMU in that template, but the reviewed sources do not publish one universal codec, packetization, DTMF or transcoding matrix for every trunk, proxy and route.
T.38 fax
Not verifiedThe reviewed first-party material does not establish T.38, audio pass-through, fallback, number eligibility or support scope for the selected trunk. Qualify fax separately.
Signaling and media encryption
DocumentedWavix says TLS signaling and SRTP media are available. Availability does not establish enablement, certificate validation, negotiated keying, protection on every leg or fallback behavior.
Concurrent calls and call starts
DocumentedPortal and API workflows expose global account limits, trunk maximum simultaneous calls and number-level inbound channels; the FAQ says new accounts receive two outbound channels. Confirm every applied layer and the observed rejection.
Emergency calling
Not verifiedThe FAQ describes selected emergency numbers and countries for Flex Pro. Number eligibility, address validation, caller identity, callback, activation and approved test procedure remain account- and location-specific.
Pricing model
Not verifiedNumber API records include activation, monthly and inbound-minute fields, while trunk controls can include maximum call cost. Example values are not a current quote; preserve the actual transaction, route charges, add-ons and taxes.
Administration and support
DocumentedWavix documents portal and API trunk management plus near-real-time CDR retrieval for inbound, outbound and missed calls. API state and CDRs are correlation evidence rather than proof of PBX or media outcomes.
SMS
Not verifiedThe number record exposes SMS eligibility and callback fields, but sender registration, consent, direction, throughput, segmentation, carrier fees and delivery behavior remain a separate acceptance path.
Separate digest registration from IP authentication
Wavix documents Digest authentication with a generated five-digit trunk username and password, and IP Authentication for an approved dedicated static address. The 3CX workflow uses a regional proxy and shows registration for the digest path, while IP Authentication requires Wavix approval and a different PBX profile.
Do not use one model's health indicator for the other. Preserve the selected method, approval state, source address, regional proxy, REGISTER exchange when applicable and first INVITE response independently.
Trace each number to its saved destination
Wavix number records expose status, inbound destinations and number-level channel data. The product material also describes routing to a SIP-capable PBX or forwarding to an external number. Preserve the exact number record, destination type and redacted target before changing the PBX.
A destination array or forwarding choice is not a published failover contract. The reviewed sources do not define universal priority, response-code advancement, timeout, restoration or established-call survival for every destination combination.
Keep identity, formatting and layered limits distinct
The portal workflow selects a caller ID and can set trunk-level maximum simultaneous calls, duration and call cost; otherwise global account limits apply. The API also exposes number-level inbound channels. The 3CX guide requires outbound destinations in E.164 form and says new Wavix accounts initially have two simultaneous calls for security.
Account limits, trunk controls, number channels, PBX capacity, calls per second and an observed rejection are different evidence. Preserve the selected trunk, formatted destination, From and asserted identity, first response, start time and release time.
Verify protected transport and media on the actual leg
Wavix states that TLS signaling and SRTP media are available, but availability does not establish enablement, certificate validation, negotiated keying, downgrade behavior or protection on every leg. The reviewed sources do not publish one universal codec, DTMF, transcoding or fax profile for every trunk and route.
Preserve transport, responding address, SDP offer and answer, selected codec, DTMF method and packets in both directions. A registered trunk, SIP response or CDR row is not proof of decoded two-way audio.
Version API, CDR, emergency and commercial evidence
Wavix documents API-managed trunk and number records and near-real-time CDR retrieval for inbound, outbound and missed calls. Those records help correlate identifiers, duration and charges but do not replace signaling, PBX or media evidence. API examples and field values are not a current account quote.
Emergency calling is described for selected countries and Flex Pro, but number eligibility, address validation, caller identity, callback, activation and approved testing remain account- and location-specific. Record provider cases and corrections separately from service outcomes.
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.