Start with the private-access and eSBC demarcation
Cogeco describes SIP trunks delivered over its private, segmented and prioritized access facilities and says an enterprise SBC is supplied. Record the exact access, physical handoff, addressing, Cogeco eSBC ownership, customer PBX peer and operational demarcation before using a generic template.
Private access and an eSBC are meaningful controls, but they do not reveal the selected authentication, registration, transport, codec or TLS and SRTP profile. Preserve the accepted handoff and loaded state for each device that owns those settings.
Documented service facts
Reviewed 2026-10-08. Compare SIP trunk services →
SIP authentication
Not verifiedCogeco's public page describes a provider-supplied enterprise SBC but does not publish the ordered trunk's credential, digest realm or algorithms, source-address policy, certificate role or mutual-authentication behavior. Obtain the implementation handoff and map each trust decision to the Cogeco edge, supplied eSBC and customer PBX without exposing secrets.
SIP registration
Not verifiedThe reviewed public records do not state whether the selected Cogeco handoff uses REGISTER, static peering or another model. Record signaling peers, transport, Contact handling, expiry, qualification, DNS dependencies and source-address requirements from the accepted handoff and loaded eSBC or PBX state rather than inferring them from the SIP-trunk label.
Inbound delivery
DocumentedCogeco advertises local numbers for distant locations and says geo-redundancy can reroute incoming calls to an active trunk. Those claims do not establish an account's assigned inventory, completed port, delivered Request-URI, asserted identity, PBX normalization or the active failover destination. Preserve the order, number record and authorized traces for every accepted pattern.
Routing and failover
DocumentedCogeco describes physical SIP geo-redundancy and automatic failover or reroute for voice traffic. The page does not define one customer's sites, access diversity, trigger, timer, route order, established-call behavior or restoration sequence. Bind each path to the current design and exercise only a provider-approved new-call failure case.
Number and regional availability
DocumentedCogeco says service is available where technology permits and advertises local numbers for remote markets. That does not prove that one address, rate centre, number, port request, private-access facility or failover site is eligible. Retain dated serviceability, inventory and portability responses for the exact requirement.
Audio codecs and DTMF
Not verifiedThe reviewed pages 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, payload mapping, RTP evidence and decoded digit results for every required call path.
T.38 fax
Not verifiedThe reviewed Cogeco SIP-trunk and emergency-service pages do not establish T.38 or audio-fax entitlement, direction, switchover, gateway compatibility, redundancy or page limits. Treat fax as a separately ordered and accepted workflow using the current interface record.
Signaling and media encryption
Not verifiedCogeco describes private, segmented, prioritized access and a supplied eSBC as security controls. Those network and edge controls do not by themselves establish SIP TLS versions, certificate validation, client certificates, SRTP, keying or protection across every call leg. Record the ordered access and application-layer controls separately and preserve handshake and SDP evidence for the actual path.
Concurrent calls and call starts
DocumentedCogeco says customers can increase or decrease SIP channels. A channel order is not a published call-start rate, burst allowance, bandwidth entitlement, eSBC capacity or measured result. Use the dated order and implementation design for channels and limits, then validate numeric behavior only under a Cogeco-approved load plan.
Emergency calling
DocumentedCogeco states that SIP Trunking uses Basic 911: the address is not transmitted automatically, the caller must provide it verbally, and the account service address is the fallback when the caller cannot communicate. Power, network, Internet or account outages can limit access, and calls originating outside Canada cannot be routed to a foreign emergency centre. Multi-site and nomadic deployments require location-specific records, suitable caller identity, user notices and a Cogeco-coordinated validation method.
Pricing model
Not verifiedCogeco describes a customized solution and notes that activation, network connection and installation charges may apply, but the reviewed page does not publish a complete SIP-trunk price. Use a dated quote, contract and bill for access, channels, numbers, ports, usage, failover, eSBC, emergency service, support, taxes, term, renewal and cancellation.
Administration and support
DocumentedCogeco directs prospective customers to a business specialist and existing customers to My Account, while the service design includes provider-managed access and supplied eSBC equipment. Preserve portal roles, equipment ownership and return terms, change authority, support and escalation contacts, maintenance notices, tickets and the responsibility split among Cogeco, the customer PBX and site network.
SMS and MMS
Not verifiedThe reviewed Cogeco SIP-trunk 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 channels, call starts and edge capacity separate
Cogeco says the number of SIP channels can be increased or decreased. Treat ordered channels as the simultaneous-call entitlement until the current contract states otherwise; do not turn that statement into a call-start rate, burst allowance, bandwidth figure or eSBC performance result.
Capture channels, calls per second, bursts, access bandwidth, PBX resources and eSBC capacity as separate evidence. Validate numeric behavior only through an approved load plan.
Turn geo-redundancy into a route-specific acceptance plan
Cogeco advertises physical SIP geo-redundancy and automatic failover or reroute, including inbound delivery to an active trunk and outbound routing. That portfolio statement does not define the ordered sites, access diversity, trigger, timer, retry order, established-call result or restoration process.
Map the actual primary and alternate paths and exercise only a provider-approved new-call failure. Preserve before, during and restored evidence, and do not treat provider-core redundancy as proof that the customer edge, local power or PBX is redundant.
Trace numbers and local presence to the PBX route
The product page describes local numbers for distant locations. Preserve the assigned number, portability state, delivery target, Request-URI, asserted identity, normalization and matched PBX route as one traceable chain.
A quoted local presence or an account row does not prove that the live trunk delivers the expected identifier. Keep ordinary caller identity, callback identity and emergency identity distinct.
Treat Basic 911 and MLTS location as deployment data
Cogeco says SIP Trunking uses Basic 911, which does not automatically transmit the caller's address. The caller must state the location, while the account service address becomes a fallback when communication is not possible. Power, network, Internet and account interruptions can limit service, and a call outside Canada cannot be routed to an emergency centre in the caller's country.
Cogeco's MLTS guidance calls for direct 9-1-1 dialing, direct PSAP routing, current address records for primary and other locations, suitable caller identity and location-aware handling for nomadic softphones. Coordinate any validation with Cogeco and maintain an independently powered alternative path.
Resolve media, operations and commercial terms independently
The public pages do not define the selected registration, authentication, codec, DTMF, fax, signaling-protection, media-protection or messaging profile. Obtain those facts from the implementation handoff and retain offer-answer, packet and application evidence for required workflows.
Bind portal roles, supplied equipment, support, access, channels, numbers, ports, failover, emergency service, taxes, installation, term and cancellation to current account records. Marketing descriptions of security, reliability or 100 percent connections are not converted into measured availability, compatibility or performance results.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Cogeco Business SIP Trunking ↗
- Cogeco Business 911 emergency-service limitations ↗
- Cogeco MLTS 9-1-1 best practices for HPBX and SIP/PRI customers ↗
- Cogeco Business terms and conditions index ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.