Name the exact Swisscom voice service and variant
Swisscom’s current enterprise page describes Enterprise SIP for Switzerland-based sites and Enterprise SIP Cloud for cloud PBXs. The Cloud factsheet names Microsoft Teams and Webex Calling, while the Enterprise Connect guide documents another SIP-Trunk service inside that managed network offer. Smart Business Connect is presented separately for SMEs. Preserve the ordered name, access variant, country, legal entity, service access point and document date before reusing any field.
A Swisscom logo, SIP label or shared portal does not make these products interchangeable. Enterprise SIP Standard, Unbundled, WAN, Cloud and Shared Connectivity also have different handoff and responsibility boundaries.
Documented service facts
Reviewed 2026-10-25. Compare SIP trunk services →
SIP authentication
Not verifiedThe public records distinguish provider eSBC, approved customer SBC and application-service-provider SBC variants but do not publish one universal credential, certificate or source-address profile. The selected order and implementation record govern.
SIP registration
Not verifiedNo universal REGISTER model, registrar, realm, Contact policy or expiry was established for Enterprise SIP. Keep order activation, access, SBC reachability, peer authorization, number routing, answer and media separate.
Inbound delivery and identity
DocumentedSwisscom documents number portability, caller display, forwarding scenarios, number-block administration and PBX-based call allocation. Assignment, port completion, delivered identity, SBC receipt and PBX route remain separate.
Continuity options
DocumentedSwisscom documents core-network forwarding, Multi SAP, Multi PBX, Multi Server, trunk failover and availability options. Ordered topology, trigger, alternate selection, completed result, established-call behavior and restoration remain unverified.
Site and number availability
Not verifiedEnterprise SIP is presented for Switzerland-based sites, while Enterprise SIP Cloud addresses cloud PBXs. Serviceability, variant eligibility, number inventory, portability and lead time require dated qualification and order evidence.
Codecs, DTMF and RTP
DocumentedThe factsheet names G.711 A-law but does not establish the selected account’s full codec set, packetization, DTMF method, RTP tuples, transcoding or SBC anchoring. Observed SDP and decoded media govern.
Fax
DocumentedThe factsheet lists G.711 or T.38 fax. Exact gateway, negotiation, redundancy, page limits, fallback and completed-page results remain unverified for the selected path.
Access, signaling and fraud controls
DocumentedSwisscom describes secure connections, continuous monitoring and an optional anti-spoofing control per number block. Ordered enablement, SBC trust, signaling and media protection, alert scope and observed protection remain unverified.
Channels, split and bursting
DocumentedSwisscom documents ordered voice channels, per-direction channel split and bounded bursting; split and bursting cannot be used simultaneously on a trunk. Account entitlement, calls per second, PBX resources and access acceptance remain unverified.
Emergency calling
DocumentedThe current product page describes E112-based dynamic routing from maintained location information, while My Swisscom Business supports emergency-routing administration. Effective account state and an approved test result remain unverified.
Pricing and contract
Not verifiedThe factsheet notes price-plan and Voice Channel Flat structures but is not a binding offer and may be revised. Bind access, channels, numbers, usage, options, support, taxes, term and changes to the dated current order and bill.
Administration and support
DocumentedSwisscom documents My Swisscom Business administration and proactive signaling monitoring. The ordered support time, contacts, responsibility matrix, maintenance process, escalation and observed case history remain unverified.
SMS and MMS
Not verifiedThe reviewed Enterprise SIP records do not establish SMS or MMS entitlement, sender registration, API access, throughput, webhook security, retention or price for trunk numbers. Treat messaging as a separate ordered service.
Bind access and SBC ownership to the ordered variant
The Enterprise SIP factsheet describes a dedicated MPLS access with Class of Service for the base service. It also says Unbundled and WAN use an existing Swisscom IP connection under a separate contract; Unbundled requires a Swisscom-approved customer SBC, while Standard and WAN use the Enterprise SIP eSBC. Shared Connectivity instead uses an application service provider SBC and a separate customer contract.
Record the access circuit, service access point, router, provider eSBC or customer or ASP SBC, PBX peer, addresses, routing owner and support boundary independently. A reachable router or SBC does not establish an authorized or routed trunk.
Keep certification, configuration and observed behavior separate
Swisscom’s July 2026 compatibility list identifies tested PBX, communication-server and SBC versions for Enterprise SIP Standard. It includes Asterisk and PBXact combinations, but a list entry is not proof that the selected release, patches, modules, generated configuration, SBC path or current interoperation matches the tested combination.
Preserve exact hardware, software, SIP engine, SBC, topology and provider configuration. Treat certification, installed state, loaded state, successful registration or peer reachability, routed calls and two-way media as separate evidence.
Separate numbers, channels and routing options
The factsheet documents number portability, G.711 A-law, fax using G.711 or T.38, forwarding scenarios, Multi SAP, Multi PBX, Multi Server, channel split, bursting, call filtering and trunk failover. Availability depends on the selected variant, and channel split and bursting cannot be used simultaneously on a trunk.
Requested, ported, assigned, activated, routed and call-proven numbers remain different states. Preserve ordered channels, per-direction limits, burst eligibility, simultaneous calls, call-start behavior, PBX resources and access bandwidth without converting portfolio features into account facts.
Make continuity and restoration observable
Swisscom describes call forwarding in its core network, Multi SAP, Multi PBX, Multi Server, availability options, trunk failover and proactive signaling monitoring. Each has a different trigger, owner and result. Forwarding to another number is not the same as selecting another trunk or preserving an established call.
For an approved acceptance exercise, record the failed component, health evidence, provider decision, selected alternate, number and identity treatment, completed new-call result, surviving-call behavior where applicable and demonstrated return to the intended primary.
Keep emergency location, security and operations current
The current product page describes E112-based dynamic emergency number routing using maintained location information and an optional anti-spoofing control applied per number block. The factsheet also identifies My Swisscom Business for forwarding, emergency routing and inventory. These labels do not establish the selected account’s current address, number mapping, protection state, alert handling or successful emergency route.
Do not place an uncoordinated emergency call. Preserve registered location, effective update, outbound identity, route, callback and alternate method. Bind support hours, contacts, monitoring, maintenance, escalation and change authority to the current order and observed case records.
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 Cloud 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.