Skip to content

Conversation

@alexislg2
Copy link
Contributor

Hey I made 4 modifications (in 4 different commits)
-Use of GSM alphabet instead of ASCII for 7bit decryption. This allows in particular to use characters such as 'é', 'à', etc... with 7 bit
-bug fix: Remove the last character (undefined) when receiving 16bit message
-Use of GSM alphabet instead of ASCII for 7bit encryption
-The 7-bit messages concatenation was not working for me (only 16bit was working). And this is because you need to make padding after the header, as explained here http://en.wikipedia.org/wiki/Concatenated_SMS I recoded the encode7Bits to make it work

I tested all the 4 of them

@alexislg2
Copy link
Contributor Author

Sorry, I need to fix a small bug

@alexislg2
Copy link
Contributor Author

bug fixed

@alexislg2
Copy link
Contributor Author

A last sing I want to fix:

  • the length of the message is different in 7bit if the message contains escaped character such as '€'. This has an impact on the length header and also on the message splitting

for example if my message is 160 characters long and includes the € sign, then it is in fact 161 characters. So we need 2 separated messages. I'll fix this soon

The encoding is separated in 2 steps now:
* first: transform text into array of number, depending of the encoding
* second: convert the array of number into a HEXA string
@alexislg2
Copy link
Contributor Author

Everything is working fine Now. I don't plan new commits

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

Successfully merging this pull request may close these issues.

1 participant