Sinch Community

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

Question The defined HTTPS URL is not receiving Delivery Notifications?   Answer The account may still be using the HTTP configuration on the account in question, therefore, the account configuration will need to be checked and corrected. Please raise a service request with Digital Interconnect to check and confirm that the correct configuration is in place for the account, ensuring you provide the full HUB account name.   ... View more

Question How do I configure the Mobile/Handset Acknowledgement notification URL on my account?   Answer The notification URL must be supplied in each HTTP POST for each MT. It is not stored in or configured on Digital Interconnect databases or servers.   Actions: Mobile Notification is configured as part of the HTTP POST using the AckReplyAddress and MobileNotification parameters as detailed in section 3.1.2, Table 4 Optional Parameters of the SMS 365, enterprise service - HTTP Interface Specification. For example:   [MSISDN] List=+19255550000   [MESSAGE] Text=Test SMS Message   [Setup] AckReplyAddress=http://127.0.0.1/ABC/MTAckReceive.aspx MobileNotification=Yes [END]   For proper function, ensure that your firewall is correctly configured to allow the notifications from Digital Interconnect IP address using either the HTTP or HTTPS ports.   Related Articles SMS 365, enterprise service - HTTP Interface Specification ... View more

The Digital Interconnect HTTP Interface Specification is intended for Content Providers (CPs) connecting into our messaging gateway for: Mobile Terminated (MT) Standard/Premium Services Mobile Originated (MO) Standard/Premium Services The HTTP interface requires CPs to develop an HTTP client (for sending MT messages), as well as an HTTP server (for receiving MO and MT message acknowledgments. Detailed explanations and samples are provided throughout the document. For additional information and support on the HTTP interface, contact your Account manager representative. ... View more

Question How do you interpret “Destination Operator” Results?   Answer Destination Operator refers to the Operator to whom Digital Interconnect attempted to send the message.   The following three conditions exist with each message lookup:   Discrete Operator A known operator in a specific country. This is the most common condition.  The Enterprise Messaging hub interpreted the number supplied by the content provider and an attempt was made to deliver the message to that operator, using a default route known to service that operator (common with International routes) or a direct connection to the operator (normal for US and Canada). Country Only An unknown operator in a known country. When looking at an invoice or Extranet, one might be puzzled to see just a country name instead of a specific operator.  For example, sending to Mexico, one would expect to see operators such as Telcel, Movistar, Iusacell, etc.  However, when the Enterprise Messaging hub can’t identify the operator, but by virtue of the country code determines the number to belong to a Mexican operator, the message is categorized as “Mexico” and a delivery attempt is made, usually via a default route to a partner aggregator.  This often happens when a subscriber provides a non-mobile number or one that’s been ported but the numbering lookup services haven’t yet been updated.   “Unknown” Unknown operator in an unknown country. In this case, the Enterprise Messaging hub was unable to ascertain a valid operator or country from the content provider-supplied phone number, marked the message “Unknown” and made no delivery attempt.  This often happens when there’s a web-based opt-in as people mistype their number.   ... View more

Question What do you do if you have not received an expected MO from Digital Interconnect?   Answer Raise a ticket with Digital Interconnect ensuring you provide the following information: the originating MSISDN the timeline the HUB account/CustomerID into which the MO message should arrive the OPERATOR from which the MO messages are not arriving (sometimes only one operator might be affected) the destination shortcode (TPDA) that the MO was sent to. Note: You will not be able to provide the 'MessageID' as you will not have received the message. ... View more