To SMS Technical Guide

Transcription

1 To SMS Technical Guide

2 Table of Content 1 Document information Purpose Change history Release notes Contact 3 2 Introduction Overview Main features fields supported 5 3 Flow Description sent to customer SMS received by end-user received back 7 4 Sending SMS to end-user Checking Authorization Checking the field To field Subject field Body field Importance Others fields Quota checking Acknowledgment SMS sending Receiving SMS Delivery Report 11 5 Receiving SMS from end-users 12 6 Tips for managing s Receiving Duplicate error message when sending only one Managing automatically notifications 14 7 Characters accepted 16 To SMS - Technical Guide 2

3 1 Document information 1.1 Purpose Purpose This document describes the usage of the To SMS product. The latest version of the document is available at the address Change history Changes R e l e a s e d a t e C h a n g e s I n i t i a l v e r s i o n 1.3 Release notes Versions Initial version 1.4 Contact Contact The Ring Ring Company 2/F, Culliganlaan 1831 Diegem (Belgium) Coordination@ringring.be Tel (During Business Hours) : +32 (0) Tel (Outside Business hours) : (only accessible from Belgium) To SMS - Technical Guide 3

4 2 Introduction 2.1 Overview Overview ToSMS enables sending and receiving SMS messages through the use of standard messages. messages are converted to SMS and vice-versa on the RingRing Cloud platform allowing the use of SMS services without any development or integration. All software or cloud based clients are supported including (gmail, Yahoo, Outlook 365, ) Features 2.2 Main features The ToSMS is able to : - Convert to SMS - Convert SMS to - Keep track of conversation (Reply) - Work with HTML and plain text - Secure the access to individual into the organization - Protect against duplicate sending. - Provide Acknowledgment when sending - Provide Delivery notification report The side is used by the customer and the SMS side is used by the end-user with who you want to communicate. The conversation can start with an from your company converted to a SMS sent to an end-user. Or it can be a SMS sent by an end-user converted to an and sent to your company. To SMS - Technical Guide 4

5 2.3 fields supported s have different fields that are used by the ToSMS to handle them. Field Used by Description ToSMS To Yes The To field is converted into a mobile phone number that will receive the SMS Cc Yes The Cc field is converted into a mobile phone number that will receive the SMS Bcc Yes The Bcc field is converted into a mobile phone number that will receive the SMS Subject Yes Subject is not mandatory and modified by the ToSMS to add the Re: (Reply) in front of the text and add a Process ID and the end of the text. Body Yes The Body is converted to a SMS message, note that the text <END> will mak the end of the messag Importance Yes The Priority indicates if a message considered as duplicate should be sent (High Importance) or not (Normal or Low Importance). Attachment No The attachment are not processed and discarded in this version of 2SMS Sensitivity No Sensitivity is not used Reply-To No Reply-to is not used in this version To SMS - Technical Guide 5

6 3 Flow Description The flow consists of 2 directions from To SMS and from SMS to . The conversation can start from an converted to SMS or vice-versa. To allow a conversation starting from a SMS, you need a dedicated shortcode or a shared shortcode with a keyword. Please contact your Sales representative for more details sent to customer You need to end you message with the tag <END> The text after the <END> is not sent by SMS but is preserved in the communication! This will avoid sending your signature by SMS. To SMS - Technical Guide 6

7 3.2 SMS received by end-user The End-user is receiving a SMS and is able to send back a reply received back The SMS reply of the end-user is converted into an . You can continue the conversation by replying to the (don t forget the <END> tag). To SMS - Technical Guide 7

8 4 Sending SMS to end-user 4.1 Checking Authorization When sending an to To SMS, the originator ( from address) of this is checked for authorization. Authorization is specific per customer and this authorization can be set per individual address or for the complete domain name. You receive a specific message in the case you don t have the permission to use the ToSMS. 4.2 Checking the The sent to To SMS is validated before its conversion to an SMS. s are handled every minute field To The destination of the (the To field) is controlled and verified, only the following addresses are allowed phonenumber@sms .be where phonenumber is the international mobile phone number of the SMS destination without the leading 0 or the plus sign. Example: @sms .be field Subject The subject is not used by ToSMS and your text is preserved during the conversation allowing you to organize your conversation in your client. The subject is modified by the ToSMS to add the necessary Re: text in front of the subject to mark an as replied and an process ID is added at the end of the subject allowing a quick reference to individual message. To SMS - Technical Guide 8

9 field Body The body is the SMS message to be sent, SMS is a short message compared to an . To avoid issue related to the sending of long through SMS some limitations are set to avoid such kind of issues. The message to be sent by SMS must be delimited by the keyword <END>. <END> will mark the end of the SMS message and the rest of the after <END> is not sent by SMS but is kept in the conversation. <END> is not mandatory if the body contains only one sentence. The maximum length of the body is fixed to 800 normal characters (5 SMS) field Importance This field can be used to override the duplicate protection. The duplicate protection avoids sending duplicate messages (with the same destination and body) within one hour. In this case, an is sent back to you alerting that a message is already processed in the last hour for this mobile phone number with the same content. In the case you want to avoid this protection, you can set the Importance to High and then all messages will be set without checking past messages Others fields Fields Reply-to, attachments, sensitivity are not used in this version of To SMS Quota checking ToSMS is checking the quota of SMS allowed per month depending on the customer subscription. Alerts are already sent when 90% of the SMS quota is reached. Please contact your Sales Representative to increase the Quota by changing your subscription if necessary. To SMS - Technical Guide 9

10 4.3 Acknowledgment A CK Once the is received, ToSMS will send back a Success or Error Acknowledgment directly to the sender or the configured in the ToSMS product. s to acknowledge or alert customers are sent by the address mailprocessor@sms .be. 4.4 SMS sending Sending SMS After the is validated, ToSMS will send a SMS to the destination number, the originator of this SMS will be the assigned 4-digits shortcode (bulk or dedicated shortcode depending on your account). To SMS - Technical Guide 10

11 4.5 Receiving SMS Delivery Report Once the is delivered to the mobile device, a Delivery Report (DLR) will be sent out by mail-processor@sms .be allowing you to know if the message was delivered or not. Please refer to for more information about SMS Message Status. To SMS - Technical Guide 11

12 5 Receiving SMS from end-users End-users can send a SMS to a 4-digits shortcode (bulk or dedicated shortcode depending on your account) that will be converted into an and sent to your address. In the case you sent a message to the end-user using a bulk or shared shortcode, the SMS reply (sent by the end-user) must be sent within a 72 hours period to be routed to the customer address. You will not receive SMS from end-user after this 24-hours period. A solution consists of taking a dedicated shortcode where all incoming messages will be sent to your addresses. The received in the customer s inbox will have the following parameters: From : the mobile phone number of the end-user who sent the SMS in the format phonenumber@sms .be To: the address destination of the customer. Subject: In the case of a conversation started by the customer (who sent an converted into a SMS for the end-user) the subject is modified by adding the text Re: in front of the text and adding an identifier of message at the end of the subject text. If the conversation wasn t initiated by the customer (in a case where the enduser started the conversation by sending a SMS) then the subject message is filled with the default text: New SMS Message. This default subject line can be changed by whatever you want. Body: contains the SMS message of the end-user. By replying to this , you will send a SMS message to the end-user To SMS - Technical Guide 12

13 6 Tips for managing s 6.1 Receiving Duplicate error message when sending only one If you receive back an with the error Duplicate Error Message and if you are sure to just have sent ONLY ONE then your client Outlook is probably the cause of the problem. In this case, by setting the High Importance flag to true you will force sending multiple SMS to the same phone number! Solution 1 : Remove the plugin Outlook connector if you don t use it. This solution will solve the problem and you will be sure to not send duplicate message if you set the High Importance flag to true. Solution 2: Create a rule in your client to move or delete the Duplicate Error Message. This solution will not solve the problem if you set the flag High Importance to true. To SMS - Technical Guide 13

14 6.2 Managing automatically notifications Managing notifications (ACK, NACK, ERROR messages ) can be automated with rules directly from your client. Here is a simple example of creating a rule to move automatically messages to a specific folder. In Outlook, go to Rules and Create Rule. Select from mail-processor@sms .be and select with specific word in the subject or in body. Click on specific words To SMS - Technical Guide 14

15 Type the string you want to search (example: Duplicate Message Detected ) Click Add then click OK. Select now the action to perform for this rule. Here we decide to delete the . Click Finish and you are done. More information on managing rules in outlook can be found on the web site of Microsoft: To SMS - Technical Guide 15

16 7 Characters accepted Supported characters Only the character set GSM 7-bit default alphabet and extension table of 3GPP TS / GSM is supported. All other characters in the are removed or replaced with the closest character. 3GPP TS / GSM x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xa xb xc x D xe xf $ è é ù ì Ò Ç LF Ø ø CR Å å 1x Δ _ Φ Γ Λ Ω Π Ψ Σ Θ Ξ ESC Æ æ ß É 2x SP! " # % & ' ( ) * +, -. / 3x : ; < = >? 4x A B C D E F G H I J K L M N O 5x P Q R S T U V W X Y Z Ä Ö Ñ Ü 6x a b c d e f g H i j k l m n o 7x p q r s t u v w X y z ä ö ñ ü à 1B 0x 1B 1x ^ 1B 2x { } \ 1B 3x [ ~ ] 1B 4x 1B 5x 1B 6x 1B 7x FF To SMS - Technical Guide 16