[PATCH 1/2] add qmimodem/voice.h to add USSD defines
by Alexander Couzens
USSD is part of the QMI voice service.
---
drivers/qmimodem/voice.h | 62 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 62 insertions(+)
create mode 100644 drivers/qmimodem/voice.h
diff --git a/drivers/qmimodem/voice.h b/drivers/qmimodem/voice.h
new file mode 100644
index 000000000000..ca1464910914
--- /dev/null
+++ b/drivers/qmimodem/voice.h
@@ -0,0 +1,62 @@
+/*
+ *
+ * oFono - Open Source Telephony
+ *
+ * Copyright (C) 2017 by sysmocom s.f.m.c. GmbH <info(a)sysmocom.de>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ */
+
+#define QMI_VOICE_PARAM_USS_DATA 0x01
+
+#define QMI_VOICE_PARAM_ASYNC_USSD_ERROR 0x10
+#define QMI_VOICE_PARAM_ASYNC_USSD_FAILURE_CASE 0x11
+#define QMI_VOICE_PARAM_ASYNC_USSD_DATA 0x12
+
+#define QMI_VOICE_PARAM_USSD_IND_USER_ACTION 0x01
+#define QMI_VOICE_PARAM_USSD_IND_DATA 0x10
+#define QMI_VOICE_PARAM_USSD_IND_UCS2 0x11
+
+/* according to GSM TS 23.038 section 5
+ * coding group 1111, No message class, 8 bit data
+ */
+#define USSD_DCS_8BIT 0xf4
+/* coding group 01xx, Class 0, UCS2 (16 bit) */
+#define USSD_DCS_UCS2 0x48
+/* default alphabet Language unspecific */
+#define USSD_DCS_UNSPECIFIC 0x0f
+
+/* based on qmi ussd definition */
+enum qmi_ussd_dcs {
+ QMI_USSD_DCS_ASCII = 0x1,
+ QMI_USSD_DCS_8BIT,
+ QMI_USSD_DCS_UCS2,
+};
+
+enum qmi_ussd_user_required {
+ QMI_USSD_NO_USER_ACTION_REQUIRED = 0x1,
+ QMI_USSD_USER_ACTION_REQUIRED,
+};
+
+/* QMI service voice. Using an enum to prevent doublicated entries */
+enum voice_commands {
+ QMI_VOICE_CANCEL_USSD = 0x3c,
+ QMI_VOICE_USSD_RELEASE_IND = 0x3d,
+ QMI_VOICE_USSD_IND = 0x3e,
+ QMI_VOICE_SUPS_IND = 0x42,
+ QMI_VOICE_ASYNC_ORIG_USSD = 0x43,
+};
+
+struct qmi_ussd_data {
+ uint8_t dcs;
+ uint8_t length;
+ uint8_t data[0];
+} __attribute__((__packed__));
--
2.15.1
3 years, 5 months
Problem with dialstring ##21#
by Engelbert Torremans
All,
I am looking for some help in trying to fix this problem I am
experiencing when using Ofono on a RaspberryPi in "carkit/HFP mode".
Currently I can make calls (originate and terminate) and audio is fine
in combination with Bluez5 etc. also.
But I cannot disable CallForwarding via the dial-number command.
Enabling CFU via **21*destination-number# is working fine.
Trying to disable CFU via ##21# gives below error. Doing the same via
the keypad on the mobile phone works fine.
I have the impression that somwhere this ##21# is not processed
correctly but where? In ofono or in DBUS or?
Any clues?
Thanks,
Engelbert
pi@rpi-x:~/xgen/ofono $ ./dial-number BT-MAC-ADDRESS ##21#
Using modem /hfp/org/bluez/hci0/dev_BT-MAC-ADDRESS
Traceback (most recent call last):
File "./dial-number", line 40, in <module>
path = vcm.Dial(number, hide_callerid)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.ofono.Error.InvalidFormat: Argument
format is not recognized
3 years, 5 months
Vendor product extension thoughts
by Enrico Sau
Hello everyone,
I'm facing what seems to be a limit in ofono implementation.
I'm working with some Telit modems and some of them have reserved contexts
which can't be used for data connection.
Currently, from telit plugin, I can only send the "vendor" parameter to the
interface create function and there is no way to specify the product.
What you think?
Did anyone ever have to set different behaviors for different products of
the same vendor?
I'm thinking about different solutions:
- extend the vendors enum in order to be a vendor/product enum.
- add a product parameter to the function prototype
- change the vendor parameter with a structure of two variables
Do you think it would be an improvement?
P.S. happy new year!
Enrico
3 years, 5 months
