[Rtcomm] [Rtcomm] [Bug 5357] Does not accept GSM (USSD) Codes starting with *#
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Wed Dec 9 19:20:04 EET 2009
- Previous message: [Rtcomm] [Bug 6769] Can't answer a phone call with a short caller ID
- Next message: [Rtcomm] [Bug 6375] Provides SMS buttons for "Phone" entries and not only "Mobile" entries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=5357 ------- Comment #43 from thorsten at eve9.com 2009-12-09 19:19 GMT+3 ------- (In reply to comment #42) > (In reply to comment #41) > > MMI for UE is well defined in 3GPP TS 22.030. > > Most recent version to be found here: > > http://www.3gpp.org/ftp/Specs/html-info/22030.htm hope that helps. > > 22.030 is about the well-defined supplementary service procedures but most > people here are asking for USSD (which is practically everything that's not > covered by 22.030). > > We have already promised USSD support in a later update. Let's see about the > structured codes for forwarding/barring/waiting/interrogating caller id related > settings... There was a bug about these, but I believe it was resolved as > WONTFIX. Feel free to reopen or vote for it, though. > > > Sidenote: On PIN enty the "#" symbol is consequently missing as well, on most > > phones you can even press "#" after PIN to proceed ... > > Not consequently. Please file that as a separate ticket to Connectivity. > Could you point me to the BUG ?
- Previous message: [Rtcomm] [Bug 6769] Can't answer a phone call with a short caller ID
- Next message: [Rtcomm] [Bug 6375] Provides SMS buttons for "Phone" entries and not only "Mobile" entries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]