Showing results for 
Show  only  | Search instead for 
Did you mean: 

Note: Before you get started, please ensure you have your CAD (Customer Account Details) document ready. If you do not have a copy, please request one from your Sinch Account Manager.


This article outlines and describes the settings that are necessary to configure Adobe Campaign Classic.


General Settings


Friendly name of the channel.


Should be set to "Mobile (SMS)"

Use the default options for all the other settings.


Mobile channel - Connection settings

SMSC Implementation name

Specify a meaningful name for this connection.


The FQDN or IP of the Sinch SMSC you wish to connect to.

Your CAD will include this information.


3600 for unencrypted SMPP

3601 for SMPP via TLS (Requires that "Enable TLS over SMPP" is enabled under "SMSC specificities")


Known as the system_ID in the SMPP protocol. Equivalent to the username. Your CAD will include this information.


Refer to your CAD.

System type

Leave this field empty.

Number of MTA child connections

Your CAD will mention how many connections your system_ID can use - this setting should be half of that. This is due to Campaign Classic being limited to using the TX/RX bind-method as compared to TRX.


Mobile channel - SMPP channel settings

Authorize character transliteration

This setting can be ticked to allow Campaign to re-encode characters, for example "ê" to "e". More information is available in Adobes documentation

Source number

The "from" number or alpha of your messages. Also known as the originator. This can be a company name, a long number or short code.

We recommend keeping all alphas shorter than 11 characters.

Source TON/NPI

This value depends on the type of Source number set in the above section.

Refer to the Source address settings table showing common combinations in our Sinch Developer Documentation

Destination TON/NPI

Always configured as 1/1, as Sinch only support messages to International MSISDNs.

Service type

Leave this field empty.


Mobile channel- Throughput and delays

Sending window

The SMPP window size dictates how many unresponded PDUs are allowed. Best practice is to use the value in the CAD.

Max MT throughput

Must be configured with the value set in your CAD. If this is left at 0 you will see rejected messages which will in turn result in delayed messages.

Time before reconnection

No change needed – use the default setting.

Expiration period of the MT

No change needed – use the default setting.

Bind timeout

Set to 60 seconds.

enquire_link period

No change needed – use the default setting.


Mobile channel - Mapping of encodings

Sinch use GSM-7 as the SMSC default alphabet. Therefore, the following Data_coding settings apply:





GSM 03.38 (GSM-7)







Mobile channel - SMSC specificities

Activate message_payload

This setting allows you to send larger payloads than normal.

Do not select this option.

Send full phone number

Do not select this option to ensure only digits are sent in the destination address.


Use the default setting 0/0

Range of addresses

Leave this field empty.

Invalid ID acknowledge count

Leave as 0.

Extraction regex of the ID in the SR

Set to: \b[iD][dD]:([a-fA-F0-9]{32,32})\b

Extraction regex of the status in the SR

Set to: \b[sS][tT][aA][tT]:([a-zA-Z0-9]{5,8})\b

Regex applied to determine successful status

Set to: ^DELIVRD

Regex applied to determine error status


Extraction regex of the error code in the SR

Set to: \b[eE][rR][rR]:([a-zA-Z0-9]{0,3})

ID format in MT acknowledgment

Do not modify

ID format in the SR

Do not modify

SR ID or error code in optional field

Leave unchecked

SR ID or error code in text field

Leave unchecked

Service ID tag

Leave this field empty

Enable TLS over SMPP

Should be enabled if port 3601 is set under "Mobile - Connection settings"

Skip TLS certificate verification (insecure)

Leave unchecked

Featured Article
Version history
Last update:
‎10-14-2022 07:30 AM
Updated by: