mirror of
https://github.com/4IceG/luci-app-sms-tool-js.git
synced 2026-04-26 03:15:59 +03:00
[GH-ISSUE #9] no SMS Messages if some of them contain From: field with special symbols #4
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/luci-app-sms-tool-js#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bam80 on GitHub (Aug 29, 2023).
Original GitHub issue: https://github.com/4IceG/luci-app-sms-tool-js/issues/9
After installing the new version, tinkering with SIM selection and rebooting the router, can't see my massages any more:
Powered by LuCI openwrt-23.05 branch (git-23.118.79121-6fb185f) / OpenWrt 23.05.0-rc2 (r23228-cd17d8df2a)
How could I diagnose this?
@bam80 commented on GitHub (Aug 29, 2023):
The messages seem are receiving because I see increasing inbox counter, just don't see the messages themselves.
@4IceG commented on GitHub (Aug 29, 2023):
There is probably some message that breaks the json structure. Show the result of the command:
sms_tool -d /dev/ttyUSB2 recv
Please note that the sms-tool package does not support all available types of messages.
@bam80 commented on GitHub (Aug 30, 2023):
Hi @4IceG, thanks for the tip.
I made a full dump of the messages, but they contain sensitive information so I can't put if here.
It was a lot of messages received since I switched the SIM, so I started to delete one by one from the end with
sms_tool, and refresh the page with the messages.The problematic massage was this:
After I deleted it, all the messages show up in your app.
The same message in RAW format:
Can we make it work for the future?
@4IceG commented on GitHub (Aug 30, 2023):
Hi @bam80 ,
Cezary is the maintainer of the sms-tool package and he will probably need the entire content of the problematic SMS sent to an e-mail.
@obsy Cezary co o tym myslisz?
@obsy commented on GitHub (Aug 30, 2023):
But - what kind of problem? Looks like normal message.
@obsy commented on GitHub (Aug 30, 2023):
@4IceG: wygląda na normalną wiadomość, bez znaków specjalnych czy innych takich.
@bam80 commented on GitHub (Aug 30, 2023):
Any way I could reproduce the problem, as long as I have all the dump?
@bam80 commented on GitHub (Aug 30, 2023):
Does the RAW contain my phone number?
If no, I could wipe only the messages with sensitive data and provide full the dump.
@obsy commented on GitHub (Aug 30, 2023):
Show me:
Change SM and /dev/ttyUSB2 as you have.
No, only sender number.
@bam80 commented on GitHub (Aug 30, 2023):
@obsy
The message actually contains some not-plain symbols, see
^QinFrom:field:Here is the hex dump:
@obsy commented on GitHub (Aug 30, 2023):
Show us json output. Probably the json is badly formatted - sender field.
@bam80 commented on GitHub (Aug 30, 2023):
@obsy as I said, I already deleted the badly formed message.
How could I reproduce the problem now?
@obsy commented on GitHub (Aug 30, 2023):
Can you get a similar message again? Or just wait until sms are not visible again and then show the result in json.
@bam80 commented on GitHub (Aug 30, 2023):
It was advertisement SMS and I see this problem for the first time. Cant take a while to show up again.
@obsy commented on GitHub (Aug 30, 2023):
ASCII char 11, vertical tab. How it should by displayed on phone? Like'
?
@bam80 commented on GitHub (Aug 30, 2023):
When I use
-s SMI see only this until I don't refresh the page with the messages again:Without
-sI see the output then, is the-snecessary and what are the variants?@obsy commented on GitHub (Aug 30, 2023):
@4IceG: o ile treść w jsonie jest eskejpowana i znaki poza zakresu są w utf'ie, o tyle sender na chwilę obecną nie. Jeżeli to wynika z tych dodatkowych znaków w senderze to trzeba pomyśleć co z tym fantem zrobić z ogóle - wycinać to czy coś innego. Bo nie pokażesz pewnie kilku liniowego sendera czy jak w/w przykładzie znaku z kodem 11 ASCII.
@obsy commented on GitHub (Aug 30, 2023):
-s SM
-s ME
-s TE
depending on modem and sim card.
@4IceG commented on GitHub (Aug 30, 2023):
@obsy , rozumiem Cezary. To wiele wyjasnia.
Ciekawe jak to rozwiazali dedykowani producenci fw, u Nas ciezko o taki nietypowy sms, więc tego nawet nie widzimy.
@bam80 commented on GitHub (Aug 30, 2023):
@obsy
-s SM|ME|TEcould probably be in the help output of the app maybe?@bam80 commented on GitHub (Aug 30, 2023):
I found an article about these messages, apparently they look like:

https://devicess.ru/prishla-sms-ot-dit_moslog-ili-dit_mos-eto-chto-znachit/
@obsy commented on GitHub (Aug 30, 2023):
Underline.
@bam80 commented on GitHub (Aug 30, 2023):
I found a way to reproduce the problem, just need to try to login to https://www.mos.ru/ and they send a SMS with code:
Here is how the json output looks like:
@obsy the
sender:field looks OK?@obsy commented on GitHub (Aug 30, 2023):
Yes.
Does luci display it or not?
@bam80 commented on GitHub (Aug 30, 2023):
Oh, no, json actually contains the same badness with ASCII 11:
@bam80 commented on GitHub (Aug 30, 2023):
No. But see my message above.
@bam80 commented on GitHub (Aug 30, 2023):
So is it a problem with
sms_toolorluci-app-sms-tool-js?@obsy commented on GitHub (Aug 30, 2023):
Ideologically - sms_tool (badly formatted json). But @4IceG - can you test does luci process such json or does it return an error?
@4IceG commented on GitHub (Aug 30, 2023):
I'm trying with this message, but LuCi is not showing anything at the moment. I'll try again.
@bam80 commented on GitHub (Aug 30, 2023):
@4IceG please note I cut off a tail of the message with code in my dump, it's meaningless anyway
@obsy commented on GitHub (Aug 30, 2023):
I need to read the specs to see if that's how it's supposed to work.
@obsy commented on GitHub (Sep 1, 2023):
@bam80 What router are you using sms-tool on?
@bam80 commented on GitHub (Sep 2, 2023):
@obsy
Modem: Quectel EP06-E
@obsy commented on GitHub (Sep 2, 2023):
Mipsel. Try this version: https://dl.eko.one.pl/test/sms-tool_2022-03-21-f07699ab-1_mipsel_24kc.ipk
(uninstall old, install new, or unpack and replace binary in /usr/bin)
@obsy commented on GitHub (Sep 6, 2023):
@bam80 : have you tested new sms_tool?
@bam80 commented on GitHub (Sep 6, 2023):
I will soon
@bam80 commented on GitHub (Sep 21, 2023):
@obsy Hey hey, sorry for a long wait, I was really busy with other things.
But eventually I was in need to read my SMS and faced this problem again so I decided it's time now)
Thıs version solved a problem, could you publish the changes and make a bugfix release please?
I would like to see it in openwrt packages feed also.
Thank you very much both of you!
@obsy commented on GitHub (Sep 21, 2023):
Updated. You can do PR in package repo.
@bam80 commented on GitHub (Sep 25, 2023):
The fix itself:
github.com/obsy/sms_tool@1b6ca03284packages PR:
https://github.com/openwrt/packages/pull/22204
@bam80 commented on GitHub (Oct 3, 2023):
Could we please close it when the fix land in the owrt packages repo instead?
Obviously, most of the users come from pre-built owrt and don't build stuff themselves..
@bam80 commented on GitHub (Oct 3, 2023):
Thank you. I'll chase to fix it on owrt package repo side when I have chance.
Will keep you informed here.
@helllamer commented on GitHub (Jan 3, 2024):
@bam80 Looks like it is not merged since 25.09.2023, MR still in WiP status. Do you need any help?
@bam80 commented on GitHub (Jan 3, 2024):
@helllamer it's just rebasing stuff on my side, the patch must be trivial - I would appreciate if somebody finish it.
Let me know if you need me for that, thanks.