-
Notifications
You must be signed in to change notification settings - Fork 35
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
Incorrect segment counting #39
Comments
I don't believe that the segment calculator is incorrect. For GSM-7 encoding, Paraphrasing a bit:
|
Checked out this string using https://messente.com/documentation/tools/sms-length-calculator |
I spotted a similar issue to this one: #18.
When providing a message like this one:
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
Segment calculator shows it's 3 segments.
It's 153 scalars counted as 306 characters. That's 2142 bits for characters + 96 bits for 2 headers. That should add up to 2238 bits so still within 2 segments.
But when adding the last character of this string another header is added and the message takes up 2286 bits: 3 segments.
There are other calculators that show this as 2 segments (https://sakari.io/sms-length-calculator/)
But when sending the message on Twillio it is sent as 3 segments. So I have been wondering which is correct and what is causing this behaviour.
The text was updated successfully, but these errors were encountered: