LinuxQuestions.org - [SOLVED] USSD not working after upgrading to Ubuntu 14.04 from Modem Manager Gui

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - USSD not working after upgrading to Ubuntu 14.04 from Modem Manager Gui (https://www.linuxquestions.org/questions/linux-networking-3/ussd-not-working-after-upgrading-to-ubuntu-14-04-from-modem-manager-gui-4175601105/)

Subhraman Sarkar

03-05-2017 04:33 AM

USSD not working after upgrading to Ubuntu 14.04 from Modem Manager Gui

I use Modem Manger GUI for executing USSD commands for getting information about balance, validity etc. It worked fine in Ubuntu 12.04 Precise. However after upgrading to Ubuntu 14.04 Trusty, I found that when I send USSD command, I get a timeout error, but SMS, network traffic and all other tabs in Modem Manager GUI work fine. The Internet is working as well. Only somehow the ussd commands are not working. I have tried increasing the timeout (upto 40 sec), changing backends as posted here, and using PrepaidManager and mmcli commands from terminal. However, all show the same timeout error.
Modem : ZTE corporation MF190 (from ModemManger GUI).

Edit :
Here are the results of mmcli commands. I found the commands here.

Code:

subhraman ~:~> mmcli -m 0 -e

successfully enabled the modem

subhraman ~:~> mmcli -m 0 --3gpp-ussd-initiate="*111#"

error: couldn't initiate USSD session: 'Timeout was reached'

nini09

03-07-2017 03:10 PM

Upload following command output

Listing modems/finding the index number of a modem
mmcli -L

Assume modem index 0.

See the status of a modem:
mmcli -m 0

Subhraman Sarkar

03-07-2017 09:31 PM

Results of commands

Here are the results of the commands :

Code:

subhraman ~:~> mmcli -L



Found 1 modems:

        /org/freedesktop/ModemManager1/Modem/2 [ZTE CORPORATION] MF190



subhraman ~:~> mmcli -m 2



/org/freedesktop/ModemManager1/Modem/2 (device id '07350007b69421f7f889190f8a46057d1d9b466a')

  -------------------------

  Hardware |  manufacturer: 'ZTE CORPORATION'

          |          model: 'MF190'

          |      revision: 'BD_RELIANCEMF190V1.0.0B01'

          |      supported: 'gsm-umts'

          |        current: 'gsm-umts'

          |  equipment id: '911133906942575'

  -------------------------

  System  |        device: '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3'

          |        drivers: 'option1'

          |        plugin: 'ZTE'

          |  primary port: 'ttyUSB2'

          |          ports: 'ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at)'

  -------------------------

  Numbers  |          own : 'unknown'

  -------------------------

  Status  |          lock: 'none'

          | unlock retries: 'sim-pin (3), sim-puk (10)'

          |          state: 'connected'

          |    power state: 'on'

          |    access tech: 'edge'

          | signal quality: '100' (recent)

  -------------------------

  Modes    |      supported: 'allowed: 2g; preferred: none

          |                  allowed: 3g; preferred: none

          |                  allowed: 2g, 3g; preferred: none

          |                  allowed: 2g, 3g; preferred: 2g

          |                  allowed: 2g, 3g; preferred: 3g'

          |        current: 'allowed: any; preferred: none'

  -------------------------

  Bands    |      supported: 'unknown'

          |        current: 'unknown'

  -------------------------

  IP      |      supported: 'ipv4, ipv6'

  -------------------------

  3GPP    |          imei: '911133906942575'

          |  enabled locks: 'none'

          |    operator id: '40567'

          |  operator name: 'Vodafone W.B. & A&N'

          |  registration: 'home'

  -------------------------

  SIM      |          path: '/org/freedesktop/ModemManager1/SIM/2'

(Looks like the modem is in slot 2 this time.)

nini09

03-08-2017 02:38 PM

We need test whether Modem Manager can talk to the Modem.

1)Set logging level to maximum
mmcli -G DEBUG

2)You can check /var/log/messages for the message exchange during command is executed.
mmcli -m 2 --command="E0"

Subhraman Sarkar

03-08-2017 08:59 PM

Here is the output :

Code:

subhraman ~:~> mmcli -G DEBUG

Successfully set logging level

subhraman ~:~> mmcli -m 2 --command="E0"

error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot send AT command to modem: operation only allowed in debug mode

I am unable find any file or folder named "messages" in /var/log. Can I use dmesg instead? Look at the contents of my /var/log :

Code:

subhraman ~:~> ls /var/log

alternatives.log        dmesg.4.gz        mail.err

alternatives.log.1      dpkg.log          mail.log

alternatives.log.10.gz  dpkg.log.1        news

alternatives.log.11.gz  dpkg.log.10.gz    oem-config.log

alternatives.log.12.gz  dpkg.log.11.gz    pm-powersave.log

alternatives.log.2.gz  dpkg.log.12.gz    pm-powersave.log.1

alternatives.log.3.gz  dpkg.log.2.gz    pm-powersave.log.2.gz

alternatives.log.4.gz  dpkg.log.3.gz    pm-powersave.log.3.gz

alternatives.log.5.gz  dpkg.log.4.gz    pm-powersave.log.4.gz

alternatives.log.6.gz  dpkg.log.5.gz    pm-suspend.log

alternatives.log.7.gz  dpkg.log.6.gz    pm-suspend.log.1

alternatives.log.8.gz  dpkg.log.7.gz    pm-suspend.log.2.gz

alternatives.log.9.gz  dpkg.log.8.gz    pm-suspend.log.3.gz

apport.log              dpkg.log.9.gz    pm-suspend.log.4.gz

apport.log.1            faillog          pycentral.log

apport.log.2.gz        fontconfig.log    samba

apport.log.3.gz        fsck              speech-dispatcher

apport.log.4.gz        gdm              syslog

apport.log.5.gz        gpu-manager.log  syslog.1

apport.log.6.gz        hp                syslog.2.gz

apport.log.7.gz        installer        syslog.3.gz

apt                    jockey.log        syslog.4.gz

auth.log                jockey.log.1      syslog.5.gz

auth.log.1              jockey.log.10.gz  syslog.6.gz

auth.log.2.gz          jockey.log.2.gz  syslog.7.gz

auth.log.3.gz          jockey.log.3.gz  udev

auth.log.4.gz          jockey.log.4.gz  ufw.log

boot                    jockey.log.5.gz  unattended-upgrades

boot.log                jockey.log.6.gz  upstart

bootstrap.log          jockey.log.7.gz  wader.log

btmp                    jockey.log.8.gz  wtmp

btmp.1                  jockey.log.9.gz  wtmp.1

clamav                  kdm.log          wvdialconf.log

ConsoleKit              kdm.log.1        Xorg.0.log

cups                    kern.log          Xorg.0.log.old

dist-upgrade            kern.log.1        Xorg.1.log

dmesg                  kern.log.2.gz    Xorg.1.log.old

dmesg.0                kern.log.3.gz    Xorg.2.log

dmesg.1.gz              kern.log.4.gz    Xorg.2.log.old

dmesg.2.gz              lastlog

dmesg.3.gz              lightdm

nini09

03-09-2017 02:19 PM

Quote:

Can I use dmesg instead?

Yes, dmesg is good. It will dump /var/log/messages.

Subhraman Sarkar

03-09-2017 08:58 PM

Here is the last few lines of my dmesg after executing the command :

Code:

[  16.576775] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[  16.629129] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=0117

[  16.629135] usb 1-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=4

[  16.629137] usb 1-1.3: Product: ZTE WCDMA Technologies MSM

[  16.629139] usb 1-1.3: Manufacturer: ZTE,Incorporated

[  16.629141] usb 1-1.3: SerialNumber: MF1900ZTED010000

[  16.715105] type=1400 audit(1489112706.713:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=788 comm="apparmor_parser"

[  16.859643] usb-storage 1-1.3:1.3: USB Mass Storage device detected

[  16.859687] scsi8 : usb-storage 1-1.3:1.3

[  16.914313] usbcore: registered new interface driver usbserial

[  16.914331] usbcore: registered new interface driver usbserial_generic

[  16.914339] usbserial: USB Serial support registered for generic

[  17.129872] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory

[  17.171047] usbcore: registered new interface driver option

[  17.171331] usbserial: USB Serial support registered for GSM modem (1-port)

[  17.171572] option 1-1.3:1.0: GSM modem (1-port) converter detected

[  17.171763] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB0

[  17.171791] option 1-1.3:1.1: GSM modem (1-port) converter detected

[  17.171887] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB1

[  17.171910] option 1-1.3:1.2: GSM modem (1-port) converter detected

[  17.172015] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2

Also, can you please tell me why the following AT command that you gave me fails?

Code:

subhraman ~:~> mmcli -v -m 0 --command="E0"

[10 Mar 2017, 08:22:26] [Debug] ModemManager process found at ':1.3'

[10 Mar 2017, 08:22:26] [Debug] Assuming '0' is the modem index

[10 Mar 2017, 08:22:26] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/0'



[10 Mar 2017, 08:22:26] [Debug] Synchronously sending command to modem (29 seconds timeout)...

error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot send AT command to modem: operation only allowed in debug mode'

I have added the -v option for getting verbose output.

nini09

03-10-2017 03:18 PM

Quote:

Also, can you please tell me why the following AT command that you gave me fails?

Your primary port is ttyUSB2 at USB 1-1.3. Modem manager try to use this. But your command tell manager use modem 0 instead of 2.

I don't see any error after you execute mmcli -m 2 --command="E0".

You can use -v option to debug following command.
1)mmcli -m 2 --command="E0"
2)mmcli -m 2 --3gpp-ussd-initiate="*111#" -- I change -m 0 to -m 2.

Subhraman Sarkar

03-11-2017 07:17 AM

I am still getting the timeout error.

Code:

subhraman ~:~> mmcli -v -G DEBUG

[11 Mar 2017, 18:39:02] [Debug] ModemManager process found at ':1.3'

Successfully set logging level

subhraman ~:~> mmcli -v -m 2 --command="E0"

[11 Mar 2017, 18:39:08] [Debug] ModemManager process found at ':1.3'

[11 Mar 2017, 18:39:08] [Debug] Assuming '2' is the modem index

[11 Mar 2017, 18:39:08] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'



[11 Mar 2017, 18:39:08] [Debug] Synchronously sending command to modem (29 seconds timeout)...

error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot send AT command to modem: operation only allowed in debug mode'

subhraman ~:~> mmcli -v -m 2 -e

[11 Mar 2017, 18:39:15] [Debug] ModemManager process found at ':1.3'

[11 Mar 2017, 18:39:15] [Debug] Assuming '2' is the modem index

[11 Mar 2017, 18:39:15] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'



[11 Mar 2017, 18:39:15] [Debug] Synchronously enabling modem...

successfully enabled the modem

subhraman ~:~> mmcli -v -m 2 --3gpp-ussd-initiate

error: no actions specified

subhraman ~:~> mmcli -v -m 2 --3gpp-ussd-initiate="*111#"

[11 Mar 2017, 18:39:50] [Debug] Forcing request to be run asynchronously

[11 Mar 2017, 18:39:50] [Debug] Assuming '2' is the modem index

[11 Mar 2017, 18:39:50] [Debug] ModemManager process found at ':1.3'

[11 Mar 2017, 18:39:50] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'



[11 Mar 2017, 18:39:50] [Debug] Asynchronously initiating USSD session...

error: couldn't initiate USSD session: 'Timeout was reached'

What should I do next to solve this problem? Should I try
(A) Upgrading ModemManager using deb files from xenial repository or files from any other newer version.
(B) Switching to a ModemManager alternative such as Wader-core or oFono.

Can this be a problem in the modem or service provider (though I don't think this likely)?

nini09

03-13-2017 03:26 PM

You can try upgrade ModemManager. It look like ModemManager has problem. If functionality relative to AT command, it will be failure.

Subhraman Sarkar

03-18-2017 05:32 AM

Works!

I was unable to upgrade ModemManger due to dependency problems, because I already had ModemManger 1.0.0-2ubuntu1.1 version, which was the latest for trusty. However, I managed to downgrade ModemManager to version 0.6.0.0.really-0ubuntu7_amd64 and the ussd worked. I think it is probably a problem with ModemManager. What do you say about this?

nini09

03-20-2017 02:52 PM

If your ModemManger isn't able to upgrade, that means that your ModemManger is corrupted. Some module relative to ModemManger doesn't match each other.

Subhraman Sarkar

03-25-2017 05:22 AM

I have tried upgrading to ModemManager 1.4.12-1ubuntu1, but after upgrade it refuses to show my Mobile Broadband connections. It only shows Wired, Wireless and other connections, but not Mobile Broadband connections. Also,

Code:

mmcli -m 1 -e

shows a dialog notifying me that it requires the sudo password for unlocking (the dialog shows some problem with System Policy Kit). Even if I provide the password, my my Mobile Broadband connections do not show up. For now, I will be using ModemManager 0.6.
Thank you very much for your help.

Subhraman Sarkar

06-08-2017 12:38 AM

Found Bug Report

Looks like my problem has been mentioned as a bug here, https://bugs.launchpad.net/ubuntu/+s...i/+bug/1351939.
I am now using ModemManager 1.4.12-1ubuntu1_amd64 in Ubuntu 16.04. I had upgraded to Ubuntu 16.04 Xenial. But the problem still followed. Today I found a patch in the bug report. I applied it and the ussd began working. Regards.

Subhraman Sarkar

06-08-2017 12:39 AM

Found Bug Report

[Duplicate Post by mistake]

All times are GMT -5. The time now is 02:33 AM.