Voip Unlimited SIP trunks: registration, DDI routing and call evidence

Bind the review to one order, registration and channel model

Record the legal customer, service order, issued credential owner, headline number, DDI aliases, channel quantity, Bundle Plus status, minute bundle, PBX or SBC, access circuit, support path and responsible operator. The service schedule defines a SIP trunk as one registration containing one or more channels and defines one channel as one concurrent call. The product page separately describes SIP Lite, SIP Unlimited and Bundle Plus.

Do not turn those catalogue and contract definitions into the selected account state. Preserve the dated order, activated service, actual binding, inbound and outbound channel treatment, calls-per-second policy, PBX capacity and provider enforcement as separate evidence.

Treat issued credentials and a successful REGISTER as one boundary

The service schedule says Ready to Use begins when SIP credential details are sent to the technical contact and describes the standard format as one registration carrying inbound calls for the headline number and aliased DDIs. Record the issued registrar or proxy, transport, port, username owner, challenge, Contact, expiry and final response without publishing secrets.

A 200 response and current Contact prove one registration transaction and binding observation. They do not establish number assignment, completed porting, inbound delivery, outbound authorization, available channels, negotiated media or a successful call.

Keep headline numbers, DDI aliases and completed ports distinct

Voip Unlimited documents a standard arrangement in which DDIs are aliased to a headline number and calls arrive through one registered account. It also says a DDI requiring different rerouting must be configured as a separate headline number. Record the provider-side assignment, delivered Request-URI and identity headers, PBX normalization, first loaded route and final destination for each accepted number.

A submitted port, prepared PBX route, portal entry and completed inbound delivery are different states. The service schedule directs customers to check inbound call logs after a non-geographic port. Preserve the port confirmation, first provider attempt and PBX receipt before changing a route.

Separate DNS routing, portal diversion and registration alerts

The product page discusses NAPTR and SRV for resilient SIP routing. The service schedule separately documents a portal call divert for customer-system or circuit failure and optional SMS alerts for non-registration. These are different controls: DNS target selection, provider-side call diversion and a rate-limited alert do not prove one another or active-call survival.

For DNS, record the exact service name, resolver, NAPTR or SRV answers, TTLs, priority, weight, target, port and selected address. For diversion or alerting, record the configured headline number, destination, trigger, timestamp and provider result. Avoid an uncoordinated failover test that creates duplicate ringing or emergency-call risk.

Verify IPv4 or IPv6, SRTP, RTP and fax from the selected call

The product page describes IPv6, SRTP and T.38 bypass as supported technology concepts. It does not establish the selected trunk transport, certificate policy, media-keying profile, codec list, DTMF method, RTP range or fax entitlement. Preserve both SDP bodies, chosen codec, packetization, media addresses, first packet in each direction, loss, jitter and decoded result.

Keep TLS signaling, SRTP media, ordinary RTP, T.38 negotiation, audio fallback and the vendor-described bypass path separate. A capability statement, accepted INVITE, packet counter or ordinary voice call is not proof of protected media, audible two-way audio or a successful fax.

Accept emergency, fraud, commercial and operational boundaries

The SIP service schedule says broadband or power failure can prevent 999 and 112 calling and requires current address details for each DDI because emergency services use them. Verify eligibility, registered address, update propagation, caller identity, callback behavior, outage method and only a provider-approved test procedure. Maintain an accessible independent calling method.

Record fraud controls, authorized caller identity, portal custody, support entitlement, status timestamp, incident ID, pricing, term, taxes and SLA scope from the selected order. Public support tools and provider-network claims are not proof of one account, customer access path, PBX or call. No availability, quality, compatibility, emergency or call result is claimed from this documentation review.

Use the DDI-specific workflow after registration succeeds

The Voip Unlimited inbound-DDI diagnostic separates accepted registration, headline and alias assignment, port completion, provider attempt, PBX identity, route selection and media.