Page History
Last Updated:
| Lastupdatedate |
|---|
| Livesearch | ||||
|---|---|---|---|---|
|
Data Coding
The Vibes Connect SMSC currently supports the following Data Coding:
Data Coding | Charset |
|---|---|
0 | SMSC Default (ASCII/IA5) |
1 | ASCII/IA5 |
4 | GSM 7 bit |
8 | 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.
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.
TON and NPI and Other Settings
Source TON | 0 - for messages sent via Shortcode or Longcode 5 - for messages sent via Alphanumeric Code (non US ) |
| Source NPI | Always 0 |
| Destination TON | Always 0 - Non US/Canada MDNs must be sent in e.164 format. |
Destination NPI | Always 0 |
| System Type | Ignored - Leave blank |
| Service Type | Ignored - Leave blank |
| Validity Period | Leave blank. Can cause failed messages during Daylight Savings Time time change if set to missing hour. |
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.
parameter_name | Optional | Description |
|---|---|---|
Carrier Code | Yes | Used to identify the carrier on a message. |
Alternate Message Delivery | Yes | Used 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.
Overview
Content Tools