SMPP
Direct APIRules
  • How to work with SMSC
    • Introduction
    • SMPP parameters
    • Supported connection types
    • Supported packet types
    • Encoding setting
    • Concatenated SMS sending
    • Tracking SMS delivery statuses
    • Reserved error codes
Powered by GitBook
On this page
  1. How to work with SMSC

Encoding setting

PreviousSupported packet typesNextConcatenated SMS sending

Last updated 2 years ago

Messages sent via the service SMSC may consist of Latin and Cyrillic letters, as well as include special characters (Russian and Latin letters with diacritical marks, letters of the Greek and other alphabets, specific punctuation marks, as well as non-printing characters). When sending messages, it is recommended to use the settings tabled below.

Text

Data coding

Encoding

Message length

Cyrillic

0x08

UTF-16ВE (big endian)

70 characters

Latin

0x00

ASCII-8

160 characters

IMPORTANT

Be careful about using the following characters in SMS:

£,¥,è,é,ù,ì,ò,Ç,Ø,ø,Å,å,Δ,Φ,Γ,Λ,Ω,Π,Ψ,Σ,Θ,Ξ,Æ,æ,ß,É,¤,¡,Ä,Ö,Ñ,Ü,§ ¿,ä,ö,ñ,ü,à,

NUL,SOH,STX,ETX,EOT,ENQ,ACK,BEL,BS,TAB,VT,SO,SI,DLE,DC1,DC2,DC3,DC4,

NAK,SYN,ETB,CAN,EM,SUB,FS,GS,RS,US,`,DEL.

Operators may not support these characters or convert messages to Unicode due to their platform or specification, thereby increasing the number of message parts charged.

⚠️