Start with the accepted access and implementation boundary
SaskTel's current page lists IP-VPN, infiNET, DSL, VPLS and an Internet connection from any provider as possible access choices. Item 500.23 requires a customer data network that meets SaskTel bandwidth and performance requirements and says its suitability must be assessed. Record the ordered access, demarcation, assessment, voice and data subnets, PBX or SBC, peers and responsibility split before using a template.
The public records establish SIP trunks to IP-enabled customer equipment but not one universal authentication, registration, transport, codec or certificate profile. Obtain the accepted implementation handoff and prove the loaded PBX or SBC state against it.
Documented service facts
Reviewed 2026-10-08. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed SaskTel product and tariff records do not define the selected trunk's credential or source-address authentication method, digest realm or algorithms, certificate role, mutual authentication or allowlist. Obtain the implementation handoff and map each secret or trusted address to its PBX, SBC and provider owner without exposing it.
SIP registration
Not verifiedThe public records establish SIP trunks between SaskTel and IP-enabled customer equipment but do not say whether the selected service uses REGISTER, static peering or another handoff. Record peers, transport, Contact behavior, expiry, qualification, DNS dependencies and source-address rules from the accepted implementation record rather than inferring them from the service name.
Inbound delivery
DocumentedSaskTel lists inbound and outbound Calling Line Identification and Calling Name Identification, includes one primary number in the tariff description and provides additional DIDs when ordered. Those features do not establish one account's assigned inventory, port state, delivered Request-URI, asserted identity or PBX normalization. Preserve the order, number record and authorized traces for accepted patterns.
Routing and failover
DocumentedSaskTel describes optional RTM overflow within the serving central-office switch and a separate Emergency Call Redirection feature that moves voice traffic to a predetermined alternate business location only after a customer request during an emergency. Neither establishes automatic customer-access failover, trigger timers, established-call survival or restoration. Bind every continuity path to the order and an approved new-call exercise.
Number and regional availability
DocumentedThe tariff limits service to locations with suitable SaskTel facilities, qualifying exchange areas and a customer data network that meets SaskTel requirements. The current product page notes select business services outside Saskatchewan but does not prove that this service, one address, number, rate centre or port is eligible. Retain dated serviceability and portability responses for the exact requirement.
Audio codecs and DTMF
Not verifiedThe reviewed public records do not publish a complete current codec, packetization, DTMF, early-media, transcoding or media-address profile for the selected interface. Obtain the implementation handoff and retain both SDP bodies, negotiated payload mapping, RTP evidence and decoded digit results for each required path.
T.38 fax
Not verifiedThe reviewed SaskTel pages and Item 500.23 do not establish T.38 or audio-fax entitlement, direction, switchover, gateway compatibility, redundancy or page limits for the selected trunk. Treat fax as a separately ordered and accepted workflow using the current interface record.
Signaling and media encryption
Not verifiedSaskTel describes a VPN-based service and currently permits several SaskTel access products or an Internet connection from any provider. Those access descriptions do not establish SIP TLS, certificate validation, client certificates, SRTP, keying or protection across every call leg. Keep private access, Internet transport and application-layer encryption separate until the selected handoff proves each control.
Concurrent calls and call starts
DocumentedThe tariff ties required access bandwidth to total concurrent calls and defines optional inward and outward Route Traffic Managers that limit simultaneous calls. The current page says capacity can be adjusted with call volume. None of those statements publishes one account's trunks, RTM thresholds, calls per second, bursts or bandwidth. Use the order and an approved load plan for numeric acceptance.
Emergency calling
DocumentedItem 500.23 describes non-standard 9-1-1: the caller's location and number are not transmitted automatically, the caller must provide them orally, and a registered service address is a fallback when contact cannot be re-established. Calls from outside Canada cannot be completed by the operator. Power, Internet or account outages can prevent service, and the customer must inform users of the limitations. Confirm current account activation, registered addresses and the provider-approved validation method for every site and number.
Pricing model
DocumentedThe tariff provides monthly, three-year and five-year service structures, per-trunk and implementation charge categories, optional RTM and overflow charges, access-fee conditions and early-termination rules; some ranges are filed in confidence. This is not a complete account price. Use a dated quote, contract and bill for trunks, access, numbers, usage, features, emergency service, equipment, support, taxes, term, renewal and cancellation.
Administration and support
DocumentedSaskTel includes trunk-group up/down monitoring and requires a customer troubleshooting contact. The tariff assigns customer-provided equipment and LAN operation to the customer, requires network suitability assessment and calls for unique voice and data subnets when troubleshooting. Preserve monitoring recipients, assessment results, portal or change authority, implementation contacts, tickets and the responsibility split among SaskTel, the access supplier and customer equipment.
SMS and MMS
Not verifiedThe reviewed SaskTel IP Trunking records do not establish SMS or MMS entitlement on trunk numbers, sender registration, API access, throughput, webhook security, retention or price. Treat messaging as a separate product and workflow unless the exact order and current documentation say otherwise.
Separate trunks, RTM limits, bandwidth and call starts
SaskTel defines inward and outward Route Traffic Managers as optional controls on simultaneous calls. Inward RTM can choke selected call categories before they reach the trunk group; outward RTM can limit calls to a PSTN connection or toll plan. Required access bandwidth is tied to total concurrent calls.
Trunks, simultaneous calls, inward and outward RTM thresholds, call attempts, calls per second, bursts and bandwidth are different quantities. Capture each ordered value and validate numeric behavior only under a SaskTel-approved plan.
Keep identity, numbers and delivered routing traceable
The service page lists inbound and outbound Calling Line and Calling Name Identification, with optional DIDs. The tariff includes one primary number and describes additional Direct-In-Dial numbers. Those features do not prove the assigned inventory, completed port, delivered Request-URI, asserted identity, number normalization or final PBX route.
Retain the current number order and port state, then preserve authorized inbound and outbound traces for every accepted pattern. Keep display identity, emergency identity and number ownership as separate evidence.
Do not merge overflow with emergency redirection
Item 500.23 describes overflow from an RTM to a customer-defined destination within the same serving central-office switch. It separately describes Emergency Call Redirection to a predetermined alternate business location, activated only after the customer requests it during an emergency.
Neither description proves automatic access failover, customer-edge diversity, trigger timers, established-call survival or restoration. Document each ordered path and exercise only an approved new-call case, preserving the before, during and restored result.
Treat SaskTel IP Trunking 9-1-1 as a distinct workflow
The tariff describes non-standard 9-1-1. The caller's location and number are not transmitted automatically; the caller must provide them orally. If the caller cannot communicate or the call disconnects and contact cannot be restored, SaskTel uses the registered service address. Calls from outside Canada cannot be completed by the operator.
Power failure, Internet outage or account suspension can prevent service, and the customer must inform users of the limitations. Confirm current activation and registered addresses, follow SaskTel's approved validation process and retain an independently powered alternative calling path.
Resolve security, media, support and price from current account records
A VPN or private-access description does not establish SIP TLS or SRTP, and an Internet access option does not define the selected protection profile. The reviewed public records also do not publish complete authentication, registration, codec, DTMF, fax or messaging details. SaskTel's managed SBCaaS is a related service, not an included IP Trunking feature unless ordered.
Bind monitoring, change authority, support contacts, trunks, access, RTM, overflow, numbers, usage, emergency service, equipment, taxes and term to the current quote, contract and bill. Retain Item 500.23 as a service and responsibility boundary while recognizing that its linked pages carry 2016 and 2017 revision dates.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- SaskTel IP Trunking ↗
- SaskTel General Tariff competitive-services index ↗
- SaskTel CRTC 21412 Item 500.23 — IP Trunking Service ↗
- SaskTel Ethernet Services ↗
- SaskTel Session Border Controller as a Service ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.