Closed
Bug 922541
Opened 12 years ago
Closed 9 years ago
[wasabi] Unable to send SMS to the number with +xxx prefix.
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: echu, Unassigned)
Details
Attachments
(2 files)
Device can MO call to +8618911403784 but it cannot send SMS to it.
* Build Number
Gaia: 1e9470b9b6df630eddf1c4c8b25b3170ee786b0e
Gecko: 31cc146c80e45d87211c647c5601b3cd7b6234f8
BuildID 20131001031552
Version 26.0a2
http://release1-qa.corp.tpe1.mozilla.com:8080/view/B2G.v1.2.0/job/B2G.v1.2.0.wasabi/
* Reproduce Steps
1. Send a SMS to +8618911403784
* Expected Result
Message should be able to be sent.
* Actual Result
Get a error message indicating "Service currently unavailable."
* Occurrence rate
100%
Comment 2•12 years ago
|
||
Somehow modem returns GENERIC_ERROR. Need more investigation on this.
10-01 16:49:47.005 I/Gecko ( 201): RIL Worker[0]: Received chrome message {"dcs":0,"encodedFullBodyLength":18,"userDataHeaderLength":0,"langIndex":0,"langShiftIndex":0,"segmentMaxSeq":1,"segmentChars":160,"segments":[{"body":"Can I send to you?","encodedBodyLength":18}],"number":"+8618911403784","requestStatusReport":false,"rilMessageToken":34,"rilMessageType":"sendSMS"}
10-01 16:49:47.005 I/Gecko ( 201): RIL Worker[0]: New outgoing parcel of type 87
10-01 16:49:47.005 I/Gecko ( 201): RIL Worker[0]: cdma_writeMessage: {"dcs":0,"encodedFullBodyLength":18,"userDataHeaderLength":0,"langIndex":0,"langShiftIndex":0,"segmentMaxSeq":1,"segmentChars":160,"segments":[{"body":"Can I send to you?","encodedBodyLength":18}],"number":"+8618911403784","requestStatusReport":false,"rilMessageToken":34,"rilMessageType":"sendSMS","retryCount":0,"segmentSeq":1,"body":"Can I send to you?","encodedBodyLength":18,"rilRequestType":87,"rilRequestError":null}
10-01 16:49:47.015 I/Gecko ( 201): RIL Worker[0]: Outgoing parcel: 0,0,0,208,87,0,0,0,208,0,0,0,2,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,13,0,0,0,8,0,0,0,6,0,0,0,1,0,0,0,8,0,0,0,9,0,0,0,1,0,0,0,1,0,0,0,4,0,0,0,10,0,0,0,3,0,0,0,7,0,0,0,8,0,0,0,4,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,25,0,0,0,0,0,0,0,3,0,0,0,32,0,0,0,0,0,0,0,16,0,0,0,1,0,0,0,18,0,0,0,16,0,0,0,148,0,0,0,60,0,0,0,59,0,0,0,144,0,0,0,73,0,0,0,65,0,0,0,207,0,0,0,46,0,0,0,236,0,0,0,136,0,0,0,58,0,0,0,111,0,0,0,65,0,0,0,231,0,0,0,127,0,0,0,87,0,0,0,224,0,0,0
10-01 16:49:49.127 I/Gecko ( 201): RIL Worker[0]: Received 28 bytes.
10-01 16:49:49.127 I/Gecko ( 201): RIL Worker[0]: Already read 0
10-01 16:49:49.127 I/Gecko ( 201): RIL Worker[0]: New incoming parcel of size 24
10-01 16:49:49.127 I/Gecko ( 201): RIL Worker[0]: Parcel (size 24): 0,0,0,0,208,0,0,0,2,0,0,0,94,0,0,0,255,255,255,255,107,0,0,0
10-01 16:49:49.127 I/Gecko ( 201): RIL Worker[0]: We have at least one complete parcel.
10-01 16:49:49.137 I/Gecko ( 201): RIL Worker[0]: Solicited response for request type 87, token 208, error 2
10-01 16:49:49.137 I/Gecko ( 201): RIL Worker[0]: Handling parcel as REQUEST_CDMA_SEND_SMS
10-01 16:49:49.137 I/Gecko ( 201): RIL Worker[0]: _processSmsSendResult: rilRequestError = 2
10-01 16:49:49.137 I/Gecko ( 201): -*- RadioInterface[0]: Received message from worker: {"rilMessageType":"sendSMS","rilMessageToken":34,"errorMsg":2}
Comment 3•12 years ago
|
||
Enpei will test this issue on Android platform to see if this issue is in SIM cards, or in RIL.
blocking-b2g: koi? → koi+
Wasabi reference phone Android OS cannot sent SMS to +861 prefix number, need to change the + to 00 first.
Comment 5•12 years ago
|
||
(In reply to Enpei from comment #4)
Enpei, can you please try it in other android phones? I would like to make sure if this is carrier's network issue.
Hi Ken,
Another phone cannot send the message as well. So high chances this is network issue.
Comment 7•12 years ago
|
||
I am removing the blocking flag on this given comment #6. Please renom if anything was misunderstood and if this bug should still be blocking.
blocking-b2g: koi+ → -
Updated•11 years ago
|
Whiteboard: [FT:RIL]
Comment 8•11 years ago
|
||
CDMA network can not handle "+" prefix, please check with customer/operator which prefix should be converted to (Ex: "+" -> "001010") first.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•