Start with the ordered TELUS interface and access path
TELUS describes SIP Trunking delivered to a customer phone system and distinguishes a QoS-enabled private-network path from encrypted delivery over the Internet. Those are different access and protection models, not interchangeable labels. Preserve the order and service handoff, then identify the actual access circuit, edge, peers, authentication, transport and media profile.
The public pages do not publish one universal registrar, peer set, credential model, codec plan or certificate profile. Prove whether the selected service registers or peers by source address and which PBX or SBC object owns every value before changing the system.
Documented service facts
Reviewed 2026-10-07. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed TELUS public pages do not define the selected trunk's credential or source-address authentication method, digest realm or algorithms, certificate role, mutual authentication or IP allowlist. Preserve the current order and handoff, then map each secret or trusted address to its PBX or SBC owner without exposing it.
SIP registration
Not verifiedThe reviewed public pages do not establish whether a TELUS enterprise or partner trunk registers, uses static IP peering or supports another interconnect model. Record peers, transport, Contact behavior, expiry, qualification, DNS dependencies and source-address requirements from the exact service handoff rather than inferring them from the SIP Trunking label.
Inbound delivery
DocumentedTELUS describes SIP Trunking as integrating inbound and outbound voice with a customer phone system, and its guide says DIDs can be added or ported. Those descriptions do not establish an account's assigned numbers, port completion, Request-URI, asserted identity or PBX normalization. Retain the number record and an authorized call trace for each accepted pattern.
Routing and failover
DocumentedTELUS advertises redundancy, failover and a geo-redundant platform. The public pages do not define the selected account's failure trigger, timers, destination, customer-access diversity, established-call outcome or restoration sequence. Bind continuity to the order and a provider-approved new-call failure exercise.
Number and regional availability
DocumentedTELUS describes Canada-wide SIP Trunking and says its footprint includes 95 percent of Canada's population for new number requests. This marketing coverage statement is not proof that a service address, rate centre, number, port, destination or regulatory use is eligible. Preserve dated serviceability and portability responses for the exact requirement.
Audio codecs and DTMF
Not verifiedThe reviewed public pages do not publish a complete current codec, packetization, DTMF, early-media, transcoding or media-address profile for the selected interface. Obtain the TELUS handoff and retain both SDP bodies, negotiated payload mapping, RTP evidence and decoded digit results on each required path.
T.38 fax
Not verifiedThe reviewed pages do not establish T.38 or audio-fax entitlement, direction, switchover, gateway compatibility, redundancy or page limits for the selected TELUS trunk. Treat fax as a separately ordered and accepted workflow using the current interface record.
Signaling and media encryption
DocumentedTELUS describes either a QoS-enabled private-network delivery path or secure encryption over the Internet, and separately promotes encryption as a security measure. Those statements do not identify SIP TLS versions, certificate validation, client certificates, SRTP mode, key exchange or protection across every call leg. Bind the actual controls to the order and retain handshake and SDP evidence.
Concurrent calls and call starts
DocumentedTELUS advertises burstable SIP trunks, purchased sessions and Canada-wide capacity shared across locations for peak traffic. Bursting is not an unlimited or measured calls-per-second result. Use the dated order for base sessions, burst ceiling and charges, CPS, simultaneous calls, site allocation, bandwidth and abuse controls, then validate only under an approved load plan.
Emergency calling
Not verifiedThe reviewed TELUS SIP-trunk pages do not define the selected enterprise service's 911 activation, civic-address workflow, nomadic-user handling, caller identity, callback routing, test method or outage limitation. Obtain the current emergency-service schedule for every number and site, preserve provider-approved validation evidence and maintain an independently powered alternative calling method.
Pricing model
Not verifiedTELUS describes reduced costs, purchased sessions and burstability but does not publish a complete current enterprise price on the reviewed pages. Use a dated quote, contract and bill for access, base sessions, burst usage, calls, numbers, ports, continuity, emergency service, support, taxes, term, renewal and cancellation.
Administration and support
DocumentedTELUS publishes sales and support paths, a partner SIP-trunk ordering portal and escalation resources. Its Universal Call Blocking guidance tells SIP Trunking customers to verify equipment with a SIP call trace and contact IP Trunking support when needed. Preserve portal roles, named escalation, purchased support hours, tickets, traces and the responsibility split among TELUS, the access provider and customer equipment.
SMS and MMS
Not verifiedTELUS Partner Solutions lists separate messaging products that can integrate with SIP Trunking, but the reviewed enterprise trunk pages do not establish SMS or MMS entitlement on trunk DIDs, sender registration, API access, throughput, webhook security, retention or price. Treat messaging as a separately ordered product and workflow.
Separate base sessions, bursts and site pooling
TELUS advertises purchased sessions, burstable trunks and enterprise capacity shared across locations for peak traffic. Record the contracted base sessions, burst ceiling and charges, simultaneous-call counting rule, CPS, site allocation, overflow, bandwidth and abuse controls separately.
A successful burst call does not establish the full ceiling, sustained load or restoration behavior. Validate numeric limits only under a TELUS-approved plan, while protecting emergency and critical traffic and preserving both provider and customer-edge evidence.
Turn geo-redundancy and failover into an acceptance plan
The product page describes redundancy, failover and a telco-grade geo-redundant platform. Record the ordered customer access, primary and alternate peers or destinations, DNS dependencies, trigger, timers, retry order, established-call expectation and restoration procedure.
Provider-core redundancy does not remove a single customer circuit, firewall, SBC, DNS resolver or PBX. Exercise only the authorized new-call failure case, confirm both directions and preserve the before, during and restored results rather than treating a marketing continuity statement as observed availability.
Keep number coverage, ports and delivered identity traceable
TELUS says its footprint covers 95 percent of Canada's population for new number requests and that DIDs can be added or ported. Keep the requested rate centre, number inventory, port order, activation state, delivery target, Request-URI, asserted identity, PBX normalization and final destination distinct.
Coverage language does not prove that one number or port is eligible or active. Retain dated serviceability and portability responses plus an authorized inbound and outbound trace for each accepted number pattern.
Accept encryption, media and caller identity independently
TELUS promotes private-network delivery or encryption over the Internet but does not publish a complete selected-interface TLS, certificate, SRTP, codec, DTMF or fax profile on the reviewed pages. Obtain the handoff and preserve transport negotiation, certificate validation, SDP and media evidence for each required call leg.
TELUS's Universal Call Blocking support advises SIP Trunking customers to verify their equipment through a SIP call trace. Keep Calling Line ID syntax and authorization separate from registration, number ownership and media acceptance; correct only the demonstrated layer.
Resolve emergency service, operations and commercial terms before cutover
The reviewed enterprise trunk pages do not define 911 activation, civic-address maintenance, nomadic use, callback routing, test procedure or outage limitations. Obtain the current emergency schedule for each number and site, follow the provider-approved validation method and keep an independently powered alternative calling path.
Bind portal roles, ordering, support and escalation, base sessions, burst charges, calls, numbers, ports, access, continuity, emergency service, taxes and term to dated account records. Separate TELUS enterprise SIP Trunking from Hosted SIP, One Voice+, Direct Routing and messaging products unless the exact order includes them.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- TELUS Business SIP Trunking ↗
- TELUS guide to SIP Trunking ↗
- TELUS Universal Call Blocking support ↗
- TELUS Partner Solutions ↗
- TELUS Partner Solutions support ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.