Start with the ordered access and service demarcation
TELUS describes delivery through a QoS-enabled private network or encrypted service over the Internet. Its R4 service terms place the demarcation at the applicable Customer Interface Unit when the VoIP service uses the specified connectivity. Those are order-specific access and responsibility boundaries, not interchangeable implementation profiles. Preserve the signed order, service terms, connectivity, demarcation device, required IP addresses, peers and customer equipment.
The public material does not publish one registrar, source-address rule, credential model, transport, codec or certificate profile for every customer. Do not infer REGISTER or static peering from the product label. The observed transaction and current handoff govern.
Documented service facts
Reviewed 2026-10-21. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed TELUS pages and R4 terms do not define one account credential or source-address authentication method, digest profile or certificate role. Preserve the current order, handoff, required IP addresses and observed exchange without publishing secrets.
SIP registration
Not verifiedThe reviewed public material does not establish whether an ordered trunk registers or uses static IP peering. Required-IP routability and the CIU demarcation are not registration proof; preserve peers, transport, Contact behavior and source controls from the exact handoff.
Inbound delivery
DocumentedTELUS describes inbound and outbound service and DIDs that may be added or ported. Number inventory, port state, trunk-group selection, provider attempt, customer-edge receipt, Request-URI and PBX normalization remain separate evidence.
Routing and failover
DocumentedTELUS service terms distinguish additional trunk groups for connectivity resiliency, customer-equipment resiliency and carrier SBC geo-redundancy. The public pages do not establish one trigger, timer, selection rule, restoration sequence or active-call result.
Number and regional availability
DocumentedTELUS markets broad Canadian number coverage. Preserve serviceability, number inventory, port state, delivery target and regulatory use for the exact site; population coverage is not account eligibility or activation proof.
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 markets purchased sessions, burstable trunks and shared multi-site capacity. These are not an account base-session count, burst ceiling, CPS, site allocation, bandwidth, price or measured sustained performance.
Emergency calling
Not verifiedThe R4 service terms contain a VoIP 9-1-1 section and identify a nomadic 9-1-1 portal. Portal address, calling identity, callback, ordered treatment, PBX route and provider-approved validation remain separate records.
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
DocumentedThe R4 terms identify an applicable CIU demarcation for specified connectivity and require routability to service IP addresses. Demarcation, provider attempt, edge receipt, PBX routing and media remain separately observable.
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.
Keep trunk groups and resiliency purposes distinct
The R4 terms describe additional trunk groups for connectivity resiliency, customer-equipment resiliency or carrier session-border-controller geo-redundancy. These are separate purposes. A second trunk group does not by itself prove diverse access, a redundant PBX, a carrier-core event or that the intended edge received a call.
Record each ordered trunk group, associated site, access, CIU or edge, carrier target, customer equipment, direction, priority and restoration process. Preserve the provider attempt and customer-edge result before changing Asterisk or FreePBX.
Trace provider delivery through the customer edge and PBX
TELUS requires traffic to be routable to the IP addresses required for the VoIP service. Routability, provider delivery, firewall receipt, PJSIP identification, endpoint selection, context, digit normalization and the first loaded route remain separate evidence.
For one authorized call, align provider records with the expected edge trace. Preserve source, Request-URI, To, asserted identity, Via, Contact, SDP and response sequence, then follow the effective identify, endpoint, transport, context and route. A reachable IP or SIP response does not prove correct routing or two-way media.
Separate platform redundancy, access and customer continuity
TELUS markets added redundancy, failover and a geo-redundant platform. The reviewed public pages do not publish one universal trigger, timer, response-code policy, retry order, customer-edge selection rule, restoration sequence or established-call result. Bind each behavior to the order and approved acceptance plan.
Carrier SBC geo-redundancy, trunk-group selection, customer connectivity, the CIU, customer equipment, PBX routing and number forwarding are different layers. An alternate answer proves only that a later leg answered; it does not identify the failing layer or prove normal service was restored.
Bind sessions, bursting and number state to account records
TELUS advertises purchased sessions, burstable trunks and enterprise capacity shared across locations for peak traffic. These statements do not establish an account base-session count, burst ceiling, call-start rate, site allocation, bandwidth, price or sustained performance. Keep them separate from PBX channels and observed simultaneous calls.
The guide says DIDs can be added or ported, but marketing coverage does not prove that one number is assigned, portable or active. Preserve the number inventory, port state, delivery target, caller-identity authorization and an authorized trace for each accepted pattern.
Keep VoIP 9-1-1 records outside ordinary call regression
The R4 service terms contain a dedicated VoIP 9-1-1 section and identify a nomadic 9-1-1 portal. A portal address, calling identity, ordered emergency treatment, PBX route, callback path and successful emergency result are distinct records. Preserve the current site and civic-address workflow, movement controls, power and access dependencies and provider-approved validation method.
Do not place an uncoordinated emergency call. Maintain an independently powered alternative method. No TELUS account, trunk group, CIU, route, call, media, burst, continuity event, emergency result, price, availability or compatibility was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- TELUS Business SIP Trunking ↗
- TELUS SIP Trunking Service R4 eContract service terms ↗
- 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.