Closed Bug 861738 Opened 12 years ago Closed 12 years ago

[SMS] Message waiting indication with coding scheme 7-bit/UCS-2 is never recieved.

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)

Tracking

(blocking-b2g:-)

RESOLVED INVALID
1.1 QE1 (5may)
blocking-b2g -

People

(Reporter: leo.bugzilla.gecko, Assigned: alhadp)

Details

(Whiteboard: [TD-11472])

GENERAL Defect Description 1. Title : [SMS/MMS] Message waiting indication with coding scheme 7-bit/UCS-2 is never recieved 2. Precondition : 3. Tester's Action : 1) Send to DUT message waiting indication with coding scheme set to 7-bit or UCS-2. 4. Detailed Symptom (ENG.) : Message waiting indication is never recieved 5. Detailed Symptom (KOR.) : 6. Expected : Message waiting indication should be recieved. 7. Reproducibility: Y 1)Frequency Rate : 100% 8. Comparison Results : android is ok 1)Model Comparing : android
blocking-b2g: --- → leo?
Priority: -- → P1
Please check MWI Scenario. Is MWI "Discard message" displayed on the UI? We guess, the MWI "Store message" does not works(displayed on the UI) because FFOS does not support SIM storage. And what type of coding sheme supported by FFOS? - Discard Message, Store Message, ?, ?, ...
Flags: needinfo?(vyang)
Target Milestone: --- → Leo QE1 (5may)
Investigating ...
Flags: needinfo?(vyang)
Vicamo - can you put this into layman's terms? Does this impact all carriers/devices/locales?
We guess it has less-relationship with locales. It may impact of not according to sending device/carrier's servers configuration. Assume that a user has a phone and that phone support function which sending Voice Mail Message with saving to the SIM automatically, FFOS cannot receive this message because it does not support SIM Storage for SMS.
If we're losing some user's voicemail messages, this is definitely a blocker.
blocking-b2g: leo? → leo+
(In reply to leo.bugzilla.gecko from comment #4) > We guess it has less-relationship with locales. > It may impact of not according to sending device/carrier's servers > configuration. > > Assume that a user has a phone and that phone support function which sending > Voice Mail Message with saving to the SIM automatically, FFOS cannot receive > this message because it does not support SIM Storage for SMS. I don't understand the scenario what you describe. The voicemail message comes from Carrier, why can user send voicemail message? Or do you mean carrier will send a voice mail message with a flag of saving to SIM? Can you please let me know which carrier use this kind of configuration? Because the maximum number of SMS in SIM is far less than the one of SMS in ME, this kind of configuration is a little weird. Thanks.
Flags: needinfo?(leo.bugzilla.gecko)
I don't understand the scenario what you describe. The voicemail message comes from Carrier, why can user send voicemail message? => First of all, sorry for confusing comment. Yes, users cannot send voicemail message but can create this situation. When a user called to the other and the other did not receive incoming call, the caller can create voicemail, and carrier-server will send this voicemail to call-receiver. Or do you mean carrier will send a voice mail message with a flag of saving to SIM? Can you please let me know which carrier use this kind of configuration? Because the maximum number of SMS in SIM is far less than the one of SMS in ME, this kind of configuration is a little weird. Thanks. => Unfortunately, we don't know what kinds of Carriers actually use MWI with save on SIM flag. But "Store Message" MWI is a 3GPP specification... Save received MWI to SIM. Our EU R&D engineer tested the MWI functions according to the 3GPP spec and find out this problem. And from above, we guess some carriers of EU use this MWI. Could you please tell us... is it possible realization this function? Thanks.
Flags: needinfo?(leo.bugzilla.gecko)
(In reply to leo.bugzilla.gecko from comment #1) > Please check MWI Scenario. > Is MWI "Discard message" displayed on the UI? Yes, all MWI messages are sent to UI but never get stored in neither sms database nor EFmwis. See bug 768441. > We guess, the MWI "Store message" does not works(displayed on the UI) > because FFOS does not support SIM storage. But voicemail events are still dispatched. > And what type of coding sheme supported by FFOS? > - Discard Message, Store Message, ?, ?, ... Any voicemail messages indicated by PID, DCS, or IEI. Discard/store are only attributes of that message but are just never referenced in RadioInterfaceLayer.
Leo, ability to store the message to SIM or not has nothing to do with displaying the message on the UI. Could you please provide the android main logs and the radio logs by running the following command with commercial RIL. adb logcat -b radio -b main -v time
Leo, please also provide the PDU what you test to us.
Talked with Ken and Vicamo. Anshul, once the reporter provides the logs, would it be possible for you to take a look? Vicamo will also check the logs and see if MOZ RIL has problems. Here, I wouldl like to know if it's reasonble for you to be the owner and drive the analysis for now. Thank you.
Flags: needinfo?(anshulj)
The bug seems be same as Bug 862171.
Ken, I am not sure if this is the same as bug 862171. There are multiple ways of receiving voice mail and bug 862171 is specifically for DCS, which by the way I am unable to reproduce. Could the reporter please share the logs or the PDU sent by RIL for this test case. Also, would like to better understand what the issue is. Is there an issue with displaying the voice mail when a voice mail is received or the issue that the voice mail is not stored in the SIM?
Flags: needinfo?(anshulj)
Dear Anshul, The issue is DUT cannot receive the MWI. Below is the captured log which we receive from EU and find out that when receiving the MWI with “Store Message” flag shows below RIL error. 04-16 10:24:26.789 D/RIL_QC_B2G( 146): [UNSL]< UNSOL_RESPONSE_NEW_SMS_ON_SIM {error: response is not supported} Does RIL support “UNSOL_RESPONSE_NEW_SMS_ON_SIM”? And I send more-details to you by email.
Assignee: nobody → anshulj
We don't currently support UNSOL_RESPONSE_NEW_SMS_ON_SIM. Seems like your setup is sending a class 2 SMS for DCS TP_DCS=D8 and TP_DCS=D0. Is this a certification blocker; this is not currently scoped for v1.0?
Assignee: anshulj → alhadp
Flagging needinfo to Leo for the question in comment #15.
Flags: needinfo?(leo.bugzilla.gecko)
Dear Dylan, We and our vendor already know FFOS does not support "UNSOL_RESPONSE_NEW_SMS_ON_SIM". Therefore This is not a certification blocker. (We already submitted the GCF that FFOS does not support "UNSOL_RESPONSE_NEW_SMS_ON_SIM". Thanks.
Flags: needinfo?(leo.bugzilla.gecko)
Resolving invalid based on comment #15 and #17.
Status: NEW → RESOLVED
blocking-b2g: leo+ → -
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.