Last Updated:

Phone Number / MSISDN Format

The Short Message Service Center (SMSC) supports the following formats:

  • National (10 digits)
  • International (11 digits)
  • E.164

Mobile Terminated (MT) messages to Phone numbers in the US and Canada can be set in any of the previous formats. The rest should be set in the E.164 format.

Mobile Originated (MO) messages from US and Canada will default to the National format, and the rest will always be in the E164 format. The Phone number format for MOs from the US and Canada can be changed, if required, to the other supported formats when the account is being set up.

Data Coding

The Vibes Connect SMSC currently supports the following Data Coding:


Data Coding



SMSC Default (ASCII/IA5)




GSM 7 bit


UCS2 (ISO/IEC-10646)

If a Data Coding is not supported by the carrier, the message will be encoded using the carrier's default, which may result in some characters not being encoded correctly. Currently only ASCII is supported across all carriers.

TON and NPI Settings

  • The TON should be set to 0 for messages sent via a shortcode.
  • The TON should be set to 5 for international messages sent via an alphanumeric source code.
  • The NPI should be set to 0 for all messages.
  • The SMSC will set the appropriate values before submitting to the carriers.

TLV Parameters

The following are additional Type Length Value (TLV) parameters that could be set on MO and MT messages. Please see Vibes Optional TLVs for the complete specification of each TLV. 




Carrier Code


Used to identify the carrier on a message. 
It will always be set on MO messages and is optional on MT messages.

Alternate Message Delivery

YesUsed to specify if Alternate Message Delivery should be used upon message failure.
This feature is not supported for concatenated messages. 

Concatenated Messages

The SMSC supports concatenated MO and MT messages via the User Data Header (UDH).

The User Data Header Indicator bit should be set to 1 in the ESM class for concatenated messages. Refer to Wikipedia for more information on how to construct the User Data Header.