Locale Summary |
|
---|---|
Locale name |
Japan |
ISO code |
JP |
Region |
Asia |
Dialing code |
+81 |
Reachability |
Inbound |
Outbound |
---|---|---|
Domestic |
Yes |
Yes |
International |
Yes |
Yes |
Toll-Free |
Yes |
Yes |
Outbound restrictions |
Domestic calls that originate from JP calling numbers to JP destinations must use the Tokyo edge location in order avoid transiting international gateways. Calls that use JP calling numbers that transit international gateways may have the caller ID removed. • For Elastic SIP Trunking, the request URI should follow this format: example.pstn.tokyo.twilio.com Caller ID cannot be preserved for domestic calls from registered/verified caller ID. Premium-rate telephone numbers are blocked and can’t be called. These are: +81170, +81180, +81570, +81910, +81990, +8101, and +8105. Anonymous calling is not supported by default. Some underlying hosting number providers to not support anonymous calling for their number types. |
|
Outbound requirements |
N/A |
|
Best practices |
When calling Twilio phone numbers from a Japanese domestic line, the Japanese phone number must be prefixed with zero. In this number format, known as the national format, it is not necessary to include the Japan country code. |
|
Caller ID |
Inbound |
Outbound |
---|---|---|
Domestic |
+E.164 |
Local |
International |
+E.164 (Non-guaranteed) |
+E.164 |
Toll-Free |
+E.164 |
Local |
DTMF |
Inbound |
Outbound |
---|---|---|
RFC.2833 format |
Yes |
Yes |
Emergency Calling |
Outbound |
---|---|
Emergency services |
No |
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.