Closed
Bug 890907
Opened 11 years ago
Closed 11 years ago
[MMS] The country code is not shown in a thread when the MMS was sent from a corporative SIM
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
WONTFIX
blocking-b2g | leo+ |
People
(Reporter: isabelrios, Unassigned)
References
Details
(Whiteboard: MMS_TEF)
Attachments
(2 files)
Bug seen with unagi device 07/07 v1-train build: Gecko-e7708d4 Gaia-d336288 STR 1. From A: an unagi device with a corporative SIM card (6xxxxxxxx) send a MMS to another unagi device, B. (Also checked with A being an android device) 2. Check the thread created in B. EXPECTED The thread is correctly created ACTUAL The thread is created with the number with a '+' ahead of it (+6xxxxxxxx, please see screenshot attached). This is an invalid number, replying to that thread is not possible. This could be related with the short numbering used for corporative SIM Cards. In case it is useful, attached also an adb log file
Reporter | ||
Comment 1•11 years ago
|
||
Reporter | ||
Updated•11 years ago
|
Summary: [MMS] The country code is removed when sending a MMS from a corporative SIM → [MMS] The country code is not shown in a thread when the MMS was sent from a corporative SIM
Comment 3•11 years ago
|
||
We send MMS with FROM address set to null, so when that MMS is received in B, A's address is filled by MMSC, not B.
Comment 4•11 years ago
|
||
Sounds like there's nothing we can help here because MMSC fill in the sender with an invalid number. Btw, we've already normalized the phone numbers before sending an MMS at Bug 890146, which was just landed to b2g18 on 7/8 (the testing build is 7/7). Isabel, could you please give it a try with the latest build? We cannot reproduce this bug by ourselves because we don't have that special SIM/MMSC. Thanks!
Blocks: b2g-mms
Flags: needinfo?(isabelrios)
Reporter | ||
Comment 5•11 years ago
|
||
Hi Gene, Unfortunatelly I can still reproduce the problem with unagin 07/09 v1-train build: Gecko-e78450a Gaia-e251ee6 I could attach other logs if that is useful, just let me know. Thanks
Flags: needinfo?(isabelrios)
Comment 6•11 years ago
|
||
No worries! Thanks Isabel for the prompt help. I think there's nothing we can do here because the sender field is decided by the MMSC.
Comment 7•11 years ago
|
||
(In reply to Gene Lian [:gene] from comment #6) > No worries! Thanks Isabel for the prompt help. I think there's nothing we > can do here because the sender field is decided by the MMSC. So basically a wontfix here ?
Comment 8•11 years ago
|
||
Hi Vicamo, hoping to double confirm with you. So, there is no way we can help. Right? It sounds a pure MMSC issue to me.
Flags: needinfo?(vyang)
Comment 9•11 years ago
|
||
Yes, FROM address, formated as "<address>/PLMN", is assigned by MMSC. We just extract it out with a simple regular expression[1]. [1]: http://mxr.mozilla.org/mozilla-central/source/dom/mobilemessage/src/gonk/MmsPduHelper.jsm#72
Flags: needinfo?(vyang)
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•