VoIP.info Provider research

Sunrise Business Voice SIP: access, PBX and continuity boundaries

Evaluate Sunrise Business Voice SIP without importing Business Voice Direct, Microsoft Teams or Webex behavior, and keep package, access, peer, PBX, number, media and continuity evidence separate.

Reviewed 2026-10-25Current Sunrise Business Voice SIP and portfolio pages plus dated 2016, 2017, 2018 and 2021 Sunrise documents were reviewed October 25, 2026. Business Voice SIP, Business Voice Direct, Business Voice for Microsoft Teams and Cloud Connect for Webex Calling remain separate offers; dated examples are not universal current settings. No Sunrise account, order, site, circuit, Internet or VPN path, router, firewall, SBC, PBX, address, number, port, trunk, channel, call, fax, packet, media stream, backup or emergency result, price, availability, compatibility or support response was inspected or testedAdvancedDocumentation based · not lab tested

Name the exact Sunrise service and evidence date

Sunrise currently presents Business Voice SIP as a PBX connection to the public telephone network. Its portfolio separately lists Business Voice Direct, Business Voice for Microsoft Teams and Cloud Connect for Webex Calling. Preserve the ordered service name, package, access, site and document date before reusing any field.

A Sunrise brand or SIP label does not make these offers interchangeable. The 2016–2021 documents below are dated evidence for their named designs, not proof of the current configuration.

Documented service facts

Reviewed 2026-10-25. Compare SIP trunk services →

SIP authentication

Not verified

A 2018 trusted-network design uses remote IP peering without username/password. It is dated and not a universal current authentication profile; the current order and implementation worksheet govern.

SIP registration

Not verified

The 2018 example says no registrar. Do not transfer that model to another package or access path without matching current Sunrise design evidence.

Inbound delivery and identity

Documented

The current page lists number porting and the portal. Request, port completion, assignment, delivered identity, provider attempt and PBX route remain separate.

Continuity options

Documented

The current comparison refers to backup and emergency routing. Ordered topology, trigger, alternate, completed call and restoration remain unverified.

Access and serviceability

Not verified

The current page permits dedicated VPN or Internet, including third-party Internet. Package eligibility, address serviceability, circuit delivery and lead time require a dated qualification.

Codecs, DTMF and RTP

Not verified

The 2018 design places G.711 A-law first. Current codec set, DTMF, packetization, RTP tuples and decoded media require current configuration and observation.

Fax

Documented

The current page says the service supports fax; the 2018 worksheet asks for a fax-codec choice. Negotiation, gateway, fallback and completed pages remain unverified.

Access and firewall boundary

Documented

Premium is described with a VPN and dedicated firewall. Ordered package, third-party Internet responsibility, peer trust, rules and observed protection remain unverified.

Channels and call load

Not verified

Historical Business Voice Direct documents show channel examples but do not establish current Business Voice SIP capacity. The current order, simultaneous calls, PBX resources and access acceptance govern.

Emergency routing

Not verified

The current comparison refers to emergency routing, but no effective location, number mapping, route, callback or approved test was inspected.

Pricing and contract

Not verified

The 2016 price list is historical and belongs to Business Voice Direct. Current Business Voice SIP package, access, channels, numbers, support, taxes and term require a dated quote and order.

Monitoring and support

Documented

The current comparison names proactive monitoring and remote maintenance; the current support page supplies contact routes. Ordered coverage, alerts, escalation and case response remain unverified.

SMS and MMS

Not verified

The reviewed records do not establish SMS or MMS entitlement, sender registration, API, throughput, webhook security, retention or price for trunk numbers.

Bind package, access and responsibility boundaries

The current product page offers Basic and Premium. It says the service may use a dedicated VPN or Internet, including a third-party Internet connection; Premium adds voice prioritization, a VPN and a dedicated firewall. Record package, access owner, router, firewall, Sunrise handoff, PBX peer and support responsibility independently.

An Internet path is not a VPN, and a reachable address is not proof that the trunk is authorized, routed or suitable for voice. Check the dated order and accepted design.

Use the 2018 peer example only when it matches

The August 2018 Sunrise technical flyer documents one trusted-network design: a point-to-point or MPLS path, a Sunrise IP gateway in the LAN or DMZ, remote peering to a Sunrise IP, no registrar or username/password, UDP, and G.711 A-law first priority. It also asks the implementer to choose a fax codec.

Those are dated design details, not universal settings. Compare service name, package, circuit, worksheet, PBX software, peer addresses and protocol before using any field; otherwise obtain current Sunrise implementation data.

Separate numbers, channels, fax and media evidence

The current page mentions voice, fax and number porting, while the 2017 Business Voice Direct flyer and 2016 price list show historical channel and number-block examples for that different offer. Do not convert those dated examples into a Business Voice SIP entitlement or current price.

Requested, accepted, ported, assigned, activated and call-proven numbers are different states. Preserve ordered channels, simultaneous calls, PBX resources, fax negotiation, SDP, RTP tuples and decoded audio separately.

Make monitoring, backup and restoration observable

The current comparison lists proactive monitoring and remote maintenance and refers to backup and emergency routing. A listed capability does not establish that a particular account ordered it, that a trigger occurred, or that a call completed on an alternate.

For an approved exercise, record the failed component, health evidence, provider decision, selected alternate, number and identity treatment, completed new-call result and demonstrated return to the intended primary.

Keep cloud offers, support and emergency claims separate

The June 2021 Microsoft Teams factsheet describes a managed cloud SIP trunk and hosted AudioCodes SBC for that named offer. It is not a Business Voice SIP PBX template. Current portfolio and support pages should govern service selection and escalation; the dated document only explains its own scope.

Do not place an uncoordinated emergency call. Bind emergency routing, location, callback, backup, support hours, escalation, maintenance and change authority to the current order and an approved acceptance process.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.