Locale Summary
Locale name | Norway |
---|---|
ISO code | NO |
Region | Europe |
Mobile country code | 242 |
Dialing code | +47 |
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 | Norway’s mobile operators are blocking and filtering SMS content containing web addresses (URLs). If your SMS content carries a web URL, kindly reach out to Twilio customer services to get your SMS content added to an allow list to prevent delivery failure. When content registration is complete, you must send the messages with an International Long Code Sender ID or an Alphanumeric Sender ID. Sending messages using Domestic Long Code Sender ID may result in messages containing a web URL being filtered. Gambling and lottery-related content is strictly prohibited by mobile operators in Norway.
|
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Not Required | Supported | Not Supported | Supported | Not Supported |
Twilio supported | --- |
Supported
Learn more | --- | Supported | --- |
Sender ID preserved | --- | Yes | --- | Yes | --- |
Provisioning time | N/A | N/A | N/A | N/A | N/A |
UCS-2 support | N/A | Supported | N/A | Supported | N/A |
Use case restrictions | N/A | N/A | N/A | N/A | N/A |
Best practices | N/A | N/A | N/A | N/A | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Not Required |
Twilio supported | --- |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Supported |
Twilio supported |
Supported
Learn more |
Sender ID preserved | Yes |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | N/A |
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 | Supported |
Twilio supported | Supported |
Sender ID preserved | Yes |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | N/A |
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.