Country Summary
| Country name | Oman |
|---|---|
| ISO code | OM |
| Region | Middle East & Africa |
| Mobile country code | 422 |
| Dialing code | +968 |
| Major carriers | Oman Mobile, Ooredoo |
Guidelines
| Two-way SMS supported | Yes |
|---|---|
| Number portability available | Yes |
| Twilio concatenated message support | Yes |
| Message length | ----- |
| 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 | It should be generally supported, but it is recommended for unicode-encoded content to be tested first before sending. Sender IDs are overwritten with either random alphanumeric or long numbers to avoid carrier blocking and filtering.
|
Phone Numbers & Sender ID
| Preregistered | Alphanumeric | Long Code | Short Code | |
|---|---|---|---|---|
| Operator network capability | Required | Not Supported | Supported | Not Supported |
| Twilio supported | Required | Not Supported | Supported | Not Supported |
| Sender ID preserved | Yes | --- | Yes | --- |
| Provisioning time | 2 weeks | -- | -- | -- |
| UCS-2 support | Supported | -- | Supported | -- |
| Use case restrictions | -- | -- | -- | -- |
| Best practices | Alphanumeric Sender ID would only be preserved through pre-registration | -- | -- | -- |
| Preregistered | |
|---|---|
| Operator network capability | Required |
| Twilio supported | Required |
| Sender ID preserved | Yes |
| Provisioning time | 2 weeks |
| UCS-2 support | Supported |
| Use case restrictions | -- |
| Best practices | Alphanumeric Sender ID would only be preserved through pre-registration |
| Alphanumeric | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | -- |
| UCS-2 support | -- |
| Use case restrictions | -- |
| Best practices | -- |
| Long Code | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | -- |
| UCS-2 support | Supported |
| Use case restrictions | -- |
| Best practices | -- |
| Short Code | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | -- |
| UCS-2 support | -- |
| Use case restrictions | -- |
| Best practices | -- |
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.