Australian Owned-Not Rented
We don’t rent a cloud platform. We own the server hardware, employ the engineers, and control the entire stack — which is the only reason 100% server uptime is even possible.
We Own the Hardware. We Don’t Rent It.
Most PTToC providers in Australia are resellers. They’ve licensed a platform from a global vendor, layered branding on top of it, and are routing your data through servers they’ve never seen, in data centres they don’t control. When something fails at 2am, they log a support ticket and wait. We don’t have that problem.
Press2TALK™ owns its server hardware outright. Physical machines, in Australian data centres, managed by our own engineers. When we say we “own the network,” we mean the iron — not just the software layer on top of someone else’s cloud.
This matters structurally, not just operationally. It means there’s no third-party platform whose status page we need to monitor. No AWS outage that takes our network down. No shared tenancy where another customer’s traffic spike affects your communications. The only variable is us — and we’ve chosen to control every piece of it.
Our parent company has been in radiocommunications since 2003. Press2TALK™ was founded in 2017 specifically to build a PTToC network the right way: owned infrastructure, integrated hardware, Australian engineers. Not a quick reseller play — an investment in the architecture that makes reliability possible.
Owned vs Rented — What the difference actually means
100% Server Uptime. What It Means and Why It’s Possible.
When a competitor says “enterprise-grade reliability,” ask them for their uptime record. Ask them what it is in hours per year, not a percentage. The numbers are more honest that way.
Industry “gold standard”
Five nines allows approximately 5.26 minutes of downtime per year. That sounds negligible — but it’s a gap. For most providers, that’s best-case. Many offer 99.9% (around 8.76 hours per year of allowed downtime). Almost none publish a verified uptime figure at all.
Press2TALK™
We’re not rounding up. We’re not excluding scheduled maintenance. Our server system has not gone down. We can say that because we own the hardware and control every variable that determines whether it stays up.
The causal chain that makes 100% possible
You can’t reliably achieve 100% server uptime unless you control the entire stack. Any dependency on a third-party platform — even an excellent one — introduces failure modes you can’t directly resolve. Here’s why our architecture removes them:
This isn’t a marketing claim dressed as architecture — it’s the architecture explaining itself. The infrastructure design is the reason the uptime record exists, not the other way around.
Your Data Stays in Australia. Structurally, Not Just as Policy.
Most providers say something like “we’re compliant with Australian data laws.” That’s not the same as what we can say: your data physically cannot leave Australia, because of how we’ve built this. There’s nowhere else for it to go.
What the Privacy Act means for your comms data
The Australian Privacy Act 1988 — significantly updated in 2024 — tightens obligations around personal data, breach notification, and cross-border data transfers. If your comms provider routes voice recordings, GPS tracks, and operational data through overseas servers, you’re exposed to foreign jurisdiction. A data breach on an overseas server is still your compliance problem.
Why “Australian-hosted” doesn’t always mean what you think
A provider can claim Australian hosting while running on AWS Sydney — a US-owned platform subject to US legal process (including the CLOUD Act). We own the physical hardware. It is not a tenancy on a US hyperscaler’s infrastructure. There is no legal mechanism for a foreign government to compel access to our hardware.
What data sovereignty means in our architecture
Voice recordings, GPS location data and messaging logs are processed and stored on our hardware, in Australian data centres. This is a technical fact, not a compliance checkbox.
The question to ask any PTT provider
“Can you show me, technically, how my voice recordings and GPS data are stored — and confirm that data doesn’t transit through or reside on any overseas infrastructure?” Most cannot answer it. We can — because the architecture makes the answer straightforward. Australian hardware. Australian data centres.
AES-256 Encryption. 36 Months of Retained Data.
The specifics matter here — and not just as compliance checkboxes. The encryption standard, the retention period, and the backup architecture directly affect what you can prove if an incident occurs and what you can recover if something goes wrong.
AES-256 Encryption
AES-256 is the Advanced Encryption Standard at 256-bit key length. It is the same encryption used by Australian government agencies, defence organisations, and banks to protect classified and sensitive data. In practical terms: your voice calls and location data are encrypted at the hardware level. Even if data were intercepted in transit, it would be mathematically unreadable.
Bank & Government Standard36-Month GPS & Voice Recording Retention
GPS location data and voice recordings are retained for 36 months. This matters operationally for incident investigation, compliance reporting, and insurance claims. If a dispute arises — a route question, a safety incident, a vehicle location query — you have three years of evidence to draw on. Most providers offer significantly shorter retention windows because storage capacity, on AWS or Azure for example, cost money, sometimes a lot.
3 Years of Evidence On DemandComprehensive Data Backup
All data is backed up comprehensively. Backup integrity is part of our automated monitoring — we don’t assume backups are working, we verify they are. This means your operational data isn’t just encrypted and retained — it’s recoverable under any failure scenario we can engineer for.
Automated Backup VerificationEnd-to-End Data Architecture
Encryption, retention, backup, and sovereignty aren’t treated as separate policy layers. They’re designed into the same infrastructure by the same engineering team. The hardware that stores your data is the hardware our engineers manage. There are no gaps in the chain between where data is created and where it lives.
No Architecture Gaps24/7/365 Automated Monitoring — With Humans Behind It
Automated monitoring catches most issues before they affect service. Australian engineers catch the ones that need judgment. The combination is why no customer has experienced server downtime in over 48 months.
Automated System Monitoring
Our infrastructure is monitored 24 hours a day, 7 days a week, 365 days a year using customised automated alerting. The system watches for performance anomalies, capacity trends, and failure indicators — not just whether the server is responding.
Australian Engineer Response
When an alert fires, it goes to our engineers — not to a Level 1 helpdesk that logs a ticket for someone else. Australian engineers, in your timezone, with direct access to the hardware. No offshore escalation chain. No waiting 12 hours for a response because of time zone gaps.
No Shared Failure Points
Because we own the hardware, our monitoring covers the physical layer — not just the application. We’re not dependent on a cloud provider’s status page to know whether our infrastructure is healthy. We see it directly, continuously.
Remote Support for Customer Devices
Our Over-The-Air Programming (OTAP) capability means we can diagnose and reconfigure your devices remotely — without a technician visit. Most issues are resolved before you’ve had a chance to report them. Those that aren’t are handled by people who know the system end to end.
4G/5G Nationwide — With Coverage Validated Before You Commit
Our network runs on Australia’s 4G and 5G cellular infrastructure, augmented by WiFi where appropriate. But coverage statements only matter if they’re honest about the edges — so before any customer deploys, we validate their specific routes and sites.
- 4G LTE and 5G coverage across Australia’s major road, rail, and metropolitan networks
- WiFi augmentation for indoor facilities, depots, and sites with known cellular limitations
- Route-specific coverage validation — we can test your routes, not just national coverage maps
- Known dead zones disclosed upfront — we’d rather lose the sale than oversell the network
- Works on Australia’s leading carrier networks — no single-carrier dependency
- Runs on 4G/5G cellular with automatic fallback — consistent performance across coverage areas
- Coverage scales as the cellular network improves — no infrastructure investment required from you
Why route validation matters more than coverage maps
National coverage maps are marketing tools. A map that shows 98% population coverage doesn’t tell you whether your drivers on the Pacific Highway between Grafton and Ballina will have signal in every location that matters.
Before we deploy, we assess your specific operational area. If there’s a known gap on a route your fleet uses, we’ll tell you — and we’ll tell you whether WiFi augmentation solves it or whether it’s a genuine limitation.
This is how a provider who owns the responsibility for your comms behaves. We’d rather have the honest conversation upfront than explain downtime after the fact.
Hardware and Network Designed by the Same Team
Most PTToC solutions are assembled. A hardware vendor. A platform vendor. A local reseller. Three different organisations responsible for different parts of your comms stack — and nobody who owns the whole thing when something goes wrong.
Purpose-Built Hardware
The M50K, T60K, and T65 were not generic devices we relabelled. They were designed from the ground up to run on this P2T network. Integration isn’t an afterthought. It’s the design intent.
View M50K →Network Optimised for the Devices
Because the hardware was built for the network, we can optimise at the interface between them — latency, call setup time, OTAP programming, GPS reporting frequency. A reseller running third-party hardware on a third-party platform can’t always make those optimisations. We can, and we have.
How PTToC Works →Web Dispatcher — Same Stack, No Bolt-Ons
Our Web Dispatcher — the fleet management and control room platform — runs on the same network, reads the same GPS data, records the same voice calls. There’s no API integration between a hardware vendor’s system and a software vendor’s platform. It’s one system, built to work together.
Web Dispatcher →One Number for Everything
Hardware question. Network question. Software question. Billing question. It’s all the same team. There’s no pointing at a third party. No “that’s a Motorola issue, not a network issue.” If it’s part of your P2T system, we own the answer.
Why Choose P2T →Questions IT Managers and Procurement Teams Ask Us
These are the questions we hear most from the people who need to understand the architecture before they approve a purchase. Plain answers, no deflection.
Most PTToC providers in Australia have licensed a platform and are reselling access to it. They do not own the servers. They are tenants on cloud infrastructure controlled by a third party, often AWS or Microsoft Azure. When that infrastructure has an incident, the provider’s only option is to wait for it to be resolved upstream.
Press2TALK™ owns the physical server hardware too, outright. We purchased them, we house them in Australian data centres, and our engineers manage it directly. “Owned infrastructure” means the iron — not just the software layer on top of someone else’s cloud.
Cloud is excellent for many applications. For critical communications infrastructure — where downtime isn’t acceptable, data sovereignty is a compliance requirement and you have a heap of data to store securely — owned hardware offers capabilities cloud tenancy cannot: direct intervention when something fails, zero shared failure points with other tenants, and physical control over where data lives.
Our 100% server system uptime record over 48+ months isn’t a coincidence. It’s the outcome of owning every layer of the stack.
All data — voice recordings, GPS location history, messaging logs, and network traffic — is processed and stored on our server hardware in Australian data centres.
This is a technical guarantee, not a policy statement. The servers are in Australia, the data lives on those servers, and the data doesn’t leave them for overseas infrastructure.
AES-256 is the Advanced Encryption Standard at 256-bit key length. It is used by the Australian Signals Directorate, NATO, banking institutions, and government agencies worldwide to protect classified and sensitive data. The “256” refers to the key length — which means there are 2²⁵⁶ possible decryption keys.
In operational terms: even if your voice communications or GPS data were somehow intercepted in transit, it would be completely unreadable to anyone without the decryption key. It is not “secure enough” encryption — it is the encryption standard that governments use for their most sensitive data.
Our automated monitoring system would have already detected the issue — alerting our engineers before customers are affected in most scenarios. If an engineer response is required, they have direct access to the hardware. There’s no platform vendor to contact first, no overseas support desk, no time-zone gap.
For comparison: a provider running on a cloud platform they don’t own would need to first confirm the fault is on their infrastructure (not yours), then log a ticket with their cloud provider, then wait for that provider’s SLA response clock to start. Their resolution time begins where ours already ends.
The Press2TALK™ network operates on Australia’s 4G and 5G cellular infrastructure, with WiFi augmentation available for sites with known limitations. This means coverage is extensive — but we validate it for your specific routes and operational areas before you commit.
This is part of the deployment process, not an afterthought.
More from Press2TALK™
How Push-to-Talk over Cellular Works
The technical explanation — how PTToC differs from traditional radio and why cellular coverage changes the game.
8 Reasons to Choose Press2TALK™
Owned network. Exclusive importer. Turnkey deployment. 100% server uptime. The full case for choosing us over any alternative.
PTT for Bus Companies
Route-wide coverage, driver panic buttons, GPS tracking, voice recording. Built for Australian bus operators.
PTT for Transport & Linehaul
Coast-to-coast coverage, real-time dispatcher, GPS. For fleets that go further than a UHF radio can reach.
M50K Mobile Radio
The in-vehicle PTT unit. Built for P2T’s network from the ground up. 12–24V vehicle power, keypad mic, GPS.
Web Dispatcher
Browser-based fleet management. Live GPS map, voice recording playback, duress alerts, lone worker system.
Ready to See the Network in Action?
Book a live demo and we’ll show you the infrastructure, the coverage map for your routes, and what 100% server uptime looks like in practice — not just in a claim.