Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSM7Bit SMPP codec should be able to fallback to UCS2. #838

Open
smn opened this issue Aug 14, 2014 · 1 comment
Open

GSM7Bit SMPP codec should be able to fallback to UCS2. #838

smn opened this issue Aug 14, 2014 · 1 comment

Comments

@smn
Copy link
Member

smn commented Aug 14, 2014

This comes out of #836.

Wikipedia says:

Note that on many GSM smartphones, there's no specific preselection of the UCS-2 encoding. 
The default is to use the 7-bit encoding above, until one enters a character that is not present 
in the GSM 7-bit table (for example the lowercase c with cedilla 'ç'). In that case, the whole 
message gets reencoded using the UCS-2 encoding, and the maximum length of the message 
sent in only 1 SMS is immediately reduced to 70 code units, instead of 160.

This results in some MNOs sending us UCS2 data without changing the data coding value that's been communicated as being GSM 7bit.

Without a fall back we then wouldn't be able to decode the message and respond with an ESME_RDELIVERYFAILURE or something similar.

@smn
Copy link
Member Author

smn commented Aug 14, 2014

In practice, we've also seen MNOs send us stuff in ISO-8859-2 / latin2 when it's not available in the gsm0338 alphabet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant