Asterisk Australian numbering and site settings
An Australian Asterisk deployment needs a consistent number plan and site settings on the server, phones and provider path. A country label in one configuration file does not set every number format, prompt, timezone or service arrangement.
Source-reviewed, 20 October 2026. Prepared from the cited documentation. No Australian carrier path has been independently tested by Phone Guides. Scope: Asterisk 22 planning with current ACMA public references; provider settings and site obligations need their own applicable sources.
Keep number categories separate
ACMA's phone-number guide describes Australian geographic numbers starting with 02, 03, 07 or 08, mobile numbers starting with 04, and separate local-rate/freephone categories including 13, 1300 and 1800 numbers. These categories should not be forced through one guessed geographic-number rule.
Keep the number a person sees, the digits they dial and the exact string a provider accepts as separate fields. Record authorised caller ID separately too. A trunk account's username may have no direct relationship to the public number presented to recipients.
| Record | What to establish |
|---|---|
| Public number | Assigned number, category and owning service |
| User input | Supported local/national/international dialling forms |
| Provider output | Exact required destination format and any access-prefix treatment |
| Inbound delivery | Exact token/field delivered to the dialplan |
| Identity | Caller-ID format and permitted presentation under the service |
Use the provider's public service/configuration documentation for its required strings. Do not use a number-allocation page as proof that a particular provider accepts a particular dial string. See inbound/outbound routing for the configuration boundary.
Set time and regional audio deliberately
Use the site's named timezone for opening-hours decisions and review daylight-saving behaviour where relevant. Multiple Australian sites can need different schedules. Do not hard-code one fixed UTC offset as the definition of all Australian business hours.
Check the chosen release's indication/tone definitions, installed sound packages and endpoint regional settings. Asterisk-generated tones and a phone's locally generated tones can have different configuration owners. A selected language also needs the corresponding prompt files to exist.
The official internationalisation section links sound-package and prompt-language references; its overview is unfinished, so use its detailed linked sources and matching release samples for actual settings. Time/holiday routing explains timezone-aware route design.
Document emergency arrangements for the actual service
ACMA identifies 000 as Australia's main emergency number. Its current emergency-calls guidance, updated 21 September 2026, says 000 is available through certain VoIP services; 112 is for mobiles, and 106 is for TTY. For VoIP calls, the 000 operator asks for the caller's town and state because the caller may not be at the home or billing address. Confirm whether the exact service supports emergency calling and what location information it supplies. A dialplan match, caller-ID value or FreePBX site setting alone does not establish where an emergency call will be routed or how its location will be handled.
The Telecommunications (Emergency Call Service) Determination 2019 is listed in force; the registry's latest compilation at this review was F2025C01030, effective 1 November 2025. This guide does not interpret the instrument or determine which legal duties apply to a particular provider or organisation.
Keep these arrangements distinct from ordinary international calling permissions and caller-ID presentation. Arrange any emergency-path verification with the provider; do not place casual live emergency calls while configuring a PBX. This guide does not certify a service or determine all obligations applying to a deployment.
Reader review record
For your own site, retain the provider reference, number inventory, normalisation examples, timezone, prompts/tones and approved verification procedure. Check an ordinary inbound/outbound destination and an invalid/denied number under that procedure. Review multi-site overrides and remote-user location assumptions separately.
When a provider or number plan changes, update the evidence and intended routes together. Preserve the old configuration for reversal without changing an assigned public number as an incidental configuration step.
Return to Asterisk documentation.