Identify the ordered product, Site and access boundary
Rogers documents a PBX-facing SIP Trunking service delivered to a Site over an ordered fibre, Ethernet-over-cable or Rogers Business Internet access model. The same schedule separately describes Microsoft 365 Business Voice with SIP Trunking, including Rogers-managed SBCs and different Internet and user boundaries. Do not transfer a control, emergency workflow or quality statement between those products without current order evidence.
Preserve the product name, schedule edition, agreement, Site, access type, demarcation, PBX or IAD, peer addresses, DID inventory and responsible owner. A provider-managed or private path does not by itself prove PBX-facing TLS, SRTP, diverse entrances or successful media.
Documented service facts
Reviewed 2026-10-20. 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
DocumentedRogers documents purchased DIDs and provider-side delivery, but public material does not define one current Request-URI or identity pattern for every order. Preserve DID inventory, port state, provider-selected peer, edge receipt and PBX route separately.
Routing and failover
DocumentedRogers separately documents SIP Peer Failover, Peer Load Balancing, Peer Overflow and Emergency Redirect; a branded sheet also uses Access Failover, Enterprise Failover and DID Number Re-route labels. Map the signed order instead of assuming equivalence, inclusion, triggers, timers or precedence.
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
DocumentedRogers defines purchased SIP Sessions and relates access bandwidth to session quantity. Provider CDRs, concurrent calls, call attempts, PBX channels, SBC resources and capacity-triggered overflow remain separate observations; no account capacity or load result was tested.
Emergency calling
DocumentedRogers requires a Canadian emergency address for each SIP Trunking office location and describes specialized-call-centre handling plus verbal location confirmation. A continuity destination is not automatically the current emergency address; preserve registered location, calling identity, callback and approved validation separately.
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 verifiedRogers advertises customer-portal authentication/account-code controls, CDR reporting, interoperability testing and 24/7/365 support. Those statements do not prove one portal role, report field, acceptance result, PBX compatibility or support response for a current account.
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.
Name the exact purchased continuity control
The April 2021 schedule separates SIP Peer Failover, SIP Peer Load Balancing, SIP Peer Overflow and Emergency Redirect. Failover redirects identified incoming trunk traffic during an emergency or outage; load balancing distributes calls across active peers; overflow acts when the primary trunk is fully utilized; Emergency Redirect is an as-needed customer-identified emergency action. The branded information sheet uses Access Failover, Enterprise Failover, DID Number Re-route and SIP Trunk Overflow labels.
Treat those names as document-specific until the signed order maps them. Preserve covered Sites, peers, DIDs, destination, trigger, approval, activation state and restoration procedure. The public material does not publish one common probe, SIP-code matrix, timer, precedence rule or established-call result.
Keep peer routing and physical diversity separate
The schedule requires paired continuity Sites to use compatible public or private access models. It separately describes access diversity, route diversity and POP diversity, all subject to survey and order. A secondary peer can still share a building entrance, access segment, router, power source or provider POP unless the accepted design proves otherwise.
Map the PBX, LAN, edge, demarcation, primary and secondary access, geographic routes, POPs and provider peers. A call answered at another Site proves only that one new call reached that destination; it does not prove the primary access recovered or that an established call survived.
Separate sessions, utilization, CDRs and end-to-end capacity
Rogers defines a SIP Session as a purchased virtual connection comparable to one PRI voice channel and says required IP bandwidth depends on the session quantity. The information sheet advertises scaling to large session counts and a customer portal with CDR reporting. These are order and provider-record boundaries, not proof of one account's active calls, call-start rate, codec bandwidth, PBX channels, SBC resources or spare capacity.
Retain the ordered sessions, active-call observations, call attempts, CDR filters, timezone, access utilization, PBX channel state and provider identifiers separately. A customer case study records one customer's pilot, topology and results; it is not a universal availability, quality, savings or compatibility result.
Follow one DID from provider selection to the first PBX route
For a wrong-peer or unexpected-redirect complaint, freeze one DID, caller, UTC and local time, expected Site, ordered continuity option, primary and alternate peer state, provider call identifier and relevant CDR. Match any provider attempt to an authorized customer-edge trace. If no matching request reaches the edge, keep the investigation with number inventory, provider selection, access or continuity state.
If a request arrives, preserve its source, Request-URI, To and asserted identity, SDP and response sequence. Then follow the effective PJSIP identify, endpoint, transport, context, digit normalization and first loaded Asterisk or FreePBX route. Keep provider selection, edge receipt, PBX route, answer and media as separate outcomes.
Keep emergency location, commercial terms and tests bounded
The schedule requires a Canadian emergency address for each SIP Trunking office location and describes specialized-call-centre handling, verbal location confirmation, callback limitations and service dependencies. A continuity destination, alternate Site or forwarded DID is not automatically the current emergency address. Preserve the registered location, accepted calling identity, user notice, callback route, power and access dependencies and provider-approved validation separately.
The April 2021 schedule and branded material are dated evidence, not a current quote or entitlement record. No Rogers account, order, Site, peer, DID, CDR, PBX, packet, continuity event, emergency result, price, availability, compatibility or support response was inspected or tested.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Rogers Business Fixed Network Terms — SIP Services schedule (April 2021) ↗
- Rogers Business SIP Trunking information sheet ↗
- Rogers Business SIP trunking overview ↗
- Rogers Microsoft 365 Business Voice over SIP trunking ↗
- Rogers SIP Trunking Pizza Pizza case study ↗
- Rogers Business phone-fraud guidance ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.