You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
my idee is that the client should automatically convert the charset (ie UTF-8 with only GSM 03.38 chars) to GSM 03.38 or if need (Unicode with other chars as in GSM 03.38) to USC2 charset.
If the message lenght is longer than 160/70(USC2) than split to messages with 153/63 chars.
CSMS_8BIT_UDH = 153 chars in concat mode
CSMS_16BIT_TAGS = 152 chars in concat mode
CSMS_PAYLOAD = for me unknown; not possible to test with my partners
my idee is that the client should automatically convert the charset (ie UTF-8 with only GSM 03.38 chars) to GSM 03.38 or if need (Unicode with other chars as in GSM 03.38) to USC2 charset.
If the message lenght is longer than 160/70(USC2) than split to messages with 153/63 chars.
with header support like in php-smpp
https://github.com/onlinecity/php-smpp/blob/master/smppclient.class.php#L280
CSMS_8BIT_UDH = 153 chars in concat mode
CSMS_16BIT_TAGS = 152 chars in concat mode
CSMS_PAYLOAD = for me unknown; not possible to test with my partners
some encodings in smpp (5.0)
https://github.com/farhadi/node-smpp/blob/master/lib/defs.js#L227
example like:
apihard@791e1b1
The text was updated successfully, but these errors were encountered: