diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2018-06-14 14:58:28 +0200 |
|---|---|---|
| committer | Dan Williams <dcbw@redhat.com> | 2018-10-16 17:09:21 +0000 |
| commit | 0090124ec0d0d28fa78f5a0dd153e36584a0f171 (patch) | |
| tree | 4205e8cda1794580e160d9d5867be0262167861c /docs/reference/api/ModemManager-sections.txt | |
| parent | 7c10db26c20cd39862059e08ddd237e6eeb406d0 (diff) | |
base-call: ACTIVE after start() if detailed transitions unavailable
The most detailed call state transition flow for a new outgoing call
would be:
UNKNOWN -> DIALING -> RINGING -> ACTIVE
But, if the modem doesn't support reporting intermediate states
(e.g. DIALING or RINGING) then a successful start() should imply
getting into ACTIVE state right away.
For now, only the Huawei plugin implements the detailed transition
support, so make them configurable via call object properties.
Diffstat (limited to 'docs/reference/api/ModemManager-sections.txt')
0 files changed, 0 insertions, 0 deletions