Is the Australian RCM enough to activate a cellular IoT device on Telstra?

No. The Regulatory Compliance Mark attests to radio, EMC and electrical safety conformance under ACMA supervision, in line with the Radiocommunications Act 1992. It is a regulator-side step. Telstra, as a carrier, adds its own device acceptance process covering network behaviour (attach, handover, throughput), eUICC management, IMEI registration and application-level testing. An IMEI not accepted by Telstra may transit the network in test mode but will be filtered at durable commercial activation. Optus and TPG operate equivalent programmes, distinct from the RCM.

Which Australia-specific LTE band is most often missed in radio dossiers?

Band B28 (700 MHz, APT700 plan) is central for Telstra and Optus rural and suburban coverage and must be explicit in the radio dossier. Many cellular modules designed for Europe declare B3 (1800 MHz) and B7 (2600 MHz) but omit B28 or B5 (850 MHz, Telstra legacy band). B5 850 MHz is specific to Telstra indoor and rural coverage; its absence frequently explains disappointing coverage on Australian territory. A band-by-band review is essential when transposing a European module to Australia.

Is 3G still available in Australia?

No. The 3G (UMTS) sunset is complete in Australia. Telstra finalised its 3G network shutdown in August 2024, followed by Optus and TPG in close windows. Cellular modules supporting only 2G and 3G no longer work in the Australian market. Any new IoT project must target 4G LTE (including Cat-1, Cat-M, NB-IoT) and, depending on the case, 5G NR sub-6 GHz. Dual-mode LTE-M + NB-IoT modules are the de facto standard for cellular LPWAN in Australia.

Why does Telstra have a more visible acceptance programme than Optus or TPG?

Telstra is the incumbent carrier from the privatisation of Telecom Australia, first by market share, first in rural coverage, first in 5G rollout. Its device acceptance programme, articulated around the Telstra Data Hub and partner labs, is publicly documented for IoT manufacturers. Optus (Singtel group) and TPG (TPG Telecom and Vodafone Hutchison Australia merger since 2020) operate similar but less publicly formalised programmes, often via their B2B IoT teams rather than via a self-service portal. The underlying logic is identical: a carrier MoU test plan on top of the RCM.

What role does eUICC play in Telstra acceptance?

Central. Telstra typically requires conformance to GSMA SGP.22 for consumer profiles and SGP.32 for IoT RSP, with a device-side LPA able to dialogue with the chosen SM-DP+. Acceptance tests cover profile download, enable, disable, delete and behaviour on network failure during the operation. An eUICC not GSMA SAS-UP certified, or a non-conformant proprietary LPA, is a frequent cause of rejection. Telstra publishes its eUICC requirements via the IoT partner channel, in line with GSMA bulletins.

After CE + RED certification, does the full radio test need to be redone for Australia?

Not entirely. AS/NZS CISPR 32 / 35 mirrors CISPR 32 / 35, so EMC reports from EN 55032 / EN 55035 are generally accepted under AS/NZS. For cellular radio, Australian bands (B5 850 MHz, B28 700 MHz APT700) typically require complementary measurements if they were not covered under RED. For 5G NR, n78 (3.5 GHz) is common but n258 mmWave is specific to Australian metropolitan deployments and needs verification. Carrier acceptance (Telstra, Optus, TPG) remains to be done after the RCM, it does not inherit from the European dossier.

Must the IMEI be declared separately with each Australian carrier?

Yes, in practice. Each carrier maintains its own list of authorised IMEIs and applies its own filters at attach and at activation. An IMEI accepted by Telstra is not automatically recognised by Optus or TPG, and vice versa. For an IoT product targeted at several Australian carriers, plan a parallel IMEI registration process, with a common IMEI numbering range but separate submissions. MVNO programmes generally inherit the IMEI base of their host carrier (an MVNO on the Telstra network inherits the Telstra list).

Is mmWave n258 useful for IoT in Australia?

In the vast majority of IoT cases, no. Band n258 (26 GHz) is deployed in targeted metropolitan coverage (Sydney CBD, Melbourne CBD, Brisbane CBD) with very short range. It addresses high-throughput use cases (FWA, premium video) rather than distributed IoT. An industrial IoT device or a LPWAN sensor does not need n258 support. For FWA or high-definition IP cameras in urban areas, n258 may be relevant; it then requires specific RF integration and an extended carrier acceptance. The sub-6 GHz band n78 (3.5 GHz) remains the most broadly useful 5G NR band.

Telstra, Optus, TPG: cellular IoT acceptance in Australia

Author Hugues Orgitello Last updated 27 May 2026 ~13 min read

Guide - Telstra / Optus / TPG

Bringing a cellular IoT device to the Australian market does not reduce to obtaining the Regulatory Compliance Mark under ACMA supervision. The RCM attests to radio, EMC and electrical safety conformance at the federal regulator level; on its own, it does not authorise durable activation of an IMEI on the commercial network of Telstra, Optus or TPG. Each of these three carriers - the only full-scale cellular MNOs in Australia since the TPG / Vodafone Hutchison Australia merger in 2020 - operates its own device acceptance programme that layers on top of the regulator regime. This page describes the RCM + carrier acceptance stack, the three-carrier landscape, the bands specific to Australia (B5 850 MHz, B28 700 MHz APT700, n78 3.5 GHz, n258 26 GHz mmWave), the 3G sunset completed in 2024, the role of eUICC under SGP.22 and SGP.32, and the most frequent pitfalls when transposing a European IoT dossier to Australia.

Regulator and carrier, two distinct layers

The first structuring mistake a European manufacturer makes when approaching Australia is to consider the RCM as sufficient. The RCM, described in detail in ACMA and RCM, covers three federal regulator regimes: radio under the Radiocommunications Act 1992, electromagnetic compatibility under the EMC Standard 2017, and electrical safety under the EESS administered by the States. It does not cover, and has never been intended to cover, interoperability with the commercial network of any particular carrier.

Layer	Authority	Scope	Output
Regulator radio + EMC + safety	ACMA + ERAC / EESS	Conformance to ACMA Class Licences, AS/NZS CISPR, AS/NZS 62368.1	RCM affixed, Supplier Code Number, EESS registration for Declared items
Carrier acceptance	Telstra, Optus, TPG (separately)	Network interoperability, eUICC, IMEI, throughput, fail-over	IMEI listed in the carrier database, commercial SIM contract

The conceptual diagram reads as:

Cellular IoT product
  |
  v
Regulator layer (federal + States)
  ACMA  -> radio Class Licences + EMC Standard 2017
  EESS  -> electrical safety for Declared items
  ====> RCM affixed, compliance folder
  |
  v
Carrier layer (private, per carrier)
  Telstra ----> Telstra MoU test plan, IMEI Telstra Approved
  Optus  -----> Optus test plan, IMEI Optus Approved
  TPG    -----> TPG test plan, IMEI TPG Approved
  ====> durable commercial activation

The RCM is a necessary but not sufficient condition. Without RCM, a product cannot legally be sold. Without carrier acceptance, the product may technically transit a network (test mode, test SIM, roaming) but will be filtered at durable commercial activation. The two layers are often pursued in parallel, but they are functionally disjoint.

See also PTCRB, the North American multi-carrier reference programme that forms a useful pre-test baseline but is not formally recognised by Australian carriers, although generally accepted as prior evidence to reduce test scope.

The three Australian carriers

The Australian mobile network market is, since the 2020 merger, a three-MNO market complemented by a long list of MVNOs hosted mainly on Telstra infrastructure. This three-MNO concentration is an Australian particularity, compared with Europe where most markets host four or five MNOs.

Telstra, incumbent carrier

Telstra, from the progressive privatisation of Telecom Australia engaged at the end of the 1990s, remains the first Australian mobile operator by market share, by geographic coverage and by 5G investment. Its rural coverage, historically built on low bands (850 MHz B5, 700 MHz B28), is the most extensive in the country. Telstra is typically the carrier selected for IoT rollouts distributed nationally (logistics, agriculture, energy, environmental monitoring).

The Telstra device acceptance programme is organised around a Telstra-specific MoU test plan, a Telstra Approved IMEI list populated after acceptance, the Telstra Data Hub (an IoT fleet management platform that also serves as an entry point for manufacturers), and lab partnerships designating which laboratories can produce admissible reports. Telstra does not operate a public self-service portal equivalent to the Verizon ODI; manufacturers route through their B2B IoT contact.

Optus, second carrier

Optus, a subsidiary of the Singaporean Singtel group since 2001, is the second carrier by market share. Its metropolitan coverage is dense; its rural coverage is more restricted than Telstra's. Optus pushed the first commercial 5G mmWave rollouts in Australia (n258 on Sydney, Melbourne, Brisbane CBDs) and invests strongly in IoT enterprise services under the Optus Enterprise brand. Acceptance rests on a Optus-specific device test plan, an IMEI list separate from Telstra's, and the enterprise IoT team as entry point, in a more targeted, less mass-market logic.

TPG, TPG Telecom + Vodafone Hutchison Australia merger

The third network operator, from the 2020 merger of TPG Telecom and Vodafone Hutchison Australia (the local joint venture of Vodafone Group and Hutchison), operates under the commercial brand TPG Telecom for enterprise and keeps the Vodafone brand for consumer. The merger unified two historically separate networks, with progressive site and band rationalisation underway. TPG / Vodafone often positions itself as a competitive alternative in dense metropolitan and urban segments, with more limited rural coverage than Telstra. The IoT acceptance programme benefits from the Vodafone Global heritage in formalising acceptance testing, requires an explicit device test plan with IMEI validation, and ties in with Vodafone Group IoT programmes for multinational customers.

MVNOs and IMEI inheritance

The Australian market hosts a long list of MVNOs (Boost Mobile, Belong, Aldi Mobile, Woolworths Mobile, amaysim, Felix, etc.) hosted mainly on Telstra or Optus. An IMEI accepted by the host carrier is automatically usable on its MVNOs, which simplifies go-to-market for manufacturers targeting the MVNO long tail via the host carrier.

Deployed cellular technologies

Australia engaged the legacy technology sunset early. 2G GSM was switched off at Telstra in late 2016 and at the other carriers shortly after. 3G UMTS was switched off at Telstra in August 2024, followed by Optus and TPG in the following months. From 2025 onwards, the Australian market is LTE 4G + 5G NR only.

4G LTE and the Cat-1, Cat-M, NB-IoT profiles

For cellular IoT, three LTE categories are commonly deployed. LTE Cat-1 offers moderate throughput (~10 Mbps DL, ~5 Mbps UL), low latency, and VoLTE voice; target: trackers and M2M needing throughput above LPWAN without Cat-4 cost. LTE Cat-M (LTE-M, Cat-M1) is a LPWAN profile with PSM and eDRX, ~1 Mbps throughput, improved coverage (CE Mode A/B); target: distributed sensors, asset tracking, metering. NB-IoT (Cat-NB1, Cat-NB2) is a very low rate LPWAN profile (~60 kbps DL, ~20 kbps UL), maximum coverage (CE up to 20 dB gain), reduced consumption; target: fixed sensors, meters, devices in hard-to-reach areas.

The three Australian carriers deploy Cat-M and NB-IoT with varying coverage. Telstra was earliest and broadest on its low bands (B5, B28), with claimed national Cat-M coverage since 2018 and NB-IoT since 2019. Optus and TPG follow with progressive, mainly metropolitan and suburban coverage.

5G NR

5G NR has been deployed by the three carriers since 2019-2020. n78 (3.4 - 3.8 GHz), sub-6 GHz, forms the core of the national 5G rollout with extensive metropolitan and suburban coverage; 5G IoT compatibility via Reduced Capability (RedCap, NR-Light) is being introduced. n258 (24.25 - 27.5 GHz, mmWave) is deployed in targeted metropolitan coverage (Sydney CBD, Melbourne CBD, Brisbane CBD, selected stadiums, industrial sites): very short range, high throughput, FWA and premium use cases rather than distributed IoT.

For the vast majority of IoT, n78 is the only useful 5G NR band; n258 is only required for FWA or high-definition video in urban areas.

Cellular bands deployed in Australia

The table below summarises the bands used by Telstra, Optus and TPG in LTE and in NR sub-6 GHz / mmWave. Frequencies are indicative; exact allocations may shift over time.

Band	Frequency (MHz)	Technology	Telstra	Optus	TPG / Vodafone	Typical use
B3	1800 (DL 1805-1880)	LTE	Yes	Yes	Yes	Metropolitan capacity band
B5	850 (DL 869-894)	LTE, Cat-M, NB-IoT	Yes (legacy)	Limited	Limited	Telstra rural and indoor coverage, LPWAN IoT
B7	2600 (DL 2620-2690)	LTE	Yes	Yes	Yes	High metropolitan capacity
B28	700 (DL 758-803, APT700)	LTE, Cat-M, NB-IoT	Yes	Yes	Yes	Rural and suburban coverage, LPWAN IoT
B1	2100 (DL 2110-2170)	LTE	Limited	Yes	Yes (Vodafone heritage)	Secondary capacity band
B40	2300 (DL 2300-2400)	LTE TDD	Limited	Yes	Limited	Complementary TDD band
n78	3500 (3.3 - 3.8 GHz)	5G NR sub-6	Yes	Yes	Yes	Core of the national 5G rollout
n258	26 000 (24.25 - 27.5 GHz)	5G NR mmWave	Yes (targeted)	Yes (first rollout)	Limited	Metro CBDs, FWA, premium sites

For a cellular IoT module targeted at Australia, the recommended minimum for decent coverage is: B3, B5, B7, B28 in LTE, plus Cat-M and NB-IoT on B5 and B28 for LPWAN. 5G NR n78 is recommended if the product lifecycle extends beyond 2027-2028 and benefits from higher throughput.

The Telstra MoU test plan

The Telstra device acceptance programme rests on an MoU test plan signed between Telstra and the manufacturer, which defines the test scope and acceptance criteria. Main test families:

Network and protocol conformance

Verification of device behaviour on the 3GPP procedures most critical for Telstra: attach initial on the Telstra network with correct PLMN, SIM and certificate handling; detach and re-attach cleanly after reset, signal loss, or eUICC profile change; handover between cells, between technologies (LTE -> NR, NR-NSA -> NR-SA) and between bands (B28 -> B5, B5 -> B3 depending on coverage); PLMN selection respecting Telstra priorities without undue carrier locking; Tracking Area Update; CSFB or VoLTE behaviour for voice-capable products.

Throughput and fail-over

IP throughput measurements under realistic conditions (DL and UL in average and weak cellular, cell-edge, latency, jitter, long-session stability, carrier aggregation on Telstra combos B3+B7+B28, n78+B3+B7, etc.) and device robustness under adverse conditions (sudden signal loss and reconnection, 5G SA -> 5G NSA -> LTE fallback, n78 -> B3 fallback on 5G cell loss, PSM and eDRX behaviour for LPWAN modules with wake-up and TAU validation, SM-DP+ error handling during a profile download in degraded network).

SMS, messaging and eUICC RSP

SMS over IP and SMS over NAS are verified depending on the module profile (send and receive in LTE and in 5G, behaviour when SMSC is unreachable, OTA provisioning SMS and command SMS for legacy M2M products). eUICC is one of the most demanding subjects of modern Telstra acceptance; it has its own section below.

eUICC and RSP, the structuring topic for 2025-2026

Telstra has aligned its acceptance with the GSMA specifications GSMA SGP.22 (consumer RSP) and GSMA SGP.32 (IoT RSP), with progressive retirement of the legacy M2M architecture GSMA SGP.02.

SGP.22 (consumer) targets devices with UI (smartphone, tablet, watch): the local LPA (LPAd) dialogues with an SM-DP+ and an SM-DS, profile download via QR code or activation code, user-triggered. SGP.32 (IoT) targets headless or weakly interactive devices (sensors, trackers, gateways): it introduces the eSIM IoT Manager (eIM) role and splits responsibilities between IPAd (IoT Profile Assistant device side) and IPAe (eUICC side), with the profile pushed via eIM with no user interaction. Telstra accepts both profiles depending on product category.

Telstra requires an eUICC certified GSMA SAS-UP, a LPA conformant to GSMA specifications with ES9+ (profile download) and ES10b (eUICC management) support, correct handling of enable / disable / delete operations without hardware reset, robustness under degraded network during profile download (clean rollback, exploitable log), and TLS compatibility with the SM-DP+ used. A non-conformant proprietary LPA and a non-GSMA-certified eUICC are the two most frequent causes of rejection.

Legacy M2M devices on SGP.02 architecture are end-of-life at Telstra; the retirement schedule is communicated via IoT partner channels. For any new IoT project in 2025-2026, target SGP.32 directly, unless integrating into an existing SGP.02 fleet that is not migratable.

Optus and TPG programmes, the differences

The Optus and TPG programmes follow the same conceptual architecture as Telstra's, with operational differences. Optus runs a less publicly formalised test plan (routed through the Optus Enterprise IoT team), with emphasis on B3, B7, n78 and n258 (Optus pioneered commercial mmWave) and more limited B5 coverage; acceptance is often pursued alongside a connectivity contract. TPG / Vodafone benefits from the Vodafone Global heritage in test plan structure, with the ability to re-use Vodafone Group acceptance reports in other geographies subject to coverage of Australia-specific bands (B28 progressive from the merged network); it is relevant for multinational customers rolling out a cross-border IoT fleet with Vodafone Group.

For a product targeted at the three carriers, three distinct acceptance programmes must be planned on an identical module and product. The radio and eUICC core is generally reusable, but the IMEI must be submitted to each carrier separately. A realistic schedule plans Telstra first (most structured, most visible), then Optus and TPG in parallel.

PTCRB, GCF and inheritance of reports

PTCRB is a North American multi-carrier radio certification programme; the GCF (Global Certification Forum) is its European and international counterpart, shared by many EMEA and Asia carriers. Neither is a formal acceptance condition for Telstra, Optus or TPG. Their reports are nevertheless generally accepted by Australian carriers as prior evidence to reduce radio test scope: a case-by-case review with the carrier distinguishes tests already covered (typically TS 36.521, TS 38.521 on shared bands), those specific to Australian bands (B5, B28 APT700, n78 AU allocation) which are not, and the carrier-specific network and application tests which always have to be done.

Efficient strategy for a European manufacturer: GCF as the baseline (useful for Europe + Asia), PTCRB as a complement if the US market is targeted, then Telstra / Optus / TPG as dedicated carrier acceptance for Australia.

Project sequencing, the right timing

For a cellular IoT product targeting the Australian market in 2025-2026, the rational sequence: select a module supporting B3, B5, B7, B28 in LTE (plus Cat-M and NB-IoT on B5 and B28, n78 if the lifecycle extends beyond 2027) with eUICC SGP.22 / SGP.32 compatibility; build the RCM dossier in parallel (ACMA and RCM) with AS/NZS lab testing and Supplier Code Number registration; contact in advance the B2B IoT teams at Telstra (Telstra Data Hub), Optus Enterprise IoT and TPG IoT to open dossiers; run the Telstra acceptance campaign on the MoU test plan, then Optus and TPG in parallel with maximum re-use of the radio and eUICC core; register IMEI ranges in each carrier database, sign the connectivity contract, cut over production; manage lifecycle changes (radio or eUICC = full review, application = delta).

For the global timing of an international cellular project see Certification timeline and Certification costs.

Common pitfalls

1. Assuming RCM covers the carrier

This is the structuring mistake. The RCM is a regulator-side step (ACMA + EESS); it has no effect on Telstra, Optus or TPG acceptance. Discovery is often late, when the commercial team tries to activate the first commercial SIMs.

2. Missing band B5 850 MHz for Telstra

B5 is Telstra's historic indoor and rural coverage band. Many cellular modules designed for Europe declare B3 + B7 + B28 but omit B5. The result: disappointing coverage in rural and indoor Telstra zones. B5 validation must be explicit in both the AS/NZS radio dossier and the carrier test plan.

3. Missing band B28 700 MHz APT700

B28 follows the APT700 plan, distinct from the US 700 MHz plan. A module designed for the US supporting B13 (Verizon) or B17 (AT&T) does not necessarily cover B28.

4. Confusing n78 and n258

n78 (3.5 GHz sub-6) is the national 5G coverage band. n258 (26 GHz mmWave) is a very targeted metropolitan band. Many integrators assume n258 support that the module does not provide, or conversely budget n258 support that is irrelevant for IoT.

5. Missing per-carrier IMEI registration

An IMEI accepted by Telstra is not recognised by Optus or TPG. IMEI submission must be done to each carrier separately; the shared database assumption does not hold in Australia.

6. eUICC mismatch SGP.02 vs SGP.32, or non-conformant proprietary LPA

SGP.02 is end-of-life; a new IoT project on SGP.02 will be rejected. Using SGP.22 on a headless IoT device creates activation UX problems (no screen to scan a QR code). Conversely, a hand-rolled proprietary LPA almost never passes carrier acceptance on enable / disable / delete operations. Use the LPA from the module (when integrated and certified) or a certified third-party LPA SGP.22 / SGP.32.

7. Under-estimating administrative time

Opening an acceptance dossier with Telstra requires a B2B IoT contact, sometimes a commercial review, and an MoU signature. This administrative phase often takes several weeks before the first lab test. To plan upstream in the product schedule, not downstream.

Key takeaways

Carrier acceptance (Telstra, Optus, TPG) is distinct from the regulator regime (ACMA + EESS / RCM). Both layers are necessary for durable commercial activation in Australia.
The Australia-specific bands to cover: B3, B5 (central to Telstra), B7, B28 (APT700, central to rural) in LTE; n78 for national 5G coverage; n258 mmWave only for FWA / video metro cases.
The 3G sunset is complete since 2024. The eUICC under GSMA SGP.22 and SGP.32 is central; SGP.02 is end-of-life. The device-side LPA must be GSMA-certified.
PTCRB and GCF are not formal Australian acceptance conditions, but their reports are generally accepted as prior evidence. The IMEI must be submitted to each carrier separately.

For the vocabulary (PVG, EPC, LPA, IPAd, SM-DP+, eUICC, eIM, RSP, PLMN), see the spilma glossary. For the Australian regulator layer, see ACMA and RCM. For the North American counterpart, see PTCRB.