Sinch Community

The following external links may prove useful for finding additional information related to USA and Canada mobile best practices:   MMA Best Practices http://www.mmaglobal.com/bestpractice CWTA – Consumer Rights Wireless Code of Conduct https://crtc.gc.ca/eng/phone/mobile/code.htm   ... View more

DB52 is a SMS 365, enterprise service status code meaning ‘Rejected by operator’. DB52 is a final and intermediate status code as described in the sections below.   DB52 is used when there is no configured mapping between standard API error codes and SDI API error codes. The table below shows the SMPP Status Report code alongside the configured Sinch SDI API mapping. Any number not in the list below, for example, error codes 1, 2, 3, 4 and 5, will be mapped to DB52:   Nobill Code Configured SDI Mapping  0  '450A'  9  'DB63'  10  'DB63'  11  'DB52'  16  'DB05'  17  '4503'  18  'DB52'  40  'DBA6'  61  'DB05'  62  'DB05'  63  'DB05'  64  'DB05'  74  'DB62'  100  'DB63'  102  'DB77'  103  'DB60'  104  'DB60'  107  'DBA6'  109  'DB63'  110  'DBF2'  113  'DB77'  114  '4527'  150  'DB63'  151  '4524'  152  'DB43'  153  'DBA4'  155  'DB77'  156  'DB60'  157  'DB60'  158  'DB44'  159  'DBA3'  200  'DB63'  201  'DB63'  202  'DB63'  205  'DB63'  207  'DB77'  208  'DB60'  209  'DB60'  217  'DB62'  250  'DB05'  251  'DB05'  252  'DB05'  253  'DB05'  254  'DB05'  255  'DB05'  256  'DB05'  257  'DB05'  300  'DB48'  301  'DB48'  302  'DB48'  303  'DB48'  310  'DB48'  311  'DB48'  312  'DB48'  330  'DB23'  331  'DB23'  334  'DB23'  335  'DB23'  336  'DB23'  337  'DB23'  338  'DB23'  339  'DB23'  340  'DB23'  341  'DB23'  342  'DB23'  343  'DB23'  344  'DB23'  345  'DB23'  346  'DB23'  347  'DB23'  348  'DB23'  349  'DB52'  399  'DB52'  Any other code  'DB52'     Possible Reasons for a DB52 response There are a number of reasons why the DB52 status code is returned. Some of these along with the actions that should be taken, are detailed below:   Category Description Action Operator The MT message encountered an error while sending due to error which occurred during the sending process to operator.  DB52 may be returned in intermediate delivery receipts. The customer should retry the service after a short period to confirm if the issue persists. Operator The MT message encountered an error while sending due to error which occurred during the sending process to operator. DB52 may be returned in intermediate delivery receipts. 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.   Additional information: https://developers.sinch.com/docs/sms/smpp/error-codes/#status-reports-error-codes ... View more

DB05 is a SMS 365, enterprise service status code meaning ‘Call barred by destination operator’ or ‘Rejected by destination operator’, which indicates that the MT message could not be delivered and cannot be retried.   Possible Reasons for a DB05 response   There are a number of reasons why the DB05 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’s operator has restrictions set on the account based on the tariff and the associated terms and conditions of the account. The end user should contact their network operator, to either remove the restrictions in place, or change the contract to a tariff which permits the SMS MT services.   For example, a daily or monthly usage limit has been set End User MSISDN is barred The end user should contact their network operator, to either remove the restrictions in place. The MSISDN may be blacklisted or not permit certain SMS based transactions End User The end user does not have short code messaging enabled on their account, or is using an MVNO service of an operator that does not support messaging The end user should contact their network operator to either enable the short code messaging.   Where the operator is a MVNO, the end user should confirm that their operator has no contractual restrictions in place with the backbone operator - i.e., The operator used by the MVNO to supply its products and services to end users. Customer ALL MT traffic using a specific service number with a specific US operator have returned DB05 The customer should supply the Campaign ID when submitting the MT to Digital Interconnect, when sending traffic to US based end users. Operator Rejected By operator due to the campaign not being active on the operator network 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

4524 is a SMS 365, enterprise service status code, which indicates that the MSISDN has been blacklisted.   Reason for a 4524 response   The reasons why the 4524 status code is returned, and the actions which should be taken, are described below:   Category Description Action End User The end user’s MSISDN is not reachable due to a blacklist process. The end user should be informed that their MSISDN has been added to a blacklist.   A request to blacklist can be due to a single, problem service number sending unsolicited SMS MT messages to the end user.   If they wish to remove this blacklist, they should contact their network operator, providing the service number from which they wish to receive SMS MT messages, so that the network operator can request a whitelist.   Note: The whitelisting of any MSISDN must originate from the network operator to which the MSISDN belongs.   The network operator owns the relationship with their end user, and can advise them accordingly on any additional outcome of whitelisting the MSISDN.   Customer Many MSISDN for a single destination operator are blacklisted. Raise a ticket to the Digital Interconnect Service Desk (SD), detailing the OrderID, MSISDN, operator and date/time the MT messages were sent, so that the SD team can investigate.   ... View more

450D is a SMS 365, enterprise service status code, which indicates that the HUB Account used to send MT traffic has reached the maximum amount of messages (SMS) setting configured on the account.   Reason for a 450D response   The reason why the 450D status code is returned, and the action which should be taken, is described below:   Category Description Action Account The HUB Account used to send MT messages has contractually agreed MT Volume limits. Contact the SMS 365, enterprise service, Account Management team.   The Account Management team will provide further information regarding this response and what action is required going forward.     ... View more

450A is a SMS 365, enterprise service status code, which indicates that the mobile terminating (MT) message has been correctly delivered.   Reason for a 450A response   The reason why the 450A status code is returned, and the action which should be taken, is described below:   Category Description Action Message The MT message sent from HUB Account has been correctly delivered.   Where handset acknowledgement has been requested the 450A indicates, that the message reached the handset and returned a delivery notification. Where a 450A response has been returned, there are no actions required.   This is a confirmation of message delivery.     ... View more

DBF6 is a SMS 365, enterprise service status code (response code), which means ‘The SMS MT has been rejected by operator. User must send MO to unblock messages’. This indicates that the end-user has restrictions set on their account, until such time they opt into a service provided by the service number.   Possible Reasons for a DBF6 response   A reason why the DBF6 response is returned, along with the actions that should be taken, are detailed below:   Category Description Action End User End-user is not registered to the service The End-user has not opted into the service being provided   The End-user should use the appropriate MO opt-in process associated with the service provider, in order to receive the SMS MT messages.   ... View more

DB99 is a SMS 365, enterprise service status code, which indicates that the MSISDN is an ‘Unknown’ or ‘Ported’ Number’.   Possible Reasons for a DB99 response   There are a number of reasons why the DB99 response is returned, some of which along with the actions which should be taken, are detailed below:   Category Description Action MNP The operator is in the process of porting the MSISDN to another operator.   During this time the MSISDN is neither on the originating Operator Network, nor on the New Destination Operator Network. The porting process must complete before the MSISDN is available on the new operator network.   The time taken to complete this process varies from operator to operator and country to country. MNP The end-user has ported from one operator network to another.   The porting has not been correctly registered on the home location register (HLR), which means that the new operator is not reflected correctly against the MSISDN in the HLR.   Any ‘look-up’ against, or data extracted from, this information will return the old operator details, until the HLR is correctly updated. The end-user should be contacted to confirm their MSISDN with full international prefix and operator details.   A ticket can be raised using the collected details, to the SMS 365, enterprise service, Service Desk to verify that the lookup against this MSISDN is returning the correct operator.   The Service Desk will check and escalate the issue further as required. Customer The MSISDN provided by the end-user has been incorrectly stored in the database This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details.   The correct MSISDN details should be captured as well as the operator to which the MSISDN is registered. Customer The MSISDN is taken from a ‘paper’ form, and transcribed incorrectly due to handwriting misinterpretations. This is a data quality issue. The end-user should be contacted to confirm their MSISDN with full international prefix details, and recorded accurately. End-user The end-user providing the MSISDN does not conform to the form template, leaves out the international prefix or transposes part of the MSISDN. The end-user should ensure that the MSISDN is correctly provided in any form (online or otherwise) which captures the MSISDN.   ... View more

DB78 is a SMS 365, enterprise service status code, which means ‘Billing No Balance’. This indicates that the end-user has insufficient or no credit available on their account.   Possible Reasons for a DB78 response   There are a number of reasons why the DB78 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 has a pre-pay (top-up) account, where there is no credit remaining on the account The end-user should ensure that there is sufficient credit remaining on the account to send and receive SMS messages. End User The end user has a pre-pay (top-up) account, where there has been no credit added to the account for a prolonged period of time sufficient to keep the end user on the network.   Note: Some operators will keep an end-user (handset) connected to their network even when no credit is available on the account. This allows the end user to receive calls and use services which may be operator specific. If after a set threshold, there is no top-up, as per the contract terms and conditions associated with the pre-pay (top-up) scheme, the operator may permanently disconnect the end-user from their network, and re-cycle the MSISDN (phone number). The end-user should ensure that they top-up regularly or set up an ‘auto top-up’ on the account, ensuring that there is sufficient credit available to send and receive SMS messages and to make voice calls.   Where the account is correctly funded, the account will remain active and correctly connected to the operator network.   End User End-user has set monetary limits on their account, to ensure that their bills are manageable.   This can affect any SMS message sent from or to the end-user’s handset. The end-user can increase the limit set or remove it altogether based on the tariff and the associated terms and conditions of the account.     ... View more

DB76 is a SMS 365, enterprise service status code, which means ‘Subscriber profile does not permit the service’. This indicates that the end-user has restrictions set on their account.   Possible reasons for DB76   There are a number of reasons why the DB76 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’s operator has restrictions set on the account based on the tariff and the associated terms and conditions of the account. The end user should contact their network operator, to either remove the restrictions in place, or change the contract to a tariff which permits the SMS MT services. End User MSISDN is barred The end user should contact their network operator, to either remove the restrictions in place. The MSISDN may be blacklisted or not permit certain SMS based transactions End User End-user cannot be billed, or receive bills. Certain End-users cannot be billed as they do not have an appropriate billing profile, or require age verification before services can be rendered. In such cases the end user should contact their network operator in order to manage the services which can be subscribed to. End User End-user is not registered to the service The End-user has not opted into the service being provided, and may be subject to local opt-in processes. Operator Rejected By operator The operator may restrict services rendered to customers for a variety of reasons. The end-user should contact their network operator to understand the reason and resolve.   ... View more

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