Skip to main content

Locale Summary

Locale nameSudan
ISO codeSD
RegionMiddle East & Africa
Mobile country code634
Dialing code+249

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou 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. 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.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityRequiredNot Supported --- --- ---
Twilio supported Required
Learn more
Supported Supported --- Not Supported
Sender ID preservedYesYesYes --- ---
Provisioning time3 weeksNone---------
UCS-2 support---------------
Use case restrictions---

Dynamic Alphanumeric Sender ID is only supported for international customers. For the MTN Sudan network specifically, Alphanumeric Sender IDs must be pre-registratered.

---

Numeric International Sender ID is not supported by the MTN network in Sudan. Messages submitted with a Numeric Sender ID will not be delivered. Send only with an Alphanumeric Sender ID to this network.

---
Best practices

Please refrain from using generic Sender IDs like InfoSMS, INFO, Verify, Notify, etc. to avoid being blocked by network operators.

Please refrain from using generic Sender IDs like InfoSMS, INFO, Verify, Notify, etc. to avoid being blocked by network operators.

---------
Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Required
Learn more
Sender ID preservedYes
Provisioning time3 weeks
UCS-2 support---
Use case restrictions---
Best practices

Please refrain from using generic Sender IDs like InfoSMS, INFO, Verify, Notify, etc. to avoid being blocked by network operators.

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported Supported
Sender ID preservedYes
Provisioning timeNone
UCS-2 support---
Use case restrictions

Dynamic Alphanumeric Sender ID is only supported for international customers. For the MTN Sudan network specifically, Alphanumeric Sender IDs must be pre-registratered.

Best practices

Please refrain from using generic Sender IDs like InfoSMS, INFO, Verify, Notify, etc. to avoid being blocked by network operators.

Long Code - Domestic
Operator network capability ---
Twilio supportedSupported
Sender ID preservedYes
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions

Numeric International Sender ID is not supported by the MTN network in Sudan. Messages submitted with a Numeric Sender ID will not be delivered. Send only with an Alphanumeric Sender ID to this network.

Best practices---
Short Code
Operator network capability---
Twilio supportedNot 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.