aboutsummaryrefslogtreecommitdiff
path: root/examples/modem-watcher-python
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2019-07-12 10:45:46 +0200
committerDan Williams <dcbw@redhat.com>2019-07-15 04:43:54 +0000
commit22afa8a74e959642e664806cf8d8e6bd896bfa2f (patch)
treebcd8fa6358aaa938738e707e681955f940cb5ace /examples/modem-watcher-python
parent417c0ed882847f2258d2c07aa210b4ad2abc5ac5 (diff)
shared-qmi: monitor attempt after NAS initiate network register
The QMI NAS Initiate Network Register command will return a successful response when the request to register is received and accepted by the module, but this does not mean the requested registration has been completed yet. This issue was making e.g. manual registration attempts to a forbidden network report success right away, even if the actual registration would end up failing. In order to avoid that, the QMI based network registration relies on receiving QMI NAS Serving System indications after QMI NAS Initiate Network Register replies. As soon as we get a non-searching registration state in the indication, we'll report the operation as successful. Note that the 3GPP interface logic is anyway in charge of checking if the specific request was successful or not, no need to do that explicitly in the QMI implementation.
Diffstat (limited to 'examples/modem-watcher-python')
0 files changed, 0 insertions, 0 deletions