Openmoko Bug #1832: 2008.8 cannot dial *123
Openmoko Public Trac
bugs at docs.openmoko.org
Wed Dec 3 21:48:26 CET 2008
#1832: 2008.8 cannot dial *123
--------------------+-------------------------------------------------------
Reporter: hedora | Owner: john_lee
Type: defect | Status: assigned
Priority: normal | Milestone: Om2008.10
Component: Qtopia | Version: Om2008.8
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
--------------------+-------------------------------------------------------
Comment(by zecke):
Replying to [comment:15 Treviño]:
> As I've said in #2038, imho the implementation isn't correct.
>
> The first I did was tricky, but it works since it before sets the codec
to GSM to place the request using the command AT+CUSD="<string-number-
coded-using-current-codec>",<code-for-codec> with the <string-number-
coded-using-current-codec> in plain ascii text and the <code-for-codec>
set to the "known" 15 value; then decodes the answer using the current
codec.
>
> As I've previously said using the AT+CUSD="<string-number-coded-in-
ucs2>",15 couldn't work since "15" is not the code for the ucs2 codec
(that according to GSM 03.38 should be 01001000 and so 72 in decimal).
>
> I've not tested the code living in git for this task in my phone since
I'm still using my implementation, but I figure that I've already given
all that I know about this.
My issue:
- People can not test this in Taiwan as supplementary services are not
used there.
- I'm working on something not GTA0X/phone related and didn't have a
spare cycle to work on this since leaving Taipei...
The issue with your implementation:
- Temporarily switching the codec will open a can of worms. It opens a
race with phonebook and SMS handling. and as an expert in racing I can
assure you, you will not win this.
How to proceed:
- I think the approach taken by the implementation in git (using CUSD,
specifying a codec, touching the set of files) is the right thing to do.
- The implementation, e.g. the codec value might be wrong...
How to continue:
- Some one with time and a neo might just issue AT+CUSD and change the
15 to 72 (as from the bug)...
- Extra points for testing this within a network with supplementary
services..
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1832#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list