Independent Business Communications · Australia needtoknowit.com.au / needtoknowai.com / About / Methodology

VOIP for FIFO and Remote Site Workers in Australia

FIFO workers and remote site businesses have a phone problem that standard office setups do not solve: staff rotate between remote sites and home, connectivity is limited or satellite-based, and the business number needs to reach the right person regardless of where they are.

Our Recommendation

Get a recommendation tailored to businesses like yours. Free and no lock-in.

Independent · Australian-based · No vendor affiliation

Not right for your setup? Get a personalised recommendation →

This guide covers VOIP phone options for Australian FIFO (fly-in fly-out) businesses, remote mining and resources operations, offshore facilities, and any business where staff move between a remote site and a metro base. It covers softphone apps for mobile workers, VOIP over satellite connections, site-to-HQ calling, and why hosted VOIP is better suited to this environment than any on-premise phone system.

The FIFO Phone Problem

A standard office phone system assumes staff are in one place. A FIFO business has the opposite reality: a worker might be at a Perth head office one week, at a Pilbara mine site the next, then back in Perth. Their phone needs to follow them without requiring IT support at the remote end or a separate number for each location.

Where personal mobiles are used without employer-controlled telephony or CRM integration, the business may lack central call records, clients may receive the worker's personal number, and device-held contact history may be lost when the worker leaves. There is a better setup, and it runs on software the worker already has on their phone.

Softphone Apps: Your Phone Number Follows You

A softphone is a phone application that runs on a mobile or laptop and connects to a hosted VOIP service the same way a desk phone does. The worker installs the app on their personal or company mobile. When they make or receive calls through the app, the company's business number appears -- not their personal number. They can be in Perth, at a Bowen Basin mine site, or offshore, and callers see the same business number and reach the same extension.

Softphone apps require only a data connection -- mobile data, Wi-Fi, or satellite broadband. Softphone app availability and pricing vary by provider and plan. For a FIFO workforce, this can mean no additional dedicated phone hardware at the remote site: the worker's mobile acts as the phone, while the site still requires functioning connectivity and network equipment.

VOIP Over Satellite: What You Need to Know

Geostationary satellite connections commonly have roughly 500 milliseconds or more of round-trip propagation delay. Ku and Ka describe frequency bands rather than orbital type; Starlink also uses Ku- and Ka-band antennas. High delay can impair conversational flow and make echo more noticeable; clipping is more commonly associated with packet loss, late packets, jitter-buffer behaviour or echo-control processing. This is manageable with the right configuration but requires attention.

Starlink's low Earth orbit service lists expected latency of 30 to 60 milliseconds for fixed Standard plans and 25 to 60 milliseconds for fixed Priority plans on land, although performance varies by location and plan. Starlink can support VOIP, but performance is not identical to NBN: ACCC testing found lower latency than NBN Fixed Wireless but more packet loss and outages. Test voice quality at each site and adjust network or jitter settings if measurements show a problem.

Codec Selection for High-Latency Links

A codec is the algorithm that compresses voice audio for transmission over the internet. G.711 and G.729 are supported by several Australian VOIP services. G.711 uses more bandwidth, while G.729 is a compressed, lower-bandwidth codec; availability and preference depend on the provider and equipment. On a geostationary satellite link where bandwidth is limited and latency is already high, At a 20 ms packetization interval, Cisco lists approximately 80 kbps for G.711 and 24 kbps for G.729 before Layer-2 overhead, so G.729 uses about 30% as much bandwidth.

Codec availability and priority may be configured at the endpoint, PBX and SIP trunk or provider; the codec used by a call must be supported and negotiated by both ends. Your VOIP provider can advise on the correct codec setting for your connection type. For Starlink connections, G.711 is usually fine. For older geostationary satellite, request G.729 support from your provider.

VOIP Over 4G and 5G for Remote Sites

Modern 4G LTE networks carry VOIP calls well. A softphone app using 4G data can deliver call quality close to a standard office VOIP call where signal is solid, though actual quality depends on signal strength, network congestion and latency at the specific site, not coverage alone. 5G improves this further with lower latency and higher bandwidth, though 5G availability at remote mining or resources sites varies by location and carrier and should be checked site by site.

Where adequate 4G coverage and capacity are available, compare 4G and satellite using site-specific cost, reliability and performance rather than assuming one will be cheaper. Whether a softphone automatically changes between Wi-Fi and mobile data, and whether an active call survives the change, depends on the app and mobile operating system; confirm this behaviour with the provider. Workers do not need to do anything differently -- the app manages the connection.

Site-to-HQ Calling: Free Internal Calls Between Locations

On a hosted VOIP system, all extensions are on the same platform regardless of physical location. A worker at a remote site calling the Perth HQ dials an internal extension, not a geographic number. The call uses the internet connection at both ends; whether same-platform extension calls incur a per-call charge depends on the provider and plan and should be confirmed before deployment. For operations that involve frequent coordination between field staff and HQ, this removes a meaningful cost and simplifies communication.

The same applies to calls between different remote sites. If both sites are configured as extensions on the same hosted VOIP platform, they can call each other as internal extensions; confirm with the provider whether the plan imposes any per-call charge. Many current Australian mobile plans include unlimited standard national mobile calls, so mobile-to-mobile calls often have no incremental per-call charge; compare total plan costs and exclusions instead.

Why Hosted VOIP Beats On-Premise for Remote Operations

An on-premises deployment does not necessarily require a PBX server at every site: centralized call-processing designs can serve remote phones over a WAN, although they create WAN dependency and may use local survivability equipment. At a remote mining or resources site, hardware maintenance is expensive and slow. A failed on-premise PBX at a remote site can knock out communications for days while parts and technicians are sourced.

Hosted VOIP requires no hardware at the remote site beyond a router and the devices staff already have. The PBX is in the cloud, maintained by the provider. Hosted VOIP removes the on-site PBX, and provider-side maintenance is generally handled by the provider. The remote site still depends on power, its router or satellite equipment, the WAN connection and endpoint devices; failover capabilities vary by service and configuration.

Handling Roster Changes: Staff Moving Between Sites

On a hosted VOIP system, reassigning a worker to a different site requires no phone system reconfiguration. The worker takes their mobile with the softphone app to the new location, connects to the site Wi-Fi or uses mobile data, and their extension works identically to how it worked at the previous site. No number changes, no hardware moves, no IT involvement.

When a FIFO worker rotates off site and back to a home office or Perth base, the same applies: they are reachable on the same extension via the app on their mobile, or they pick up a desk phone at the HQ that is registered to their extension. For ordinary extension routing, a worker can change location without reconfiguring the extension. Location still matters for emergency calling: confirm that the service supports 000 and ensure workers can provide their actual location.

What Most FIFO Businesses Get Wrong

One possible problem is running two separate communication systems: a traditional office phone system at HQ and mobile phones for all site staff. Without integration between the office and mobile systems, this may result in no common call record, limited internal transfers and difficulty routing business-number calls to site workers. A single hosted VOIP platform covers both environments from day one.

The second mistake is assuming VOIP will not work on satellite because of earlier bad experiences with high-latency geostationary satellite. Starlink has changed the calculus. Starlink's lower latency can make VOIP more practical than older geostationary satellite, but packet loss and outages vary, so voice quality should be tested at each site. Test with a softphone app on a Starlink connection before concluding VOIP is not suitable.

The third mistake is not separating business calls from personal calls for site workers. A worker using their personal mobile for all business calls has no call history visible to the employer, no recording for compliance, and no clear separation between work and personal communication. A hosted VOIP softphone can separate business calls from personal calls without requiring a separate work mobile; central call logs, recording and retention depend on the provider, plan and configuration.

Your Next Steps

Confirm the connectivity type at each remote site: Starlink, older satellite, 4G, or a fixed link. Starlink or 4G may work with the provider's standard hosted VOIP configuration, but test each site and adjust app, network, codec or jitter settings if measurements or call quality indicate a problem. For older geostationary satellite, ask your VOIP provider about G.729 codec support and jitter buffer settings. Then set up a hosted VOIP plan, assign extensions to each worker, install the softphone app, and test a call from the remote site to HQ.

For a guide to VOIP call quality on NBN and remote connections, see our VOIP call quality guide. For a comparison of hosted VOIP vs on-premise systems, see our cloud vs on-premise phone system guide.

Comparing the Cost: Mobile-Only vs Hosted VOIP for FIFO Operations

Some FIFO businesses rely on workers’ personal or company mobiles, with the business covering or reimbursing some costs; depending on how the service is configured, this may provide no central phone number or centralised call history. For a 10-person operation, the cost of this approach varies by provider, plan, data inclusions and whether workers are reimbursed for calls or given company SIM cards. Without central telephony, CRM integration or employer-managed devices, the business may lack central call records and transfer functions and may lose access to device-held communication history when a worker leaves.

Based on advertised pricing from MaxoTel and GoCall, a hosted VOIP system with softphone apps for 10 workers can cost about $100 to $300 per month, depending on the provider, plan, app fees, call inclusions and GST treatment. Workers use their existing mobiles with a softphone app: the business number appears as the caller ID, Depending on the provider, plan, configuration and retention policy, softphone calls can appear in central call logs and may be recorded and stored in a portal. Confirm recording costs, consent requirements and retention settings before relying on this for compliance. The data usage for softphone calls is low: a one-hour call at G.711 uses approximately 90MB of mobile data. On a standard $30 to $40 AU mobile plan with 10 to 20GB of data, softphone call usage is a small fraction of the plan data allowance.

The financial case for a hosted VOIP system depends on mobile-plan inclusions, whether workers still need mobile data, hosted-plan pricing, call volume, setup costs and optional feature charges, and the operational benefits -- central call history, transferable numbers, call recording, and no dependency on individual workers' personal phone numbers -- become significant as the roster grows.

Setting up VOIP for a FIFO or remote site operation?

Get a Free Recommendation

For FIFO businesses ready to move to a hosted VOIP system, our comparison of the best phone system for small business in Australia covers the top AU-hosted options, including which providers support softphone apps on mobile data and which ones offer per-user seat pricing suited to variable FIFO rosters.

The VOIP setup challenges for FIFO businesses overlap with the broader remote teams problem: calls need to reach workers regardless of location, and call history and voicemail need to be accessible from any device. For a full breakdown of how hosted VOIP handles distributed team communication, see our guide to VOIP for remote teams in Australia.

For fixed site locations such as camp offices or control rooms where a physical handset is preferred, the Yealink W76P DECT system supports up to 10 cordless handsets on a single base station and supports up to 10 SIP accounts; confirm provisioning, feature support and compatibility with the chosen Australian VOIP provider. It is a practical option for camp environments where workers need to move between areas without losing calls, and it avoids mobile data dependency for on-site communication.

Does VOIP work on satellite internet at remote Australian sites?
VOIP can work over Starlink, which lists 25 to 60ms latency for fixed Standard and Priority plans on land, though latency can be higher for mobility and some remote locations. VOIP on older geostationary satellite (500 to 800ms latency) is possible but requires codec tuning: use G.729 instead of G.711 to reduce bandwidth, and enable jitter buffer settings if the softphone or phone supports it. Confirm satellite VOIP support with your AU provider before deploying.
How do FIFO workers keep a business number when moving between sites?
A softphone app on a worker's mobile registers them as an extension on the hosted VOIP system regardless of physical location. At the mine site, on Starlink or 4G, or back at the Perth office, the same extension number reaches them. Callers see the business number, not the personal mobile. The worker does not need a separate work phone or any hardware at each site.
Can remote site staff call HQ for free on a VOIP system?
Yes. On a hosted VOIP system, all extensions are on the same platform regardless of location. A worker at a remote site calling the head office dials an internal extension number. The call travels over the internet connection at both ends; confirm with the provider whether internal extension calls are included without a per-call charge. The same applies to calls between two remote sites, as long as both sites have a data connection and the VOIP app installed.
Why is hosted VOIP better than an on-premise system for remote sites?
On-premise PBX hardware at a remote site is expensive to maintain, slow to repair when it fails, and requires IT support at the location. Hosted VOIP requires no hardware at the remote site beyond a router and the devices staff already carry. The phone system is maintained in the cloud by the provider. Provider-managed updates may happen automatically, but failover capability depends on the hosted service, plan and configuration. For a remote mining or resources operation, removing on-site hardware dependency is a significant operational simplification.
Does VOIP work on 4G for FIFO workers in regional Australia?
Yes. Modern 4G LTE networks carry VOIP calls well. A softphone app using 4G data can deliver call quality close to a standard office VOIP call where signal is solid, though actual quality depends on signal strength, network congestion and latency at the specific site, not coverage alone. Whether a softphone automatically changes between Wi-Fi and mobile data, which network it prefers, and whether an active call survives the change depends on the app, device and operating-system settings; confirm and test this behaviour before deployment.
What codec should be used for VOIP over satellite?
For Starlink (low latency LEO satellite), G.711 is suitable and delivers good call quality. For older geostationary satellite with high latency (500ms or more), G.729 uses less bandwidth than G.711, but jitter is handled by the receiving endpoint's jitter buffer and satellite propagation delay remains. Codec choice should also account for provider support, packet loss and measured call quality. G.729 quality is slightly lower than G.711 but is entirely adequate for voice calls. Codec availability and priority may be configured at the softphone or IP phone, PBX, session border controller and SIP trunk or provider; the selected codec must be supported and negotiated across the relevant call path. Ask your provider to confirm G.729 support.

VOIP for a remote or FIFO operation

Get a Free Recommendation
Got a question about your situation? Ask us directly. We reply personally, usually within one business day.
Ask a Question →