USSD

Markatrafik · 3 Apr 2021, 09:27

I used USSD services because they are simple and convenient. But in UT (UBports) dialler-app application just hangs when calling USSD service. Does this code work at all or not yet?

As I understand it, work has been done in this direction:

phablet@ubuntu-phablet:~$ find / 2>/dev/null | grep -i -e ussd
/usr/share/ofono/scripts/initiate-ussd
/usr/share/ofono/scripts/cancel-ussd
/usr/share/ofono/scripts/send-ussd
/usr/share/dialer-app/Dialogs/UssdProgressDialog.qml
/usr/share/dialer-app/Dialogs/UssdResponseDialog.qml
/usr/share/dialer-app/Dialogs/UssdErrorDialog.qml

My phone is Xiaomi Redmi Note 7 - maybe this is the problem and USSD does not work on this particular hardware, but MMS (and SMS) works fine, but in other application...

lduboeuf · 3 Apr 2021, 12:58

don't know much about USSD, just saw a fix that have been done few months ago. Do you have logs ( dialer-app or dbus ) ?

Markatrafik · 3 Apr 2021, 14:19

@lduboeuf where can I find logs of dialer-app in the system? maybe I need to enable debugging somehow, and there is nothing useful in /var/log

Markatrafik · 3 Apr 2021, 14:42

@lduboeuf ohh... sorry, I forgot about the dbus ...

method call time=1617460602.192946 sender=:1.222 -> destination=:1.24 serial=346 path=/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_da4fb6106a7762892d7be1da4d4277f2;interface=com.canonical.Telephony.USSD; member=Initiate
string "*100#"
error time=1617460602.194065 sender=:1.24 -> destination=:1.222
error_name=org.freedesktop.Telepathy.Error.NotImplemented reply_serial=346
string "Not implemented"
method return time=1617460602.194462 sender=:1.24 -> destination=:1.222 serial=1160 reply_serial=346
method call time=1617460602.196537 sender=:1.222 -> destination=com.lomiri.hfd serial=347
path=/com/lomiri/hfd; interface=org.freedesktop.DBus.Introspectable; member=Introspect
error time=1617460602.196990 sender=org.freedesktop.DBus -> destination=:1.222
error_name=org.freedesktop.DBus.Error.ServiceUnknown reply_serial=347
string "The name com.lomiri.hfd was not provided by any .service files"
method call time=1617460602.197761 sender=:1.222 -> destination=org.freedesktop.DBus
serial=348 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',
member='NameOwnerChanged',arg0='com.lomiri.hfd'"
method call time=1617460602.198329 sender=:1.222 -> destination=org.freedesktop.DBus
serial=349 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner
string "com.lomiri.hfd"
error time=1617460602.198459 sender=org.freedesktop.DBus -> destination=:1.222
error_name=org.freedesktop.DBus.Error.NameHasNoOwner reply_serial=349
string "Could not get owner of name 'com.lomiri.hfd': no such name"
method call time=1617460602.200812 sender=:1.222 -> destination=org.freedesktop.DBus
serial=350 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch
string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',
member='NameOwnerChanged',arg0='com.lomiri.hfd'"
signal time=1617460602.359120 sender=:1.0 -> destination=(null destination)
serial=39679 path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; member=EventEmitted

lduboeuf · 4 Mar 2021, 14:48

@markatrafik you can see logs from the logviewer app, or in .cache/upstart/

Don't see much from dbus
Edit: we can see an error in dbus log. But i personally don't know where to look at Maybe someone know better ?

Markatrafik · 3 Apr 2021, 14:47

@lduboeuf no information in the ~/.cache/upstart

Connection :1.224 (uid=32011 pid=20883 comm="dbus-monitor ") became a monitor.
void ToneGenerator::playDTMFTone(uint) 10
void ToneGenerator::playDTMFTone(uint) 1
void ToneGenerator::playDTMFTone(uint) 0
void ToneGenerator::playDTMFTone(uint) 0
void ToneGenerator::playDTMFTone(uint) 11
Monitoring connection :1.224 closed.

But utility dbus-monitor say enough...

The USSD functions is not implemented yet

Markatrafik · 4 Mar 2021, 15:07

Maybe I don't understand something, but I can clearly see python scripts to onofo, for example:

phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/initiate-ussd
Usage: /usr/share/ofono/scripts/initiate-ussd [modem] <ussd-string>

also, the QML componets menu scripts for dailer-app:

phablet@ubuntu-phablet:~$ cd /usr/share/dialer-app/Dialogs/
phablet@ubuntu-phablet:/usr/share/dialer-app/Dialogs$ ls -al
total 44
drwxr-xr-x  2 root root 4096 oct 15 23:47 .
drwxr-xr-x 12 root root 4096 oct 15 23:47 ..
-rw-r--r--  1 root root 1631 oct 13 22:56 DisableFlightModeDialog.qml
-rw-r--r--  1 root root 1866 oct 13 22:56 FlightModeProgressDialog.qml
-rw-r--r--  1 root root 3347 oct 13 22:56 NoDefaultSIMCardDialog.qml
-rw-r--r--  1 root root  994 oct 13 22:56 NotificationDialog.qml
-rw-r--r--  1 root root 2380 oct 13 22:56 SetDefaultSIMCardDialog.qml
-rw-r--r--  1 root root 2529 oct 13 22:56 SimLockedDialog.qml
-rw-r--r--  1 root root 1012 oct 13 22:56 UssdErrorDialog.qml
-rw-r--r--  1 root root 1088 oct 13 22:56 UssdProgressDialog.qml
-rw-r--r--  1 root root  991 oct 13 22:56 UssdResponseDialog.qml

What is missing from the system so that I can work with my ISP's USSD dialog menu? May be from terminal using python scripts?

kugiigi · 3 Apr 2021, 14:58

USSD works fine on most of my phones (Xperia X, Nexus 5, MX4, Bq E5) so it's most likely an issue or missing implementation on your specific device model.

Markatrafik · 3 Apr 2021, 15:04

@kugiigi said in [USSD] (/post/48876):

USSD works fine on most of my phones (Xperia X, Nexus 5, MX4, Bq E5) so it's most likely an issue or missing implementation on your specific device model.

Yes, I have no luck with this equipment, the echo is such that the other side hears itself after a second, like a parrot, calls can not hear - you can miss an important call, and so the USSD at the end...
I hope this can all be fixed, or is it easier to order another machine?

Keneda · 4 Mar 2021, 15:06

@kugiigi
Works on MX4 too.

I didn't even know about USSD, just decovered this with this thread ^^
Tested #123# from orange.

lduboeuf · 3 Apr 2021, 17:06

@markatrafik humm already heard the echo issue for some devices, here ?: https://forums.ubports.com/topic/5968/caller-echo?_=1617469387193

Markatrafik · 3 Apr 2021, 18:34

This post is deleted!

Markatrafik · 4 Jun 2021, 05:22

I tried to use the onofo python scripts directly. For a one-step USSD request from the shell everything looks good, the data is output to the console:

~$ /usr/share/ofono/scripts/initiate-ussd /ril_1 "*100#"
State: idle
USSD:  Current: 235.79, Limit: 300

But if a dialog is required, the answer appears on the screen, asks you to enter the number of USSD menu item, and press the button. If I click the button, the window closes and the script crashes with the following errors:

~$ /usr/share/ofono/scripts/initiate-ussd /ril_1 "*222#"
State: idle
Traceback (most recent call last):
  File "/usr/share/ofono/scripts/initiate-ussd", line 35, in <module>
    result = ussd.Initiate(ussdstring, timeout=100)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.ofono.Error.Failed: Operation failed

So there is USSD processing in the system. Only for some reason it does not work. For example, there is no possibility to "call" a number beginning with an asterisk "*".

Is there any way to get this program code to work completely?