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 /src/mm-base-call.h | |
| 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 'src/mm-base-call.h')
| -rw-r--r-- | src/mm-base-call.h | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/src/mm-base-call.h b/src/mm-base-call.h index 02c6d72a..da31a9b9 100644 --- a/src/mm-base-call.h +++ b/src/mm-base-call.h @@ -35,9 +35,11 @@ typedef struct _MMBaseCall MMBaseCall; typedef struct _MMBaseCallClass MMBaseCallClass; typedef struct _MMBaseCallPrivate MMBaseCallPrivate; -#define MM_BASE_CALL_PATH "call-path" -#define MM_BASE_CALL_CONNECTION "call-connection" -#define MM_BASE_CALL_MODEM "call-modem" +#define MM_BASE_CALL_PATH "call-path" +#define MM_BASE_CALL_CONNECTION "call-connection" +#define MM_BASE_CALL_MODEM "call-modem" +#define MM_BASE_CALL_SUPPORTS_DIALING_TO_RINGING "call-supports-dialing-to-ringing" +#define MM_BASE_CALL_SUPPORTS_RINGING_TO_ACTIVE "call-supports-ringing-to-active" struct _MMBaseCall { MmGdbusCallSkeleton parent; |