Locale Summary |
|
---|---|
Locale name |
Australia |
ISO code |
AU |
Region |
Oceania |
Dialing code |
+61 |
Reachability |
Inbound |
Outbound |
---|---|---|
Domestic |
Yes |
Yes |
International |
Yes |
Yes |
Toll-Free |
Yes |
No |
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:
|
|
Outbound requirements |
N/A |
|
Best practices |
N/A |
|
Caller ID |
Inbound |
Outbound |
---|---|---|
Domestic |
+E.164 |
Local |
International |
+E.164 |
+E.164 |
Toll-Free |
+E.164 |
N/A |
DTMF |
Inbound |
Outbound |
---|---|---|
RFC.2833 format |
Yes |
Yes |
Emergency Calling |
Outbound |
---|---|
Emergency services |
Yes |
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.