Locale Summary
Locale name | Russia |
---|---|
ISO code | RU |
Region | Europe |
Mobile country code | 250 |
Dialing code | +7 |
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 | Mobile operators in Russia are continuously improving their firewalls and routes that use longcode and generic alphanumeric sender IDs are actively being blocked. To avoid this risk and to ensure optimal delivery, we recommend you opt for pre-registered alphanumeric sender IDs. Please contact your account manager or Twilio customer support for more details. 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:
|
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 | Not Supported | Not Supported | Not Supported | Not Supported | Not Supported |
Sender ID preserved | Yes | --- | --- | --- | --- |
Provisioning time | Temporarily not supported | N/A | N/A | N/A | N/A |
UCS-2 support | Supported | --- | N/A | --- | N/A |
Use case restrictions | Content related to gambling, alcohol, tobacco and pornography is strictly prohibited. | N/A | N/A | N/A | N/A |
Best practices | Alphanumeric Sender ID registration is temporarily paused. If you are related with humanitarian aid and in line with the work of our Twilio.org team, then please reach out to us at senderid@twilio.com and we will review your application individually | Sender ID Registration is Required in Russia. | N/A | Sender ID Registration is Required in Russia. | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Required |
Twilio supported | Not Supported |
Sender ID preserved | Yes |
Provisioning time | Temporarily not supported |
UCS-2 support | Supported |
Use case restrictions | Content related to gambling, alcohol, tobacco and pornography is strictly prohibited. |
Best practices | Alphanumeric Sender ID registration is temporarily paused. If you are related with humanitarian aid and in line with the work of our Twilio.org team, then please reach out to us at senderid@twilio.com and we will review your application individually |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | --- |
Use case restrictions | N/A |
Best practices | Sender ID Registration is Required in Russia. |
Long Code - Domestic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not 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 | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | --- |
Use case restrictions | N/A |
Best practices | Sender ID Registration is Required in Russia. |
Short Code | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not 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.