Guidelines

Serbia (RS)

We've compiled regulatory and compliance information to help ensure you're communicating effectively and compliantly around the world.

Back to Guidelines

Locale Summary
Locale name	Serbia
ISO code The International Organization for Standardization two character representation for the given locale.	RS
Region	Europe
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.	220
Dialing code The dialing prefix used to establish a call or send an SMS from one locale to the given locale.	381

Guidelines
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.	No
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.	Converted to SMS with embedded URL
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. The following are some general best practices: Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications. Only communicate during an end-user’s daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language. Do not contact end-users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

Alphanumeric

	Global Pre-registration	Dynamic
Operator network capability Whether mobile operators in the given country support the feature.	Supported (Optional) There is no segregation between International and Domestic Traffic	Not Supported
Twilio supported Whether Twilio supports the feature for the given country.	Supported (Optional) Learn more and register via the Console	Supported Learn more
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.	16 days	---
UCS-2 support	Supported	Supported
Use case restrictions	---	Dynamic Alphanumeric Sender IDs are not fully supported by the networks Telenor and mt:s (Telekom Srbija). Sender IDs may be overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to ensure delivery for this network.
Best practices	In case the traffic is promotional we suggest the customer adding the phrase " Odjava STOPMFL na 1599, 0din" at the end of each SMS. This will allow the subscriber that receives the SMS to OPT - OUT the promotional content in case they want to stop receiving such messages	We suggest our clients to OPT IN the optional Sender ID Registration service we offer in case they need to use a specific Alpha Sender ID

Long codes and short codes

	Long code domestic	Long code international	Short code
Operator network capability Whether mobile operators in the given country support the feature.	---	Not Supported	Not Supported
Twilio supported Whether Twilio supports the feature for the given country.	---	Supported	Not 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.	---	---	---
UCS-2 support	---	Supported	---
Use case restrictions	---	Dynamic Numeric Sender IDs are not supported by mobile operators in Serbia. Sender IDs will be overwritten with a Generic Alphanumeric Sender ID outside the Twilio platform to ensure delivery.	---
Best practices	---	We suggest our clients to OPT IN the optional Sender ID Registration service we offer if hey can use a specific Alpha Sender IDs instead of a Numeric Sender ID.	---

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.