Start with the ordered access and supplied eSBC demarcation
Cogeco currently describes SIP trunks over its private, dedicated, segmented and prioritized access facilities and says it supplies an enterprise session border controller. The product page also describes fibre and cable delivery contexts. Preserve the signed order, physical access, demarcation, addressing, Cogeco eSBC ownership and management, customer PBX peer and operational responsibility split.
Private access and an eSBC are meaningful controls, but they do not publish one authentication, registration, transport, codec, certificate or media-encryption profile for every order. The accepted handoff and loaded state govern; a supplied eSBC is not proof that a specific request reached the PBX.
Documented service facts
Reviewed 2026-10-21. Compare SIP trunk services →
SIP authentication
Not verifiedCogeco describes private access and a supplied eSBC but does not publish one selected trunk credential, source-address policy, digest realm, certificate role or mutual-authentication method. Preserve the accepted handoff and observed exchange without exposing secrets.
SIP registration
Not verifiedThe reviewed public records do not establish whether the selected Cogeco service uses REGISTER, static peering or another handoff. Preserve peers, transport, Contact handling, expiry, qualification, DNS dependencies and source controls from the accepted design.
Inbound delivery
DocumentedCogeco advertises local numbers for distant locations and inbound delivery to an active trunk under geo-redundancy. Number inventory, port state, provider selection, eSBC receipt, Request-URI, asserted identity and PBX normalization remain separate evidence.
Routing and failover
DocumentedCogeco advertises physical SIP geo-redundancy and automatic failover or reroute for inbound and outbound voice traffic. The public page does not publish one account’s triggers, timers, route order, established-call behavior or restoration sequence.
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 verifiedPrivate access and the supplied eSBC are distinct from the PBX security controls in Cogeco guidance: remote-access logs, DISA credentials, CDR review, toll restrictions, voicemail ports, through-dialing, forwarding limits, dormant codes and physical security.
Concurrent calls and call starts
DocumentedCogeco says SIP channels can be increased or decreased. Ordered channels, active calls, call attempts, calls per second, access bandwidth, eSBC sessions and PBX resources remain different quantities.
Emergency calling
DocumentedCogeco says SIP Trunking uses Basic 911 and requires caller-provided location, current primary and per-DID or extension addresses, direct dialing, direct PSAP routing, user notices and coordination before endpoint moves. Keep provider-approved validation separate from ordinary regression.
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
DocumentedPreserve supplied-eSBC ownership, access and PBX responsibilities, provider and customer records, change authority, support contacts, maintenance state and restoration approval. A provider status, CDR, eSBC receipt, PBX route and media result remain separate evidence.
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, access, eSBC and PBX capacity separate
Cogeco says customers can increase or decrease SIP channels. The product page does not turn that channel order into a universal call-start rate, burst allowance, access-bandwidth figure, eSBC performance limit or PBX resource guarantee. Preserve the ordered channel count and effective time separately from active calls, call attempts, calls per second, access bandwidth, eSBC sessions and PBX channels.
A rejected or rerouted call does not by itself prove channel exhaustion. Align provider records, eSBC evidence and PBX counters in the same time window before changing capacity.
Treat geo-redundancy as provider selection evidence
Cogeco advertises physical SIP geo-redundancy and automatic failover or reroute so inbound calls can terminate on an active voice trunk and outbound calls can be routed. That portfolio statement does not publish one customer’s trunks, sites, access diversity, health criteria, timer, retry order, established-call behavior or restoration sequence.
Provider-core selection, customer access, eSBC receipt, PBX routing and local forwarding remain separate continuity layers. An alternate answer proves that one later leg answered; it does not identify the trigger, prove that another trunk was attempted or show that the primary path recovered.
Trace the selected trunk through the eSBC and PBX
For one authorized call, preserve time, calling and called identities, expected trunk, provider result and any correlation identifiers. At the customer edge, retain source and destination addresses, transport, Request-URI, To, asserted identity, Via, Contact, SDP and the complete response sequence. Then follow the effective endpoint match, context, normalization and first loaded route.
A provider status, eSBC receipt, SIP response, PBX CDR, answer and two-way media are different observations. Correct only the first demonstrated divergence, and do not infer live delivery from a local-number inventory or marketing compatibility statement.
Keep PBX fraud controls distinct from trunk authentication
Cogeco’s PBX security guide discusses remote-access logs, DISA credentials, calling patterns, CDR review, toll restrictions, voicemail ports, through-dialing, dormant access codes, external call forwarding and physical equipment security. The voice terms separately assign responsibility for attached-device security and charges arising from unauthorized use.
Those operational controls do not reveal the trunk’s credential, source-address policy, certificate role or registration model. Preserve secrets outside broad logs, restrict evidence access and use CDRs as correlation records rather than proof of authorization, edge receipt or decoded audio.
Treat Basic 911 and MLTS location as separate records
Cogeco’s current limitation page says SIP Trunking uses Basic 911: the address is not automatically transmitted, the caller must provide location verbally, and the last service address becomes a fallback if the caller cannot communicate. Power, network, Internet or account interruption can limit service, and calls originating outside Canada cannot be routed to a foreign emergency centre.
The MLTS page calls for direct 9-1-1 dialing, direct PSAP routing, current primary and per-DID or extension civic addresses, coordination before moving or distributing endpoints and an on-site endpoint-location registry. Keep the address record, calling identity, PBX route, callback, user notice and provider-approved validation distinct. Do not place an uncoordinated emergency call.
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 terms and conditions index ↗
- Cogeco specific terms — Business Phone, SIP Trunking and Hosted PBX ↗
- Cogeco Business 911 emergency-service limitations ↗
- Cogeco MLTS 9-1-1 best practices for HPBX and SIP/PRI customers ↗
- Cogeco PBX security guidelines for SIP Trunking customers ↗
- Cogeco Business Managed Telephony support and security-guideline index ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.