Outbound SMS restrictions - Hottelecom

Outbound SMS restrictions

Hong Kong Special Administrative Region (HKSAR)
p>We are using Adaptive Routing throughout Hong Kong which will ensure several routes are constantly being tested and the optimum one will be used for your traffic.

To ensure delivery, numeric Sender ID will be replaced by SMS, NXSMS or a local number. Also, all Sender ID on China Mobile Hong Kong 45412 will be replaced by local number.

Concatenated SMS and handset delivery receipts are supported on all Hong Kong networks.

Hungary (Direct route)

Carriers in Hungary are increasing their interworking fees and closing down the routes which don’t have interworking fees. We have heard that regulation changes mean dynamic Sender ID will not be possible for A2P traffic in the future. To ensure stable delivery, Nexmo is delivering via local connections.

Pricing is €0.0600 to all networks.

Handset DLR is supported, only restriction aside from the usual ‘no spam’ policy is the Sender ID is changed to +36707177171. You can get your own numeric Sender ID which can be used to enable 2-way SMS with your customers. See our inbound pricing at www.nexmo.com/pricing.

Indonesia (Direct route)

Nexmo is using Adaptive Routing to deliver messages throughout Indonesia. We have access to local direct routes, although several backup routes are used as Indonesia is historically quite an unstable destination to send SMS.

Delivery receipts are extremely unreliable also across all networks in this country, some are missing completely, and therefore making any data based on DLR’s very inaccurate.

Our route also supports concatenated messages and sending messages to ported numbers.

Unicode encoding is not officially supported by any of the networks in Indonesia, and we suggest using default Latin/GSM7 characters. Extended characters such as brackets “[” and “]” are often problematic.

Sender ID might be replaced to different alpha or numeric Sender ID to ensure delivery. If you wish to send a customised Sender ID, Nexmo can help to pre-register for volumes exceeding 100k messages per month.

If you subscribe to one of Nexmo’s
Indonesian virtual numbers and set this as the Sender ID, then it will not be changed and the recipient will be able to reply to your messages.

India: Features & Restrictions

India is a very complex market and there are a number of different regulations and restriction you must comply with:

NDNC registration

Messages sent to numbers registered in the Indian NDNC (National Do Not Call registry) list will be blocked. You can check the destination number on the Telecom Regulatory Authority of India registry using the following search tool: www.nccptrai.gov.in/nccpregistry/search.misc (omit India International prefix 91)

Permitted Hours of Delivery

We can only guarantee message delivery between 9am to 9pm. Messages submitted after 9pm we will attempt to send, but due to local regulations, these messages will be queued until the morning and you will be charged for them as usual.

Transactional route application

If you have transactional messages which are either user-generated or expected, you can register to bypass these two filters. It requires a 6 – Alpha sender ID and SMS example for registration (minimum 25k SMS per month). Please submit your registration request at nexmo.com/india. This SenderID will be used as often as possible but a major percentage of traffic will still be overwritten to ensure delivery: SenderID will be prefixed with 2 letters depending on which carrier was used to deliver the SMS to the final operator, or more commonly a random number; e.g. MD-XXXXXX (where XXXXXX is the registered SenderID). This is due to recent regulation changes.

Any unregistered sender ID is fixed to a local shortcode as required by Indian regulations, whether the destination number is registered on the NDNC list or not.

Anti-spam measures

Number of messages to the same number limitations:

  • More than 6 messages with the same sender or text to the same number within an hour may be blocked
  • Users may not be able to receive more than a total of 200 SMS per day across all incoming streams.

Political Reasons

Messages towards Jammu and Kashmir networks (example, 405/55 – Airtel J&K) will be blocked by the government due to political sensitivity.

SUPPORTED FEATURES:
Reliable handset delivery receipts – Yes
Dynamic SenderID – Pre-registered Alpha (6 letters) or Fixed local shortcode
Unicode – Yes
Concatenated Messages – Yes

India Pre-registered Sender ID Prefixes

Questions:

  • Why does my Sender ID have extra letters in front of it?
  • Why is my Brand name not displayed as I defined it?
  • Why do my messages have the initials MD in front of the Sender ID?

Solution:

Sender IDs in India may be prefixed with additional letters to identify who delivered it and through which gateway.

The following are the list of SMS prefixes used in India and their explanation:

Service Provider Code
Aircel, Dishnet Wireless D
Airtel A
BSNL B
BPL Mobile/Loop Telecom L
Datacom Solutions C
HFCL Infotel H
Idea Cellular I
MTNL M
Reliance Communications R
Reliance Telecom E
S tel S
Shyam Telecom Y
Spice Telecom P
Swan Telecom W
Tata Teleservices T
Unitech U
Vodafone V

State Codes that signify the SMS Gateway Origin:

Service Circle Code
Andhra Pradesh A
Assam S
Bihar B
Delhi D
Gujarat G
Haryana H
Himachal Pradesh I
Jammu & Kashmir J
Karnataka X
Kerala L
Kolkata K
Madhya Pradesh Y
Maharashtra Z
Mumbai M
North East N
Orissa O
Punjab P
Rajasthan R
Tamil Nadu T
UP-East E
UP-West W
West Bengal V

So if the Sender ID is received as VD-NEXSMS, this will mean the carrier delivering was Vodafone, and the region was Delhi.

Iraq

Asiacel Iraq (41805) all senders are changed to a shortcode or a long number in order to ensure delivery. Please note that we do not currently expect handset DLRs for messages to this network.

Zain Iraq (41820) filters shortcode and alphanumeric senders. We suggest to use international format numeric sender to bypass Zain Iraq filtering. Avoid using senders starting with 46. Please note that we do not currently expect handset DLRs for messages to this network. Also please do not add parenthesis , “( ” or “)” into the content since this will be filtered.

Iraq Korek (41840) does not support alpha senderIDs. We advise you to use numeric senders to avoid this problem. All alpha senders will be overwritten but delivery is not guaranteed.

If messages are nevertheless sent with alphanumeric sender ID, there are routes to Iraqi networks where the sender ID will be automatically modified to a numeric string to bypass the above networks filtering, and ensure delivery.

Please note that we are using Adaptive Routing throughout Iraq to ensure minimal downtime. Therefore senders may deviate from the above as Iraq is historically quite an unstable market to send SMS.

Israel (Direct route)

Our route to Israel operators is fully featured, supporting handset DLRs and sending to ported numbers. The route includes support for messages longer than 160 characters (concatenated messages). Dynamic Sender ID is supported, but sometimes this may be changed to another alphanumeric or random numeric Sender ID to ensure delivery.

Please note, SMS cannot be delivered to kosher phone numbers.

“Kosher” phones and networks are essentially phones with Haredi rabbinical approval that can be used for communication without entertainment functionality or connectivity. This is a line that has a predefined prefix and it is blocked to content that Haredi activists feel is not appropriate for their community. Such blocking includes cellular internet access, chat rooms, SMS, etc. It should not be imputed that other phones are not kosher according to Jewish law, as evidenced by the fact that a very large number – if not the majority – of observant Orthodox Jews worldwide do not restrict themselves to “kosher” phones; rather the description “kosher” phones is a loose description implying an added level of stringency accepted by some communities.

Some mobile plans include a large allocation of minutes to kosher numbers, which are:

Italy (Direct route)

Like most of Western Europe, the Italian Operators charge for SMS delivery. Today Nexmo is launching a local direct to provide a saving on the SS7 fees, In addition to the usual anti spam policy, the Italian networks are keen to stress that using a company name in the Sender ID is only allowed when the message is from that company.

Our direct route to Italy

  • supports most features, including handset DLR, unicode, binary, concatenation.
  • allows only alphanumeric Sender IDs and local numeric sender IDs with a maximum of 11 digits and sent in local format
  • Any SMS sent with an international numeric Sender ID will not be sent via the direct route, but rather via international p2p routes.

In addition to the usual anti spam policy, the Italian networks are keen to stress that using a company name in the Sender ID is only allowed when the message is from that company.

Supported Features
Reliable handset delivery receipts – Yes
Dynamic SenderID – Fully dynamic
Unicode – Yes
Concatenated Messages – Yes

Ivory Coast (Direct route)

We are using a high-quality direct route into Cote d’Ivoire.

Our route to Atlantique Telecom (61202)and MTN (61205) is Fully featured, supports all senders and returns real DLRs. Hypens (-) and underscores (_) are not allowed within the Sender ID.

Our route to Orange (61203) all senders will be overwritten to “NXSMS” to ensure delivery

Japan: Features & Restrictions

The following set of restrictions apply to all Japan Networks:

  • Unicode messages are supported when the content is Japanese characters. For other languages, some handsets may not be able to display them correctly, or messages will not be delivered (e.g. Chinese)
  • Concatenated messages are currently not supported, max of 140 bytes (160 GSM7 characters/ 70 unicode characters) for all Japan networks. SMS would be split to multiple parts of SMS.
  • Delivery Receipts are unreliable.
  • For messages classified as illegal and are either discarded completely or part of the illegal text will be removed

For Sender IDs to:

Au KDDI (44007)

  • Alphanumeric Sender ID’s are not supported and will be overwritten by a numeric sender, all local senders start with prefix +81 will be blocked.

NTT Docomo (44010)

  • Alphanumeric Sender ID’s are supported, all local senders start with prefix +81 will be blocked therefore all numeric Sender ID would be forced to NXSMS.

Softbank Mobile (44020)

  • Alphanumeric Sender ID’s are supported, all local senders start with prefix +81 will be blocked therefore all numeric Sender ID would be forced to NXSMS.

eMobile (44000)

  • All Sender IDs will be modified to be numeric to ensure delivery.

Supported Features

Reliable handset delivery receipts – No
Dynamic SenderID – No
Unicode – Yes
Concatenated Messages – No

Jordan (Direct route)

Carriers in Jordan, have implemented spam filters to prevent A2P traffic reaching their network. Spam filters can return in some cases fake delivery receipts and don’t discriminate between spam and legitimate traffic. What makes delivery highly unlikely to that market is the sophisticated spam filter of Zain, which has over 70% market share.

Nexmo uses our new Adaptive Routing throughout Jordan to ensure messages are delivered. We are using a local connection as our main supplier and several others as backup ones in order to minimize downtime.

Depending on the network, all senderID’s will be overwritten by either a local number or a fixed alpha (such a ANSMS).

As with all of the Middle East, you may not send any adult content.

Please note that advertising/marketing messages require you to add the prefix “adv” before the sender id e.g FROM=”adv Nokia” to be in line with the Telecom Regulation Commission of Jordan. Also these promotional messages should not be sent after 9:00 PM Amman time (GMT + 3:00).

Kazakhstan

GSM Kazakhstan Kcell (40102)

Sender ID would be forced to “SMSInfo” or “MESSAGE” to ensure delivery.

Kenya

All networks in Kenya, particularly Safaricom and Airtel, are heavily filtering international routes so Nexmo is delivering via a local connection to all networks in Kenya.

Delivery Receipts are supported except for Airtel, where they are network receipts rather than handset receipts. There are substantial DLR Delays from the Kenya operators at most times so DLR latency should not be used to measure delivery time.

All senders to Safaricom will be overwritten to a fixed alpha to ensure delivery. If you have very large volumes of 2FA traffic to send to Safaricom please get in touch with your account manager.

Your request has been sent! Thanks!
We will reply you in the nearest time.
Your request has been sent! Thanks!
We will reply you in the nearest time.
Your request has been sent! Thanks!
We will reply you in the nearest time.
Did not find the number you need?
Leave a request and we will contact you!
Your request has been sent! Thanks!
We will reply you in the nearest time.