Start with the ordered access and assessed customer network
SaskTel currently 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. The customer remains responsible for customer equipment and voice traffic on the LAN. Preserve the order, access, assessment, demarcation, voice and data subnets, PBX or SBC and responsibility split.
The public records establish SIP trunks to IP-enabled customer equipment but do not publish one authentication, registration, transport, codec, certificate or source-address profile for every order. The accepted implementation handoff and observed exchange govern.
Documented service facts
Reviewed 2026-10-21. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed SaskTel product and tariff records do not define one selected trunk credential, source-address authentication method, digest realm, certificate role or allowlist. Preserve the accepted implementation handoff and observed exchange without exposing secrets.
SIP registration
Not verifiedThe public records establish SIP trunks to customer equipment but do not say whether the selected service uses REGISTER, static peering or another handoff. Preserve peers, transport, Contact behavior, expiry, qualification and source controls from the accepted handoff.
Inbound delivery
DocumentedSaskTel lists calling-line and calling-name identification, one primary number in the tariff description and optional DIDs. Number inventory, port state, RTM scope, overflow selection, provider attempt, Request-URI and PBX normalization remain separate evidence.
Routing and failover
DocumentedItem 500.23 describes RTM overflow within the same serving central-office switch and separately describes customer-requested Emergency Call Redirection to a predetermined alternate business location. Neither establishes automatic access failover, universal triggers, active-call survival or restoration.
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
DocumentedInward and outward RTM are simultaneous-call controls, while access bandwidth is tied to total concurrent calls required. Ordered trunks, thresholds, active calls, call attempts, PBX channel limits and bandwidth remain distinct.
Emergency calling
DocumentedItem 500.23 describes non-standard 9-1-1 with caller-provided location and number plus registered-address fallback under stated conditions. Preserve the current service address, PBX route, callback, alternative calling method and SaskTel-approved validation workflow.
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 troubleshooting contact; the tariff assigns customer equipment and LAN operation to the customer and requires assessed network suitability. Monitoring, provider selection, edge receipt, PBX routing and media remain separate evidence.
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.
Keep RTM thresholds, trunks, calls and bandwidth separate
Item 500.23 describes inward and outward Route Traffic Managers as optional simultaneous-call controls. Inward RTM can choke selected call categories before they reach the IP Trunking system group. Outward RTM can limit calls to a PSTN connection or certain toll plans. The tariff separately ties sufficient access bandwidth to the total concurrent calls required.
An RTM threshold is not the same as a purchased trunk count, call attempt rate, PBX channel limit, access bandwidth or observed active-call count. Preserve the ordered direction, scope, threshold, affected category or destination and effective time before diagnosing capacity.
Treat overflow as a defined RTM destination
The tariff describes overflow from an RTM to another customer-defined destination within the same serving central-office switch. That is a bounded routing control, not universal access failover or proof of diverse facilities. Preserve the selected RTM, overflow destination, number treatment, provider attempt, customer-edge receipt and first loaded PBX route.
An alternate answer proves only that one later leg answered. It does not prove why the RTM threshold was reached, that every eligible call overflowed, that the primary trunk recovered or that established calls survived.
Do not merge overflow with emergency redirection
Item 500.23 separately describes Emergency Call Redirection to a predetermined alternate business location after a customer request during an emergency. SaskTel emergency-redirection material likewise limits the service to previously specified locations, available facilities and capacity, with access at the alternate location already in place.
RTM overflow, customer-requested emergency redirection, provider trunk monitoring, customer access, PBX routing and number forwarding are different controls. Record who requested a change, the approved locations, effective time, affected numbers, restoration authority and observed new-call result.
Trace monitoring and number evidence through the PBX
The current product page lists trunk-group up/down monitoring, calling-line and calling-name identification, optional DIDs, RTM and overflow. Monitoring state, DID inventory, provider selection, edge receipt, identity normalization and PBX routing remain separate evidence.
For one authorized call, align the current number and RTM records with the provider attempt and expected edge trace. Preserve Request-URI, To, asserted identity, source, Via, Contact, SDP and responses, then follow the effective PJSIP identify, endpoint, context and first loaded route. A provider monitor or SIP response does not prove correct routing or two-way media.
Keep non-standard 9-1-1 outside ordinary routing regression
Item 500.23 describes non-standard 9-1-1 in which location and telephone number are not automatically transmitted and the caller must provide them orally; it also records power, Internet, suspension and physical-location limitations. Those older tariff pages remain listed through the current tariff index, but the current order, service address and SaskTel-approved process govern.
Do not use an uncoordinated emergency call to test RTM, overflow or redirection. Keep registered service address, calling identity, PBX route, callback, alternate calling method and provider-approved validation as separate records. No SaskTel account, trunk, RTM, overflow, redirection, call, media or emergency result was tested for this guide.
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 index for all tariffs — effective June 17, 2026 ↗
- SaskTel Ethernet Services ↗
- SaskTel Session Border Controller as a Service ↗
- SaskTel Special Facilities Tariff 21413 index ↗
- SaskTel Emergency Voice Local Network Access Redirection — Item 1000.03 ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.