1111075 - [SMS][MMS] When device with roaming sim recieves an MMS the sender number is listed as "1"

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[Brogan Zumwalt [Inactive]]

Attachment: Logcat

Summary (title) Field:
[SMS][MMS] When device with roaming sim recieves an MMS the sender number is listed as "1"
  
Description:
When user has a Chunghwa Telecom SIM in device, and receives an MMS from a US SIM
(AT&T) the sending device number is displayed as "1" instead of it's actual number. 

This occurs whether or not user had roaming enabled or disabled.

User receives message as though auto-retrieve is disabled (whether it is or not) and is never able to retrieve content.

Multiple devices and SIMs were used and issue reproduced 100%

Repro Steps:
1) Update a Flame device to BuildID: 20141212040206
2) Have roaming SIM in device (not in home network)
3) Receive an MMS from a second device with a non-roaming SIM
4) Observe sender phone number in received MMS
  
Actual:
Sender phone number is listed as "1"
  
Expected: 
Sender phone number is displayed accurately
  
Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141212040206
Gaia: 1d9ae9cca415ad093beba9521c429350e1f2b14d
Gecko: 5288b15d22de
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Repro frequency: 3/3, 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/8252/
See attached: Youtube video clip & logcat
Youtube link: http://youtu.be/KAww2TY9n0E

Comment 1

[Brogan Zumwalt [Inactive]]

Leaving QAWanted for branch checks

Comment 2

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue occurs on Flame 2.2, Flame 2.1, and Flame 2.0.

For those attempting to reproduce: Roaming mms recieve much faster when connected to wifi.

Environmental Variables:
Device: Flame 2.2
BuildID: 20141212045251
Gaia: 0de95b4017de73e72c897e2dcb87564d8f3756eb
Gecko: 28fdae830289
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 2.1
BuildID: 20141212123253
Gaia: 97873dca486abf4162a3345e71b375806937bdec
Gecko: ec87f4f41d3d
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0
BuildID: 20141212132154
Gaia: f3b9806f687fbbd7eba6b0e1f6ebb8bde09840ea
Gecko: 200dcb57e69e
Version: 32.0 (2.0) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 3

[Joshua Mitchell (Inactive)]

NI to SMS owner for blocking call

Comment 4

[Julien Wajsberg [:julienw]]

Hey,

it would help if you can try the same setup (same SIMs) on a non-Firefox OS device. The goal is to determine whether it's a network issue.

Thanks!

Comment 5

[Bevis Tseng[:bevis][:btseng](Exited)]

This is expected to be an network issue in CHT network:
1. The address of the MMS notification will always be "1".
2. You will see this notification if MMS is not auto-retrieval in CHT network.
3. I can reproduce this with my device (HTC M8).