Bind the review to the Australian order and contracting boundary
Identify the legal customer, VoIPline entity, service order, point of interconnect, ordered channels, numbers, call plan, support path and responsible PBX or SBC. Keep the Australian service separate from similarly branded services in other countries; public product and network pages do not replace the selected order, critical-information summary or service schedule.
Preserve dated order and portal evidence without exposing credentials. The pricing page is volatile and plan-specific, so record the approved quote, currency, taxes, fair-use terms, term, cancellation and support rather than copying a universal price.
Documented service facts
Reviewed 2026-10-16. Compare SIP trunk services →
SIP authentication
DocumentedRegistration is one documented operation mode. Preserve the account-issued server and credential owner, challenge, Contact, expiry and rotation without publishing secrets.
Registration, bindings and operation mode
DocumentedRegistration, SIP URI diversion and Microsoft Teams gateway are distinct modes, while public-internet and ordered private-IP delivery are separate interconnect boundaries. For registration, preserve the issued registrar, Contact, expiry and complete response sequence; a successful binding does not prove number routing, outbound authorization or media.
Numbers and inbound delivery
DocumentedNumbers can be activated or ported and mapped into call flow, but selected inventory, completion, delivered identity, target and fallback remain account specific.
Routing groups and failover
DocumentedThe schedule states one trunk routing group per point of interconnect unless the order specifies otherwise. Provider-network redundancy does not establish customer failover behavior.
Service and number coverage
DocumentedAustralian local, mobile, toll-free and international number surfaces are published, but destination authorization, availability, portability and regulatory eligibility remain current-order questions.
Codecs, DTMF and RTP
DocumentedThe service schedule lists G.711 A-law and mu-law, G.722 and G.729 at 20 ms and per-call offer/answer selection. DTMF, RTP range and selected transcoding remain unverified.
Fax and analogue dependencies
Not verifiedThe reviewed SIP-trunk sources do not establish T.38 or pass-through acceptance for the selected order. Inventory fax, alarm, lift, door-entry, payment and monitoring dependencies separately.
Signaling and media protection
DocumentedThe product says encryption can be configured, not that every trunk is encrypted. Selected transport, certificate trust, SRTP, keying and downgrade behavior require order-specific evidence.
Channels and call starts
DocumentedThe service schedule defines ordered channels as logical concurrent calls and says voice service is bidirectional by default. Calls-per-second, burst and overload treatment remain order specific.
Emergency calling
Not verifiedSelected-trunk eligibility, registered location, callback identity, propagation, failure behavior and an approved test procedure were not established by the reviewed accessible sources.
Pricing, SLA and contract
DocumentedCurrent Australian channel plans and legal documents are public, but approved price, taxes, fair-use treatment, SLA scope, exclusions, term and support remain the dated order and contract.
Status, support and demarcation
DocumentedThe provider publishes status and network material. These do not prove the selected account, customer access path or PBX; record owners, timestamps, correlation data and escalation.
SMS and MMS
Not verifiedSMS is a separate product and the schedule includes SMS obligations. The SIP-trunk material does not establish messaging on every voice number; keep eligibility, consent, registration, filtering and price separate.
Choose one documented operation mode
The product page presents SIP registration, SIP URI diversion and Microsoft Teams gateway as separate modes. Record which mode the order actually authorizes. Registration uses a provisioned account and server; URI diversion routes an inbound call to a specified SIP URI; the Teams option places Direct Routing in the path. Do not combine their identities, routing rules or acceptance tests.
For registration, retain the issued server, username owner, transport, challenge, Contact, expiry and final response. For URI diversion, retain the exact target URI, DNS result, port, response and fallback. A green registration state does not prove that an inbound number is mapped or that an outbound call is authorized.
Keep channels, routing groups and numbers separate
The current service schedule defines ordered channels as the logical number of concurrent calls, says voice service is bidirectional by default and describes a single trunk routing group per point of interconnect unless the service order says otherwise. Treat each as a contract boundary, not a PBX default.
Record inbound number ownership and route, outbound normalization, valid caller identity, channel use by direction, overload response and alternate treatment. The porting page allows call-flow preparation before completion and warns that cutover can involve a temporary interruption; a configured route is not proof that the number has ported or is currently reachable.
Verify negotiated media from the service schedule and the call
The reviewed service schedule lists G.711 A-law and mu-law, G.722 and G.729 with 20 ms packetization, and says codec selection occurs per call during offer and answer. Preserve the actual SDP, chosen codec, packetization, addresses, first packet in each direction, loss, jitter and decoded result.
The reviewed public sources do not establish one selected-account DTMF, fax, RTP-range or transcoding profile. Obtain those boundaries for the order and verify them from the permitted call. A supported codec list, accepted INVITE or packet counter is not evidence of audible two-way media.
Scope network, security and resilience claims
VoIPline describes public-internet and private-IP delivery and publishes network, redundancy and security statements. The product page says encryption can be configured; it does not make encryption a default for every trunk. Record the selected signaling transport, certificate identity and trust, media protection, keying, downgrade behavior, customer access path and demarcation.
Provider geo-redundancy or a public status indicator does not prove the customer access circuit, DNS, firewall, PBX, account or active call. Capture the failed interval and change only the first demonstrated owner; do not expose broad SIP or RTP ranges to compensate for missing order-specific data.
Accept regulatory, operational and commercial boundaries
The service schedule constrains caller identity to valid allocated numbers under the customer or end user’s control and makes the customer responsible for its access connection outside the provider network boundary. Confirm number eligibility, emergency calling and registered location, portability, caller identity, fraud controls, maintenance, monitoring, retention, escalation, SLA exclusions and an independent emergency method.
Use only an approved emergency-test procedure. No availability, compatibility, security, quality, porting, caller-identity, emergency or call result is claimed from these public documents.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- VoIPline Telecom SIP trunking ↗
- VoIPline Telecom pricing and rates ↗
- VoIPline Telecom legal documents ↗
- VoIPline Voice and SMS (IP) service schedule ↗
- VoIPline SIP trunks critical information summary ↗
- VoIPline Telecom network ↗
- VoIPline Telecom number porting ↗
- VoIPline Telecom service status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.