Best Voice AI for Inbound Calls on an AU Number - Zian AI

Best Voice AI for Inbound Calls on an AU Number

Quick answer: Decide how calls will reach the agent (a platform number, a port, a SIP trunk or call forwarding) before you choose a platform. Of ten platforms we checked on 4 October 2026, six supply an Australian number: Twilio, Telnyx, Synthflow, Voxworks, AiDial and ElevenLabs Reception.ai. Vapi, Retell AI and ElevenLabs Agents need one you bring; Bland documents porting in but not which countries qualify. From Sydney, Twilio’s Sydney edge and Bland’s Asia-Pacific SIP edge answered in about 1 ms; Telnyx, a carrier with its own AI agents, also lists an Australian SIP region. The other agent platforms’ SIP hosts we timed took about 140 to 297 ms.

If you typed “best voice AI platform for automating inbound calls with an Australian phone number”, you are really asking three things. Can the platform answer on a +61 number at all? How does a call to that number reach the AI: a number the platform rents you, one you port in, a SIP trunk, or plain call forwarding? And where is the call processed once it arrives? This page answers each from the vendors’ own documentation, read on 4 October 2026, plus one measurement of our own. Australian outbound caller ID is a different problem, covered in our guide to AI cold calling from an Australian local caller ID. This page is inbound only.

Our #1 pick: Zian AI. AI receptionist and appointment-setting agents that answer inbound calls 24/7, book appointments, handle answering machines and voicemail, and follow up by voice, SMS, WhatsApp, Instagram and Facebook in 30+ languages, with HubSpot, Salesforce, HighLevel and Zapier integrations. In partnership-application beta. Apply For Partnership

Best done-for-you option: LeadsNow.ai. A pay-per-result AI appointment setting agency that runs the agents for you: leads answered in under 60 seconds, 24/7, and 50,769+ appointments set. leadsnow.ai

Which voice AI platforms can answer inbound calls on an Australian number?

All ten can answer a call to a +61 number. The difference is who supplies the number, and how much carrier work lands on you. Every cell below comes from that company’s own page (links in the source table at the end).

Platform Australian number supplied by the platform? How an existing Australian number gets in Region facts the vendor publishes
Twilio (Programmable Voice; the carrier layer six other platforms here can connect to) Yes. Local, mobile and toll-free (1800), each behind a regulatory bundle Port in: local, mobile, 1300, 1800 and 13 numbers are listed as portable AU1 Region “located in Sydney”. Incoming calls go to US1 unless you set a different processing Region
Telnyx (carrier with its own Voice AI Agents) Yes. Local, national and toll-free; its requirements page also covers 1300 shared-cost numbers Port in through the portal or API (self-stated) Says it runs “AI compute, telephony, and edge nodes in the same Sydney facility” (self-stated). Lists an Australian SIP region, sip.telnyx.com.au
Synthflow Yes, at US$1.50 a month, sold “for quick testing”. An address is required Connect your Twilio account, or import over SIP (Enterprise plan only) Three regions: Global, US and EU
Voxworks (Australian-built) Yes. Area (02/03/07/08) and mobile (04) numbers from its own pool Call forwarding (self-serve). Porting is “not yet available”; bringing your own carrier is not self-serve Storage, including call recordings, in AWS Sydney (ap-southeast-2)
AiDial (Australian-built) Yes, a new dedicated number, provisioned through its telecommunications provider Its home page says it can “usually” work with your setup through “call forwarding, SIP routing, a dedicated number or porting, depending on your carrier”. Its pricing FAQ describes forwarding your main number to the AI line Says it is “AI Hosted & Processed in Australia” (self-stated)
ElevenLabs Reception.ai (ElevenLabs’ receptionist product) Yes, through a regulatory request. Australia is on its list; only US and Canadian numbers are “Instant, no paperwork” Forward an existing number (“forward unanswered calls”), or bring a Twilio or SIP-trunk number A number held for regulatory review “Cannot receive calls or texts until the request is approved”
Vapi No. Free Vapi numbers “use US area codes and support US national calling only” Import a Twilio, Vonage or Telnyx number, or bring your own SIP trunk Its Twilio SIP guide lists two regions: US (sip.vapi.ai) and EU (sip.eu.vapi.ai)
Retell AI No. “Retell-managed numbers are US and Canada only” Custom telephony over SIP, such as a Twilio elastic SIP trunk Its latency guide says to “use a phone number in the same region as your users”
ElevenLabs Agents (developer platform) Its Phone Numbers API endpoint is titled “Import phone number”; the docs describe connecting Twilio, SIP trunks and other carriers A Twilio number you bought, or a SIP trunk. Twilio Verified Caller IDs cannot take inbound calls Twilio numbers route through us1 by default; its regional-routing guide lists au1 (Australia) among the regions you can set. Its static SIP block spans US, EU, India and Singapore
Bland Not for sale outside the US and Canada. Its Dispatch page says buying is “United States and Canada only, $15/month” and, separately, “Anywhere else, bring your own.” A new organisation’s one free number lets you “pick a country”, but the page does not list which countries, as at 4 October 2026 Connect your Twilio account, point your carrier or PBX at Bland over SIP, or port in. Its SIP page documents porting, which “typically takes 7 to 14 business days”; it does not state which countries’ numbers are eligible, as at 4 October 2026 Four regional SIP edges: United States, Canada, Asia-Pacific (asia2.sip.bland.ai) and Europe, with separate signalling and media IPs

So the honest short list depends on your starting point. If you have no number yet and want the platform to hand you one, the first six rows do that. If your Australian number already lives with a carrier, every row can work, but the last four mostly make you run the carrier side yourself. Bland is the partial exception: it documents porting numbers in, without saying which countries qualify. Note that ElevenLabs appears twice: its receptionist product, Reception.ai, offers Australian numbers, while its developer platform, ElevenLabs Agents, imports them.

The Number–Path–Region check

We use three questions, in this order, to pick an inbound stack. We call it the Number–Path–Region check. Each answer rules options in or out before the next question matters.

  1. Number: which number must the caller dial? Is it a new number, or the one already on your website, your vehicles and your Google listing?
  2. Path: how does a call to that number reach the agent? There are four paths: a number the platform supplies, a port into the platform’s carrier, a SIP or BYOC trunk from your carrier, or call forwarding from your carrier.
  3. Region: where is the call processed? Where does the audio go between the moment the caller stops speaking and the moment the agent replies?

The quotable version: for inbound calls in Australia, the number decides who your callers reach, the path decides how long you wait to go live, and the region decides how long each reply takes.

The four ways to put an AI agent on an Australian inbound number

Path Keeps your existing number? Published time to live Who holds the number afterwards The catch, in the vendor’s words
Platform-supplied number No, callers dial a new number Voxworks: a pool number “is claimed immediately”. Twilio: up to five business days for the KYC review The provider. AiDial: “the number remains registered to or controlled by AiDial or its provider” unless agreed in writing Synthflow sells Australian numbers “for quick testing”; for production it says to bring numbers from Twilio or another SIP provider
Port in Yes Twilio: local numbers “up to 6 weeks”, mobile “1 week”, 1300/1800/13 “up to 6 weeks”. Bland: “typically takes 7 to 14 business days” The carrier you ported to Twilio ports mobiles only from a listed set of carriers: Telstra, Lebara, Lyca Mobile, Telstra Wholesale Service Providers, TPG-Vodafone, Vodafone Service Providers and Pivotel
SIP or BYOC trunk Yes, if your carrier can trunk it Not published as a duration; it is engineering work on both sides Your carrier Synthflow limits custom SIP numbers to Enterprise. Voxworks says connecting your own carrier is “Not self-serve today”
Call forwarding Yes Voxworks: it “takes a few minutes with standard carrier dial codes, and is fully reversible” Your current carrier (you also keep the AI number) Voxworks: “the forwarded leg of each call may be billed to your account depending on your plan.” AiDial: you maintain service for both numbers

Forwarding is easy to overlook, and for inbound it is often the right first step. It is useless for outbound caller ID, but for answering calls it gets the agent onto your existing number in minutes. Voxworks documents the standard Australian GSM codes. *21*<number># forwards every call. *61*<number># forwards only unanswered calls, after about 15 seconds by default. Telstra and Optus let you set the ring time from 5 to 30 seconds; Vodafone fixes it at 15 seconds. Voxworks also warns that many prepaid plans, including Vodafone prepaid, amaysim, Kogan and felix, do not support conditional forwarding.

Forwarding also solves the porting gap. A Twilio port of an Australian local number can take up to six weeks. Forward the number to a temporary AI number on day one, then switch the agent onto the ported number once the carrier gives you a date. Twilio’s porting article says to configure the number before the porting date: “This will minimise the service downtime.”

A trunk makes sense when you already run a PBX or contact centre and want the AI to sit inside it, taking overflow or after-hours calls. If you build on Twilio but your numbers stay with another carrier, Twilio’s BYOC trunk is, in its own words, “A SIP Trunk to interconnect your PSTN Carrier to the Twilio platform.”

What Australian numbers need before an AI can answer them

Every route ends at a carrier that must know who you are. The requirements below are each provider’s own, read on 4 October 2026. Twilio says its Australian KYC policy reflects “current expectations” under the Scams Prevention Framework and that the details “are subject to change”, so check the page on the day you apply.

Provider and number type Address rule Other documents (business applicant) Published review time
Twilio, local Must be within Australia; no PO Box ASIC long-form extract, ABN or ACN, proof of address, representative’s ID, a Letter of Authorisation if the representative is not on the extract “The review can take up to five business days”
Twilio, mobile Business address “May be anywhere in the world” Commercial registry or equivalent, business ID number Same KYC article: up to five business days
Twilio, toll-free (1800) Anywhere in the world; no PO Box No documents at submission; details are digitally verified. Representative’s email domain “should match business name or website” Same KYC article: up to five business days
Telnyx, local Address in Australia, with proof dated within 3 months Authorised representative’s name “approximately 72 hours” once documents are received
Telnyx, toll-free and 1300 shared-cost Worldwide address Toll-free also asks for the representative’s passport or ID and proof of address within 3 months Same page: about 72 hours
Voxworks, pool numbers A team service address on every assigned number Pool numbers are “already provisioned”; business verification needs company name, address and ABN where it applies “typically takes 3–5 business days” where verification applies
Synthflow, Australian numbers An address is required to buy one Not listed on the phone numbers page “Address validation may take some time”

Two inbound-specific points sit under that table. First, the service address is not paperwork for its own sake. Voxworks explains that carriers supply it to the Integrated Public Number Database (IPND), the register Triple Zero (000) services use to help locate callers. Second, some number types are inbound-only by rule. Twilio’s Australian voice guideline says 13, 1300, 1800 and 1900 numbers “must be used for inbound calls only”. That makes them natural homes for an AI answering line, and useless as its outbound caller ID. For what each number type signals to callers, see our guide to Australian +61 number types for AI voice agents. For how long the bundle review takes when it is rejected, see how long UK and Australian number KYC review takes.

Twilio also flags a trap for local numbers taken from another charging district. Calls to such a number “will be charged as if you were located within the relevant charging district”, and “You may not be able to port the number to another service provider.” If you might move platforms later, pick a local number from the district you operate in.

Answering calls is half the job. Zian AI runs autonomous agents across live phone, SMS, email and WhatsApp, including a Customer Support Agent that works 24/7 in 30+ languages, with CRM integrations for HubSpot, Salesforce and HighLevel. Zian is in partnership-application beta.

Apply For Partnership

How much latency does an offshore AI platform add to an Australian call?

We measured it. On 4 October 2026, between 13:06 and 13:12 UTC, we opened TCP connections from a server in AWS’s Sydney region (ap-southeast-2) to the SIP signalling host each platform publishes for inbound calls. Bland’s four regional edges accept SIP only over TLS on port 5061, so we timed them on that port the same way, between 13:32 and 13:33 UTC. We ran three rounds of 15 connections each. A TCP handshake takes one network round trip, so the median handshake time is the network round trip from Sydney to that host. It does not include speech recognition, the model or text-to-speech. A platform’s signalling and media servers can also sit in different places, so treat each figure as the distance to that platform’s front door.

Destination (vendor-published host, or a name on the vendor’s published pattern) Where it is Median round trip from Sydney, per round
Twilio sydney edge (test.sip.sydney.twilio.com) Sydney 1.2 ms in all three rounds
Bland Asia-Pacific edge (asia2.sip.bland.ai, TLS port 5061) Asia-Pacific region (city not stated) 0.6–1.5 ms
Twilio umatilla edge US West Coast (Oregon) 139.5–139.7 ms
Vapi US region (sip.vapi.ai) US region 139.5–139.7 ms
Retell AI (sip.retellai.com) Not stated on the pages we read 139.6–139.9 ms
Bland United States edge (us2.sip.bland.ai, TLS port 5061) United States region 139.6–140.0 ms
ElevenLabs Singapore residency (sip-static.rtc.sg.residency.elevenlabs.io) Singapore residency region (an Enterprise feature) 162.1–166.4 ms (two rounds)
ElevenLabs default (sip.rtc.elevenlabs.io) Default US/International environment 187.7–188.5 ms (two rounds)
Synthflow (sip.synthflow.ai, port 32681) Global region (Synthflow’s legacy cluster, which it says it is retiring in Q4 2026; Synthflow says new workspaces should use its US or EU clusters, whose SIP hosts we did not time) 198.4–198.9 ms (two rounds)
Bland Canada edge (ca2.sip.bland.ai, TLS port 5061) Canada region 195.5–196.3 ms
Twilio ashburn edge US East Coast (Virginia) 197.0–208.3 ms
Bland Europe edge (eu2.sip.bland.ai, TLS port 5061) Europe region 252.6–252.8 ms
Vapi EU region (sip.eu.vapi.ai) EU region 296.4–296.7 ms

Why it matters: every reply the agent gives costs about one extra round trip. The caller’s last word has to reach the platform before it can start answering, and the first syllable of the answer has to travel back. Vapi says its end-to-end voice processing is “typically around 800 milliseconds”. It does not say where that was measured, but if an Australian caller adds a 140 ms round trip on top, each turn is 940 ms, 17.5% longer. On an EU-region workspace the round trip is about 296 ms, which would make it about 1,096 ms per turn.

Of the agent platforms in the latency table, Bland is the one with a published SIP edge about as close to Sydney as Twilio’s own Sydney edge. That shows where a call enters Bland, not where its model, speech recognition or text-to-speech run. Bland separates signalling from media, lists different media IPs for each region, and its SIP page does not say where the AI processing for an Asia-Pacific call happens. Ask before you rely on it for reply speed.

We left Telnyx out of the table on purpose. Telnyx anchors call audio at a separately chosen AnchorSite, which by default it picks by measured latency, so a handshake with its signalling host would say nothing about where the audio goes. Telnyx does publish an Australian SIP signalling region, sip.telnyx.com.au, and says its SIP regions “affect only the signaling path”.

One default catches inbound teams on Twilio itself. Twilio’s regions guide says “Incoming calls and messages are routed to US1 if no specific routing is specified”, even for an Australian number. It gives the example of an IVR on Australian servers behind a US1 number and says “a certain degree of elevated round-trip latency is unavoidable”, causing “an awkward period of silence” after the caller’s input. If your agent runs in Sydney, set the number’s inbound processing Region to AU1. Twilio’s AU1 Region supports Programmable Voice and Elastic SIP Trunking, minus a published list of exclusions, among them Verified Caller IDs, <Connect><VirtualAgent> and BYOC trunks with static IP addresses. Check that list against the features your agent uses. Twilio also says that during the rollout it “doesn’t guarantee that all data will remain within your selected Region”. ElevenLabs makes the same default point: Twilio numbers route through us1 “even if the phone number itself is from another country”. Its regional-routing guide lists au1 for Australia and says to choose a region “closest to your users for optimal latency”, but it describes this as Twilio’s routing setting, not a separate ElevenLabs region.

What an inbound Australian AI line costs at the number layer

The number is the cheap part. This worked example uses Twilio’s published Australian rates, in US dollars, as at 4 October 2026: its number price list (CSV) and its Australian voice pricing page, which is marked “current as of August 2026”. Assume 1,200 inbound calls a month at an average of 3 minutes, so 3,600 minutes.

Line type Monthly number fee Inbound rate per minute Arithmetic Number-layer cost Plus Conversation Relay at $0.07/min
Local (02/03/07/08) $3.00 $0.0100 $3.00 + 3,600 × $0.0100 $39.00 $39.00 + $252.00 = $291.00
Mobile (04) $8.25 $0.0100 $8.25 + 3,600 × $0.0100 $44.25 $44.25 + $252.00 = $296.25
Toll-free (1800) $20.00 $0.0500 $20.00 + 3,600 × $0.0500 $200.00 $200.00 + $252.00 = $452.00

Two findings. A 1800 number costs five times as much per inbound minute as a local or mobile number. At 3,600 minutes, that is $161.00 a month more than a local line. And on a local line, the AI layer is most of the bill: Conversation Relay alone is $252.00 of the $291.00. Twilio’s pricing page is not fully consistent: its in-depth “Receive calls” table lists the mobile and toll-free rows the other way round. The CSV and the page’s summary table agree with each other, so we used them. Forwarding adds whatever your existing carrier charges for the forwarded leg, which Voxworks says depends on your plan. None of these figures include speech recognition, model or voice costs on a platform that bills them separately.

Which inbound setup fits your situation?

If this is you Path Platforms that document it What to check first
Your existing number is printed everywhere and you need the agent answering this week Call forwarding to an AI number Voxworks (self-serve forwarding guide); AiDial (forward to its AI line); ElevenLabs Reception.ai (forward unanswered calls); any platform with an Australian number That your plan supports conditional forwarding, and what it charges for the forwarded leg
You want the agent and the number on one account long term Port in, forwarding in the meantime Twilio (local, mobile, 1300, 1800, 13); Telnyx (self-stated porting); Bland (porting documented; eligible countries not stated, as at 4 October 2026) Up to 6 weeks for a Twilio local port; whether your mobile’s carrier is on Twilio’s port list
You run a PBX or contact centre and want AI on overflow or after hours SIP trunk Vapi, Retell AI, ElevenLabs Agents and Reception.ai, Bland; Synthflow on Enterprise; AiDial (“SIP routing”) The platform region your trunk lands in (see the latency table)
You want a national 1300 or 1800 number answered by AI Toll-free number from a carrier, imported or trunked Twilio (1800 numbers for sale; 1300 and 13 numbers by port-in, and it activates Australian toll-free numbers through its porting form); Telnyx (toll-free and 1300 requirements published) The 1800 inbound rate: $0.0500/min on Twilio against $0.0100 for local
Your callers must not hear a gap before each reply Keep processing near Sydney Twilio AU1 with a Sydney-hosted agent; Telnyx and AiDial say they process in Australia (self-stated), and Telnyx lists an Australian SIP region (sip.telnyx.com.au); Bland’s Asia-Pacific SIP edge (asia2.sip.bland.ai), measured at about 1 ms from Sydney, though its SIP page does not say where the AI runs The number’s inbound processing Region: Twilio defaults to US1
You only want to hear it work before committing Platform-supplied test number Synthflow (US$1.50 a month, “for quick testing”); Voxworks (trial number held 14 days) That you can move to a production number later without reprinting anything

Who each option is wrong for

Twilio is wrong for you if nobody on your team will configure regions, bundles and an AI connector. It is a carrier and a toolkit, not a finished agent, and its default sends Australian inbound calls to US1.

Telnyx suits teams that want the carrier, the numbers and the AI from one vendor with Sydney infrastructure. It is wrong for you if you need independent evidence of its onshore claims before you buy: the Sydney GPU and data statements are Telnyx’s own.

Synthflow is wrong as your long-term production number by its own guidance: it sells Australian numbers “for quick testing”, and importing your own number over SIP needs Enterprise.

Voxworks is wrong for you, as at 4 October 2026, if you must move your existing number onto the platform. Porting is “not yet available” and own-carrier connections are not self-serve, so you forward instead. Its residency statement covers storage, including call recordings, in AWS Sydney.

AiDial is wrong for you if you need to own the number it gives you. Unless your Scope of Work provides for a customer-supplied or ported number, the number stays with AiDial or its provider, with no guarantee “that it can be ported or retained after termination”.

ElevenLabs Reception.ai is wrong for you if the agent must answer on a brand-new Australian number from day one. An Australian number needs a regulatory request, and a held number cannot receive calls until it is approved. Forwarding your existing line avoids that wait.

Vapi, Retell AI and ElevenLabs Agents are wrong for teams with nobody to run a carrier account. With all three, the Australian number comes from a carrier account you run, and the SIP hosts we measured for them were 139 ms or more from Sydney. Retell’s own docs disagree with themselves on numbers. Its purchase page says “Currently we only support purchase of US and Canada numbers”, but its international page says “Retell also offers international numbers to purchase”. We went with the more specific purchase page.

Bland is wrong for you if you need to buy an Australian number from the platform: it sells only US and Canadian numbers. It documents porting numbers into Bland “without maintaining a separate SIP provider”, but its SIP page does not state which countries’ numbers are eligible, as at 4 October 2026, so run its portability check on your number first. Its Asia-Pacific SIP edge measured about 1 ms from Sydney, the closest of any agent platform we timed, but that shows where calls enter, not where the model runs. Bland’s docs also carry a banner saying the product “is getting a major upgrade”, so recheck its options before you build.

Where does Zian AI fit? Zian AI is an autonomous AI sales-agents platform, not a carrier. Its AI customer support agents for 24/7 tier-1 resolution work across phone, SMS, email and WhatsApp, and SmartReach AI™ sets the channel, timing and pacing of follow-up. Teams with data-residency requirements can deploy models privately on their own infrastructure. Ask us the same three questions you ask everyone above: whose number, which path, which region.

An inbound caller has already chosen to call you. Zian’s agents have set 50,769+ qualified sales appointments, and they follow up across phone, SMS, email and WhatsApp. Apply to work with us during the partnership-application beta.

Apply For Partnership

Frequently asked questions

Can I keep my existing Australian business number and have an AI answer it?

Yes, in three ways. Forward it to the AI platform’s number, which Voxworks says takes a few minutes with standard carrier dial codes. Port it to a carrier the platform connects to. Or, if your carrier offers it, trunk it to the platform over SIP. A Twilio port of a local number can take up to six weeks, so many teams forward first and port later.

Which AI voice platforms sell Australian phone numbers directly?

Of the ten we checked on 4 October 2026, six supply one. Twilio, Telnyx, Synthflow and Voxworks sell or assign Australian numbers. AiDial provisions one through its provider, and ElevenLabs Reception.ai offers one after a regulatory request. Synthflow labels its numbers “for quick testing”. Vapi, Retell AI and ElevenLabs Agents need a number you bring through an import or a SIP trunk. Bland sells only US and Canadian numbers; it documents porting numbers in but does not state which countries qualify, as at 4 October 2026.

What documents do I need for an Australian number for an AI agent?

For a Twilio local number, a business needs an address within Australia (not a PO Box) with proof of it, its ABN or ACN, the ASIC long-form company extract, the representative’s ID, and a Letter of Authorisation if that person is not on the extract. Twilio’s Australian KYC article says the review “can take up to five business days”.

Why does my AI agent pause before every answer on an Australian number?

Often because the call is processed overseas. Twilio routes incoming calls to its US1 Region unless you choose another, even for Australian numbers. Twilio says US1 is located in the eastern United States; from a Sydney server we measured round trips of about 197 to 208 ms to Twilio’s Virginia (ashburn) edge, against 1.2 ms to Twilio’s Sydney edge. Set the number’s processing Region to AU1 if your agent runs in Australia.

Can a 1300 or 1800 number be answered by an AI agent?

Yes, and they suit it, because Twilio’s Australian voice guideline says 13, 1300, 1800 and 1900 numbers must be used for inbound calls only. Twilio lists 1300, 1800 and 13 numbers as portable. On Twilio a 1800 number costs $0.0500 a minute inbound, five times the local rate.

Does call forwarding to an AI number cost extra?

It can. Voxworks warns that the forwarded leg of each call may be billed to your account depending on your plan, and that many prepaid plans do not support conditional forwarding at all. AiDial notes you keep paying for both your original number and the AI line.

Where every figure on this page comes from

Figure Who published it Link Date read
Round-trip medians from Sydney: 1.2 ms (Twilio sydney), 0.6–1.5 ms (Bland asia2), 139.5–139.9 ms (Twilio umatilla, Vapi US, Retell), 139.6–140.0 ms (Bland us2), 162.1–166.4 ms, 187.7–188.5 ms (ElevenLabs), 195.5–196.3 ms (Bland ca2), 197.0–208.3 ms (Twilio ashburn), 198.4–198.9 ms (Synthflow), 252.6–252.8 ms (Bland eu2), 296.4–296.7 ms (Vapi EU); 940 ms, 17.5%, 1,096 ms per-turn arithmetic Zian AI measurement (AWS ap-southeast-2, 3 rounds × 15 TCP handshakes, 13:06–13:12 UTC; Bland on TLS port 5061, 13:32–13:33 UTC) and calculation This page 4 October 2026
AU1 Region located in Sydney; AU1 exclusions (Verified Caller IDs, <Connect><VirtualAgent>, static-IP BYOC) Twilio Regional product availability 4 October 2026
Incoming calls routed to US1 by default; US1 “located in the eastern United States”; no guarantee data stays in Region Twilio Understanding Twilio Regions 4 October 2026
BYOC trunk definition Twilio BYOC Trunking for Programmable Voice 4 October 2026
Edge locations: sydney, umatilla (Oregon), ashburn (Virginia) Twilio Edge Locations 4 October 2026
Number fees $3.00 local, $8.25 mobile, $20.00 toll-free; inbound $0.0100, $0.0100, $0.0500 per minute Twilio Number price list (CSV) 4 October 2026
Conversation Relay $0.07/min; “current as of August 2026”; receive-calls rows Twilio Programmable Voice pricing, Australia 4 October 2026
Port timelines: local up to 6 weeks, mobile 1 week, 1300/1800/13 up to 6 weeks; mobile donor carrier list Twilio Australia Porting 4 October 2026
KYC review up to five business days; business documents; Scams Prevention Framework notice Twilio Know Your Customer (KYC) in Australia 4 October 2026
Address rules by number type; charging-district note Twilio Australia: Regulatory Guidelines 4 October 2026
13/1300/1800/1900 inbound only; inbound call receives originator’s caller ID Twilio Australia: Voice Guidelines 4 October 2026
About 72 hours to validate; address and proof-of-address rules incl. 1300 shared-cost Telnyx Australia DID Requirements 4 October 2026
Sydney inference, telephony and edge “in the same Sydney facility”; porting (self-stated) Telnyx Telnyx Australia 4 October 2026
AnchorSite media selection; latency is the default Telnyx Guide to SIP AnchorSite Settings 4 October 2026
Australian SIP region sip.telnyx.com.au; SIP regions “affect only the signaling path” Telnyx SIP information (signalling addresses and regions) 4 October 2026
Australian numbers US$1.50/month “for quick testing”; Enterprise for custom SIP numbers Synthflow Phone Numbers 4 October 2026
Regions Global, US, EU; sip.synthflow.ai (Global) port 32681 Synthflow SIP trunking network guidelines 4 October 2026
Pool of 02/03/07/08 and 04 numbers; porting not yet available; 14-day trial hold Voxworks Phone Numbers 4 October 2026
Own-carrier connection not self-serve; forwarding “takes a few minutes” Voxworks SIP Trunking & BYO Carrier 4 October 2026
Forwarding codes; ~15-second default; 5–30 second ring time on Telstra and Optus; forwarded-leg charges; prepaid limits Voxworks Forward Your Existing Number 4 October 2026
Service address and IPND; verification 3–5 business days Voxworks Service Addresses & Regulatory Verification 4 October 2026
Storage in AWS Sydney (ap-southeast-2) Voxworks Security & Compliance Overview 4 October 2026
Dedicated number; forwarding keeps both services; number stays with AiDial unless agreed; hosted and processed in Australia (self-stated) AiDial AI Call Pricing 4 October 2026
Australia among “With a regulatory request” countries; US and Canada instant; held numbers cannot receive calls until approved; forwarding unanswered calls ElevenLabs (Reception.ai) International numbers and Phone numbers 4 October 2026
Phone Numbers API endpoint titled “Import phone number”; telephony integrations listed ElevenLabs ElevenLabs docs index 4 October 2026
Works through “call forwarding, SIP routing, a dedicated number or porting, depending on your carrier” AiDial AiDial home page 4 October 2026
Free numbers US-only and inbound-only Vapi Creating Free Phone Numbers 4 October 2026
Imports from Twilio, Vonage, Telnyx or bring-your-own Vapi Create Phone Number 4 October 2026
SIP regions US (sip.vapi.ai) and EU (sip.eu.vapi.ai) Vapi Twilio SIP Integration 4 October 2026
“typically around 800 milliseconds” Vapi Frequently Asked Questions 4 October 2026
Managed numbers US and Canada only Retell AI Purchase a number 4 October 2026
“Retell also offers international numbers to purchase” Retell AI International calling 4 October 2026
sip.retellai.com origination URI Retell AI Connect Retell to Twilio 4 October 2026
Use a number in the same region as your users Retell AI Troubleshoot high latency 4 October 2026
Purchased Twilio numbers inbound and outbound; Verified Caller IDs outbound only ElevenLabs Twilio native integration 4 October 2026
Twilio numbers route through us1 by default; au1 among the regions you can set; “closest to your users for optimal latency” ElevenLabs Twilio regional routing 4 October 2026
Legacy Global cluster retiring during Q4 2026 Synthflow Data Region 4 October 2026
Data residency is an Enterprise feature ElevenLabs Data residency 4 October 2026
Static SIP block across US, EU, India and Singapore; SIP hostnames ElevenLabs SIP trunking 4 October 2026
Buy numbers US and Canada only, $15/month; bring your own elsewhere Bland Dispatch 4 October 2026
Inbound and outbound SIP; four regional edges (us2, ca2, asia2, eu2), TLS 5061 only, separate media IPs; porting “typically takes 7 to 14 business days”, “without maintaining a separate SIP provider” Bland SIP 4 October 2026
Worked cost table ($39.00, $44.25, $200.00, $252.00, $291.00, $296.25, $452.00, $161.00) Zian AI calculation from the Twilio rows above This page 4 October 2026

Related Blogs

Related from Zian AI