Identify the ordered service and governing records
2degrees presents SIP Trunks as a business service that connects an existing PBX to IP networks and the public telephone network. The current page positions the service from businesses with ten or more phone lines through larger enterprises, but that audience description is not an order, minimum channel quantity, site acceptance or compatibility result.
Record the exact legal service name, customer agreement, service schedule, order, site and current implementation pack. The terms index lists business schedules and current service-level material, while the older linked termination-fee schedule names SIP Trunk per channel; none of those records alone proves the commercial terms governing one live account.
Documented service facts
Reviewed 2026-10-28. Compare SIP trunk services →
SIP authentication
Not verifiedThe public overview does not establish a universal credential, certificate or source-address model. The current implementation pack governs.
SIP registration
Not verifiedA universal REGISTER requirement, registrar, proxy, expiry or Contact policy was not established.
DDIs and inbound delivery
Not verifiedThe reviewed public record does not establish DDI allocation, port state, delivered format or routing for one account.
Rerouting and continuity
DocumentedThe product page describes rerouting to a data line or PBX redirection to mobile during disruption. Inclusion, trigger, target, call result and restoration remain unverified.
Access and demarcation
Not verifiedThe service uses internet infrastructure, but the public record does not establish one universal access, handoff, router or demarcation for every order.
Signaling and media
Not verifiedPublic pages do not establish universal signaling targets, transport, codecs, DTMF or media ranges. Implementation evidence and observed packets govern.
Fax and non-voice use
Not verifiedThe reviewed records do not establish fax, T.38, modem, EFTPOS or alarm compatibility.
Transport and media protection
Not verifiedNo universal TLS, certificate or SRTP profile was established by the reviewed public record.
Trunks, channels and calls
DocumentedThe product page describes scaling and targets businesses with ten or more phone lines; a linked fee schedule names SIP Trunk channels. Account quantity and concurrency remain unverified.
111 and power evidence
Documented2degrees documents that fibre and modem-dependent landlines can fail without local power. One business trunk location, callback and alternate path remain unverified.
Term, price and availability
Not verifiedThe older fee schedule is not a current quote and the overview does not establish one universal current price, term, installation or site availability.
PBX, QoS and support
DocumentedThe overview connects an existing PBX and recommends enough bandwidth and router QoS. PBX acceptance, measured quality, support target and service level remain unverified.
SMS and MMS
Not verifiedThe reviewed SIP Trunks record does not establish SMS or MMS on trunk DDIs.
Bind the PBX to the actual access and demarcation
The product page describes connecting an existing phone system or PBX over internet infrastructure. It says an existing VoIP-capable PBX is closer to migration and that older systems may need migration help. It does not publish one universal access circuit, router, addressing plan, demarcation, PBX approval list or customer/provider responsibility boundary.
Preserve the ordered access, provider handoff, router or SBC, IP addressing, routing, firewall, PBX model and software, and the boundary at which each party observes the service. A working broadband session or reachable address does not prove that the SIP trunk, identity, number or media path is accepted.
Treat QoS and call-quality language as design guidance
2degrees says call quality can be excellent when the service is configured correctly and has enough internet bandwidth, and recommends router QoS to prioritise voice. Those are conditional design statements, not measured results for a site. They do not establish bandwidth, latency, jitter, loss, congestion policy, codec selection, audibility or a service-level commitment.
Measure the exact access path under representative load. Keep signaling success, negotiated session description, packet arrival, decoded media and heard audio as separate observations, and retain the current order and service-level definition before making an availability or quality claim.
Separate trunks, channels, lines, DDIs and active calls
The public page says SIP Trunks can scale up or down and discusses adding or removing phone lines. The termination-fee schedule refers to a fee per SIP Trunk channel. Neither source publishes a universal included quantity, concurrency rule, DDI allocation, number format, porting state or current price for every account.
Record the ordered trunk, channel entitlement, portal or provider record, concurrent dialogs, PBX resources, DDIs and actual call attempts separately. A visible number, accepted portal change or SIP response does not prove inbound routing, outbound identity, remaining capacity or a completed call.
Prove rerouting and continuity end to end
2degrees describes business continuity in terms of rerouting phone services to a data line or redirecting them to mobile phones through the PBX during failures or national emergencies. That does not establish that one account includes automatic rerouting, the trigger or control plane, target numbers, preserved features, media behavior, physical diversity, recovery time or restoration.
Name the ordered continuity feature and owner. Exercise it only through an approved plan that records the initiating fault, provider and PBX actions, new-call result, established-call behavior, media in both directions, restoration and rollback. A configured target or second path is not proof of completed failover.
Keep emergency, price and compatibility claims bounded
2degrees documents that fibre and modem-dependent landline services can fail when local power fails and recommends a charged mobile or protected power; vulnerable-consumer guidance describes alternative means for qualifying retail landline users. These general pages do not establish the 111 location, callback, power or alternate-path behavior of one business SIP trunk.
Obtain provider-approved emergency-calling instructions and validate readiness through a coordinated non-live process; do not place an uncoordinated 111 call. Obtain a current quote, feasibility result, PBX acceptance and implementation specification rather than inferring price, availability, authentication, codecs, encryption or compatibility from the public overview.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- 2degrees Business — SIP Trunks ↗
- 2degrees Business — Business services ↗
- 2degrees — Terms and conditions index ↗
- 2degrees Business — Early Termination Fees ↗
- 2degrees — What happens in a power cut ↗
- 2degrees — Vulnerable consumers and calling 111 during a power outage ↗
- 2degrees — Privacy policy ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.