Iran (IR)

Locale name

Iran

ISO code
The International Organization for Standardization two character representation for the given locale.

IR

Region

Middle East & Africa

Mobile country code
A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.

432

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+98

Two-way SMS supported
Whether Twilio supports two-way SMS in the given locale.

No

Number portability available
Whether number portability is available in the given locale.

Yes

Twilio concatenated message support
Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one. 

Yes*
For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.

Message length
How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.

-----

Twilio MMS support
Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.

Not Available

Sending SMS to landline numbers
How Twilio handles an SMS message destined for landline telephone number.

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. This table lists some general best practices.

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:

1. Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications.
2. Only communicate during an end-user’s daytime hours unless it is urgent.
3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language.
4. Do not contact end-users on do-not-call or do-not-disturb registries.

Please take note that gambling, betting, political, religious or adult-related content is strictly prohibited in Iran.

URL links are not allowed in Iran. Sending messages with such a content will result in the messages getting filtered.

Operator network capability
Whether mobile operators in the given country support the feature.

Required

There is no segregation between International and Domestic Traffic

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Supported
Learn more and register via the Console

Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

No

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

2 weeks

N/A

UCS-2 support

Supported

N/A

Use case restrictions

Submitting content with URLs will result in message filtering even if the the Sender ID is registered. Please avoid using URLs when sending messages in Iran.

The registered Sender ID will not be reserved for the Network MTN to due local compliance reasons. The Sender ID will be replaced from a Longcode outside Twilio's platfrom

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 attempted on a best effort basis

Operator network capability
Whether mobile operators in the given country support the feature.

Not Supported

Not Supported

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

---

Supported

---

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

---

No

---

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

N/A

UCS-2 support

N/A

N/A

N/A

Use case restrictions

N/A

N/A

N/A

Best practices

N/A

Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be attempted on a best effort basis

N/A