Locale Summary
Locale name | Iran |
---|---|
ISO code | IR |
Region | Middle East & Africa |
Mobile country code | 432 |
Dialing code | +98 |
Guidelines
Two-way SMS supported | No |
---|---|
Number portability available | Yes |
Twilio concatenated message support | Yes |
Message length | ----- |
Twilio MMS support | Not Available |
Sending SMS to landline numbers | You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged. |
Compliance considerations | Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. Per local regulations, peer-to-peer (P2P) traffic is prohibited by Iranian networks. The following are some general best practices:
Please take note that gambling, betting, political, religious or adult-related content is strictly prohibited in Iran. |
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Required | Not Supported | Not Supported | Not Supported | Not Supported |
Twilio supported |
Required
Learn more | Supported | --- | Supported | --- |
Sender ID preserved | Yes | No | --- | No | --- |
Provisioning time | 2 weeks | N/A | N/A | N/A | N/A |
UCS-2 support | N/A | N/A | N/A | N/A | N/A |
Use case restrictions | Only Sender IDs related to International OTP traffic will be allowed. Other type of traffic as well as the one generated from Domestic Companies is not permitted in Iran. | N/A | N/A | N/A | N/A |
Best practices | During registration please provide a representative sample as SMS as content allow listing is also required in Iran. Messages submitted via a registered Sender ID with content that is different from the allowlisted one will be rejected | Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis | N/A | Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Required |
Twilio supported |
Required
Learn more |
Sender ID preserved | Yes |
Provisioning time | 2 weeks |
UCS-2 support | N/A |
Use case restrictions | Only Sender IDs related to International OTP traffic will be allowed. Other type of traffic as well as the one generated from Domestic Companies is not permitted in Iran. |
Best practices | During registration please provide a representative sample as SMS as content allow listing is also required in Iran. Messages submitted via a registered Sender ID with content that is different from the allowlisted one will be rejected |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis |
Long Code - Domestic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | --- |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Long Code - International | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis |
Short Code | |
---|---|
Operator network capability | Not Supported |
Twilio supported | --- |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
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.