Beruflich Dokumente
Kultur Dokumente
TABLE OF CONTENTS
1 INTRODUCTION ............................................................................................................................... 5
2 SENDING SMTP MESSAGES .......................................................................................................... 5
2.1 MSISDN Section ............................................................................................................................... 5
2.1.1 List ..................................................................................................................................................... 5
2.2 Message Section .............................................................................................................................. 5
2.2.1 Text .................................................................................................................................................... 6
2.2.1.1 Latin character set ............................................................................................................................. 6
2.2.1.2 Chinese character set ........................................................................................................................ 6
2.2.2 Binary ................................................................................................................................................. 6
2.2.3 Length ................................................................................................................................................ 6
2.3 Setup Section ................................................................................................................................... 7
2.3.1 Class .................................................................................................................................................. 7
2.3.2 2.3.2 DCS (Data Coding Scheme) .................................................................................................... 7
2.3.3 PID (Protocol Identifier) ..................................................................................................................... 7
2.3.4 MobileNotification .............................................................................................................................. 7
2.3.5 MailAckType ...................................................................................................................................... 7
2.3.6 ValidityPeriod ..................................................................................................................................... 8
2.3.6.1 Coding:............................................................................................................................................... 8
2.3.7 DestinationPort .................................................................................................................................. 8
2.3.8 OriginatorPort .................................................................................................................................... 9
3 DELIVERY NOTIFICATIONS .......................................................................................................... 10
3.1 Delivery Notifications Returned by the SMTP Interface ............................................................ 10
3.1.1 What is a Temporary Positive Notification Status?.......................................................................... 13
3.1.2 What is a Final Positive Notification Status? ................................................................................... 13
3.1.3 What is a Temporary Negative Notification Status? ........................................................................ 13
3.1.4 What is a Final Negative Notification Status?.................................................................................. 13
3.1.5 What is a Retriable Status? ............................................................................................................. 13
4 RECEIVING SMTP MESSAGES..................................................................................................... 14
4.1 Message Format ............................................................................................................................ 14
4.1.1 SERVICE Section ............................................................................................................................ 14
4.1.2 MSISDN Section .............................................................................................................................. 14
4.1.3 Message Section ............................................................................................................................. 14
4.1.4 Parameters Section ......................................................................................................................... 14
4.1.4.1 DCS (Data Coding Scheme)............................................................................................................ 14
4.1.4.2 ReceivedTime .................................................................................................................................. 14
4.1.4.3 Coding:............................................................................................................................................. 14
5 APPENDIX A: GSM DEFAULT ALPHABET .................................................................................. 15
6 APPENDIX B: ISO-8859-1 TO GSM 3.38 ALPHABET TRANSLATION ....................................... 16
7 APPENDIX C: CREATING BINARY CONTENT ............................................................................ 27
7.1 Ringtone Format ............................................................................................................................ 27
7.1.1 Ringtone Creation ............................................................................................................................ 27
7.1.2 RTTL ................................................................................................................................................ 28
7.1.3 MIDI ................................................................................................................................................. 28
7.1.4 Mail Transfer Format ....................................................................................................................... 28
7.1.5 Ports................................................................................................................................................. 28
7.2 Operator Logo Format ................................................................................................................... 28
7.2.1 Format Coding ................................................................................................................................. 29
7.2.2 Ports................................................................................................................................................. 29
2
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
3
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
IMPORTANT NOTICE:
The information in this document is subject to change without notice and should not be construed as a
commitment by SAP. SAP assumes no responsibility for any errors that may appear in this document.
4
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
1 INTRODUCTION
The SAP SMS 365, enterprise service, SMTP interface is intended for Content Providers (CPs) connecting
into SAP messaging gateway for:
[MSISDN]
List=
[MESSAGE]
Text=
Binary=
Length=
[SETUP]
Class=
DCS=
PID=
MobileNotification=
MailAckType=
ValidityPeriod=
DestinationPort=
OriginatorPort=
[END]
Note: The SMTP message must be sent in plain-text format. An HTML email will not be allowed by the mail
server.
2.1.1 List
The MSISDN section contains the phone number(s) of the recipient(s) of the short message. The phone
number(s) shall be given in international format (i.e., “+” followed by the international country code phone
number). Phone numbers are separated by commas. The maximum number of phone numbers that can be
specified in a single request is 200. To achieve optimal performance, we recommend that you specify up to
20 phone numbers per request.
Example:
[MSISDN]
List=+44777123123,+39789432445
Note: This field is mandatory. No spaces are allowed between the comma and the phone number.
5
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
2.2.1 Text
This field specifies the text that will be sent to a mobile phone. This field is mandatory if you send a text
message, and in this case the “Binary” field should not be present. Two character sets are accepted: Latin
and Chinese (see below).
All the characters defined in the ISO-8859-1 format and not permitted by the GSM 3.38 characters will be
transformed as described in Appendix B - ISO-8859-1 to GSM 3.38 alphabet translation.
Use the specific marker <LF> to insert the line feed character. The use of the <CR> (carriage return) is not
recommended, as most handsets are incompatible with this feature. The list of permitted characters is shown
in Appendix A - GSM Default Alphabet.
Example:
[MESSAGE]
Text=This is a text message. <LF> Courtesy of SAP.
Note: In this example, the text following the <LF> marker will be displayed on a new line regardless of the
width of the handset's display.
Example:
[MESSAGE]
Text=¬¬¬¬
[SETUP]
DCS=BIG5
2.2.2 Binary
This field contains the binary data to be submitted, such as ringtones or logos. The maximum length is 512
bytes (i.e., 1,024 ASCII characters, spaces being omitted). Each hexadecimal value of the binary data shall
be encoded in ASCII code in order to allow the correct transfer over the Internet (see example below). This
field can also contain a Chinese message (UCS2 binary data encoded in ASCII). In this case, the DCS field
must be set to UCS2.
2.2.3 Length
The length is mandatory when binary data is submitted and is only used in this case. The length indicated is
the size of the binary data before encoding (i.e., the number of bytes).
Example:
[MESSAGE]
Binary=024A3A4000
Length=5
Note: In this example, each four-bit word of the original message is encoded in ASCII before being sent.
6
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
[SETUP]
DCS=UCS2
Note: For Chinese messages, the DCS field must be set to UCS2. For other binary messages, the DCS will
be automatically set to 8b.
2.3.1 Class
This field defines the class of the short message to be sent. The following are the possible values:
0: Class 0. The message will be displayed immediately on the handset, but will be erased after the first
keypad entry.
1: Class 1. The message will be displayed on the screen or stored in the SIM card, depending on the
handset.
2: Class 2. The message will be stored in the SIM card of the handset. Usually, the user will be notified with
a beep and/or an icon on the screen. This is the default value.
The Data Coding Scheme values are described in GSM 03.38 [1].
2.3.4 MobileNotification
This field indicates whether a delivery notification from the handset is requested or not. The handset delivery
information is operator dependent. The possible values are Yes or No. The default value is No. See section
4 below for the set of delivery notifications returned by the SAP365 messaging gateway.
2.3.5 MailAckType
This field indicates the level of reporting that SAP will send back to the originator of the incoming message.
The following values are allowed:
Order: When this option is set, SAP will only acknowledge the receipt of the message by giving an order
identifier and the number of messages generated. This is the default value.
Message: When this option is set, SAP will return a delivery notification acknowledging the message was:
• Delivered to the operator’s SMS-C
• Delivered to the user/handset (where supported by the destination operator)
• Failed delivery
The table below summarizes the results obtained depending on the two notification options.
7
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
2.3.6 ValidityPeriod
Each short message submitted to SAP is assigned a Validity Period setting the maximum time that the short
message is retained in SAP’s network and/or in the network of the corresponding wireless operator. Failure
to deliver the short message successfully within the short message lifetime (if the subscriber is out of
coverage for instance) leads to those messages being purged.
Setting specific short message Validity Periods is important for many SMS-based applications. For example,
a daily short message informing you of a stock quotation at the end of the day would have a 24-hour Validity
Period. In this case, the information is not necessarily relevant when received a day after having been sent.
The validity period defined when sending an SMTP message to SAP is independent of the maximum validity
period allowed on each specific wireless network. The validity period is counted from the moment SAP
receives the message.
2.3.6.1 Coding:
ValidityPeriod=n [w|d|h|m]
Where:
n stands for the number of units
w stands for week
d stands for day
h stands for hour
m stands for minute
Example:
ValidityPeriod=2w ; Two weeks
ValidityPeriod=3d ; Three days
ValidityPeriod=10m ; Ten Minutes
2.3.7 DestinationPort
This field contains the receiving port used for specific applications such as Smart Messaging. This field is
mandatory when binary data is submitted and only used in this case. The hexadecimal value is sent.
Example:
DestinationPort=1581 ; Nokia Ringtones
8
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
2.3.8 OriginatorPort
This field contains the sending port used for specific applications like Smart Messaging. This field is
mandatory when binary data are submitted and only used in this case. The hexadecimal value is sent.
Example:
OriginatorPort=1581; Nokia Ringtones
9
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
3 DELIVERY NOTIFICATIONS
Delivery Notifications are message acknowledgments sent from the SAP network to customers. When
delivering messages through our network, customers can request to receive the following three levels of
acknowledgment: SAP Ack, SMS-C Ack, and Handset Ack. For unsuccessful delivery attempts, SAP will
return a negative acknowledgment (NACK) outlining the failure reason.
Customer
Notification Notification Notification Message Sent Notification
Receives
Status Code Indicates to Customer Retriable?
(Example)
Temporary Positive
Final Positive
10
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Customer
Notification Notification Notification Message Sent Notification
Receives
Status Code Indicates to Customer Retriable?
(Example)
Temporary Negative
Final Negative
11
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Customer
Notification Notification Notification Message Sent Notification
Receives
Status Code Indicates to Customer Retriable?
(Example)
12
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Customer
Notification Notification Notification Message Sent Notification
Receives
Status Code Indicates to Customer Retriable?
(Example)
13
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Example:
[MSISDN]
Phone=+44777123123
The specific markers <CR> (carriage return) and <LF> (line feed) are used to insert the special characters.
4.1.4.2 ReceivedTime
This field contains the reception date and time of the short message by SAP's network.
4.1.4.3 Coding:
ReceivedTime=ddd, dd mm yyyy hh:mm:ss +GMT
Where
ddd stands for day (Mon)
dd stands for day
mm stands for month
yyyy stands for year
hh stands for hour
mm stands for minute
14
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Example:
ReceivedTime= Wed, 3 Jul 2001 20:37:19 +0100
@ SP 0 i P ¿ p
£ ! 1 A Q a q
$ “ 2 B R b r
¥ # 3 C S c s
è ¤ 4 D T d t
é % 5 E U e u
ù & 6 F V f v
ì ‘ 7 G W g w
ò ( 8 H X h x
(1)
) 9 I Y i y
Ç
LF * : J Z j z
Ø + ; K Ä k ä
ø , < L Ö l ö
CR - = M Ñ m ñ
Å . > N Ü n ü
å / ? O § o à
(1) This character is uppercase. The lowercase version of this character is not accepted by the GSM
3.38 specification.
15
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
16
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
17
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
\ 092 5c Backslash /
18
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
_ 095 5f Underscore -
19
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
~ 126 7e Tilde -
€ 128 80 (unassigned) E
20
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Ž 142 8e (unassigned) Z
21
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
ž 158 9e (unassigned) z
Ÿ 159 9f (unassigned) Y
¢ 162 a2 Cent c
© 169 a9 Copyright C
22
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
µ 181 b5 mu Space
À 192 c0 A Grave A
Á 193 c1 A Acute A
 194 c2 A Circumflex A
à 195 c3 A Tilde A
23
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
È 200 c8 E Grave E
Ê 202 ca E Circumflex E
Ë 203 cb E Diaeresis E
Ì 204 cc I Grave I
Í 205 cd I Acute I
Î 206 ce I Circumflex I
Ï 207 cf I Diaeresis I
Ò 210 d2 O Grave O
Ó 211 d3 O Acute O
Ô 212 d4 O Circumflex O
Õ 213 d5 O Tilde O
Ù 217 d9 U Grave U
Ú 218 da U Acute U
Û 219 db U Circumflex U
24
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
Ý 221 dd Y Acute Y
á 225 e1 a Acute a
â 226 e2 a Circumflex a
ã 227 e3 a Tilde a
ç 231 e7 c Cedilla Ç
ê 234 ea e Circumflex e
ë 235 eb e Diaeresis e
í 237 ed i Acute i
î 238 ee i Circumflex i
ï 239 ef i Diaeresis i
25
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
ó 243 f3 o Acute o
ô 244 f4 o Circumflex o
õ 245 f5 o Tilde o
÷ 247 f7 Division /
ú 250 fa u Acute u
ý 253 fd y Acute y
ÿ 255 ff y Diaeresis y
26
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
024A3A51D195CDD008001B205505906105605585505485408208499000
The first 3 bytes code the smart messaging ringtones command information:
• 02 stands for 2 command parts
• 4A stands for the first command part: ringtone programming
• 3A stands for the second command part: sound
The subsequent few bytes encode the song title (name of the .ott file), while the remaining bytes encode the
ringtone content as follows:
27
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
10000 <beats per minute> 160 (i.e. length of 1/4 note = 0,38 sec.)
7.1.2 RTTL
If the RTTL format is being used as the source format. The file will need to be converted to the MIDI format.
7.1.3 MIDI
The MIDI file needs to be converted to an OTA file before being sent over SMS. Nokia PC Composer found
in Nokia Data Suite 3.0 includes a MIDI-to-OTA converter.
Note: Thirty-second notes from a MIDI file are replaced by eighteen-second notes in the OTA file. The tempo
of the music may also be modified.
To test the resulting ringtone with different mobile phones, use the phone’s serial cable or infrared link and
the Data Suite compatible with the target phone. This allows you to test the ringtone quality or length without
actually sending it over SMS.
If variations are noticed between MIDI and OTA files, you can modify either of them using the Nokia PC
Composer music editor.
7.1.5 Ports
For this application, both the originating port and destination port values are 1581. The length value depends
on the length of the ringtone.
28
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
4E4C4D20010000480E0100000000000000000000000000000000000000000000000000000000000000038
0000000000000001C4000000000000003E0200000000001FFFC0020018000000600000010024000000000
000010044000000000000010183000000000000010E0300000000000000F00100000000000000000100000
0000000000001000
The first six bytes relate to the NLM coding. These bytes are removed by the LOGOTOASCII utility. The
subsequent bytes form the PDU of the OTA bitmap. Inside this PDU, the first 4 bytes (the blue text above)
contain bitmap data information.
7.2.2 Ports
For this application, both the originating port and destination port values are 1582. The length value is
always 133.
4E4C4D20010000480E0100000000000000000000000000000000000000000000000000000000000000038
0000000000000001C4000000000000003E0200000000001FFFC0020018000000600000010024000000000
000010044000000000000010183000000000000010E0300000000000000F00100000000000000000100000
0000000000001000
The first six bytes provide the NLM coding. These bytes are removed by LOGOTOASCII utility.
The subsequent bytes form the PDU of the OTA bitmap. Inside this PDU, the four first bytes (the blue text
above) contain bitmap data information.
The first byte ("00") is the info-field of the smart messaging.
The second byte ("48"), meaning 72 in decimal, is the width of the bitmap.
The third byte ("0E"), meaning 12 in decimal, is the height of the bitmap.
A caller group logo bitmap is always 72*12 pixels.
The fourth byte is the depth of the bitmap (the number of gray scales).
All subsequent bytes form the OTA bitmap data.
No other bytes need to be added in front of the OTA PDU. The overall PDU is therefore the following:
00480E01000000000000000000000000000000000000000000000000000000000000000380000000000000
001C4000000000000003E0200000000001FFFC00200180000006000000100240000000000000100440000
29
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
00000000010183000000000000010E0300000000000000F001000000000000000001000000000000000001
000
7.2.4 Ports
For this application, both the originating port and destination port values are 1583. The length value is
always 130.
30
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
00000000000000000000000000000000000000000000000000820105000000000000820101000000000000
C60101000000000000C639E53924E4800000AA4515452414800000AA45157D54F4800000924515415514
8000009245154489130000008239E53888F200000000000000000200000000000000000C000
The GMS version is the first byte.
The three following bytes encode the first GMS item (i.e., the text) noted in red.
The ASCII coded text follows.
After the text, is the GMS header (composed of three bytes noted in red) of the picture.
Finally the 256 bytes of the picture itself appear at the end of the message.
7.3.3 Ports
For this application, both the originating port and destination port values are 158A.
BEGIN:VCARD
N:<surname firstname>
TEL:+<international phone number>
END:VCARD
For example :
BEGIN:VCARD
N:SAP Mobile Services
TEL:+1555123456
END:VCARD
This message must be translated in hexadecimal ASCII format and forms the PDU to be sent. For this
application, both the originating port and destination port values are 00E2.
BEGIN: VCALENDAR
VERSION:1.0
BEGIN:EVENT
DESCRIPTION:<text>
DTSTART:<date>T<time>
DTEND: <date>T<time>
AALARM: <date>T<time>;;;
END:VEVENT
END:VCALENDAR
For example :
BEGIN:VCALENDAR
VERSION:1.0
BEGIN:EVENT
DESCRIPTION:SAP Mobile Services meeting
DTSTART:20000906T090000
DTEND:20000906T120000
AALARM:20000906T084500;;;
END:VEVENT
END:VCALENDAR
This message must be translated in hexadecimal ASCII format and forms the PDU to be sent.
31
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
For this application, both the originating port and destination port values are 00E4.
7.6 TTML
TTML specifies downlink messages (from server to mobile) and uplink messages (from mobile to server).
Concatenation of downlink messages is supported, but uplink TTML requests must be sent with only one
SM.
.>Question
.>*choice_1
.>*choice_2
.>*choice_x
<<question with digit answer
<question with alphanumeric entry
><Rmessage appearing for sending form
Note: the ><R symbol used in the last line is for sending back the form.
In the following example, the customer is given several choices from which (s)he needs to make a selection
before sending the form back.
..Example in TTML
Have time for a few questions ?
This message just has to be converted in hexadecimal ASCII format and forms the PDU to be sent.For this
application, both the originating port and destination port values are 15CC.
32
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
6010 6010 Bad format for field DCS in section SETUP. check syntax of DCS field
6011 6011 Bad format for field PID in section SETUP. check syntax of PID field
6012 6012 Bad format for field MobileNotify in section SETUP. check syntax of MobileNotify
field
6013 6013 Bad format for field MailAckType in section SETUP. check syntax of MailAckType
field
6017 6017 Bad format or missing mandatory value for field Text Text or Binary field must be
in section MESSAGE. fulfilled
6018 6018 Bad format or missing mandatory value for field List in List field must be fulfilled
section MSISDN.
6019 6019 Bad format for field List in section MSISDN. check syntax of MSISDN field
(coma separated)
601A 601A Bad format for field Class in section SETUP. check syntax of Class field
6024 6024 Bad format for field ValidityPeriod in section SETUP. check syntax of ValidityPeriod
field
6026 6026 Bad format or missing mandatory value for field DestinationPort= empty field
DestinationPort in section SETUP.
33
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
6028 6028 Bad format or missing mandatory value for field must have Length when Binary
Length in section MESSAGE. field
6029 6029 Bad format or missing mandatory value for field binary message must be
Binary in section MESSAGE. prepended by Binary=
602A 602A The message contained an invalid character. check the message compared
to GSM 3.38 table
602B 602B The message contained a an invalid binary string compare the length of binary
length. field and Length=
6100 6100 Error when processing the message. check message syntax
8000 8000 Server currently unavailable to process your message send an email to
please try later. service.desk@sybase.com
34
SAP SMS 365, ENTERPRISE EDITION - SMTP INTERFACE
9 REFERENCES
[1] GSM TS 03.38: Digital cellular telecommunications system (Phase 2+); Alphabets and language-specific
information (GSM 03.38 version 5.5.1)
[2] GSM TS 03.40: Digital cellular telecommunications system (Phase 2+); Technical realization of the Short
Message Service (SMS); Point-to-Point (PP) (GSM 03.40 version 5.7.1)
[3] Smart Messaging Specification, Revision 2.0.0 – Nokia Mobile Phones Ltd
[4] Graphic Message Service Syntax, Revision 1.0.0 – Nokia Mobile Phones Ltd
Nokia FAQ: http://www.forum.nokia.com/
35
www.sap.com
These materials are provided by SAP AG and its affiliated companies (“SAP
Group”) for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in
Germany and other countries.
Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.