Re: AW: QMI protocol error (14): 'CallFailed''
On Mon, 2021-03-01 at 11:11 +, Federico Murciano wrote: > The same happens if I try with: > > sudo qmi-network /dev/cdc-wdm0 start > > Profile at '/etc/qmi-network.conf' not found... > Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data- > format '... > Device link layer protocol retrieved: raw-ip > Getting expected data format with 'qmicli -d /dev/cdc-wdm0 --get- > expected-data-format'... > Expected link layer protocol retrieved: raw-ip > Device and kernel link layer protocol match: raw-ip > Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network= > --client-no-release-cid '... > error: couldn't start network: QMI protocol error (14): 'CallFailed' > call end reason (1): generic-unspecified > verbose call end reason (2,208): [internal] pdn-ipv4-call-disallowed This says you can't use IPv4 on this APN. Try setting the IP family to v6 only, or v4v6 (maybe?). sudo mmcli -m 1 --simple-connect="apn=internet.telekom,ip-type=ipv6" sudo START_NETWORK_ARGS="ip-type=6" qmi-network or something like that. In the mmcli case earlier, it the verbose error code was "verbose call end reason (2,241): [internal] interface-in-use- config-match" which might indicate that the connection was already active but using different settings than you asked MM to use. Dan > Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 17) > error: network start failed, no packet data handle > Clearing state at /tmp/qmi-network-state-cdc-wdm0... > edge2@dai-edge2:~$ > > > Federico Murciano > > B.Sc. Telecommunications Engineer > federico.murci...@dai-labor.de > Tel. +49 (0) 30/314 -74 025 > Future in touch > DAI-Labor > Technische Universität Berlin > Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14 Ernst- > Reuter-Platz 7 > 10587 Berlin, Germany > > http://www.dai-labor.de/ > DAI-Labor - Distributed Artificial Intelligence Laboratory Chief > Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak > > > Von: ModemManager-devel < > modemmanager-devel-boun...@lists.freedesktop.org> im Auftrag von > Federico Murciano > Gesendet: Montag, 1. März 2021 11:20 > An: Giacinto Cifelli > Cc: modemmanager-devel@lists.freedesktop.org > Betreff: AW: QMI protocol error (14): 'CallFailed'' > > Hello everyone, > > Could someone help me with what is going wrong? I am still having > problems when I try to connect the Modem. I follow the steps: > > Sudo mmcli -i 0 -- > pin= > Enter PIN SIM > Sudo mmcli -m 1 --enable -- > timeout=120 > Enable Modem > sudo mmcli -m 1 --simple- > connect="apn=internet.telekom" > Connect modem to APN > > After this step I always get the error: > > error: couldn't connect the modem: > 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI > protocol error (14): 'CallFailed'' > > It looks like it is connecting right but then this error happens and > I dont achieve to set the status = Connected, even if I have already > an IP from the operator: > > at+cgpaddr=1 > +CGPADDR: > 1,"10.174.67.152,42.1.5.152.177.132.73.56.0.1.0.0.134.113.2.203" > > I get the following logs from ModemManager: > > ModemManager[485235]: [1614593449.789165] [modem0] user > request to connect modem > ModemManager[485235]: [1614593449.789225] [modem0] simple > connect started... > ModemManager[485235]: [1614593449.789242] [modem0] PIN: > unspecified > ModemManager[485235]: [1614593449.789255] [modem0] > operator ID: unspecified > ModemManager[485235]: [1614593449.789267] [modem0] allowed > roaming: yes > ModemManager[485235]: [1614593449.789277] [modem0] APN: > internet.telekom > ModemManager[485235]: [1614593449.789289] [modem0] IP > family: unspecified > ModemManager[485235]: [1614593449.789300] [modem0] allowed > authentication: unspecified > ModemManager[485235]: [1614593449.789310] [modem0] User: > unspecified > ModemManager[485235]: [1614593449.789320] [modem0] > Password: unspecified > ModemManager[485235]: [1614593449.789330] [modem0] simple > connect state (4/8): wait to get fully enabled > ModemManager[485235]: [1614593449.789356] [modem0] simple > connect state (5/8): register > ModemManager[485235]: [1614593449.789379] [modem0] already > registered automatically in network '26201', automatic registration > not launched... > ModemManager[485235]: [1614593449.789400] [modem0] si
AW: QMI protocol error (14): 'CallFailed''
The same happens if I try with: sudo qmi-network /dev/cdc-wdm0 start Profile at '/etc/qmi-network.conf' not found... Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data-format '... Device link layer protocol retrieved: raw-ip Getting expected data format with 'qmicli -d /dev/cdc-wdm0 --get-expected-data-format'... Expected link layer protocol retrieved: raw-ip Device and kernel link layer protocol match: raw-ip Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network= --client-no-release-cid '... error: couldn't start network: QMI protocol error (14): 'CallFailed' call end reason (1): generic-unspecified verbose call end reason (2,208): [internal] pdn-ipv4-call-disallowed Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 17) error: network start failed, no packet data handle Clearing state at /tmp/qmi-network-state-cdc-wdm0... edge2@dai-edge2:~$ Federico Murciano B.Sc. Telecommunications Engineer federico.murci...@dai-labor.de Tel. +49 (0) 30/314 -74 025 Future in touch DAI-Labor Technische Universität Berlin Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14 Ernst-Reuter-Platz 7 10587 Berlin, Germany http://www.dai-labor.de/ DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak Von: ModemManager-devel im Auftrag von Federico Murciano Gesendet: Montag, 1. März 2021 11:20 An: Giacinto Cifelli Cc: modemmanager-devel@lists.freedesktop.org Betreff: AW: QMI protocol error (14): 'CallFailed'' Hello everyone, Could someone help me with what is going wrong? I am still having problems when I try to connect the Modem. I follow the steps: Sudo mmcli -i 0 --pin= Enter PIN SIM Sudo mmcli -m 1 --enable --timeout=120 Enable Modem sudo mmcli -m 1 --simple-connect="apn=internet.telekom" Connect modem to APN After this step I always get the error: error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI protocol error (14): 'CallFailed'' It looks like it is connecting right but then this error happens and I dont achieve to set the status = Connected, even if I have already an IP from the operator: at+cgpaddr=1 +CGPADDR: 1,"10.174.67.152,42.1.5.152.177.132.73.56.0.1.0.0.134.113.2.203" I get the following logs from ModemManager: ModemManager[485235]: [1614593449.789165] [modem0] user request to connect modem ModemManager[485235]: [1614593449.789225] [modem0] simple connect started... ModemManager[485235]: [1614593449.789242] [modem0]PIN: unspecified ModemManager[485235]: [1614593449.789255] [modem0]operator ID: unspecified ModemManager[485235]: [1614593449.789267] [modem0]allowed roaming: yes ModemManager[485235]: [1614593449.789277] [modem0]APN: internet.telekom ModemManager[485235]: [1614593449.789289] [modem0]IP family: unspecified ModemManager[485235]: [1614593449.789300] [modem0]allowed authentication: unspecified ModemManager[485235]: [1614593449.789310] [modem0]User: unspecified ModemManager[485235]: [1614593449.789320] [modem0]Password: unspecified ModemManager[485235]: [1614593449.789330] [modem0] simple connect state (4/8): wait to get fully enabled ModemManager[485235]: [1614593449.789356] [modem0] simple connect state (5/8): register ModemManager[485235]: [1614593449.789379] [modem0] already registered automatically in network '26201', automatic registration not launched... ModemManager[485235]: [1614593449.789400] [modem0] simple connect state (6/8): bearer ModemManager[485235]: [1614593449.789414] [modem0] creating new bearer... ModemManager[485235]: [1614593449.789602] [modem0] simple connect state (7/8): connect ModemManager[485235]: [1614593449.789673] [modem0/bearer2] connecting... ModemManager[485235]: [1614593449.789698] [modem0] state changed (registered -> connecting) ModemManager[485235]: [1614593449.789855] [modem0/bearer2] launching connection with QMI port (cdc-wdm0) and data port (wwan0) ModemManager[485235]: [1614593449.789887] [modem0/bearer2] no specific IP family requested, defaulting to ipv4 ModemManager[485235]: [1614593449.789913] [modem0/bearer2] defaulting to use static IP method ModemManager[485235]: [1614593449.789927] [modem0/bearer2] running IPv4 connection setup ModemManager[485235]: [/dev/cdc-wdm0] Sent message... <<<<<< RAW: ModemManager[485235]: [/dev/cdc-wdm0] Received generic response (translated)... <<<<<< QMUX: <<<<<< length = 19 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< clie
AW: QMI protocol error (14): 'CallFailed''
Hello everyone, Could someone help me with what is going wrong? I am still having problems when I try to connect the Modem. I follow the steps: Sudo mmcli -i 0 --pin= Enter PIN SIM Sudo mmcli -m 1 --enable --timeout=120 Enable Modem sudo mmcli -m 1 --simple-connect="apn=internet.telekom" Connect modem to APN After this step I always get the error: error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI protocol error (14): 'CallFailed'' It looks like it is connecting right but then this error happens and I dont achieve to set the status = Connected, even if I have already an IP from the operator: at+cgpaddr=1 +CGPADDR: 1,"10.174.67.152,42.1.5.152.177.132.73.56.0.1.0.0.134.113.2.203" I get the following logs from ModemManager: ModemManager[485235]: [1614593449.789165] [modem0] user request to connect modem ModemManager[485235]: [1614593449.789225] [modem0] simple connect started... ModemManager[485235]: [1614593449.789242] [modem0]PIN: unspecified ModemManager[485235]: [1614593449.789255] [modem0]operator ID: unspecified ModemManager[485235]: [1614593449.789267] [modem0]allowed roaming: yes ModemManager[485235]: [1614593449.789277] [modem0]APN: internet.telekom ModemManager[485235]: [1614593449.789289] [modem0]IP family: unspecified ModemManager[485235]: [1614593449.789300] [modem0]allowed authentication: unspecified ModemManager[485235]: [1614593449.789310] [modem0]User: unspecified ModemManager[485235]: [1614593449.789320] [modem0]Password: unspecified ModemManager[485235]: [1614593449.789330] [modem0] simple connect state (4/8): wait to get fully enabled ModemManager[485235]: [1614593449.789356] [modem0] simple connect state (5/8): register ModemManager[485235]: [1614593449.789379] [modem0] already registered automatically in network '26201', automatic registration not launched... ModemManager[485235]: [1614593449.789400] [modem0] simple connect state (6/8): bearer ModemManager[485235]: [1614593449.789414] [modem0] creating new bearer... ModemManager[485235]: [1614593449.789602] [modem0] simple connect state (7/8): connect ModemManager[485235]: [1614593449.789673] [modem0/bearer2] connecting... ModemManager[485235]: [1614593449.789698] [modem0] state changed (registered -> connecting) ModemManager[485235]: [1614593449.789855] [modem0/bearer2] launching connection with QMI port (cdc-wdm0) and data port (wwan0) ModemManager[485235]: [1614593449.789887] [modem0/bearer2] no specific IP family requested, defaulting to ipv4 ModemManager[485235]: [1614593449.789913] [modem0/bearer2] defaulting to use static IP method ModemManager[485235]: [1614593449.789927] [modem0/bearer2] running IPv4 connection setup ModemManager[485235]: [/dev/cdc-wdm0] Sent message... <<<<<< RAW: ModemManager[485235]: [/dev/cdc-wdm0] Received generic response (translated)... <<<<<< QMUX: <<<<<< length = 19 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 19 <<<<<< QMI: <<<<<< flags = "response" <<<<<< transaction = 4 <<<<<< tlv_length = 7 <<<<<< message = "Set Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Result" (0x02) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = SUCCESS ModemManager[485235]: [1614593449.806193] [modem0/bearer2] starting IPv4 connection... ModemManager[485235]: [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 32 <<<<<< data = 01:1F:00:00:01:13:00:05:00:20:00:13:00:14:10:00:69:6E:74:65:72:6E:65:74:2E:74:65:6C:65:6B:6F:6D ModemManager[485235]: [/dev/cdc-wdm0] Sent generic request (translated)... <<<<<< QMUX: <<<<<< length = 31 <<<<<< flags = 0x00 <<<<<< service = "wds" <<<<<< client = 19 <<<<<< QMI: <<<<<< flags = "none" <<<<<< transaction = 5 <<<<<< tlv_length = 19 <<<<<< message = "Start Network" (0x0020) <<<<<< TLV: <<<<<< type = "APN" (0x14) <<<<<< length = 16 <<<<<&
AW: QMI protocol error (14): 'CallFailed''
Hi Giacinto, I will try that again! -- Federico Murciano B.Sc. Telecommunications Engineer federico.murci...@dai-labor.de Tel. +49 (0) 30/314 -74 025 Future in touch DAI-Labor Technische Universität Berlin Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14 Ernst-Reuter-Platz 7 10587 Berlin, Germany http://www.dai-labor.de/ DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak Von: ModemManager-devel im Auftrag von Giacinto Cifelli Gesendet: Samstag, 27. Februar 2021 18:42 An: Federico Murciano Cc: modemmanager-devel@lists.freedesktop.org Betreff: Re: QMI protocol error (14): 'CallFailed'' Hi Federico, On Sat, Feb 27, 2021 at 6:16 PM Federico Murciano wrote: > > > Hardware: > Quectel > RG500QEA_VH > firmware revision: RG500QEAAAR11A03M4G according to the brochure it might support VoLTE. I think the normal profile for t-mobile uses CID #2 for the combined attach (and not CID #1). Try to set this CID #2 empty or also with internet.telekom, and then it might work. Otherwise I have no other ideas :( > > System: > device: /sys/devices/pci:00/:00:14.0/usb2/2-2 > drivers: qmi_wwan, option > plugin: quectel > primary port: cdc-wdm0 > ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps), wwan0 (net) > > The result to lsusb -t is: > > edge2@dai-edge2:~$ lsusb -t > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M > |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 1, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 2, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 3, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 4, Class=Vendor Specific Class, Driver=qmi_wwan, > 5000M > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M the drivers seem all ok, the device is mapped correctly. Regards, Giacinto ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: QMI protocol error (14): 'CallFailed''
Hi Giacinto, Thanks for your reply. My modem is: Hardware: Quectel RG500QEA_VH firmware revision: RG500QEAAAR11A03M4G System: device: /sys/devices/pci:00/:00:14.0/usb2/2-2 drivers: qmi_wwan, option plugin: quectel primary port: cdc-wdm0 ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps), wwan0 (net) The result to lsusb -t is: edge2@dai-edge2:~$ lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=option, 5000M |__ Port 2: Dev 6, If 1, Class=Vendor Specific Class, Driver=option, 5000M |__ Port 2: Dev 6, If 2, Class=Vendor Specific Class, Driver=option, 5000M |__ Port 2: Dev 6, If 3, Class=Vendor Specific Class, Driver=option, 5000M |__ Port 2: Dev 6, If 4, Class=Vendor Specific Class, Driver=qmi_wwan, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M -- Federico Murciano B.Sc. Telecommunications Engineer federico.murci...@dai-labor.de Tel. +49 (0) 30/314 -74 025 Future in touch DAI-Labor Technische Universität Berlin Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14 Ernst-Reuter-Platz 7 10587 Berlin, Germany http://www.dai-labor.de/ DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak Von: Giacinto Cifelli Gesendet: Freitag, 26. Februar 2021 17:13 An: Federico Murciano Cc: modemmanager-devel@lists.freedesktop.org Betreff: Re: QMI protocol error (14): 'CallFailed'' Hi Federico, On Fri, Feb 26, 2021 at 4:52 PM Federico Murciano wrote: > > Hello everyone, > > > since a while I have been experimenting this problem when I try to connect my > modem to the APN. It was working for a long time till a upgraded the firmware > and after that it always appear so I cant use ModemManager to connect the > modem. I just tried upgrading to ModemManager1.16 but it seems to be the same > (Also upgraded qmi and mbim to the last stable releases in > https://www.freedesktop.org/software)<https://www.freedesktop.org/software>? > > > Could someone give me a hint? Thanks. The error is the following: > > > sudo mmcli -m 0 --simple-connect="apn=internet.telekom" > > error: couldn't connect the modem: > 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI protocol > error (14): 'CallFailed'' > what is your modem and can you give the "lsusb -t" result for your device? Regards, Giacinto ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: QMI protocol error (14): 'CallFailed''
Hi Federico, On Sat, Feb 27, 2021 at 6:16 PM Federico Murciano wrote: > > > Hardware: > Quectel > RG500QEA_VH > firmware revision: RG500QEAAAR11A03M4G according to the brochure it might support VoLTE. I think the normal profile for t-mobile uses CID #2 for the combined attach (and not CID #1). Try to set this CID #2 empty or also with internet.telekom, and then it might work. Otherwise I have no other ideas :( > > System: > device: /sys/devices/pci:00/:00:14.0/usb2/2-2 > drivers: qmi_wwan, option > plugin: quectel > primary port: cdc-wdm0 > ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps), wwan0 (net) > > The result to lsusb -t is: > > edge2@dai-edge2:~$ lsusb -t > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M > |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 1, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 2, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 3, Class=Vendor Specific Class, Driver=option, 5000M > |__ Port 2: Dev 6, If 4, Class=Vendor Specific Class, Driver=qmi_wwan, > 5000M > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M the drivers seem all ok, the device is mapped correctly. Regards, Giacinto ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: QMI protocol error (14): 'CallFailed''
Hi Federico, On Fri, Feb 26, 2021 at 4:52 PM Federico Murciano wrote: > > Hello everyone, > > > since a while I have been experimenting this problem when I try to connect my > modem to the APN. It was working for a long time till a upgraded the firmware > and after that it always appear so I cant use ModemManager to connect the > modem. I just tried upgrading to ModemManager1.16 but it seems to be the same > (Also upgraded qmi and mbim to the last stable releases in > https://www.freedesktop.org/software)<https://www.freedesktop.org/software>? > > > Could someone give me a hint? Thanks. The error is the following: > > > sudo mmcli -m 0 --simple-connect="apn=internet.telekom" > > error: couldn't connect the modem: > 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI protocol > error (14): 'CallFailed'' > what is your modem and can you give the "lsusb -t" result for your device? Regards, Giacinto ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
