VoIP.info Provider research

Aussie Broadband SIP Trunks: order, channel and handoff evidence

Evaluate Aussie Broadband SIP Trunks without turning public product copy, broadband dependencies, channel quantities or adjacent VoIP settings into an assumed PBX configuration.

Reviewed 2026-10-27Aussie Broadband SIP Trunks, the 1 July 2026 Critical Information Summary and related help, network and legal records were reviewed October 27, 2026. The public sources do not establish one universal SIP proxy, authentication model, registration requirement, transport, codec list, media range, encryption option, DID format, caller-identity rule or PBX template; the current order, supplier identity, service handoff and provider confirmation govern. No Aussie Broadband or Nexgen account, quote, order, NBN service, SIP trunk, credential, adapter, PBX, route, number, port, channel, NAT mapping, packet, call, media stream, emergency outcome, price, availability, compatibility, incident or support response was inspected or testedAdvancedDocumentation based · not lab tested

Identify the ordered service, supplier and responsibility boundary

Aussie Broadband presents SIP Trunks as a way to connect an existing PBX to Internet calling. Its current product page also says enquiries may be handled by Nexgen after its acquisition and that Nexgen invoices the resulting solution. Preserve the quoted seller, contracting and billing entity, product name, service identifier, number inventory, channel quantity, site, access service and support owner from the current order.

Do not merge SIP Trunks with Aussie Broadband single-line VoIP, Hosted Phone System, enterprise voice, wholesale voice or a legacy FaktorTel service. A product page, consultation, accepted quote, provisioned service, delivered handoff and completed call are different states.

Documented service facts

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

SIP authentication

Not verified

The reviewed public SIP-trunk sources do not publish one universal authentication identity, secret, realm or source-address policy. The selected service handoff governs; BYO VoIP credentials are not transferred.

SIP registration

Not verified

A universal REGISTER requirement, registrar, proxy, expiry, refresh and Contact policy were not established publicly for the selected trunk. Preserve the provider handoff and observed exchange.

Numbers and inbound delivery

Documented

The product supports transferred business numbers in most cases. Port completion, assignment, provider attempt, delivered number, PBX match and completed inbound call remain unverified.

Continuity and restoration

Not verified

The reviewed trunk records do not establish account-level failover, alternate destinations or established-call behavior. Public outage information and a fault ticket remain context, not restoration proof.

Access and serviceability

Documented

The July 2026 CIS requires an active Aussie Broadband NBN plan and says availability follows where that NBN connection can be supplied. The exact address, access order, lead time and delivered result remain unverified.

Codecs, RTP and audio

Not verified

The public SIP-trunk records reviewed here do not publish a universal codec, DTMF, packetization or media-port contract. SDP, RTP directions, decoding and audibility require call-specific evidence.

Fax

Not verified

The reviewed sources do not establish T.38, audio passthrough, fallback, gateway support or completed pages for one SIP trunk. Do not infer fax from an adapter or another voice product.

Transport, addressing and protection

Not verified

Transport, firewall sources, TLS, certificate policy and SRTP were not established publicly for the selected trunk. General CGNAT guidance is not a trunk configuration contract.

Channels and simultaneous calls

Documented

The product says each SIP channel supports one simultaneous call; the CIS displays two-channel examples and allows additional channels. Ordered quantity, call starts, dialogs, PBX resources and bandwidth remain separate.

Emergency-service evidence

Documented

Aussie Broadband documents IPND emergency-service addresses and lists 000 across all phone services. Effective address, identity, callback, route, power, Internet and independent access remain unverified for the selected trunk.

Plans, pricing and term

Documented

The 1 July 2026 CIS publishes Basic and Premium channel examples, a two-channel minimum example, month-to-month service and possible equipment or installation costs. The current quote, order, taxes and later changes govern.

Administration and support

Documented

The CIS names MyAussie for usage and fault lodging; the business contact page separates sales, service delivery and technical support. A portal entry, ticket or restoration notice does not prove call recovery.

SMS and MMS

Not verified

The reviewed SIP-trunk sources do not establish SMS or MMS on trunk numbers, sender registration, API access, throughput, retention or price. Do not transfer messaging claims from another product.

Treat the current CIS and service handoff as separate records

The 1 July 2026 Critical Information Summary says the service adapts a customer-supplied fixed voice system and requires an active Aussie Broadband NBN plan. It also names equipment, plan, channel, support and commercial conditions. The same document describes an Aussie Broadband-supplied analogue-to-VoIP adapter in its access list while later saying available adapters are not mandatory, so the exact ordered architecture and installation record must resolve the apparent scope difference.

The public sources do not publish one universal proxy, username, password, source-address rule, REGISTER requirement or called-number format. Preserve the provider handoff exactly; never copy settings from BYO VoIP, another account, another supplier or a generic PBX template.

Keep access, NAT and SIP acceptance independently observable

The CIS makes an active Aussie Broadband NBN plan a service dependency and says call quality depends on the Internet connection. Ethernet or NBN access state, public addressing, routing, DNS, NAT, a sent SIP request, provider response and an accepted dialog remain separate evidence.

Aussie Broadband publishes a general process for opting an Internet service out of CGNAT or adding a static address, but that article is not a SIP-trunk requirement. Establish whether the ordered handoff uses registration, source-address trust, an adapter or another managed boundary before changing CGNAT, port forwarding, firewall or PBX transport.

Separate channels, numbers, routes and media

The current product page says each SIP channel supports one simultaneous call; the CIS prices its displayed examples from two channels and allows additional channels. Ordered channels, configured PBX limits, offered attempts, active dialogs, call starts and completed calls remain different quantities.

Number assignment, port completion, provider delivery, the called-number value, PBX route match, answer, SDP, packet flow and audible two-way media also remain separate. The public SIP-trunk sources reviewed here do not establish a universal codec, DTMF, fax, RTP, TLS or SRTP contract, so those fields stay unverified until the selected handoff or support response supplies them.

Bound adjacent VoIP, porting and outage guidance

Aussie Broadband publishes BYO VoIP proxy and credential guidance for its VoIP service. That page is useful only as evidence that adjacent product settings exist; it must not be copied into a SIP-trunk PBX unless the provider explicitly binds the ordered trunk to those values.

The number-porting article says most ports take four to six business days and warns not to cancel the former service before the new one is working. That dated expectation is not a guaranteed cutover time. Likewise, a public Internet or mobile outage notice is context rather than proof that a particular trunk, number, route or media path is affected.

Make support, emergency readiness and commercial facts time-bound

The CIS directs usage review and fault lodging through MyAussie; the current business contact page separates sales, service delivery and technical support. Preserve the fault identifier, opened time, affected service, provider observations, changes, restoration claim and customer-side retest rather than treating a ticket or status page as resolution.

Aussie Broadband says IPND stores phone-service address data and lists 000 and crisis numbers across its phone services. Confirm that the selected trunk number has the intended effective emergency-service address, identity, callback and routing under the approved process; never place an uncoordinated 000 test. Prices, eligibility, plan inclusions, support hours and port timing are date-sensitive and must be rechecked against the current order and provider records.

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.