Closed Bug 1077776 Opened 10 years ago Closed 6 years ago

Bug: MMS does not reliably send to contacts

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Mozilla_BEC, Unassigned)

Details

Attachments

(4 files)

Working MMS send logcat
852.11 KB, text/plain
Details
capture.pcap
44.21 KB, application/octet-stream
Details
logcat.txt
1.38 MB, text/plain
Details
capture.pcap
436.95 KB, application/octet-stream
Details 
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:24.7) Gecko/20140907 Firefox/24.7 PaleMoon/24.7.2
Build ID: 20140907202139

Steps to reproduce:

Compose MMS to various contacts using various devices on various cellular networks


Actual results:

Practically NONE of my contacts receive my MMS messages. All receive my SMS messages, and I can receive MMS from ALL of those contacts who can't get mine.


Expected results:

MMS should send to every contact.

My phone/network configuration:
Mozilla Flame - v2.2 Nightly (v1.30 Gonk/Base Image)
Provider: CricKet (AIO Wireless/ AT&T MVNO)
SIM Card: SIM 1
Network Type: Auto, Auto Selection
Data APN:
ndo \ no auth \ ipv4 (confirmed working)
MMS APN: 
ndo \ proxy.aiowireless.net \ http://mmsc.aiowireless.net \ port 80 \ no auth \ ipv4 (confirmed working for all inbound, some outbound)

Phone/Network of working recipient:
Nokia Lumia 521 (T-Mobile/Brightspot) WindowsPhone 8.1 dev preview
Hi,

May I have your help to 
1. have adb logcat & tcpdump for further analysis?
   https://github.com/bevis-tseng/Debug_Tools
2. What is the behavior of the same test SIM in other devices? Are the same contacts receives the mms accordingly?

Thanks!
Component: Gaia::SMS → RIL
Flags: needinfo?(Synper311)
Absolutely Bevis.

1) Working on getting this, I don't have a linux box at present so I need to do the script steps by hand

2) I just tested my cricKet SIM in my previous phone, my dumbphone (Samsung SGH-A667 (Evergreen) AT&T Firmware), and every person I sent MMS to was able to receive the MMS without an issue, and even could read the Subject field.

After transferring the SIM back to my Flame v2.2 [v1.30 base image] nightly, it exhibits the problematic behavior of only sending MMS successfully to one contact that I know of, and even she does not get the Subject field.
Flags: needinfo?(Synper311)
1) Have the files and prefs set.

How do you wish me to test this? Compose/send MMS to known working contact and compose/send MMS to known not-working contact?

Or just the non-working contact?
(In reply to Brett Edmond Carlock from comment #2)
> Absolutely Bevis.
> 
> 1) Working on getting this, I don't have a linux box at present so I need to
> do the script steps by hand
> 
> 2) I just tested my cricKet SIM in my previous phone, my dumbphone (Samsung
> SGH-A667 (Evergreen) AT&T Firmware), and every person I sent MMS to was able
> to receive the MMS without an issue, and even could read the Subject field.
> 
> After transferring the SIM back to my Flame v2.2 [v1.30 base image] nightly,
> it exhibits the problematic behavior of only sending MMS successfully to one
> contact that I know of, and even she does not get the Subject field.
1) I am wondering that the successfully one is a SMS instead of a MMS.
2) Regarding sending MMS to other contacts that never received, does that means the MMS was actually not sent (With a red '!' icon) by your Flame or it was sent but not received by the remote party?
3) May I have your help to capture logs for the not-working contact you mentioned for further analysis?
4) From the APN settings you provide in comment 0, I expect to see some issue regarding the DNS query of the MMS proxy if it is not IP-based (proxy.aiowireless.net). Currently, we have 2 bugs (Bug 992772, Bug 1053650) ongoing to improve it.
Flags: needinfo?(Synper311)
1) No, still MMS. I send her picture messages and she always gets them.

2) Sent, but never delivered. The Flame shows no red !, and I have turned on delivery report and read report. It simply never gets to anyone's phone.

3) Yes, I will be attaching logs for that presently.

4) The link below is the official APN settings for CricKet. I have them as written on my Flame.
https://www.cricketwireless.com/support/apps-and-services/bring-your-own-device-byod/customer/bring-your-own-android.html

5) New Info: I tested sending MMS to my family who are also on CricKet with me, but they also never get my MMS. Father: CricKet + Android, Mother: CricKet + Samsung dumbphone.
Flags: needinfo?(Synper311)
A logcat of a working MMS send to the one contact that seems to work.
Attached file capture.pcap — 
TCPdump of working MMS send to one known working contact.

This TCPdump consists of a SMS first, then a MMS, then is ended after the MMS reports back delivered.
Attached file logcat.txt — 
Logcat of non-working MMS send to three contacts.

Contact1: One MMS to CricKet + Android

Contact2: Two MMS to Verizon + Android

Contact3: One MMS to ??? + iPhone
Attached file capture.pcap — 
TCPdump of non-working MMS send to three contacts.

Contact1: One MMS to CricKet + Android

Contact2: Two MMS to Verizon + Android

Contact3: One MMS to ??? + iPhone
Flags: needinfo?(btseng)
Extra Info:

Working contact is T-Mobile + WindowsPhone 8.1 Developer Preview (Lumia 521)
After checking both the successful and the failed ones,
Unfortunately, I didn't see any error from the device side.
No matter it was received or not even notified in the receiving parties, 
All the MMS are sent sucessfully with positive response from MMSC in M-Send.conf with "x-mms-response-status" set to 128 which means "OK".

I am wondering 
1. if there is any additional configuration needed to this carrier.
2. Or, if there is something wrong in server side similar to bug 1029453 and need to be configured correctly in the server-side.

However, we don't have any information from carrier-side to clarify this yet. :(
Flags: needinfo?(btseng)
Summary: [v2.2] Bug: MMS does not reliably send to contacts → Bug: MMS does not reliably send to contacts
1) This previously was working on my ZTE Open under older versions of FFXOS.
As noted, my Samsung dumbphone can take the CricKet SIM with same settings as my Flame and send MMS reliably to every contact I test. The Evergreen was never designed to work with CricKet as technically, they didn't exist as a GSM carrier during the time when the Evergreen's firmware was made.

2) How does that issue get addressed?

3) Is there other information I need to provide you? Could it be because of my outdated v1.30 base image Gonk layer?
Bevis,

I tested my MMS sending once again, this time to someone else who is also on T-Mobile. They received my MMS just fine.

They are using a very old Nokia dumbphone that can't even download MMS, but the phone did get notified that it received an MMS and displayed this system message.
Bevis,

Tested MMS sending to a contact I previously had no trouble sending to using this SIM in my ZTE Open running FFXOS v1.2 to v2.1

They, like practically everyone else, did not receive my MMS.

I am using FFXOS v2.2 nightly on Flame over v1.80 base image.
As you mentioned in comment 14, even the working one with ZTE is not working now.
It's really hard to tell what was happening in carrier side unless we got more detailed information from them. :(
(In reply to Bevis Tseng [:bevistseng] (btseng@mozilla.com) from comment #15)
> As you mentioned in comment 14, even the working one with ZTE is not working
> now.
> It's really hard to tell what was happening in carrier side unless we got
> more detailed information from them. :(

I don't think it is carrier side. I can take this SIM right now and put it into other devices and they will all send MMS perfectly fine. It has to be something FFXOS is doing, right?
(In reply to Brett Edmond Carlock from comment #16)
> (In reply to Bevis Tseng [:bevistseng] (btseng@mozilla.com) from comment #15)
> > As you mentioned in comment 14, even the working one with ZTE is not working
> > now.
> > It's really hard to tell what was happening in carrier side unless we got
> > more detailed information from them. :(
> 
> I don't think it is carrier side. I can take this SIM right now and put it
> into other devices and they will all send MMS perfectly fine. It has to be
> something FFXOS is doing, right?

Yes, I believe so.
However, we don't know what we should change to allow carrier to deliver our message to the remote party.
The only thing I can image is to compare the tcpdump sent by FFOS & by other reference device from the same sender to the same receiver.
Then, do some try/error to change the fields that was not the same in these 2 tcpdump.

Bevis
I can't collect TCP dump from any of my other devices. They're all dumbphones :\
Could it be because FFXOS doesn't let us set the MNC and MCC for the MMS APN settings?
(In reply to Brett Edmond Carlock from comment #19)
> Could it be because FFXOS doesn't let us set the MNC and MCC for the MMS APN
> settings?

No, MNC/MCC is only use to retrieve the APN settings correctly from pre-built APN database.
If the APN name, MMSC/MMS Proxy is correctly displayed in the UI,
that means we right APN settings for setup data connection for MMS.
I have the right settings because I can retrieve fine from any phone/carrier and I can send fine to T-Mobile.

I still can't figure out what is going on here.

Is FFXOS MMS malformed in some way? Non-standard? Maybe TOO standards compliant?
As of 2014-10-25 15:54:57
20141026160206
and the version prior, I can no longer send MMS to any of my.contacts with them able to receive the message. This includes my T-Mobile contact that previously worked properly.
As of 2014-10-27 17:43:23
20141027160203
I can once again send MMS to my T-Mobile contact
Update:

It looks like nobody with an iPhone can receive my MMS, and nobody on Verizon can receive my MMS.

Both my parents on Cricket now can receive my MMS
Parent 1: Android 4.4.2
Parent 2: Samsung Dumbphone
I still can not send MMS messages to most of my contacts, even under v3.0 nightly.

Can we please get this resolved? Having to keep my dumbphone around just to MMS is getting beyond obnoxious.
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: