How to Make International Calls: Australian PBX Guide
- stfsweb
- 1 day ago
- 10 min read
You’re probably in one of two situations right now. Your team needs to call customers, suppliers, or staff overseas, and every option feels wrong. Mobile calls are expensive, consumer apps are inconsistent, and half the online advice assumes you’re in the US instead of Australia.
That’s where small business owners usually lose time. Not on the call itself, but on the mess around it: figuring out the right dialling format, working out why some calls fail, and trying to control costs without making staff jump through hoops.
For Australian businesses, how to make international calls properly comes down to three things. Get the PBX ready, dial in the right format, and use business-grade features that improve connection rates without creating compliance risk.
Preparing Your Hosted PBX for Global Calls
International calling used to be slow, expensive, and uncertain. Australia’s first direct high-capacity trans-Pacific link was the COMPAC submarine cable in 1963, replacing short-wave radio calls that had success rates below 50%. Before that shift, a 3-minute call to the US cost the equivalent of AUD 150 today, which shows how far business telephony has come through modern VoIP and hosted systems, as noted in this history of direct transoceanic dialling.
A lot of consumer-app guides ignore what small businesses need. They focus on one-off calls. They don’t deal with multiple staff, call records, routing, handset setup, permissions, or number presentation. A hosted PBX does.
If you want a broader grounding in the commercial side of cloud calling, this ultimate guide to business VoIP is a useful companion read. It helps frame why desk phones, softphones, and cloud routing matter more once international calling becomes part of day-to-day operations.
Check the plan before staff start dialling
The first practical step is simple. Confirm whether your hosted PBX plan includes international calling by default or treats it as an add-on.
In most business systems, that means checking:
Included destinations. Some plans include selected countries, others bill by destination.
User permissions. International dialling can often be enabled only for nominated extensions.
Outbound call policy. The PBX should decide which trunk handles overseas calls and who can use it.
Rate visibility. Your provider should be able to show a rate deck for the countries you call most often.
That setup matters because it’s where cost control starts. Sales or support staff may need regular overseas access. Admin, warehouse, or internal-only roles often don’t.
Practical rule: Give international access by role, not by default. It keeps spending predictable and reduces avoidable misuse.
Prepare the routing, not just the handset
A Yealink handset such as the T53, T54W, or T57W will place an international call easily enough, but the handset is only the front end. The primary work sits in the PBX and SIP trunk.
Your admin portal should have outbound routes that recognise international patterns and send those calls through the right provider path. If your business uses SIP connectivity, this primer on IP SIP trunk setup for business telephony helps explain the link between your hosted PBX and the carrier network.
A sound business setup usually includes:
PBX area | What to check | Why it matters |
|---|---|---|
Outbound permissions | Which extensions can call overseas | Prevents bill shock |
Route patterns | Recognition of + and 0011 dialling | Stops failed attempts |
Caller ID policy | Which business number presents outbound | Improves trust and answer rates |
Device support | Desk phone and softphone provisioning | Gives staff flexibility |
Set up for flexible work, not just the office
Small business owners often think of international calling as a desk-phone task. It isn’t anymore. If your staff work from home, across multiple sites, or on the road, the same hosted PBX should let them make calls through a softphone with the same business identity and routing rules.
That gives you consistency. The person calling London from a home office should still use the company’s outbound policy, company caller ID, and company call records.
A good hosted PBX makes remote staff feel like they’re sitting in the same office, even when they’re spread across suburbs, states, or countries.
Mastering the International Dialling Process
Most international call failures aren’t complicated. They’re formatting mistakes.
For Australian VoIP users, the most common error is the wrong trunk prefix, which accounts for 25% of failed connections according to the ACMA-related guidance summarised in this international calling mistakes overview. The correct sequence is “+” or “0011”, then the country code, then the number with the leading local zero removed.
Use the Australian format every time
From an Australian hosted PBX, the cleanest way to dial is to store and use numbers in E.164 format. That means the full international number starts with a plus sign, followed by country code and national significant number.
The working sequence is:
Dial + or 0011 On many Yealink handsets and softphones, the plus sign is easiest because it’s internationally standardised.
Enter the destination country code Examples include +1 for the US and Canada, +44 for the UK, and +64 for New Zealand.
Drop the leading zero from the local number If the recipient gives you a number written with a starting zero, remove it before dialling internationally.
Enter the remaining national number Keep the full string clean and consistent in your contacts.
What this looks like in practice
Businesses get tripped up when they copy a number exactly as it appears on a website or email signature. Domestic formatting often doesn’t travel well.
Here’s the logic:
UK example. If a London number is written locally with a leading zero, remove that zero when dialling from Australia, then add +44.
US example. Add +1 before the full national number.
NZ example. Add +64, then remove any local leading zero.
A few habits make this easier:
Save contacts in international format so staff don’t have to rewrite numbers on the fly.
Train staff to think in full numbers rather than local shorthand.
Standardise CRM entries so the PBX, handset, and softphone all use the same format.
Store customer and supplier numbers with the plus sign from day one. It prevents repeat errors and makes click-to-call tools work far more reliably.
Check the PBX settings behind the number
The dial string is only one part of success. Hosted PBX platforms also need clean outbound routing and sensible media settings.
For business use, I’d look at the following before blaming the carrier:
Outbound route pattern. It should accept both + and 0011 where needed.
Codec choice. If your provider supports it, choose a quality setting suited to international voice traffic.
Jitter handling. A properly configured jitter buffer helps smooth unstable links.
Softphone testing. Trial the number from a softphone before rolling it out across the team.
A quick pre-call checklist
Before staff make regular overseas calls, run through this short checklist:
Number format. Is it saved as + country code plus number?
Zero removed. Has the local leading zero been dropped where required?
Extension rights. Does that user have permission to dial internationally?
Correct device. Is the call going through the business PBX, not a personal mobile?
Time zone. Is the recipient likely to answer now?
That last point sounds basic, but it matters. A technically perfect call at the wrong local hour still produces a poor outcome.
Optimising Call Costs and Quality
If you’re still using mobile carriers for regular overseas calls, there’s usually money leaking out of the business every month. Small businesses using mobile carriers can face rates 25-40% higher than with a VoIP PBX, and average SME spending sits at AUD 150-500 monthly on international calls that could often be reduced significantly through hosted PBX routing, according to the ACMA-related figures cited in this guide to business telephone calling costs.
That’s why I usually tell owners not to compare “phone systems” in the abstract. Compare call paths. One path runs through a mobile carrier charging retail international rates. The other runs through a hosted PBX with business routing options, extension control, and central billing.
Cheap isn’t the same as efficient
A low advertised per-minute rate doesn’t always mean a better result. Some least-cost routes are fine. Others save a small amount and create poor audio, answer delays, or unreliable completion.
The practical trade-off looks like this:
Option | Usually good for | Main risk |
|---|---|---|
Mobile carrier international calling | Ad hoc personal use | Higher ongoing cost |
Consumer app | Casual one-to-one conversations | Poor business control and inconsistent presentation |
Hosted PBX with managed routing | Teams, repeat calling, reporting, flexible work | Needs proper setup |
Unknown bargain route | Chasing the lowest sticker price | Quality and reliability can suffer |
The right target isn’t “cheapest possible”. It’s lowest total cost for a call that connects and sounds professional.
Focus on three settings that matter
For small businesses using hosted PBX, I’d pay attention to these first:
Routing policy. Your provider should route common destinations sensibly, not throw every call onto the lowest-cost path.
Codec selection. Voice codecs decide how your audio is compressed and transmitted. Better choices often give cleaner speech over long distances.
Jitter control. International traffic can vary in timing. A jitter buffer helps smooth that variation so conversations don’t sound choppy.
If you’re comparing plan structures, this overview of business telephone plans for Australian organisations is useful for understanding what should be included beyond the handset itself.
Clear voice quality saves money too. Staff repeat themselves less, calls finish faster, and customers don’t ask for follow-up because the line was hard to understand.
What works for small teams
For a business making frequent calls to suppliers in Asia, customers in New Zealand, or prospects in the UK or US, a hosted PBX usually wins because it centralises the whole process:
One provider relationship instead of a patchwork of mobiles and apps
One calling identity across desk phones and softphones
One place to control permissions, records, and reporting
One structure for office staff and remote staff alike
That flexibility is where significant value sits. A phone system that follows the staff member, rather than tying them to one desk or one SIM, saves time every week and removes a lot of workarounds.
Advanced Strategies for Better Connection Rates
Getting an international call to connect is only half the job. Getting the other person to answer is where many teams struggle.
If your staff are calling overseas from an Australian number, the recipient may not recognise it, may assume it’s spam, or may ignore it. Using a local Caller ID can lift pickup rates from 20% to as high as 70%, according to the results referenced in this guide to improving international call pickup rates.
Local presence changes the conversation
A local presence number means your PBX presents a number that looks familiar in the country you’re calling. That doesn’t make the call deceptive when it’s configured properly. It makes the call accessible.
For a small Australian business, this matters most when:
Sales staff are calling leads in one overseas market repeatedly
Account managers need customers to answer without confusion
Service teams call clients who won’t return international missed calls
Remote teams need one consistent identity across countries
When the number looks local, the call feels lower risk to the recipient. That’s often the difference between a missed opportunity and a live conversation.
Remove the awkward pause
One of the fastest ways to lose a prospect is a noticeable silence after they answer. The same guidance notes that a three-second post-connect pause triggers 75% of hang-ups and is problematic under ACMA anti-spam rules when businesses handle outbound calling poorly on automated or badly configured systems.
That pause usually comes from poor routing, bad dialler behaviour, or a PBX that isn’t configured cleanly.
I’d check:
Caller ID presentation
Trunk response timing
Any automated call flow before human speech
Softphone and desk phone consistency across users
For businesses that rely on timed routing and operational modes, features like auto day and night routing in hosted PBX systems make a practical difference. They help teams place and receive calls at the right times, through the right path, with less manual intervention.
A professional outbound call should feel immediate. The other person answers, hears a human voice straight away, and knows who’s calling.
Use timing and channel support properly
Time-based routing isn’t just for inbound calls. It also helps outbound teams avoid poor contact windows. If your staff are calling the US, UK, or Europe, set rules and habits around local business hours instead of leaving it to guesswork.
A few habits work well:
Call when the recipient is likely to be at their desk
Send a short email before first contact if the call is expected
Use voicemail carefully, then retry later rather than hammering the same number
Keep the PBX synced with your CRM so staff see local time and call notes
A short demonstration helps when you’re training staff on outbound handling and response timing:
Don’t sound like a call centre
The strongest setups still fail when the human side is poor. Over-scripted calls sound artificial. Staff who read word-for-word intros get interrupted, screened, or shut down quickly.
What works better is simple:
say the business name clearly
state the reason for the call early
confirm the person has a moment to talk
keep the first exchange natural
That’s how business calling sounds credible. The PBX gives you the tools, but staff still need to use them well.
Ensuring Compliance and Troubleshooting Issues
A lot of businesses start with consumer apps because they seem easy. That works until the call contains client information, staff details, commercial terms, or anything sensitive enough to create legal exposure.
According to a 2026 AusCERT report, 42% of Australian small businesses report international call data breaches, often linked to non-compliant consumer apps, and fines for unencrypted overseas data leaks can exceed AUD 500k, as summarised in this overview of international calling risks and options. For Australian businesses, data sovereignty and provider compliance aren’t side issues. They’re part of choosing the calling method.
What to check before you rely on any platform
If your team is making international calls for business, I’d want clear answers on these points:
Where call data is handled. Australian-hosted services are easier to assess for local obligations.
Whether the provider supports business-grade records. Call detail records and admin controls matter.
Whether number porting and support are handled through a proper business process.
Whether the system fits your privacy obligations, especially where calls involve customer or medical, financial, or legal information.
If your business also deals with multilingual customers or overseas contacts, this article on demystifying real-time language translation is worth reading. It gives useful context on where translation tools can support conversations, and where businesses still need structured communication workflows.
A troubleshooting checklist that solves most issues
When an international call fails, don’t start by assuming the carrier is at fault. Work through the basics in order.
Check the number format Make sure the contact is stored in international format and the leading local zero has been removed where required.
Confirm extension permissions The user may be blocked from making international calls by policy.
Review outbound routing The PBX must recognise the dial pattern and push it through the correct trunk.
Test on another device Try the same destination from a softphone and then from a desk phone. That isolates whether the problem is user-specific or system-wide.
Listen for one-way audio or delay If the call connects but behaves badly, look at codec choice, jitter handling, and local network quality.
Some international call problems are dialling errors. Others are policy errors. Others are audio path problems. Treat them as separate categories and diagnosis gets much faster.
What usually works best
For most Australian small businesses, the safe pattern is straightforward. Use a hosted PBX, keep international dialling rights controlled, present a trustworthy caller ID, and make sure the provider supports Australian business requirements rather than consumer convenience.
That approach gives you something consumer apps never really offer: one managed system for cost control, flexible work, cleaner support, and fewer surprises.
If your business needs a practical hosted PBX setup for international calling, flexible remote work, and Australian-based support, Hosted Telecommunications is worth a closer look. They provide small business phone systems with Yealink handsets, softphone access, number porting, and local support, which makes it much easier to give staff reliable overseas calling without the usual carrier cost and admin headaches.
Comments