Freeze one call and classify the first divergence
Record UTC and local time, calling and called identities, expected trunk and site, known provider state, observed destination, access state, eSBC receipt, PBX route, final response and media result. Redact credentials and personal data.
Classify the first unexpected observation: provider selected another active trunk; the expected access or eSBC did not receive the request; the request reached another edge; identity normalization changed the number; the PBX loaded another route; or an internal forward changed the destination.
Reconcile the ordered trunks and provider selection first
Cogeco advertises physical SIP geo-redundancy and automatic failover or reroute but does not publish one universal trigger, timer or route order for every customer. Confirm the current order, trunk and site inventory, expected active path, maintenance or incident state, effective time and provider call record.
Do not infer failover from an answered alternate leg. If the provider evidence shows another trunk was selected, retain the selection and restoration records before changing the customer PBX.
Separate access state from eSBC receipt
Private or dedicated access is a transport prerequisite, while the supplied eSBC is the SIP demarcation described by the product page. Record interface and route state, source and destination addresses, transport and the exact time window. Then determine whether the eSBC received the request.
A reachable interface or healthy access circuit does not prove that an INVITE arrived. An eSBC log entry does not prove the PBX received the same request or selected the intended route.
Correlate one SIP transaction without exposing secrets
At the authorized capture point, preserve Request-URI, To, asserted identity, From, Via, Contact, Call-ID, SDP and the response sequence. Align them with the provider record and eSBC evidence by time and correlation identifiers.
Cogeco’s security guidance treats remote access, passwords, DISA, voicemail, forwarding and calling-pattern records as protected operational evidence. Redact secrets and personal data before tickets or analytics. A CDR is useful correlation evidence, not proof of endpoint authorization, media delivery or intelligible audio.
Follow the first loaded PBX route
When the request reaches the PBX, inspect the effective endpoint or trunk match, context, digit normalization, inbound route, time condition, destination and any forwarding feature. For generated FreePBX configuration, compare the intended GUI record with loaded Asterisk objects instead of editing generated files directly.
Correct only the first demonstrated divergence. Do not broaden authentication, firewall or routing rules merely because the call appeared on an unexpected trunk.
Retest ordinary calls and keep 9-1-1 separate
After an authorized correction, retest the affected ordinary number and one unaffected control. Record provider selection, access state, eSBC receipt, PBX match, answer and each media direction separately, then verify restoration under the approved continuity plan.
Do not place an uncoordinated 9-1-1 call. Basic 911 address, per-DID or extension location, caller-provided location, calling identity, PBX route, callback and provider-approved validation require a separate workflow. No Cogeco trunk, eSBC, PBX, packet, call, failover, media or emergency result was inspected or tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Cogeco Business SIP Trunking ↗
- Cogeco specific terms — Business Phone, SIP Trunking and Hosted PBX ↗
- Cogeco PBX security guidelines for SIP Trunking customers ↗
- Cogeco Business 911 emergency-service limitations ↗
- Cogeco MLTS 9-1-1 best practices for HPBX and SIP/PRI customers ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.