OutOfCall error

Aleksander Morgado aleksandermj at chromium.org
Fri Feb 3 09:38:28 UTC 2023


Please next time send the output of the commands as text, not as
attachments or embedded HTML images. These messages are archived forever
and indexed by search engines, and the text in the images is not considered
by the indexing engine.

>> I'm using qmicli version 1.30.6 and can't figure out why I keep getting
>> the OutOfCall error when calling the --wds-get-current-settings command.
>> These are the modem details:
>> I'm running the cli on an armv7l Debian 11 system.
Without knowing much more, I would bet you're not
using --client-no-release-cid and --client-cid=[CID] properly, that would
be the simplest explanation.
You must use --client-no-release-cid with your --wds-start-network command,
so that the WDS client id is kept allocated. After that, every other
--wds-XX operation you run should be run with --client-cid=[CID] including
the CID value you got when using --client-no-release-cid. As soon as the
WDS client id is released, the corresponding network would be stopped, and
you would get the OutOfCall error.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20230203/fd0b52d6/attachment.htm>

More information about the libqmi-devel mailing list