SMS: UCS-2 concatenation with UTF16 emoticons

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Tobias Engel t-openbsc at tobias.org
Tue Nov 20 15:01:39 UTC 2018


On 20.11.18 09:04, Keith wrote:
> As Harald said, it would be good to test with a commercial core network,
> but I don't have one :)

I don't know if this helps, but I got curious and sent the
40-emoji-message from a phone connected to a commercial network and
captured it via SS7. (So no Osmocom involved.)

The pcap file is attached (addresses removed).

It looks like the 4-byte characters don't get split in half, but the
last two bytes get pushed to the next message, and all emojis are
received unharmed.

One thing I don't get though: where is it even specified that you can
use UTF-16 in SMS? Even the latest 23.038 only lists UCS-2.

-Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20181120_forwardSM_utf16_emojis.pcap
Type: application/octet-stream
Size: 744 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20181120/eb39ab93/attachment.obj>


More information about the OpenBSC mailing list