Bind the trunk deliberately and keep registration separate
ThinkTel documents SIP-trunk authorization against the configured IP-and-port binding for the pilot. Its authentication guide says the Via and Contact must carry the configured contact address and port and that a call from another address is rejected. The current trunk overview describes OPTIONS monitoring and says REGISTER should be disabled whenever possible. Record the assigned proxy, address, port, pilot and configuration owner before changing the PBX.
ThinkTel separately documents digest authentication for VoIP lines, and its broader trunk overview mentions credential authentication alongside IP binding. That is not permission to blend two procedures. Confirm the account-specific interop model, then preserve an address binding, an OPTIONS response, a digest exchange if required and a completed call as separate evidence states. Redact credentials and do not copy addresses or older PBX examples without comparing them with the current assigned service details.
Documented service facts
Reviewed 2026-09-28. Compare SIP trunk services →
Authentication
DocumentedThinkTel documents SIP-trunk authorization against the configured IP-and-port binding for the trunk pilot, checked through an access-control list. The Via and Contact must carry that contact address and port; traffic from another address is rejected. A separate digest procedure is documented for VoIP lines, so do not apply line-registration instructions to an IP-authorized trunk without an account-specific interop decision.
SIP registration
DocumentedThinkTel's current trunk overview says OPTIONS monitoring negates the need for REGISTER and registration should be disabled whenever possible. Treat an address binding, a response to OPTIONS and a completed call as separate states. Preserve the assigned proxy, source address, contact port and any explicit technical-services exception rather than inferring a registrar from older PBX examples.
Inbound delivery
DocumentedA pilot identifies the trunk, while DIDs can be ordered from available rate centres and assigned through uControl. The service overview says each configured binding can be used for origination and termination. Preserve the exact DID, pilot, binding order, delivered called-party format and PBX context; a working outbound call does not prove the inbound route.
Inbound failover
DocumentedThinkTel documents round-robin and lowest-available routing across configured bindings, OPTIONS-based binding state and SureCall forwarding after all bindings are down. Response-code retry behavior and the selected mode still require account confirmation. Test each binding, exhaustion case, all-down forwarding and restoration separately; a secondary binding does not establish established-call survival.
Number and regional availability
Not verifiedThinkTel describes a Canadian network and lets eligible accounts order trunk DIDs by rate centre in uControl. The ordering guide directs customers to the orders team when inventory is absent. Exact availability, portability, activation, identity requirements, caller-ID rights and number features remain specific to number, account and date.
Audio codecs and DTMF
DocumentedThinkTel lists G.711 and G.729 as default trunk codecs and RFC 2833 for out-of-band DTMF. That capability statement is not proof of route availability, licensing, payload selection or transcoding. Capture the offer, answer, RTP endpoints, negotiated payload and DTMF result for representative inbound and outbound routes.
T.38 fax
Not verifiedThinkTel says renegotiation from G.711 to T.38 is accepted when supported for fax over IP. This does not establish both endpoints, every route, fallback, error correction or document reliability. Qualify the exact DID, direction, gateway, initial codec and approved document set, and keep the result scoped to that path.
Signaling and media encryption
Not verifiedThe reviewed trunk overview publishes UDP signaling and RTP firewall requirements for its documented proxies but does not establish a customer-trunk TLS profile, certificate validation, SRTP or downgrade policy. IP authorization is not encryption. Obtain supported protected transports and identities in writing and verify the negotiated customer-facing leg.
Concurrent calls and burst
DocumentedThinkTel separates committed channels from the maximum channel total across bindings and documents changing both in uControl. Binding distribution affects the maximum, and lowest-available routing can change how capacity is consumed. Capture the account's commit, each binding maximum, total burst, call-start limits and billing treatment before any authorized load test.
Emergency calling
DocumentedThinkTel documents 911 address maintenance in uControl and a coordinated test process requiring a support request, a scheduled window and explicit same-day confirmation before placing the test. A custom caller ID can separate the displayed number from the expected service address. Validate every production location and calling identity, retain an independent fallback and never place an unconfirmed test call.
Pricing model
Not verifiedThe reviewed public service and help-centre pages do not publish a complete current SIP-trunk rate card. Channel commit, maximum channels, DIDs, destinations, emergency service, forwarding and professional services can affect the account. Obtain a dated quote and preserve currency, billing increment, commitments, taxes, usage rates and renewal terms.
Administration and support
DocumenteduControl exposes trunk bindings, DIDs, emergency addresses, billing and CDR functions according to assigned sub-user permissions. ThinkTel also publishes a service-status dashboard. These controls and status notices do not define an account's SLA, response targets or credits; retain the governing contract, applied configuration, redacted trace and provider case together.
SMS and MMS
Not verifiedThe reviewed SIP-trunk, DID-ordering and uControl pages do not establish SMS or MMS on a trunk DID. A voice-capable number does not prove messaging eligibility, campaign registration, sender approval, consent, API behavior, throughput or fees. Verify the exact number and messaging program independently.
Prove inbound identity and every configured binding
A pilot identifies the trunk, and ThinkTel says DIDs can be added from available rate centres. Each configured binding can be used for origination and termination. Preserve the exact DID, pilot, proxy, customer destination, binding order, delivered called-party format, caller identity and PBX context. The DID ordering workflow is inventory- and plan-dependent, so an advertised rate centre or a working outbound call is not evidence that one inbound number is active.
ThinkTel documents round-robin and lowest-available binding selection. It also describes retrying another binding for specified SIP responses. Test one controlled call to each binding, a busy or channel-full condition, an application rejection and restoration. Do not treat multiple bindings as established-call resilience: the published material describes new-call selection, not survival of a dialog whose signaling or media path has failed.
Separate binding failover from all-down forwarding
ThinkTel monitors bindings with SIP OPTIONS and documents an unavailable-forwarding feature called SureCall when all configured bindings are down. This is a different layer from moving a new call from one binding to another. Confirm the active selection mode, OPTIONS source and destination, response-code triggers, timers, binding priority and the single destination used for the all-down case.
Run bounded tests for a failed primary binding, an exhausted primary, every binding down, the forwarded destination unavailable and service restoration. Capture SIP messages and provider-side state without changing firewall, PBX routing and provider controls together. A successful forwarded call does not prove the original DID headers, calling-name behavior, emergency treatment or return path are equivalent.
Allocate channel commit, burst and media explicitly
ThinkTel distinguishes committed channels from maximum channels and says the maximum is the combined channel count across bindings. The allocation across bindings matters, and the failover guide warns that lowest-available routing affects maximum-channel behavior. Capture the account commit, each binding maximum, total burst, call-start controls, billing treatment and the expected result when a binding is unavailable before any authorized load test.
The trunk overview lists G.711 and G.729 by default, RFC 2833 DTMF and conditional renegotiation from G.711 to T.38 when supported. These are service statements rather than completed-call evidence. Capture SDP offers and answers, payloads, RTP endpoints and DTMF for representative routes. Qualify fax by DID, direction, gateway, initial codec and document set. The reviewed public pages do not establish trunk TLS, certificate validation or SRTP; IP authorization is not encryption.
Control caller identity and coordinate every 911 test
ThinkTel's default Owned DN treatment allows the pilot or DIDs belonging to it, while a Valid Format option can permit other authorized numbers. The caller-ID guide warns that masking the number on a 911 call can separate the identity from the expected service address. Preserve the approved outbound identities, number format, pilot association and validated emergency address for every site; do not use successful ordinary caller ID as evidence of emergency routing.
ThinkTel publishes a coordinated 911 test procedure: update the emergency information in uControl, request a scheduled test through support, wait for explicit same-day confirmation and do not place the call if that confirmation is absent. Follow the current provider process, limit the test to the approved time and scope, retain an independent emergency fallback and record the callback identity and address result without exposing personal data.
Snapshot operations and close only measured gaps
uControl permissions can cover bindings, numbers, emergency addresses, billing, CDRs and number ports, and ThinkTel publishes a service-status dashboard. Preserve least-privilege roles, configuration exports, CDR evidence, the status incident and the support case together. A portal control or public status page does not define the account's SLA exclusions, credits or response targets.
The reviewed public pages do not publish a complete current SIP-trunk rate card or establish SMS or MMS on a trunk DID. Obtain a dated quote covering channel commit and burst, DIDs, destinations, emergency service, forwarding, currency, taxes and renewal; qualify messaging separately by exact number and program. No ThinkTel account, binding, trunk, number, call, codec, DTMF, fax, encryption, failover, capacity, emergency call, message, price, availability or support response was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- ThinkTel network and services ↗
- ThinkTel SIP trunk service overview ↗
- ThinkTel SIP trunk help centre ↗
- ThinkTel SIP authentication ↗
- ThinkTel IP-binding workflow ↗
- ThinkTel SIP failover ↗
- ThinkTel channel commit and burst ↗
- ThinkTel DID ordering ↗
- ThinkTel pilot-number role ↗
- ThinkTel caller-ID guidance ↗
- ThinkTel 911 testing procedure ↗
- ThinkTel uControl permissions ↗
- ThinkTel CDR download ↗
- ThinkTel service status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.