Name the ordered voice product before designing
Rogers' public material describes a PBX-facing SIP Trunking service, while the same schedule separately describes Microsoft 365 Business Voice with SIP Trunking. Those are not interchangeable architectures: the Microsoft offer describes Rogers-managed SBCs and Internet access, whereas the PBX trunk describes delivery to a Site over ordered access. Current Teams Phone Mobile, Operator Connect and other hosted voice offers also have different ownership boundaries.
Record the exact product, schedule edition, Site, access type, demarcation, PBX or IAD role, number inventory and signed options. A feature from an adjacent Rogers voice offer is not evidence for the PBX trunk.
Documented service facts
Reviewed 2026-10-06. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public sources do not publish one digest credential, certificate identity or source-address policy for every Rogers Business SIP Trunking order. The schedule refers to confidential access codes or passwords but does not define a universal PBX-facing authentication flow. Obtain the current implementation record and protect credentials and peer addresses.
SIP registration
Not verifiedThe public overview and April 2021 schedule establish a PBX-facing SIP service delivered at a Site, but not whether the current order uses REGISTER, static peering or another method. Preserve the ordered access type, demarcation, peer addresses, transport, CPE role and refresh behavior from Rogers' current implementation documents.
Inbound delivery
DocumentedThe schedule defines purchased Direct Inward Dial numbers and SIP sessions connecting the customer location to the PSTN. It does not establish one current Request-URI, P-Asserted-Identity, Diversion, number-format or PBX-destination rule. Record the delivered identifiers and matching policy for the actual order.
Routing and failover
DocumentedThe April 2021 schedule describes separately purchased peer failover, load-balancing, overflow and emergency-redirect features, with public/private access constraints for paired Sites. These are orderable schedule terms, not proof that a current account includes them, that access paths are diverse or that established calls survive. Confirm the signed order and test approved new-call failures.
Number and regional availability
DocumentedThe schedule describes Canadian DIDs, Canadian rate centres and availability within Rogers' local footprint for the adjacent Microsoft 365 offer. It does not establish serviceability, inventory or port eligibility for a particular address or number today. Use a dated serviceability result, order and port response.
Audio codecs
Not verifiedThe reviewed public sources do not publish one current codec, packetization, DTMF, RTP-addressing or transcoding profile for every access and PBX combination. Obtain the current interface specification and preserve the actual SDP offer, answer, RTP path and decoded audio for each PBX-facing leg.
T.38 fax
Not verifiedThe April 2021 schedule describes an optional integrated access device for legacy PBX conversion, but the reviewed sources do not establish T.38 entitlement, pass-through behavior, gateway settings, page profile or current support for a particular fax path. Validate the exact design and delivery report.
Signaling and media encryption
Not verifiedRogers describes dedicated access that bypasses public-Internet congestion and a range of fibre or cable delivery models. That does not itself prove SIP TLS, certificate validation, SRTP, media encryption or downgrade policy on the PBX-facing leg. Obtain the current security specification and inspect every signaling and media hop.
Concurrent calls and call starts
DocumentedThe schedule defines purchased SIP Sessions as PRI-channel equivalents and says required IP bandwidth depends on the session quantity. This documents an ordering unit, not observed simultaneous calls, calls per second, burst tolerance or PBX/SBC capacity. Keep sessions, active calls, call starts and access bandwidth separate in acceptance evidence.
Emergency calling
DocumentedThe schedule requires a Canadian 9-1-1 Emergency Address for each SIP Trunking office location and explains specialized-call-centre routing and customer maintenance duties. The exact current emergency terms, registered address, callback identity and permitted test process remain account- and location-specific; use provider-approved testing.
Pricing model
Not verifiedThe April 2021 schedule describes per-session and monthly billing, usage charges, optional features, access and termination terms, but it is not a current quote. Obtain a dated proposal and signed agreement for sessions, DIDs, usage, access, equipment, continuity, emergency service, support, minimums, taxes, renewal and cancellation.
Administration and support
Not verifiedThe reviewed sources discuss installation, interoperability testing, billing, service changes and reporting, but they do not establish one current portal, support tier, response target or escalation path for every order. Preserve the acceptance window, current contacts, service demarcation, change control and support schedule from the signed agreement.
SMS and MMS
Not verifiedThe schedule's general SIP definition mentions messaging applications, but the reviewed PBX-trunk sources do not establish SMS or MMS entitlement on DIDs, API access, sender registration, throughput, webhook security or price. Do not convert a protocol definition into a service claim.
Treat the Site and access circuit as part of the service record
The April 2021 schedule says SIP Trunking is delivered to a Site over dedicated IP access routed across Rogers' fibre or cable network, with fibre, Ethernet-over-cable or Rogers Business Internet among the stated models. It also defines the demarcation as the provider or partner device port facing the customer network. Preserve the current order because technology, interface, addressing, availability and provider boundary can differ by location.
A dedicated or provider-managed access path does not prove TLS or SRTP, and a statement about network redundancy does not prove diverse entrances, routes or power at one Site. Map every failure domain from PBX through LAN, edge, access and provider demarcation.
Keep sessions, bandwidth and call rate separate
The schedule defines a SIP Session as a purchased unit comparable to one PRI voice channel and says more sessions may require more IP bandwidth. Use the ordered session quantity as a commercial capacity input, not as proof of observed concurrency, successful media or call-start rate. Measure active calls, call attempts per second, codec bandwidth, PBX channels, SBC resources and access utilization separately.
The reviewed public sources do not publish one universal authentication, registration, codec, DTMF, TLS, SRTP or T.38 profile. Obtain the current implementation specification and preserve signaling, SDP, RTP, decoded audio and fax results for the actual PBX-facing legs.
Purchase, configure and test continuity explicitly
The April 2021 schedule describes optional peer failover, load balancing, overflow and emergency redirect. It also restricts paired continuity Sites to compatible public or private access types and separately discusses access, route and POP diversity. Confirm which options remain available and are actually in the signed order; do not infer them from general resiliency language.
Document primary and alternate peers, route order, retryable responses, timers, access paths, provider action, restoration and monitoring. Test approved new-call failures in both directions and report established-call behavior separately.
Use current account evidence for numbers, 9-1-1 and price
The schedule describes purchased DIDs and requires a Canadian 9-1-1 Emergency Address for each SIP Trunking office location. It explains specialized-call-centre handling and the customer's duty to maintain accurate location data. Confirm the current registered address, outbound identity, callback route and provider-approved test procedure for every Site.
Use dated serviceability, port results, quote and signed agreement for numbers, sessions, usage, access, equipment, optional continuity, emergency service, support, term and cancellation. The reviewed material does not establish SMS or MMS on trunk DIDs. No account, order, circuit, trunk, number, PBX, call, media, fax, security, failover, emergency workflow, message, availability, price or support response was inspected or tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Rogers Business SIP trunking overview ↗
- Rogers Business Fixed Network Terms — SIP Services schedule (April 2021) ↗
- Rogers Business phone-fraud guidance ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.