Qmicli Failed 20160303085133

[Randy Yates]

Aleksander Morgado <aleksander at aleksander.es> writes:

> On Thu, Mar 3, 2016 at 3:24 PM, Randy Yates <yates at digitalsignallabs.com> wrote:
>> Hello Everyone,
>>
>> Our LE910 modem and libqmi has been connecting successfully and working at
>> multiple sites. However, we consistently failed to connect at a new site in
>> the past day or so where there was a very strong signal (4 bars on a phone).
>> Here are the log messages from the qmicli connect attempt:
>>
>> Mar  2 15:48:32 arm timed[292]: error: couldn't start network: QMI protocol
>> error (14): 'CallFailed'
>> Mar  2 15:48:32 arm timed[292]: call end reason (12): (null)
>> Mar  2 15:48:32 arm timed[292]: verbose call end reason (2,201): [internal]
>> error
>> Mar  2 15:48:32 arm timed[292]: [/dev/cdc-wdm0] Client ID not released:
>> Mar  2 15:48:32 arm timed[292]: Service: 'wds'
>> Mar  2 15:48:32 arm timed[292]: CID: '10'
>> Mar  2 15:48:32 arm timed[292]: 2016-03-02 15 48 32: system command qmicli
>> -d /dev/cdc-wdm0 --wds-start-network=["11583.mcs"] --client-no-release-cid
>> failed.
>>
>> It appears the reason is that the CID release failed. Unfortunately I am too
>> ignorant to even understand what this means. I would appreciate if someone
>> could explain this and/or the other information reported.
>
>
> What failed is the "WDS Start Network" command, the
> --client-no-release-cid is just an argument to specify how the WDS
> client id handling is done (it must not be released or otherwise the
> connection will get dropped).
>
> The call end reason with id #12 is unknown to us at the moment, at
> least in libqmi sources. Verbose call end reason 2/201 means just
> "internal" (2) and "error" (201). Yey.
>
> You say it has 4 bars of signal in the phone; but is the modem
> actually registered in the network before you try to start the
> connection? You can check that with "--nas-get-system-info" and
> "--nas-get-signal-info", for example.

Aleksander,

Thank you for your very quick response. 

I will try this as soon as I can get access. The system is at a remote
location and internet network access (i.e., ssh) is being arranged.
Hopefully some time this afternoon, EST.
-- 
Randy Yates, DSP/Embedded Firmware Developer
Digital Signal Labs
http://www.digitalsignallabs.com