Sinch Community

DB65 is a SMS 365, enterprise service status code, which indicates that the Operator/SMSC was unable to deliver the MT message within the Validity Period (VP), defined for the message.     The Validity Period can be set to a period of seconds, minutes, hours, days or weeks in varying increments up to one year, and is set for each MT message.   Possible reasons why a MT message may expire   There are a number of reasons why the operator SMSC was unable to deliver the MT message within the validity period set, some of which are detailed below:   Category Description Action Handset The handset is not on the network and so is unreachable. In such cases the operator network in general has not received the ‘handset switched off’ signal and therefore is ‘absent’ from the operator network The end-user should ensure that the handset is switched on and correctly connected to their network operator.   Faulty handset and reception issues should be addressed by the end-user with their network operator. Handset The handset is switched off and a signal from the handset to the operator confirms this action. In this case, the message will be set to retry until the validity period has expired The end-user should ensure that the handset is switched on and correctly connected to their network operator. Handset The handset is in a low coverage area causing intermittent connectivity to the operator network resulting in  messages to the handset to not be correctly delivered   This can also cause handset acknowledgement issues, whereby the notification can either, not be sent or is sent but arrives with delay, by which time the message is entered into, or remains in the retry cycle until the message expires The end-user should ensure that the handset is correctly connected to their network operator.   Faulty handset and reception issues should be addressed by the end-user with their network operator. Handset SMS inbox is full. The end-user should delete any unwanted SMS messages from the inbox to allow new SMS messages to be correctly delivered. End User The end user (and by extension the handset) is roaming on another network   In general a MT message sent to a MSISDN which is roaming is ‘best effort’, and is not guaranteed, however where peering agreements exist, the possibility of message delivery increases, although these messages  are subject to many more constraints and delays which may result in message expiry The end-user should use a local operator with whom their home network operator has a peering agreement.   This increases the possibility of message delivery, however any such message, is subject to many more constraints and delays, which may still result in message expiry End User The end user has a pre-pay account, where there is no credit remaining on the account sufficient to keep the end user on the network; This will put the MT into a retry cycle. The end-user should ensure that there is sufficient credit remaining on the account to send and receive SMS messages and to keep the handset connected to the operator network.   ... View more

DB62 is a SMS 365, enterprise service status code meaning ‘Rejected by operator’ or ‘Out of coverage’, which indicates that the end-user is currently out of their network operator coverage zone or has been rejected.   Possible Reasons for a DB62 response   There are a number of reasons why the DB62 status code is returned, some of which along with the actions that should be taken, are detailed below:   Category Description Action End User The end user is temporarily un-reachable as they are not correctly on their operator network. The end-user should ensure that there is sufficient network coverage available to their handset to receive SMS MT messages. End User The end user’s SIM card is full, and no further SMS MT messages can be delivered The end user should ensure that any unwanted SMS MT messages are removed to resume SMS MT delivery. SMSC MT messages which return a DB62 response can be escalated to the Service Desk for further clarity, if the MT message was submitted with a handset acknowledgement request. Raise a single user issue (SUI) ticket to the Service Desk (SD), detailing the OrderID, MSISDN and date/time the MT message was sent, so that the SD team can investigate.   ... View more

The Campaign Automator allows Content Providers (CPs) to be able to automate the list creation and schedule campaign process instead of having to configure it using the web interface. CPs send both subscriber lists and configuration files to Digital Interconnect using sFTP/FTP. Information is added to logs while the Automator picks up the .csv and configuration file for processing. After a subscriber list group is created and a campaign is scheduled, an email is sent to the CP notifying them of the process status.   The message manager Automator User Guide describes the Campaign Automator in more detail and explains how to use it ... View more

message manager add-on for SMS 365, enterprise service, is the central hub for managing Tasks that generate and respond to SMS messages. Tasks (also referred to as campaigns) are designed to be easy to set up, view, and manage. Using message manager, customers can easily deploy a wide variety of fun, engaging, and relevant mobile services from voting to instant win competitions to text alerts and broadcasts. message manager is connected to Digital Interconnect’s global distribution platform, providing unparalleled subscriber reach around the world. The message manager platform is hosted in a 24x7 data center and has redundancy across all the major components. It has flexible, real-time reporting, regardless of the load condition of the service (including mobile acknowledgments). The reporting tools included in message manager provide a unique capability for users to gain valuable insight into their subscriber base, resulting in a higher quality of service for the management and delivery of SMS, content, campaigns, and applications. The message manager User Guide describes how to access and use message manager: ... View more

Question Why does a concatenated SMS not appear correctly on a user’s mobile phone?   Answer If a user reports that the concatenated messages they are receiving on their mobile phones: appear as separate messages are being truncated have message parts missing. There are several reasons why a concatenated message (multi-part message) may not be correctly displayed on the handset: The MT message parts arrived in the wrong order, which the handset is unable to process and display correctly. The concatenated message is displayed as several separate text messages. This is usually due to the handset operating system, and its management process of the header information for each message part. The handset may be busy, and the MT message part delivery may be postponed, which may cause the order of the message parts to be delivered in the wrong order. The operating system on most handsets, manage this scenario and wait until all message parts have been received, and then proceed to re-construct the message in the correct order, displaying the MT message as one complete message. However, it is important to note that the order of the MT message part can change several times during transit, right up until the MT message part is delivered to the handset. This is due to routing technologies, load-balancing systems and re-try cycles, all of which have an impact on the delivery of the concatenated MT message. ... View more

Digital Interconnect offers two connectivity options to the Enterprise Messaging Hub: Hypertext Transport Protocol (HTTP) Short Message Peer-to-Peer (SMPP). The differences between the two protocols are discussed in the article SMPP vs. HTTP. In general using SMPP results in throughput of between 150-220 MTs/sec, while HTTP is closer to 50 MTs/sec.    These rates are impacted by a number of issues, including: current load on the input server connectivity between the customer’s data centre and the Enterprise Messaging hub customer’s ability to generate message volume. There is no specific/discrete answer to the question of throughput.   Throughput to US and Canada Operators   Digital Intereconnect scales throughput to Operators based on historical and projected volume forecasts. Offering dedicated bandwidth is under consideration.   ... View more

Depending on the country and operator, multiple options exist for the Transmission Path Originating Address (TPOA) setting, also known as the “From” field on the handset. Operators often use the TPOA as a means to regulate MT delivery to their subscribers.   Typically in countries where only the sender pays for messaging, there are few if any TPOA restrictions. At the other end of the spectrum, in countries where both the sender and the recipient pay (for example, the US and Canada), operators require a registered short code that adheres to a sometimes exhaustive list of requirements. Most of the world however falls somewhere in the middle.   The other use for long codes and short codes is to permit two-way messages with the subscriber. Short codes are country-specific while long codes can be country-specific (National long code) or supported in multiple countries (International long code).   Note: For specific country availability and restrictions, refer to our SMS Country Guidelines documents and for other countries check with your Account Manager. ... View more

Question If a user turns off the Caller ID on their mobile phone and sends a MO through Digital Interconnect platform, will the MSISDN be seen in the MO?   Answer The Caller ID feature is only available in ordinary voice calls, and NOT in SMS messages. Therefore, regardless of whether the Caller ID feature is turned on or off on the mobile phone, the MSISDN will always show up in the MO.   To test this, take the following steps:   Turn Caller ID off (hidden) on you mobile phone and then call another mobile phone near you. In the display of the receiving phone it will show <unknown> or <hidden> or similar. Without changing the caller ID settings, send an MO from your phone to the receiving phone. You will see that your MSISDN (or what the phone has associated your MSISDN to) is displayed with the SMS. Note: That if you are present in the receiving phones address book, then your name will show in the display, but that is only because your phone knows who your MSISDN belongs to. ... View more

The purpose of the SMPP Interface Specification is to publish how SMS 365, enterprise service, supports and implements the SMPP protocol. The intended audience for this document is customers who want to communicate with the Application-to-Person (A2P) messaging systems provided using the SMPP protocol.  ... View more

Question What are the relative advantages and disadvantages of the SMPP and HTTP Protocols?   Answer Both these protocols have their respective advantages and disadvantages:   HTTP Advantages: Easy to implement, widely supported on a variety of platforms. Disadvantages: Limited throughput and “expensive” to add capacity, not specific to messaging, extra overhead in protocol. SMPP Advantages: High throughput, works well with “bursty” campaigns, scales up better than HTTP. Disadvantages: More difficult to implement.   The decision to use one or the other really comes down to the customer’s ability to develop the API as well as the expected campaign type. Large blasts or urgent alerts are best provisioned on SMPP accounts, while information on demand, activation code delivery or MO-originated queries work well on HTTP.   Digital Interconnect offers an API for both:   Short Message Peer-to-Peer (SMPP) - refer to the SMPP Interface Specification Hypertext Transport Protocol (HTTP) - refer to the HTTP Interface Specification. ... View more

Question How do you start or stop receiving Digital Interconnect Enterprise NOC Maintenance Notifications by e-mail?   Answer Stop receiving Enterprise NOC Maintenance Notifications by e-mail   If you want to REMOVE an individual from a Hub Account Alert list, do the following:   Check any existing internal distribution list you may have to which alerts are being received from Enterprise NOC, and if the person is listed, remove them from that list. You do not need to send a ticket to the Service Desk. If the email address is not contained in the distribution list: Raise a ticket to Service Desk, providing the Hub account details and the email address of the contact to remove. If this contact can be found, the entry will be removed from the account, and confirmation of the removal will be provided.   Start receiving Enterprise NOC Maintenance Notifications by e-mail   If you want to start receiving Enterprise NOC maintenance notifications, then send your request to the Service Desk providing the following details:   An external facing distribution email address. Note: The account to which the external facing distribution email address should be assigned must be a Customer Contact. ... View more

Wikipedia maintains a comprehensive and regularly updated list of the latest HTTP Error and Status Codes.   Therefore, for a full up-to-date list of HTTP Error or Status Codes view the HTTP Interface Specification or search for 'HTTP status codes' or 'HTTP error codes' in Wikipedia. ... View more

Question Is it possible to send EMOJI / emoticons characters?   Answer Yes, EMOJI / emoticons characters are supported as part of the UNICODE standard.   Note: This applies only to MT messages. Additionally, these characters are only be supported on select Operators that support UCS2, namely Verizon Wireless, AT&T and T-Mobile.  Sprint does not support EMOJI / emoticons characters.   Action: Ensure the data coding schema (DCS) used is UCS2, when encoding the messages and that you understand the constraints that UCS2 encoding introduces to the message and message length. See the EMOJI Wiki page for more details: https://en.wikipedia.org/wiki/Emoji. Example: Refer to the HTTP example below:   [MSISDN] List=+449876543210 [MESSAGE] binary=D83DDE03D83CDDEFD83CDDF5D83CDDEBD83CDDF7D83CDDECD83CDDE7D83DDC40 length=32 [SETUP] DCS=UCS2     ... View more

Question What is HTTP Error '403 - ERROR: Access Denied'?   Answer If you are connecting using the HTTP interface, and the connection is denied with the HTTP Error 'Error 403 - ERROR: Access Denied', then before Digital Interconnect can investigate this issue, the following information must be provided:   Hub Account (old or new) Login details Source IP Address Destination Port Number Error Message. For information on and the meaning of other HTTP Error or Status Codes check the HTTP Interface Specification or search for 'HTTP status codes' or 'HTTP error codes' in Wikipedia. ... View more

Question What is HTTP Error '401 - ERROR: Access Denied'?   Answer The HTTP 401 – Unauthorised response generally occurs when there is a problem with the credentials used or the completeness of the HTTP POST.   Actions: Please check the HTTP POST sent to the Digital Interconnect Hub, and ensure that the user details are correct. Tip: You may want to capture a TCP dump (a .pcap file) to ensure that you have full visibility of the POST being sent. If any of the user details are missing, check your application to find out why the full set of details is not present.   Ensure the application is using a POST request, and not a GET request. Check and confirm that there were no changes applied to your HTTP application or servers, which may have contributed to the HTTP 401 response. If the above checks do not show any cause for the HTTP 401 response, please raise a service request to the Digital Interconnect Service Desk, ensuring you provide the following details: Digital Interconnect Hub account details (for example, username/password, MT URL) Date/time when the issue started Any supportive documentation, for example, TCPDump, log file, screen shots detailing the response and so on. Example: From our Apache_access logs we can see the username ‘customerxxx’ is present in the first two examples which are shown as underlined in the example below, indicating a successful POST.   The HTTP 401 shows a ‘-‘ in place of the username, and therefore indicates that it was not present in the HTTP POST, therefore returning the HTTP 401 – Unauthorised response.   ### Correct Submission - HTTP 200 OK 23.32.23.32 - customerabc [24/Oct/2012:17:31:26 +0200] "POST /customerabc/customerabc.sms HTTP/1.1" 200 171 "messaging.sybase365.com" 0 99.88.77.66 - customerdef [24/Oct/2012:17:31:26 +0200] "POST /customerdef/customerdef.sms HTTP/1.1" 200 182 "messaging.sybase365.com" 0   ### HTTP 401 - Unauthorised 11.22.33.44 - - [24/Oct/2012:17:31:18 +0200] "POST /customerzzz/customerzzz.sms HTTP/1.0" 401 477 "messaging.sybase365.com" 0   Note: The entries above are amended from real examples and so the IP Address and username details are not real, and is provided for illustrative purposes only.   For information on and the meaning of other HTTP Error or Status Codes check the HTTP Interface Specification or search for 'HTTP status codes' or 'HTTP error codes' in Wikipedia.   ... View more