Locale Summary
Locale name | Oman |
---|---|
ISO code | OM |
Region | Middle East & Africa |
Mobile country code | 422 |
Dialing code | +968 |
Guidelines
Two-way SMS supported | No |
---|---|
Number portability available | Yes |
Twilio concatenated message support | Yes |
Message length | 160 Characters |
Twilio MMS support | Converted to SMS with embedded URL |
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 | We recommend that you test Unicode-encoded content before sending it, although Unicode characters should be supported. Sender IDs are overwritten with either random Alphanumeric or long numbers to avoid carrier blocking and filtering.
|
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 | 18 days | N/A | N/A | N/A | N/A |
UCS-2 support | Supported | Supported | N/A | Supported | N/A |
Use case restrictions | N/A | N/A | N/A | N/A | N/A |
Best practices | N/A | Oman requires Sender ID pre-registration. Delivery via unregistered Sender IDs will be attempted on a best-effort basis but may not succeed. | N/A | Oman requires Sender ID pre-registration. Delivery via unregistered Sender IDs will be attempted on a best-effort basis but may not succeed. | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Required |
Twilio supported |
Required
Learn more |
Sender ID preserved | Yes |
Provisioning time | 18 days |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | N/A |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | Oman requires Sender ID pre-registration. Delivery via unregistered Sender IDs will be attempted on a best-effort basis but may not succeed. |
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 | Supported |
Use case restrictions | N/A |
Best practices | Oman requires Sender ID pre-registration. Delivery via unregistered Sender IDs will be attempted on a best-effort basis but may not succeed. |
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.