|
Locale Summary |
|
|---|---|
|
Locale name |
Hungary |
|
ISO code |
HU |
|
Region |
Europe |
|
Dialing code |
+36 |
|
Reachability |
Inbound |
Outbound |
|---|---|---|
|
Domestic |
Yes |
Yes |
|
International |
Yes |
Yes |
|
Toll-Free |
Yes |
No |
|
Outbound restrictions |
Following an amendment to Decree 4/2012 (I.24), calls made to Hungary using fixed or geographic numbers (like +36 1-9...) as a CLI (Calling Line Identification) are now likely to be blocked by local carriers, as of October 15, 2025. This will expand to mobile numbers (like +36 20, 30, 70...) starting June 1, 2026. Calls made with Transit Caller ID and Verified Caller ID will be delivered by Twilio on a best-effort basis when customers use a Hungarian CLI. |
|
|
Outbound requirements |
|
|
|
Best practices |
N/A |
|
|
Caller ID |
Inbound |
Outbound |
|---|---|---|
|
Domestic |
+E164 |
Local (Non-guaranteed) |
|
International |
+E164 (Non-guaranteed) |
+E164 |
|
Toll-Free |
+E164 |
N/A |
|
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.