Freeze one attempt and the exact service identity
Record UTC and local time, ordered Sunrise service and Basic or Premium package, site, Internet or VPN provider, router, firewall, Sunrise peer, PBX and software, called and calling numbers, direction, expected route, answer and media result. Redact credentials and personal data.
Do not substitute Business Voice Direct, Business Voice for Microsoft Teams or Webex documentation because a field looks familiar. Classify the first unexpected state: order or activation, access, peer or PBX reachability, number delivery, PBX selection, answer, fax or media.
Verify package, access and responsibility boundaries
Compare the current order and accepted design with loaded state. Basic and Premium have different published access and managed-edge characteristics, and third-party Internet changes the responsibility boundary. Preserve the actual circuit, VPN if any, router, firewall, peer addresses and support owner.
Do not infer Premium voice prioritization, VPN or dedicated-firewall behavior for Basic, and do not treat ordinary Internet reachability as proof of the managed path.
Confirm the selected peer model before signaling changes
Align an authorized capture with router or firewall, PBX and provider records for the same attempt. Preserve tuples, Request-URI, identity headers, Call-ID, response sequence and SDP. A reachable path or SIP response is not proof of the intended route or a completed call.
The 2018 flyer describes trusted-network remote peering without a registrar or username/password, using UDP and G.711 A-law first priority. Apply that model only if the current service, order and worksheet match; otherwise obtain current settings.
Separate number, capacity and continuity state
For inbound failures, prove whether Sunrise attempted the expected peer before changing the dialplan. Correlate called number, port state, delivered format, identity headers and route. For outbound failures, preserve selected trunk, presented number, response and owner.
The 2017 and 2016 Business Voice Direct examples do not establish Business Voice SIP channels, DDI blocks or prices. Record the current order, limit, backup or emergency-routing trigger, target 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 codec, packetization, telephone-event mapping, RTP tuples, packet direction and decoded audio at authorized points. Keep each leg and any transcoding boundary separate.
The current page says the service supports fax, while the dated technical flyer asks the implementation to choose a fax codec. Neither is a completed-page guarantee. Preserve gateway, negotiation, packet loss, page result and fallback 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, PBX receipt, loaded route, answer, media and normal hangup. If backup 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 routing, location, identity, callback and alternate method through Sunrise’s approved process. No account, access, PBX, trunk, call, fax, media, backup 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.
- Sunrise — Business Voice SIP ↗
- Sunrise — On-premises and hybrid PBX portfolio ↗
- Sunrise — SIP Trunk technical flyer, August 2018 ↗
- Sunrise — Business voice direct flyer, March 2017 ↗
- Sunrise — Business Voice for Microsoft Teams factsheet, June 2021 ↗
- Sunrise — Business support contact ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.