Sinch Community

The following are some FAQ related to the Adobe Classic Campaign for SMPP:   Q: Why I am not getting delivery reports/SRs in Adobe Campaign? A: Ensure the regex under "Extraction regex of the ID/status in the SR" are configured in line with what is mentioned on Adobe Campaign Classic with Sinchs SMPP API    Q: When sending messages in Campaign Classic, why is there a delay before they are visible on dashboard.sinch.com? A: Often this is due to misconfiguration of either throughput or bind-settings. Please see section "Mobile - Throughput and delays" on Adobe Campaign Classic with Sinchs SMPP API.   Q: How do I format my from & to number in my messages? A: Supported formats and explanations are found in our developer docs. From number  To number    Q: Why are special characters not showing up correctly on the handset? A: Ensure that the value data_coding 0 is set to GSM 03.38 (7-bit) under "Mobile - Mapping of encodings". More details are found in Adobe Campaign Classic with Sinchs SMPP API. For a full description of the supported encodings and character sets please see Message Encoding. ... View more

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 Label Friendly name of the channel. 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. Server The FQDN or IP of the Sinch SMSC you wish to connect to. Your CAD will include this information. Port 3600 for unencrypted SMPP 3601 for SMPP via TLS (Requires that "Enable TLS over SMPP" is enabled under "SMSC specificities") Account Known as the system_ID in the SMPP protocol. Equivalent to the username. Your CAD will include this information. Password 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:   Data_coding Encoding 0 GSM 03.38 (GSM-7) 3 ISO-8859-1 8 UCS2     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. Bind TON/NPI 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 Set to: ^(?:EXPIRED|DELETED|UNDELIV|UNKNOWN|REJECT) 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 ... View more

Here is a list of information that is helpful to include when opening a ticket with the Sinch Support Team: Samples. This is often the most crucial piece of any investigation. This could be a Message ID, a batch ID or an MSISDN. We are at this point unable to accept images of logs. A clear description of the problem. For example "Messages are delayed to destination XXX" Timestamps when the problem occurred. This does not need to be down to second accurate, an estimate does suffice. If your fault report is regarding message delivery, you can use this template to ensure the Sinch Support team have all information required to troubleshoot:   Account ID: API or protocol: Message ID or MSISDN: Timestamp of the fault: Fault description:   The issue field should contain a clear description of the fault. If the fault-report concerns a missing inbound message or malformed content, a screenshot from the end device would also be helpful.   If the fault report is related to connection issues, this template can be used:   Account ID: API or Protocol: System ID/Bot ID/Service Plan ID: Source IP (The IP you're connecting from): Destination IP or FQDN and port (The Sinch endpoint you're attempting to reach): Timestamps of the connection attempts:   If SMPP/HTTP Basic we appreciate an unencrypted packet capture showing the fault. ... View more

This article outlines some of the more common mistakes when using SMPP and can serve as a checklist of common misconfigurations.   Bind_Transmitter/Bind_Receiver/Bind_Transceiver: The interface_version, must be declared, most often 0x34 if your ESME supports SMPP version 3.4.   Submit_SM: source_addr_ton, Type of number needs to match the source_addr: TON Value Unknown 0x00 International 0x01 National 0x02 Network Specific 0x03 Subscriber Number 0x04 Alphanumeric 0x05   source_addr_npi, Numeric Plan Indicator needs to match the source_addr:   NPI Value Unknown 0x00 MSISDN 0x01   For example, the sender ID Sinch requires 0x05/0x00 while 467012345678 requires 0x01/0x01. dest_addr_ton and dest_addr_npi should be set to 0x01/0x01 as the receiving address is always an International MSISDN.   data_coding, commonly referred to as the DCS-value. Most often 0x00 for SMSC Default alphabet (GSM-7) or 0x08 for Unicode/UCS2. ... View more

SMPP - Refer to the Common SMS SMPP Statuses and Error Codes Explained article for a list of common SMPP error codes with troubleshooting steps. HTTP - Refer the Common SMS HTTP Statuses and Codes Explained article for a list of common HTTP error codes with troubleshooting steps. ... View more