Skip to main content

AUSTRALIA (AU)

Locale Summary

Locale nameAustralia
ISO codeAU
RegionOceania
Dialing code+61

Reachability

Inbound
Ability to call numbers in Australia
Outbound
Ability to call non-Twilio numbers in Australia
DomesticYesYes
InternationalYesYes
Toll-FreeYesYes
Outbound restrictions

Twilio participates with the Communications Alliance WC92 Reducing Scam Calls Sub-Group in order to ensure legitimate voice calling use-cases are protected and join the industry to eliminate scam calls.

The obligations of the code fall on the originating service provider. Calling use cases like call forwarding that require the originating service provider to originate a call using a phone number hosted by another provider is protected under the code. 

Per the Reducing Scam Calls Code, published in November 2020, the following guidelines are best practices to reduce your risk:

  1. Calls originated by Twilio to Australian destinations should use a Twilio phone number as the Calling Number (also called CLI, From Number, or CallerId). Phone numbers provisioned on Twilio or ported to Twilio and used as the calling number have the lowest risk of being impacted by the code.
    • By November 30, 2021, Telstra is expected to begin implementing restrictions on calls terminating at its network in order to reduce scam calls. To maintain service continuity, all Twilio users calling Telstra Australian destinations using Telstra Caller IDs will need to use Twilio Phone Numbers. For more details, please visit the Telstra Australian Caller ID Restrictions Support page.
  2. Any call using anonymous as the calling number will be blocked.
  3. Any call using Australian phone numbers (+61) as calling number not allocated by ACMA will be blocked.
  4. Any call using international calling number with an invalid format will be blocked.
  5. Any call using invalid calling numbers such as the use of usernames will be blocked.
  6. Domestic calls that originate from AU calling numbers to AU destinations must use the sydney edge location in order avoid transiting international gateways. Calls that use AU calling numbers that transit international gateways may be blocked.
    • For Elastic SIP Trunking, the request URI should follow this format: example.pstn.sydney.twilio.com
    • For SIP Interfaces, the request URI should follow this format: example.sip.sydney.twilio.com
  7. Special Service numbers (13/1300) and Toll-Free numbers (1800) and (1900) must be used for inbound calls only. These numbers are also known as Do-Not-Originate (DNO) numbers and are blocked by carriers.
Outbound requirements

N/A

Best practices

N/A

Caller ID

Inbound
Inbound call receives originator's Caller-ID
Outbound
Outbound call preserves sent Caller-ID
Domestic+E.164Local
InternationalE.164 (Non-guaranteed)+E.164
Toll-Free+E.164Local

DTMF

Inbound
Inbound call receives DTMF from PSTN
Outbound
Outbound call sends DTMF to PSTN
RFC.2833 formatYesYes

Emergency Calling

Outbound
Ability to make Emergency Calls
Emergency servicesYes

Reachability

Outbound
Ability to call non-Twilio numbers in Australia
Inbound
Ability to call numbers in Australia
DomesticYes
InternationalYes
Toll-FreeYes
DomesticYes
InternationalYes
Toll-FreeYes
Outbound restrictions

Twilio participates with the Communications Alliance WC92 Reducing Scam Calls Sub-Group in order to ensure legitimate voice calling use-cases are protected and join the industry to eliminate scam calls.

The obligations of the code fall on the originating service provider. Calling use cases like call forwarding that require the originating service provider to originate a call using a phone number hosted by another provider is protected under the code. 

Per the Reducing Scam Calls Code, published in November 2020, the following guidelines are best practices to reduce your risk:

  1. Calls originated by Twilio to Australian destinations should use a Twilio phone number as the Calling Number (also called CLI, From Number, or CallerId). Phone numbers provisioned on Twilio or ported to Twilio and used as the calling number have the lowest risk of being impacted by the code.
    • By November 30, 2021, Telstra is expected to begin implementing restrictions on calls terminating at its network in order to reduce scam calls. To maintain service continuity, all Twilio users calling Telstra Australian destinations using Telstra Caller IDs will need to use Twilio Phone Numbers. For more details, please visit the Telstra Australian Caller ID Restrictions Support page.
  2. Any call using anonymous as the calling number will be blocked.
  3. Any call using Australian phone numbers (+61) as calling number not allocated by ACMA will be blocked.
  4. Any call using international calling number with an invalid format will be blocked.
  5. Any call using invalid calling numbers such as the use of usernames will be blocked.
  6. Domestic calls that originate from AU calling numbers to AU destinations must use the sydney edge location in order avoid transiting international gateways. Calls that use AU calling numbers that transit international gateways may be blocked.
    • For Elastic SIP Trunking, the request URI should follow this format: example.pstn.sydney.twilio.com
    • For SIP Interfaces, the request URI should follow this format: example.sip.sydney.twilio.com
  7. Special Service numbers (13/1300) and Toll-Free numbers (1800) and (1900) must be used for inbound calls only. These numbers are also known as Do-Not-Originate (DNO) numbers and are blocked by carriers.
Outbound requirements

N/A

Best practices

N/A

Caller ID

Inbound
Inbound call receives originator's Caller-ID
Domestic+E.164
InternationalE.164 (Non-guaranteed)
Toll-Free+E.164
Outbound
Outbound call preserves sent Caller-ID
DomesticLocal
International+E.164
Toll-FreeLocal

DTMF

Inbound
Inbound call receives DTMF from PSTN
RFC.2833 formatYes
Outbound
Outbound call sends DTMF to PSTN
RFC.2833 formatYes

Emergency Calling

Outbound
Ability to make Emergency Calls
Emergency servicesYes

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.