mirror of
https://github.com/4IceG/luci-app-sms-tool-js.git
synced 2026-04-26 11:25:58 +03:00
[GH-ISSUE #29] USSD response-reply sessions #23
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#23
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 @stefand on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/4IceG/luci-app-sms-tool-js/issues/29
For Telcos in Africa it is quite common to have a deeply nested menu behind USSD codes. sms_tool (and mmclI) can handle that on the command line, but I noticed luci-app-sms-tool-js interprets every entry as a new session and complains that the replies are malformed. These USSD sessions offer a lot of services, with purchasing data bundles being the most important one for routers.
To give an example of what this looks like on the command line:
It might be enough to relax the input validation, although it would be nice to have some information from sms_tool if it is going to interpret the ussd command as a follow-up response or a new command. (mmcli by comparison has --3gpp-ussd-initiate, --3gpp-ussd-respond and --3gpp-ussd-status)
@4IceG commented on GitHub (May 16, 2025):
Hi,
I only maintain the user interface for LuCI, not for the sms-tool package itself. New version of package will include the missing functionality.
@stefand commented on GitHub (May 17, 2025):
I can confirm that it works. Thanks a lot!
I ran into issues with stale files in my browser cache, so if anyone else updates and still gets the old behavior: Clear your browser cache.
@4IceG commented on GitHub (May 23, 2025):
I have updated the package, the USSD menu should be even easier to use.
@stefand commented on GitHub (May 24, 2025):
Thanks, the newest-first order of longer sessions is indeed helpful