Freeze one attempt and the exact service identity
Record UTC and local time, Swisscom legal entity, ordered Enterprise SIP variant, site, access, service access point, router, eSBC or SBC, PBX and software versions, called and calling numbers, direction, expected route, answer and media result. Redact credentials and personal data.
Do not substitute Enterprise SIP Cloud, Smart Business Connect or Enterprise Connect SIP-Trunk documentation because it contains a familiar field. Classify the first unexpected state: order or activation, access, SBC or PBX reachability, number or identity delivery, PBX selection, answer, or media.
Verify the access and SBC responsibility boundary
Compare the current order and accepted design with loaded state. For Standard or WAN, identify the Enterprise SIP eSBC path. For Unbundled, identify the approved customer SBC. For Shared Connectivity, identify the application service provider SBC and separate contract. Preserve the actual service access point, router, IP path, peer addresses and support owner.
Enterprise Connect own-gateway guidance is specific to that service. It says the Enterprise Connect SIP-Trunk PBX should not connect directly to the firewall and retains a cloud-gateway path for voice devices. Do not transfer that topology to Enterprise SIP without the selected order and design.
Follow signaling to the loaded PBX route
Align an authorized capture with router or firewall, SBC, PBX and provider records for the same attempt. Preserve tuples, Request-URI, From, To, P-Asserted-Identity where present, Call-ID, response sequence and SDP. A reachable access path, healthy SBC or SIP response is not proof of the intended PBX route or a completed call.
If a configuration change is proposed, compare the exact installed PBX, SIP engine and SBC with the July 2026 compatibility entry and the provider-issued implementation record. Change only the demonstrated owner.
Separate number, channel and routing-option state
For inbound failures, prove whether Swisscom attempted the expected service access point before changing the dialplan. Correlate the called number, port or allocation state, delivered format, identity headers and exact route. For outbound failures, preserve the selected trunk, presented number, response and policy owner.
Forwarding scenarios, Multi SAP, Multi PBX, Multi Server, channel split, bursting and trunk failover are not interchangeable. Record ordered entitlement, trigger, target, limit, current state and result for the one option involved.
Separate signaling success, fax and media
A 200 response or connected call does not prove audible media. Preserve negotiated G.711 or other codec, packetization, telephone-event mapping, actual RTP tuples, packet direction and decoded audio at authorized points. Keep each media leg and any transcoding boundary separate.
The factsheet lists G.711 and T.38 fax capabilities, not a universal completed-page guarantee. Preserve the exact gateway, re-INVITE, T.38 attributes, packet loss, page result and fallback behavior for a controlled fax case.
Retest one correction, continuity and emergency state separately
After an authorized correction, repeat the affected ordinary call and an unaffected control. Preserve provider attempt, SBC and PBX receipt, loaded route, answer, media and normal hangup. If continuity was involved, demonstrate the selected alternate and then prove the next eligible call returns to the intended primary.
Do not place an uncoordinated emergency call. Confirm the effective location record, number mapping, outbound identity, route, callback and alternate method through Swisscom’s approved process. No account, access, SBC, PBX, trunk, call, media, failover 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.
- Swisscom — Enterprise SIP for your private branch exchange ↗
- Swisscom — Enterprise SIP factsheet ↗
- Swisscom — Enterprise SIP compatibility list, July 2026 ↗
- Swisscom — Enterprise Connect getting started ↗
- Swisscom — Enterprise Connect order company services ↗
- Swisscom — Enterprise Connect own-gateway configuration ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.