Handle network-initiated ussd requests.
RFC PATCH 1/1 Handle network-initiated ussd requests.
This adds the methods on the D-bus interface to allow the client to handle USSD requests from the network, according to 22.090. Unfortunately this document is not clear on every point and some details can't be implemented. This includes reporting unsupported request to the network, unsupported language, ME busy etc, because there isn't an AT command for that.
To be really pedantic, the Initiate() return value and the NotificationReceived() and RequestReceived() signals should also supply the language of the string. I also first added a "Timeout" property with default value of 10 seconds after which oFono automatically replies "not supported" to network-initiated requests, so that it is compliant when no client listents to the signals, but removed it because it isn't useful.
--- doc/ussd-api.txt | 45 ++++++++++++++++++ include/ussd.h | 4 ++ src/ussd.c | 135 ++++++++++++++++++++++++++++++++++++++++++++++++++++-- 3 files changed, 180 insertions(+), 4 deletions(-) create mode 100644 doc/ussd-api.txt
doc/ussd-api.txt new file +45 -0
@@ -0,0 +1,45 @@ +SupplementaryServices hierarchy +========================== + +Service org.ofono +Interface org.ofono.SupplementaryServices +Object path [variable prefix]/{modem0,modem1,...} + +Methods string, variant Initiate(string command) + + Sends a USSD command string to the network + initiating a session. When the request is handled + by the appropriate node of the network, the + method returns the response or an appropriate + error. The network may be awaiting further response + from the ME after returning from this method and no + new command can be initiated until this one is + cancelled or ended. + + void Respond(string reply) + + Send a response to the network either when + it is awaiting further input after Initiate() + was called or after a network-initiated request. + + void Cancel() + + Cancel an ongoing USSD session, mobile- or + network-initiated. + + void NotSupported() + + Send a "not supported" response to a network's + request, ending current session. + +Signals NotificationReceived(string attribute, variant value) + + Signal is emitted on a network-initiated USSD + request for which no response is needed. + + RequestReceived(string attribute, variant value) + + Signal is emitted on a network-initiated USSD + request for which a response must be sent using + the Respond method unless it is cancelled or + the request is not supported.
include/ussd.h +4 -0
@@ -47,8 +47,12 @@ struct ofono_ussd_driver {void (*remove)(struct ofono_ussd *ussd);void (*request)(struct ofono_ussd *ussd,const char *str,ofono_ussd_cb_t ,void *data); +void (*respond)(struct ofono_ussd *ussd,const char *str, +ofono_ussd_cb_t ,void *data);void (*cancel)(struct ofono_ussd *ussd,ofono_ussd_cb_t cb,void *data); +void (*respond_not_supported)(struct ofono_ussd *ussd, +ofono_ussd_cb_t cb,void *data); };void ofono_ussd_notify (struct ofono_ussd *ussd,int status,const char *str);
src/ussd.c +131 -4
189 lines not on this page · raw message
Signature · 1 line
1.6.1
Hi Andrew,
Quoted 14 lines
This adds the methods on the D-bus interface to allow the client to handle USSD requests from the network, according to 22.090. Unfortunately this document is not clear on every point and some details can't be implemented. This includes reporting unsupported request to the network, unsupported language, ME busy etc, because there isn't an AT command for that.
To be really pedantic, the
Initiate()return value and theNotificationReceived()andRequestReceived()signals should also supply the language of the string. I also first added a "Timeout" property with default value of 10 seconds after which oFono automatically replies "not supported" to network-initiated requests, so that it is compliant when no client listents to the signals, but removed it because it isn't useful.
Quoted 5 lines
--- doc/ussd-api.txt | 45 ++++++++++++++++++ include/ussd.h | 4 ++ src/ussd.c | 135++++++++++++++++++++++++++++++++++++++++++++++++++++-- 3 files
changed,
Quoted 32 lines
180 insertions(+), 4 deletions(-)
create mode 100644 doc/ussd-api.txtdoc/ussd-api.txt new file +23
-0@@ -0,0 +1,45 @@ +SupplementaryServices hierarchy +========================== + +Service org.ofono +Interface org.ofono.SupplementaryServices +Object path [variable prefix]/{modem0,modem1,...} + +Methods string, variant Initiate(string command) + + Sends a USSD command string to the network + initiating a session. When the request is handled + by the appropriate node of the network, the + method returns the response or an appropriate + error. The network may be awaiting further response + from the ME after returning from this method and no + new command can be initiated until this one is + cancelled or ended. + + void Respond(string reply) + + Send a response to the network either when + it is awaiting further input after Initiate() + was called or after a network-initiated request.
doc/ussd-api.txt line 33
Quoted 10 lines
doc/ussd-api.txt new file +10
-0+ + void Cancel() + + Cancel an ongoing USSD session, mobile- or + network-initiated. + + void NotSupported() + + Send a "not supported" response to a network's + request, ending current session.
Let us get rid of this for now
doc/ussd-api.txt line 38
Quoted 5 lines
doc/ussd-api.txt new file +5
-0+ +Signals NotificationReceived(string attribute, variant value) + + Signal is emitted on a network-initiated USSD + request for which no response is needed.
There is no reason to use string / variant pair here. This was done on Initiate return to allow known supplementary service register/activate/interrogate/deactivate/erasure support. Since we know this is a basic text USSD, we can just send a string here.
doc/ussd-api.txt line 45
Quoted 7 lines
doc/ussd-api.txt new file +7
-0+ + RequestReceived(string attribute, variant value) + + Signal is emitted on a network-initiated USSD + request for which a response must be sent using + the Respond method unless it is cancelled or + the request is not supported.
Same as above, a simple string will do.
include/ussd.h struct ofono_ussd_driver { · line 51
Quoted 10 lines
include/ussd.h +2
-0@@ -47,8 +47,12 @@ struct ofono_ussd_driver {void (*remove)(struct ofono_ussd *ussd);void (*request)(struct ofono_ussd *ussd,const char *str,ofono_ussd_cb_t ,void *data); +void (*respond)(struct ofono_ussd *ussd,const char *str, +ofono_ussd_cb_t ,void *data);
Respond is the same as request, there's really no need for a separate method here.
include/ussd.h struct ofono_ussd_driver { · line 56
Quoted 5 lines
include/ussd.h +2
-0void (*cancel)(struct ofono_ussd *ussd,ofono_ussd_cb_t cb,void *data); +void (*respond_not_supported)(struct ofono_ussd *ussd, +ofono_ussd_cb_t cb,void *data); };
No modem I know of actually implements this and it is not in the standards. Let us just use cancel for now.
Quoted 19 lines
include/ussd.h +0
-0void ofono_ussd_notify (struct ofono_ussd *ussd,int status,const char *str); diff --git a/src/ussd.c b/src/ussd.cindex 4221dfa..6416ee9 100644
src/ussd.c +5
-0@@ -274,6 +274,11 @@ out:return ret; } +static void ussd_not_supported_callback (const struct ofono_error *error, +void *data) +{ +} +void ofono_ussd_notify (struct ofono_ussd *ussd,int status,const char *str) {DBusConnection *conn =ofono_dbus_get_connection ();
src/ussd.c void ofono_ussd_notify(struct ofono_ussd *ussd, int · line 313
Quoted 6 lines
src/ussd.c +3
-0@@ -303,14 +308,14 @@ void ofono_ussd_notify(struct ofono_ussd *ussd, int status, const char *str) goto out; } +if (!str) + str ="" ; +
This should be in a separate cleanup patch.
src/ussd.c void ofono_ussd_notify(struct ofono_ussd *ussd, int status, const char *str) · line 313
Quoted 8 lines
src/ussd.c +0
-3/* TODO: Rework this in the Agent framework */ if (ussd->state ==USSD_STATE_ACTIVE ) { reply =dbus_message_new_method_return (ussd->pending); -if (!str) - str ="" ; -
As above.
Quoted 29 lines
src/ussd.c +22
-0dbus_message_iter_init_append (reply, &iter); dbus_message_iter_append_basic(&iter, DBUS_TYPE_STRING,@@ -329,10 +334,46 @@ void ofono_ussd_notify(struct ofono_ussd *ussd, int status, const char *str) else ussd->state =USSD_STATE_IDLE ; + }else if (ussd->state ==USSD_STATE_IDLE && ussd->pending ==NULL ) { +DBusMessage *signal; +const char *signal_name; +const char *path =__ofono_atom_get_path (ussd->atom); + +if (status ==OFONO_USSD_STATUS_ACTION_REQUIRED ) { + ussd->state =USSD_STATE_USER_ACTION ; + signal_name ="RequestReceived" ; + }else { + ussd->state =USSD_STATE_IDLE ; + signal_name ="NotificationReceived" ; + } + + signal =dbus_message_new_signal (path, +SUPPLEMENTARY_SERVICES_INTERFACE , + signal_name); + +dbus_message_iter_init_append (signal, &iter); + +dbus_message_iter_append_basic (&iter,DBUS_TYPE_STRING , + &ussdstr); +
src/ussd.c void ofono_ussd_notify(struct ofono_ussd *ussd, int · line 368
Quoted 10 lines
src/ussd.c +10
-0+dbus_message_iter_open_container (&iter,DBUS_TYPE_VARIANT , sig, + &variant); + +dbus_message_iter_append_basic (&variant,DBUS_TYPE_STRING , + &str); + +dbus_message_iter_close_container (&iter, &variant); + +g_dbus_send_message (conn, signal); +return ;
g_dbus_emit_signal will be enough here.
src/ussd.c void ofono_ussd_notify(struct ofono_ussd *ussd, int status, const char *str) · line 377
Quoted 9 lines
src/ussd.c +4
-0}else {ofono_error ("Received an unsolicited USSD, ignoring for now..." );DBG ("USSD is: status: %d, %s" , status, str); +if (ussd->driver->respond_not_supported) + ussd->driver->respond_not_supported (ussd, + ussd_not_supported_callback,NULL ); +return ;
There's no reason for this else clause to exist now. The above else if condition is handling this case too. Just look carefully at ussd driver for AT command modems, we always call back first, then issue ussd_notify. This is the case for both modems with and without cancel support.
Quoted 31 lines
src/ussd.c +16
-1}@@ -380,7 +421,7 @@ static DBusMessage *ussd_initiate(DBusConnection *conn, DBusMessage *msg, if (ussd->flags & USSD_FLAG_PENDING)return __ofono_error_busy (msg); -if (ussd->state ==USSD_STATE_ACTIVE ) +if (ussd->state !=USSD_STATE_IDLE )return __ofono_error_busy (msg); if (dbus_message_get_args(msg, NULL, DBUS_TYPE_STRING, &str,@@ -411,6 +452,64 @@ static DBusMessage *ussd_initiate(DBusConnection *conn, DBusMessage *msg, return NULL; } +static void ussd_response_callback (const struct ofono_error *error,void *data) +{ +struct ofono_ussd *ussd = data; +DBusConnection *conn =ofono_dbus_get_connection (); +DBusMessage *reply; + + ussd->flags &= ~USSD_FLAG_PENDING ; + +if (!ussd->pending) +return ; + +if (error->type ==OFONO_ERROR_TYPE_NO_ERROR ) { + ussd->state =USSD_STATE_IDLE ; + + reply =dbus_message_new_method_return (ussd->pending); + }else {
src/ussd.c static DBusMessage *ussd_initiate(DBusConnection · line 480
Quoted 10 lines
src/ussd.c +10
-0+DBG ("ussd response failed with error: %s" , +telephony_error_to_str (error)); + + reply =__ofono_error_failed (ussd->pending); + } + +g_dbus_send_message (conn, reply); + +dbus_message_unref (ussd->pending); + ussd->pending =NULL ;
__ofono_dbus_pending_reply please.
Quoted 15 lines
src/ussd.c +15
-0+} + +static DBusMessage *ussd_respond (DBusConnection *conn,DBusMessage *msg, +void *data) +{ +struct ofono_ussd *ussd = data; +const char *str; + +if (ussd->flags &USSD_FLAG_PENDING ) +return __ofono_error_busy (msg); + +if (ussd->state !=USSD_STATE_USER_ACTION ) +return __ofono_error_not_active (msg); + + if (dbus_message_get_args(msg, NULL, DBUS_TYPE_STRING, &str,
src/ussd.c static DBusMessage *ussd_initiate(DBusConnection *conn, DBusMessage *msg, · line 505
Quoted 10 lines
src/ussd.c +10
-0+ DBUS_TYPE_INVALID) == FALSE) +return __ofono_error_invalid_args (msg); + +if (strlen (str) ==0 ) +return __ofono_error_invalid_format (msg); + +if (!ussd->driver->respond) +return __ofono_error_not_implemented (msg); + + ussd->flags |=USSD_FLAG_PENDING ;
Don't use this flag anymore, I've taken it out.
src/ussd.c static DBusMessage *ussd_initiate(DBusConnection *conn, DBusMessage *msg, · line 508
Quoted 3 lines
src/ussd.c +3
-0+ ussd->pending =dbus_message_ref (msg); + + ussd->driver->respond (ussd, str, ussd_response_callback, ussd);
Use driver->request here.
Quoted 22 lines
src/ussd.c +14
-0+ +return NULL ; +} +static void ussd_cancel_callback (const struct ofono_error *error,void *data) {struct ofono_ussd *ussd = data;@@ -458,15 +557,43 @@ static DBusMessage *ussd_cancel(DBusConnection *conn, DBusMessage *msg, return NULL; } +static DBusMessage *ussd_not_supported (DBusConnection *conn,DBusMessage *msg, + void *data) +{ +struct ofono_ussd *ussd = data; + +if (ussd->flags &USSD_FLAG_PENDING ) +return __ofono_error_busy (msg); + +if (ussd->state ==USSD_STATE_IDLE ) +return __ofono_error_not_active (msg); +
src/ussd.c static DBusMessage *ussd_cancel(DBusConnection *conn, · line 580
Quoted 10 lines
src/ussd.c +10
-0+if (!ussd->driver->respond_not_supported) +return __ofono_error_not_implemented (msg); + + ussd->flags |=USSD_FLAG_PENDING ; + ussd->pending =dbus_message_ref (msg); + + ussd->driver->respond_not_supported (ussd, ussd_cancel_callback, ussd); + +return NULL ; +}
Get rid of this method
Quoted 6 lines
src/ussd.c +3
-0+static GDBusMethodTable ussd_methods[] = { {"Initiate" ,"s" ,"sv" , ussd_initiate,G_DBUS_METHOD_FLAG_ASYNC }, + {"Respond" ,"s" ,"" , ussd_respond, +G_DBUS_METHOD_FLAG_ASYNC },
src/ussd.c static DBusMessage *ussd_cancel(DBusConnection *conn, DBusMessage *msg, · line 596
Quoted 10 lines
src/ussd.c +4
-0{"Cancel" ,"" ,"" , ussd_cancel, G_DBUS_METHOD_FLAG_ASYNC }, + { "NotSupported", "", "", ussd_not_supported, + G_DBUS_METHOD_FLAG_ASYNC }, { } };static GDBusSignalTable ussd_signals[] = { + {"NotificationReceived" ,"sv" }, + { "RequestReceived", "sv" },
Simple strings here
src/ussd.c static DBusMessage *ussd_cancel(DBusConnection *conn, · line 598
Quoted 3 lines
src/ussd.c +0
-0{ } };
Regards,
-Denis
Hi,
Quoted 10 lines · Denis Kenzior
Quoted 9 lines
} else {
ofono_error("Received an unsolicited USSD, ignoring for now...");DBG("USSD is: status: %d, %s", status, str);+ if (
ussd->driver->respond_not_supported)
+ ussd->driver->respond_not_supported(ussd,
+ussd_not_supported_callback, NULL); +
return;
Quoted 4 lines
There's no reason for this else clause to exist now. The above else if condition is handling this case too. Just look carefully at ussd driver for AT command modems, we always call back first, then issue
ussd_notify. This is the case for both modems with and without cancel support.
This is true but we might also get a request when we're in USSD_STATE_USER_ACTION and then by my reading we should reply that the user is busy i.e. send a cancel, what do you think? I left the clause in the patch but removed the unneeded "ussd->pending" check.
I included your other comments, thanks.
Regards
From 22ffcd009b4666e7dbbef2fc6cfd3678bc7bba3f Mon Sep 17 00:00:00 2001
From: Andrzej Zaborowski <[email protected]>
Date: Mon, 15 Feb 2010 07:47:33 +0100
Subject: [PATCH] Handle network-initiated ussd requests.
This adds the methods on the D-bus interface to allow the client to handle USSD requests from the network, according to 22.090. Unfortunately this document is not clear on every point and some details can't be implemented. This includes reporting unsupported request to the network, unsupported language, ME busy etc, because there isn't an AT command for that.
--- doc/ussd-api.txt | 40 +++++++++++++++++++++++ src/ussd.c | 91 ++++++++++++++++++++++++++++++++++++++++++++++++++++- 2 files changed, 129 insertions(+), 2 deletions(-) create mode 100644 doc/ussd-api.txt
doc/ussd-api.txt new file +40 -0
@@ -0,0 +1,40 @@ +SupplementaryServices hierarchy +========================== + +Service org.ofono +Interface org.ofono.SupplementaryServices +Object path [variable prefix]/{modem0,modem1,...} + +Methods string, variant Initiate(string command) + + Sends a USSD command string to the network + initiating a session. When the request is handled + by the appropriate node of the network, the + method returns the response or an appropriate + error. The network may be awaiting further response + from the ME after returning from this method and no + new command can be initiated until this one is + cancelled or ended. + + void Respond(string reply) + + Send a response to the network either when + it is awaiting further input after Initiate() + was called or after a network-initiated request. + + void Cancel() + + Cancel an ongoing USSD session, mobile- or + network-initiated. + +Signals NotificationReceived(string message) + + Signal is emitted on a network-initiated USSD + request for which no response is needed. + + RequestReceived(string message) + + Signal is emitted on a network-initiated USSD + request for which a response must be sent using + the Respond method unless it is cancelled or + the request is not supported.
src/ussd.c +89 -2
130 lines not on this page · raw message
Signature · 1 line
1.6.1
From c924528f264bf4262cda1fc6f065da2806e6891d Mon Sep 17 00:00:00 2001
From: Andrzej Zaborowski <[email protected]>
Date: Fri, 12 Feb 2010 05:49:18 +0100
Subject: [PATCH 3/3] Subscribe to USSD signals in test script.
--- test/test-ussd | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-)
test/test-ussd +10 -1
@@ -6,6 +6,13 @@ import gobject import dbus import dbus.mainloop.glib +def ussd_notification_received(content): + print("Network sent a Notification: " + content) + +def ussd_request_received(content): + print("Network sent a Request: " + content) + ss.Cancel() + if __name__ == "__main__": if (len(sys.argv) < 2): print "Useage: %s <ussd-string>" % (sys.argv[0])
@@ -26,8 +33,10 @@ if __name__ == "__main__": ss = dbus.Interface(bus.get_object('org.ofono', modems[0]), 'org.ofono.SupplementaryServices') + ss.connect_to_signal("NotificationReceived", ussd_notification_received) + ss.connect_to_signal("RequestReceived", ussd_request_received) + print ss.Initiate(sys.argv[1], timeout=100) mainloop = gobject.MainLoop() mainloop.run() -
Signature · 1 line
1.6.1
Hi Andrew,
Quoted 18 lines
Hi,
Quoted 10 lines · Denis Kenzior
Quoted 9 lines
} else {
ofono_error("Received an unsolicited USSD, ignoring for
now...");DBG("USSD is: status: %d, %s", status, str);(quoted diff) +3
-0+ if (ussd->driver->respond_not_supported) + ussd->driver->respond_not_supported(ussd, + ussd_not_supported_callback,NULL); +
return;Quoted 4 lines
There's no reason for this else clause to exist now. The above else if condition is handling this case too. Just look carefully at ussd driver for AT command modems, we always call back first, then issue
ussd_notify.
This is the case for both modems with and without cancel support.
Quoted 4 lines
This is true but we might also get a request when we're in
USSD_STATE_USER_ACTIONand then by my reading we should reply that the user is busy i.e. send a cancel, what do you think? I left the clause in the patch but removed the unneeded "ussd->pending" check.
In everything I've researched I understood that there can't be two concurrent ussd sessions. The only things that can happen during USSD_STATE_USER_ACTION:
- Network sends a timed out notification or terminates the ussd action
- someone else actually responds to the USSD (other local client has responded)
I think we should simply ignore the re-entrant case (which USSD operation are you canceling? First or second?) until we're told otherwise. However, we _should_ handle the network termination / other local client has responded cases.
Also, it might be a good idea to have a State property that shows the current USSD request state.
Regards,
-Denis
Hi,
Quoted 6 lines · Denis Kenzior
In everything I've researched I understood that there can't be two concurrent ussd sessions. The only things that can happen during
USSD_STATE_USER_ACTION:
- Network sends a timed out notification or terminates the ussd action
- someone else actually responds to the USSD (other local client has responded)
Quoted 7 lines
I think we should simply ignore the re-entrant case (which USSD operation are you canceling? First or second?) until we're told otherwise. However, we _should_ handle the network termination / other local client has responded cases.
Also, it might be a good idea to have a State property that shows the current USSD request state.
Ok, you're definitely right. This new patch ignores the new USSD if we're in USSD_STATE_USER_ACTION already. I also added a USSDState property as string.
Regards
From 6c92ff58242a5c0a599437753ce197d30070a200 Mon Sep 17 00:00:00 2001
From: Andrzej Zaborowski <[email protected]>
Date: Mon, 15 Feb 2010 11:05:16 +0100
Subject: [PATCH 12/13] Handle network-initiated ussd requests.
This adds the methods on the D-bus interface to allow the client to handle USSD requests from the network, according to 22.090. Unfortunately this document is not clear on every point and some details can't be implemented. This includes reporting unsupported request to the network, unsupported language, ME busy etc, because there isn't an AT command for that.
--- doc/ussd-api.txt | 64 +++++++++++++++++++++ src/ussd.c | 162 ++++++++++++++++++++++++++++++++++++++++++++++++++--- 2 files changed, 216 insertions(+), 10 deletions(-) create mode 100644 doc/ussd-api.txt
doc/ussd-api.txt new file +64 -0
@@ -0,0 +1,64 @@ +SupplementaryServices hierarchy +========================== + +Service org.ofono +Interface org.ofono.SupplementaryServices +Object path [variable prefix]/{modem0,modem1,...} + +Methods string, variant Initiate(string command) + + Sends a USSD command string to the network + initiating a session. When the request is handled + by the appropriate node of the network, the + method returns the response or an appropriate + error. The network may be awaiting further response + from the ME after returning from this method and no + new command can be initiated until this one is + cancelled or ended. + + void Respond(string reply) + + Send a response to the network either when + it is awaiting further input after Initiate() + was called or after a network-initiated request. + + void Cancel() + + Cancel an ongoing USSD session, mobile- or + network-initiated. + + dict GetProperties() + + Returns Supplementary Services related properties. See + the properties section for available properties. + +Signals NotificationReceived(string message) + + Signal is emitted on a network-initiated USSD + request for which no response is needed. + + RequestReceived(string message) + + Signal is emitted on a network-initiated USSD + request for which a response must be sent using + the Respond method unless it is cancelled or + the request is not supported. + + PropertyChanged(string property, variant value) + + Signal is emitted whenever a property has changed. + The new value is passed as the signal argument. + +Properties string USSDState [readonly] + + Reflects the state of current USSD session. The + values have the following meanings: + + "idle" No active USSD session. + "active" A session is active between the + network and the ME, the ME is + waiting for a reply from the + network. + "awaiting-user-response" The network is waiting for the + user's response, client must + call Respond().
src/ussd.c +152 -10
225 lines not on this page · raw message
Signature · 1 line
1.6.1
From ee058468cfa89140d7a3247387cdeed9c56252c4 Mon Sep 17 00:00:00 2001
From: Andrzej Zaborowski <[email protected]>
Date: Mon, 15 Feb 2010 11:05:40 +0100
Subject: [PATCH 13/13] Subscribe to USSD signals in test script.
--- test/test-ussd | 21 ++++++++++++++++++++- 1 files changed, 20 insertions(+), 1 deletions(-)
test/test-ussd +20 -1
@@ -6,6 +6,18 @@ import gobject import dbus import dbus.mainloop.glib +def ussd_notification_received(content): + print("Network sent a Notification: " + content) + +def ussd_request_received(content): + print("Network sent a Request: " + content) + ss.Cancel() + +def ussd_property_changed(name, value): + if name != "USSDState": + return + print("USSD session state is " + value) + if __name__ == "__main__": if (len(sys.argv) < 2): print "Useage: %s <ussd-string>" % (sys.argv[0])
@@ -26,8 +38,15 @@ if __name__ == "__main__": ss = dbus.Interface(bus.get_object('org.ofono', modems[0]), 'org.ofono.SupplementaryServices') + props = ss.GetProperties() + for p in props: + ussd_property_changed(p, props[p]) + + ss.connect_to_signal("NotificationReceived", ussd_notification_received) + ss.connect_to_signal("RequestReceived", ussd_request_received) + ss.connect_to_signal("PropertyChanged", ussd_property_changed) + print ss.Initiate(sys.argv[1], timeout=100) mainloop = gobject.MainLoop() mainloop.run() -
Signature · 1 line
1.6.1
Hi Andrew,
These patches have been applied with minor tweaks afterward.
Regards,
-Denis