Quick answer: Pair Twilio with a carrier that documents Twilio’s BYOC (Bring Your Own Carrier) trunk and sells Australian numbers. Of eight carriers we checked, Plivo and DIDWW do both, and Plivo is the one whose Australian per-minute rates we could read. Twilio adds US$0.0040/min each way, so BYOC only pays below US$0.0212/min to landlines or US$0.0710/min to mobiles. Otherwise, use Twilio’s own +61 numbers.
This page answers one question: if you want to recommend a SIP trunk provider to use with Twilio Voice API in Australia, which carrier do you pair with Twilio, and when should you skip BYOC? We read Twilio’s docs, price lists and Australian guidelines, and each carrier’s own pages, on 2 October 2026. Carriers are scored only on what they document. We don’t score “quality” claims we can’t check.
Recommending a SIP trunk provider to use with Twilio Voice API in Australia: the short version
Twilio gives you two ways to bring a third-party carrier into Programmable Voice. The first is a BYOC trunk, which Twilio describes as “a SIP Trunk to interconnect your PSTN Carrier to the Twilio platform”. Your TwiML or REST API call picks it with a byoc parameter. The second is to have Twilio dial the carrier’s SIP address with a token or credentials. Some carriers document only that route.
The decision comes down to one fact in Twilio’s BYOC documentation: “Twilio does not support authentication with the carrier via credentials for BYOC origination calls. The carrier needs to treat Twilio as a trusted entity and allow traffic from the appropriate Regional Twilio IP addresses.” A carrier that only accepts registered, username-and-password devices can’t be a BYOC origination target without something in between. So the first thing to ask any Australian carrier is whether it will allowlist Twilio’s Sydney signalling IPs.
The quotable rule: in Australia, a BYOC carrier has to beat Twilio by more than US$0.0040 a minute before it saves anything, and it has to accept Twilio by IP address before it works at all.
What Twilio BYOC is, and what it costs in Australia
Twilio’s Australian voice pricing (marked “current as of August 2026”, in US dollars) lists BYOC trunking at $0.0040/min to make calls and $0.0040/min to receive them. That is the Twilio platform charge. Your carrier then bills its own per-minute rate on top. If you skip BYOC and use Twilio’s own carriage, the same page lists outbound Programmable Voice calls at $0.0252/min to Australian landlines and $0.0750/min to Australian mobiles. Twilio’s number price list (CSV) puts inbound voice on a local or mobile +61 number at $0.0100/min, although the receive-calls table on Twilio’s pricing page shows $0.0500/min for mobile numbers. The worked bill below uses local numbers only.
The arithmetic is simple. Take away the $0.0040 BYOC fee and a carrier has to charge less than $0.0212/min for landline calls and less than $0.0710/min for mobile calls to come out ahead. Those two figures also happen to be the “starting at” Australian termination rates Twilio publishes for its separate Elastic SIP Trunking product. Elastic SIP Trunking connects your own PBX or SBC to the phone network and is a separate product from Programmable Voice. Our guide to whether an AI voice agent needs its own SIP trunk at all works through those Elastic SIP Trunking rates against bundled AI-platform pricing.
Twilio runs an Australian region. Its regional availability page says the AU1 Region “is located in Sydney” and supports Programmable Voice and Elastic SIP Trunking, with exclusions. The BYOC guide lists a Sydney-localised termination address for carriers in the form {example}.sip.au1.twilio.com. Twilio also lists a sydney edge and a sydney-ix Interconnect edge. Two AU1 exclusions matter for BYOC buyers. “BYOC Trunks with static IP addresses” are not yet supported in AU1, and neither are “Verified Caller IDs”. Twilio’s regions page also warns that during the rollout it “doesn’t guarantee that all data will remain within your selected Region”.
The Four-Gate BYOC Test
We built this test from Twilio’s own constraints. Run each candidate carrier through the four gates in order and stop at the first failure.
- The trust gate: will the carrier accept Twilio by IP? BYOC origination has no credential option, so the carrier must allowlist Twilio’s regional signalling IPs, ideally the AU1 set. Twilio’s guide says each region resolves to “3-4 IP addresses”. It recommends that if an INVITE gets no answer, the sender moves to the next IP “after 4 seconds”, and fails over to another region in a full outage. If the carrier needs SIP registration, the answer is an SBC in the middle, or no BYOC.
- The number gate: who holds the +61 numbers and the caller ID? Twilio’s Australian voice guidelines say calls Twilio originates to Australian destinations “should use a Twilio phone number as the Calling Number”. They also say calls presenting anonymous, invalid or “not allocated by ACMA” +61 numbers are blocked. With BYOC, the outbound call leaves through your carrier, so the numbers your agent shows should be numbers that carrier holds or has ported in. If your numbers are already Twilio numbers, this gate argues against BYOC.
- The arithmetic gate: is the saving bigger than the work? The carrier has to beat $0.0212/min (landline) or $0.0710/min (mobile). Then compare the saving with the hours it takes to build and maintain a second carrier relationship.
- The Triple Zero gate: who carries a 000 call? The Department of Infrastructure says the Telecommunications (Emergency Call Service) Determination 2019 “sets out obligations on carriers, carriage service providers and the emergency call persons”, and that access must be free of charge. An outbound-only AI agent line may never dial 000. If a human might ever use the number, though, find out which provider carries that call and who holds the IPND address record.
Australian SIP carriers checked against Twilio BYOC
Each row comes from that company’s own pages, read on 2 October 2026. “Self-stated” marks a vendor’s claim we didn’t verify independently. “Not stated on pages read” means we didn’t find it, not that the vendor lacks it.
| Carrier | Twilio interop it documents | Australian numbers and porting | Australian presence | 000 / emergency | Published AU price (USD) |
|---|---|---|---|---|---|
| Twilio itself (no BYOC; the baseline) | Not applicable: native | Local, mobile, toll-free; local numbers need an Australian address, no PO box | AU1 Region (Sydney); sydney edge |
Supported in Australia: 000, 112, 106; address registration only in US, CA, UK | Out: $0.0252 landline, $0.0750 mobile; In: $0.0100 local/mobile |
| Plivo (Zentrunk) | Twilio BYOC guide: outbound via a BYOC trunk, inbound via a Twilio SIP domain | Local, mobile and toll-free number prices listed; its porting documentation says porting is “available for US and Canada only” | Sydney IP block listed for traffic to Twilio | Not stated on pages read | Out: $0.0188 landline, $0.0580 mobile (Optus, Telstra and Vodafone mobile routes; satellite and mobility-service routes are $3.4980); In: $0.0025 local, $0.0050 mobile. Footnote: rates as of May 2026, “Subject to change” |
| Telnyx | Twilio guide labelled “(deprecated)”; it uses <Dial><Sip> with a token header, not a BYOC trunk |
Local, national, toll-free; porting (self-stated) | Sydney and Melbourne anchor sites; “Licensed Australian carrier” (self-stated) | Support article on 000, 112 and IPND upload | Per-destination rate card; we couldn’t read the AU row from a static fetch |
| Sinch (Elastic SIP Trunking) | Twilio BYOC guide: Sinch IPs on a Twilio ACL, origination URI pointed at the Sinch trunk | Porting offered (self-stated); AU coverage for this product not confirmed on pages read | An Australian SIP region (apse2) is documented for Sinch’s Voice API SIP trunking, a separate product page |
E911 documented (US); 000 not stated on pages read | Not published for Elastic SIP Trunking; Sinch’s Network SIP Trunking page says to “talk to the Sinch team” to scope international coverage |
| DIDWW | Twilio BYOC guide: inbound via a Twilio SIP domain set to the BYOC trunk; outbound via an Origination Connection Policy to DIDWW, which authenticates Twilio by Account SID | Local, mobile and toll-free numbers; its number pages mark all three as portable to DIDWW | Published PoP list has no Australian site (Asia-Pacific PoPs: Singapore, Hong Kong) | Outbound emergency calling marked supported on Australian local numbers; marked not supported on mobile and toll-free | Per-minute rates in a price list DIDWW emails after a request form, which we didn’t request; Local Outbound Termination “priced per destination country” |
| Bandwidth | Twilio guide dials a Bandwidth SIP address with SipAuthUsername/SipAuthPassword, not a BYOC origination policy |
Local, mobile, toll-free and portability listed; Australian mobile porting since 29 January 2024 for person-to-person use | Australia coverage page; PoP location not stated on it | “Emergency services” listed on its Australia coverage page | Not on the Australia coverage page (“Talk to an expert”) |
| CommPeak | Twilio BYOC marketing page; its docs say SIP accounts accept IP authentication (static IPs), but no Twilio setup steps | Local, mobile, toll-free listed | “10 global PoPs”; its SIP addresses article lists an Australian signalling PoP (au.sip.commpeak.com) | Not stated on pages read | Usage-based; AU rate not on page read |
| Symbio (Aussie Broadband Group) | None found on its site (searched 2 October 2026); integrations listed are Microsoft Teams and Webex | Numbers and porting listed as products; site aimed at providers and resellers | Says it is a licensed carrier in Australia, NZ and Singapore and can “connect directly to every carrier in Australia” (self-stated); optional dual-carrier redundancy with Aussie Broadband | Not stated on pages read | Not published on pages read |
| Telstra SIP Connect | None; guide says “only accredited IP PBX’s can be connected” | Not covered in the integration guide | Telstra network; 1,000 concurrent calls per public IP (internet variants); “automated outbound calling campaigns” not supported | Guide warns 000 may be unreachable if the access service is interrupted | Not in integration guide |
Two routes appear in the table. Plivo, Sinch and DIDWW configure Twilio’s BYOC trunk object. Bandwidth and Telnyx have Twilio dial their SIP address with credentials or a token, which sidesteps BYOC’s no-credentials rule. Twilio prices “SIP interface” calls at the same $0.0040/min, so the arithmetic gate doesn’t change. We didn’t check Optus or Vonage closely enough to score them.
How the gates sort the table: Plivo, Sinch and DIDWW document the BYOC trunk object, so they pass the trust gate on paper (DIDWW’s guide has its outbound trunk identify Twilio by Account SID rather than by an IP allowlist). Plivo and DIDWW also sell Australian numbers, and Plivo is the one whose Australian per-minute rates we could read. Only DIDWW marks its Australian numbers as portable to it; Plivo’s number-porting documentation says porting is “available for US and Canada only”. Bandwidth and Telnyx document Australian numbers but use credentialed or token SIP dialling, and Telnyx marks its guide deprecated. CommPeak accepts IP authentication, but neither its Twilio page nor its documentation index (checked 2 October 2026) has setup steps. Symbio and Telstra SIP Connect have no Twilio guide that we could find.
Does BYOC save money? A worked Australian bill
This example uses only published per-minute rates, all in US dollars: Twilio’s Australian Programmable Voice and BYOC prices, Twilio’s number CSV, and Plivo’s Australian rate card. Plivo is here because, of the three carriers that document Twilio’s BYOC trunk, it is the one whose Australian per-minute rates we could read. DIDWW sends its price list by email after a request form, and Sinch doesn’t publish them for Elastic SIP Trunking. That isn’t an endorsement. Swap in your own carrier’s quote.
Assume an AI outbound agent with this monthly volume: 20,000 minutes to Australian mobiles, 5,000 minutes to Australian landlines, and 5,000 inbound minutes on local numbers.
| Traffic | Minutes | Twilio carriage rate | Twilio cost | BYOC rate (Twilio $0.0040 + Plivo) | BYOC cost |
|---|---|---|---|---|---|
| Outbound to mobiles | 20,000 | $0.0750 | $1,500.00 | $0.0040 + $0.0580 = $0.0620 | $1,240.00 |
| Outbound to landlines | 5,000 | $0.0252 | $126.00 | $0.0040 + $0.0188 = $0.0228 | $114.00 |
| Inbound, local number | 5,000 | $0.0100 | $50.00 | $0.0040 + $0.0025 = $0.0065 | $32.50 |
| Total | 30,000 | $1,676.00 | $1,386.50 |
BYOC saves $289.50 a month, or 17.3%, on this mix. Nearly all of it comes from mobile calls, which save $0.0130/min. Landline calls save only $0.0024/min (9.5%). Change the mix to mostly landlines and the saving almost disappears: 10,000 landline minutes saves $24.00. The bill leaves out number rental, Twilio’s per-minute AI features (Media Streams is listed at $0.0044/min and Conversation Relay at $0.07/min on the same Twilio page; those are Twilio features, billed separately from the carrier line), and your speech and model costs. Plivo’s page says its rates are “as of May 2026” and “Subject to change”, so re-price on the day you decide.
The quotable rule from the bill: BYOC in Australia is mostly a mobile-termination saving. If most of your agent’s calls go to landlines, the carrier change is worth about a quarter of a cent a minute.
Rather spend your engineering time on the agent than on carriers? Zian AI runs autonomous phone, SMS, email and WhatsApp sales agents in 30+ languages, with CRM integrations for HubSpot, Salesforce and HighLevel and private model deployment on your own infrastructure. We’re in a partnership-application beta.
Who each carrier is the wrong choice for
Plivo is wrong for you if you need to port existing Australian numbers to it: its number-porting documentation says porting is “available for US and Canada only” (checked 2 October 2026). It is also wrong if you need a carrier whose Australian 000 and IPND handling you can read before you sign. We didn’t find that on the pages we read. Its guide also hard-codes four Twilio IP addresses in the allowlist step. If you process calls in AU1, use the IPs your Twilio console shows for that trunk instead.
Telnyx is wrong for you if you need a supported, vendor-written Twilio BYOC procedure. Its Twilio page is labelled deprecated and shows the <Dial><Sip> token route. It suits teams willing to build and test the BYOC trunk themselves.
Sinch is wrong for you if you need self-service Australian numbers today. We could confirm the Twilio BYOC steps for Sinch Elastic SIP Trunking. We couldn’t confirm that product’s Australian number coverage, and Sinch’s Network SIP Trunking page sends international scoping to its sales team.
DIDWW is wrong for you if you want media and signalling to stay on Australian infrastructure. Its published PoP list has no Australian site; the nearest are Singapore and Hong Kong. It is also wrong if 000 matters on mobile numbers, because its Australian mobile number page marks emergency calling as not supported (local numbers are marked supported).
Bandwidth is wrong for you if you specifically want Twilio’s BYOC trunk object, or published Australian rates. Its Twilio guide dials a Bandwidth SIP address with credentials instead, and its Australia page sends pricing to a sales conversation. Its Australian mobile porting is documented for person-to-person use.
CommPeak is wrong for you if you need to check the integration before you buy. Its Twilio page describes the integration but gives no configuration detail.
Symbio is wrong for you if you want a self-serve trunk with a price list you can read. Its site is aimed mainly at service providers, resellers, CPaaS and contact-centre platforms, and we found no published rates. It suits a platform that wants carrier-level Australian numbering and is willing to build the Twilio interconnect itself.
Telstra SIP Connect is wrong for you as a direct BYOC target, and for AI outbound in general. Its integration guide says only accredited IP PBXs can connect. It says traffic must be “normal business traffic with average holding times of 120 seconds or greater”, and that “automated outbound calling campaigns” are not supported. It also warns the service can fail to reach 000 if the access service drops.
When you should not use BYOC at all
BYOC is one route among several for giving an AI voice agent Australian telephony, and often not the best one. Skip it when:
- Your numbers can simply be Twilio numbers. Twilio’s Australian guidance names Twilio-provisioned or ported-in numbers as having “the lowest risk” under the Reducing Scam Calls code. If you can port to Twilio and your traffic is mostly landlines, the saving above is too small to justify a second carrier. Our guide to getting an Australian phone number for an AI voice agent covers number types, identity checks and porting.
- Your carrier only connects registered PBXs. Without credential support on BYOC origination you would need an SBC between the carrier and Twilio. Once you run an SBC, you may not need Twilio in the call path at all. See running an AI voice agent on direct SIP with no Twilio in the path.
- Your agent framework speaks SIP natively. If you aren’t using TwiML, Conversation Relay or Media Streams, a Twilio BYOC trunk is a hop you’re paying $0.0040/min each way for. Connect the carrier straight to the agent instead. Our walkthrough on connecting an AI agent to your own SIP trunk covers the authentication and early-offer problems that come with that route.
- You need a static IP for a BYOC trunk in Sydney. Twilio says this is “not currently available” in AU1 and is supported only in US1.
One case points the other way: showing a number held by another carrier as caller ID. Verified Caller IDs are not supported in AU1, and Twilio’s guidelines say Twilio users calling Telstra destinations with Telstra caller IDs “will need to use Twilio Phone Numbers”. The same guideline says “Calling use cases like call forwarding that require the originating service provider to originate a call using a phone number hosted by another provider is protected under the code”, so such caller IDs aren’t banned outright, but Twilio-hosted numbers carry the lowest risk. Either port the number to Twilio or send the call out through the carrier that holds it. That second option is a real reason for BYOC.
Setting up BYOC in Sydney without tripping Australian caller-ID rules
If the carrier passes all four gates, these are the Australia-specific settings, taken from Twilio’s own pages:
- Process calls in AU1. Give your carrier the
{example}.sip.au1.twilio.comtermination address and allowlist the AU1 signalling IPs shown on the trunk’s Networking Info page. Twilio’s Australian guidelines say domestic calls between Australian numbers “must use the sydney edge location” to avoid international gateways, and that calls which do transit them “may be blocked”. - Send numbers in E.164 with the plus sign. Twilio’s Elastic SIP Trunking docs say a number not in E.164 format “will be rejected with a SIP 400 Bad Request response”. Sinch’s SIP documentation asks for the same (“always E.164-formatted”). Normalise 04xx and 02 numbers to +614 and +612 before they reach the trunk.
- Never originate from 13, 1300, 1800 or 1900 numbers. Twilio says these are inbound-only “Do-Not-Originate (DNO) numbers and are blocked by carriers”.
- Check codecs early. For Elastic SIP Trunking, Twilio supports PCMU and PCMA (G.711) by default, with G.729, Opus and AMR-NB in limited availability. Twilio’s BYOC guide doesn’t list codecs separately, so confirm with a test call that both sides offer G.711.
- Configure both authentication methods on termination. Twilio’s BYOC guide says “IP ACLs alone does not protect against certain types of attacks” and recommends credentials on the termination domain as well.
The ACMA separates carriers, which own network units and need a carrier licence to use them to supply services to the public, unless a nominated carrier declaration or an exemption applies, from carriage service providers, which “do not need a licence” but must still follow rules including the Telecommunications Act 1997 and the Telecommunications (Consumer Protection and Service Standards) Act 1999. Twilio’s guideline notes that under the scam-calls code “the obligations of the code fall on the originating service provider”. With BYOC that is your carrier, which is one more reason to ask your carrier, not Twilio, how it handles caller-ID checks.
Building Australian outbound with AI phone agents? Zian AI has been running outbound acquisition since 2017, and its agents handle phone, SMS, email and WhatsApp follow-up with SmartReach AI™ pacing. Apply to work with us during the partnership-application beta.
Frequently asked questions
Can I use my own SIP trunk provider with Twilio in Australia?
Yes. Twilio’s BYOC trunks connect an outside carrier to Programmable Voice, and the BYOC guide lists a Sydney termination address in the form {example}.sip.au1.twilio.com. Twilio charges US$0.0040 a minute each way on Australian BYOC traffic. The carrier must accept Twilio by IP address, because BYOC origination has no credential option.
Which SIP trunk providers work with Twilio BYOC in Australia?
Plivo, DIDWW and Sinch publish step-by-step guides that use Twilio’s BYOC trunk. Plivo and DIDWW also sell Australian numbers, and Plivo publishes Australian rates we could read. Bandwidth and Telnyx document a different route that dials their SIP address with credentials or a token, and Telnyx labels its guide deprecated. CommPeak advertises Twilio support without setup steps. We found no Twilio guide from Symbio or Telstra SIP Connect.
Is Twilio BYOC cheaper than using Twilio’s own Australian numbers?
Only if your carrier charges less than US$0.0212 a minute to landlines or US$0.0710 a minute to mobiles, because Twilio adds US$0.0040 a minute on BYOC. In our worked example of 30,000 minutes a month, mostly to mobiles, BYOC with Plivo saved US$289.50, or 17.3%. A landline-heavy mix saves far less.
Can I keep my Telstra number as the caller ID on Twilio calls?
Not reliably on calls Twilio originates. Twilio’s Australian voice guidelines recommend Twilio numbers as caller ID for Australian calls as the lowest-risk option, and say Twilio users calling Telstra destinations with Telstra caller IDs will need to use Twilio numbers. Verified Caller IDs are not supported in Twilio’s AU1 region. Either port the number to Twilio, or send the call out through the carrier that holds the number using BYOC.
Does Twilio support 000 calls in Australia?
Yes. Twilio lists Australia among its emergency-calling countries and supports 000, 112 and 106, according to its emergency telephone numbers page. Emergency address registration is available only in the US, Canada and the UK. The Department of Infrastructure says the Emergency Call Service Determination 2019 places obligations on carriers and carriage service providers.
Does Twilio have an Australian data centre region?
Yes. Twilio’s AU1 Region is in Sydney and supports Programmable Voice and Elastic SIP Trunking, with listed exclusions such as Verified Caller IDs and BYOC trunks with static IP addresses. Twilio warns that during the rollout it does not guarantee all data stays within the selected region.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| BYOC trunking and SIP interface $0.0040/min to make and receive calls (AU) | Twilio | twilio.com/en-us/voice/pricing/au | 2 October 2026 |
| Programmable Voice outbound AU $0.0252/min landline, $0.0750/min mobile | Twilio | twilio.com/en-us/voice/pricing/au | 2 October 2026 |
| Media Streams $0.0044/min; Conversation Relay $0.07/min | Twilio | twilio.com/en-us/voice/pricing/au | 2 October 2026 |
| Inbound voice $0.0100/min on AU local and mobile numbers | Twilio (number price CSV) | SiteNumbersPricing.csv | 2 October 2026 |
| Elastic SIP Trunking AU termination from $0.0212/min; mobile $0.0710/min | Twilio | twilio.com/en-us/sip-trunking/pricing/au | 2 October 2026 |
| AU1 Region in Sydney; AU1 exclusions (static-IP BYOC, Verified Caller IDs) | Twilio | Regional product and feature availability | 2 October 2026 |
| 3–4 IPs per region; retry next IP after 4 seconds; no credential auth on BYOC origination | Twilio | BYOC Trunking for Programmable Voice | 2 October 2026 |
| SIP 400 Bad Request for numbers not in E.164 | Twilio | Elastic SIP Trunking docs | 2 October 2026 |
| No guarantee all data stays in the selected Region | Twilio | Understanding Twilio Regions | 2 October 2026 |
| Codecs: PCMU/PCMA by default; G.729, Opus, AMR-NB limited availability | Twilio | Elastic SIP Trunking codecs | 2 October 2026 |
| Emergency numbers 000, 112, 106 (Australia) | Twilio | Emergency telephone numbers | 2 October 2026 |
| Local numbers need an Australian address, no PO Box; mobile business address may be anywhere | Twilio | Australia: Regulatory Guidelines | 2 October 2026 |
| Caller-ID rules incl. call-forwarding protection; sydney edge for domestic calls; 13/1300/1800/1900 inbound only | Twilio | Australia: Voice Guidelines | 2 October 2026 |
| Plivo AU outbound $0.0188 landline, $0.0580 mobile, $3.4980 satellite/mobility services; inbound $0.0025 local, $0.0050 mobile | Plivo | plivo.com/sip-trunking/pricing/au | 2 October 2026 |
| Plivo number porting “available for US and Canada only” | Plivo | Plivo number porting docs | 2 October 2026 |
| Plivo Sydney IP block; Twilio BYOC steps | Plivo | Plivo Twilio BYOC guide | 2 October 2026 |
| Telnyx Sydney and Melbourne anchor sites | Telnyx | telnyx.com/australia | 2 October 2026 |
| Telnyx Twilio guide labelled deprecated | Telnyx | developers.telnyx.com | 2 October 2026 |
| Telnyx 000 and IPND handling | Telnyx | Telnyx support | 2 October 2026 |
| DIDWW Twilio BYOC steps (Origination Connection Policy; Account SID authentication) | DIDWW | doc.didww.com Twilio BYOC | 2 October 2026 |
| DIDWW Australian local, mobile and toll-free numbers; portability; emergency-calling support by number type | DIDWW | Local, mobile, toll-free, emergency calling | 2 October 2026 |
| DIDWW PoP list (7 sites, none in Australia) | DIDWW | Network Infrastructure | 2 October 2026 |
| DIDWW Local Outbound Termination priced per destination country; price list sent by email after a request form | DIDWW | SIP trunking pricing | 2 October 2026 |
| Bandwidth Twilio guide uses SipAuthUsername/SipAuthPassword | Bandwidth | BYOC for Twilio on the Universal Platform | 2 October 2026 |
| Bandwidth Australian local, mobile, toll-free, porting, emergency services | Bandwidth | bandwidth.com/coverage/australia | 2 October 2026 |
| Bandwidth Australian mobile porting effective 29 January 2024 (P2P) | Bandwidth | Release note | 2 October 2026 |
| Sinch Twilio BYOC steps | Sinch | Sinch EST Twilio BYOC guide | 2 October 2026 |
| Sinch Network SIP Trunking: “talk to the Sinch team” for international scope | Sinch | Network SIP Trunking | 2 October 2026 |
| Sinch Australian SIP region (apse2); codecs; E.164 | Sinch | Sinch Voice API SIP trunking | 2 October 2026 |
| CommPeak Australian signalling PoP au.sip.commpeak.com | CommPeak | SIP trunking addresses | 2 October 2026 |
| CommPeak IP authentication for SIP accounts (static IPs only) | CommPeak | SIP account authentication | 2 October 2026 |
| CommPeak “10 global PoPs”; AU number types | CommPeak | CommPeak Australia | 2 October 2026 |
| Symbio licensed in AU, NZ, Singapore; direct connection to every AU carrier | Symbio | symbio.global/why-us | 2 October 2026 |
| Telstra SIP Connect: accredited IP PBXs only; 1,000 concurrent calls per public IP; 120-second average holding time; 000 caveat | Telstra | SIP Connect Customer Integration Guide (August 2023) | 2 October 2026 |
| Carrier vs carriage service provider definitions | ACMA | acma.gov.au | 2 October 2026 |
| Emergency Call Service Determination 2019 obligations | Department of Infrastructure, Transport, Regional Development, Communications, Sport and the Arts | infrastructure.gov.au | 2 October 2026 |
| Worked bill totals ($1,676.00, $1,386.50, $289.50, 17.3%) | Zian AI calculation from the Twilio and Plivo rows above | This page | 2 October 2026 |