Closed Bug 1043445 Opened 6 years ago Closed 6 years ago

[Messages][MMS] It's impossible to send or manually download MMS with "smartmobil.de" SIM

Categories

(Firefox OS Graveyard :: Gaia, defect, major)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(blocking-b2g:2.0+, b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED INVALID
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: azasypkin, Assigned: albert)

References

Details

(Keywords: regression)

Attachments

(3 files, 1 obsolete file)

It's impossible to send or manually download MMS using my German "smartmobil.de" SIM card once patch for bug 965826 has been landed. Everything works fine for the SIM from another German operator.
Hey Albert,

Since you were working on bug 965826, could you please look into it?

Thanks!
Flags: needinfo?(alberto.crespellperez)
Oleg - This sounds like something we should block on, right? If so, can you nominate this to block?
Flags: needinfo?(azasypkin)
[Blocking Requested - why for this release]:

(In reply to Jason Smith [:jsmith] from comment #2)
> Oleg - This sounds like something we should block on, right? If so, can you
> nominate this to block?

Right, I think we should block on it, as it seems serious.
blocking-b2g: --- → 2.0?
Flags: needinfo?(azasypkin)
blocking-b2g: 2.0? → 2.0+
Albert can you have a look at it, please?
Alberto is in holiday and comes back next monday. I think we can wait for him.

Moved the component to the same component than the blocker bug.
Component: Gaia::SMS → Gaia
Oleg, can you switch the MMS debugging pref (mms.debugging.enabled) to true and get logcat ? I'm wondering if it may not be another instance of bug 1031656.
Flags: needinfo?(azasypkin)
Attached file logcat_mms.txt
Hey Alexandre, 

Here is the logcat with MMS debugging enabled captured while sending MMS.
Flags: needinfo?(azasypkin)
I'd say it's more like bug 1040700.
Assignee: nobody → alberto.crespellperez
Flags: needinfo?(alberto.crespellperez)
(In reply to Oleg Zasypkin [:azasypkin] from comment #1)
> Hey Albert,
> 
> Since you were working on bug 965826, could you please look into it?
> 
> Thanks!

What should be the expected APN settings for 'smartmobil.de'?

I don't see any reference to this provider in apns_conf.xml [1] and mcc list [2]

[1] https://github.com/acperez/gaia/blob/4833d7fed23d530513ddfb0d14ac944e2bf9f70d/shared/resources/apn/apns_conf.xml

[2] http://mcclist.com/mobile-network-codes-country-codes.asp
Flags: needinfo?(azasypkin)
Here is what I found at personal page at smartmobil.de website:

MMS settings
Name: O2 MMS
APN: internet.telco or internet.victorvox
Username: not required
Password: not required
MMSC: http://10.81.0.07:8002
MMS proxy: 82.113.100.5
MMS Port: 8080
Authentication type: PAP
APN type: mms

Previously it worked without any manual settings from my side.
Flags: needinfo?(azasypkin)
Attached patch Revert O2 apn patch (obsolete) — Splinter Review
As I haven't a smartmobile.de SIM card is difficult to see what's happening.

Please, can you check what APNs (and settings) are currently selected for data and message.

Then, apply the patch that I uploaded and check APNs again (and try to send a MMS).

Also add the mcc/mnc of your SIM card, please.
Flags: needinfo?(azasypkin)
Without the patch:

* Data settings - (custom settings), all fields are empty or "Not defined";
* Message settings - (custom settings), all fields are empty or "Not defined";

With the patch:

* Data settings - "o2 Internet"
** APN: internet;
** other fields are empty or "Not defined".

* Message settings - "o2 Internet"
** APN: internet;
** MMS proxy: 82.113.100.5;
** MMSC: http://10.81.0.7:8002;
** other fields are empty or "Not defined".

I can send\receive MMS successfully.

How to get MCC and MNC? I don't see any output from "adb logcat | grep mnc"
Flags: needinfo?(azasypkin) → needinfo?(alberto.crespellperez)
Attachment #8467634 - Attachment is obsolete: true
Flags: needinfo?(alberto.crespellperez)
(In reply to Oleg Zasypkin [:azasypkin] from comment #13)
> Without the patch:
> 
> * Data settings - (custom settings), all fields are empty or "Not defined";
> * Message settings - (custom settings), all fields are empty or "Not
> defined";
> 
> With the patch:
> 
> * Data settings - "o2 Internet"
> ** APN: internet;
> ** other fields are empty or "Not defined".
> 
> * Message settings - "o2 Internet"
> ** APN: internet;
> ** MMS proxy: 82.113.100.5;
> ** MMSC: http://10.81.0.7:8002;
> ** other fields are empty or "Not defined".
> 
> I can send\receive MMS successfully.
> 
> How to get MCC and MNC? I don't see any output from "adb logcat | grep mnc"

Given that APN settings your mcc-mnc should be 262-07.

I updated the patch to show it in logcat, grep for mcc after the ftu.
Flags: needinfo?(azasypkin)
(In reply to Albert [:albert] from comment #15)
> (In reply to Oleg Zasypkin [:azasypkin] from comment #13)
> > Without the patch:
> > 
> > * Data settings - (custom settings), all fields are empty or "Not defined";
> > * Message settings - (custom settings), all fields are empty or "Not
> > defined";
> > 
> > With the patch:
> > 
> > * Data settings - "o2 Internet"
> > ** APN: internet;
> > ** other fields are empty or "Not defined".
> > 
> > * Message settings - "o2 Internet"
> > ** APN: internet;
> > ** MMS proxy: 82.113.100.5;
> > ** MMSC: http://10.81.0.7:8002;
> > ** other fields are empty or "Not defined".
> > 
> > I can send\receive MMS successfully.
> > 
> > How to get MCC and MNC? I don't see any output from "adb logcat | grep mnc"
> 
> Given that APN settings your mcc-mnc should be 262-07.
> 
> I updated the patch to show it in logcat, grep for mcc after the ftu.

Yep, it's 262-07
Flags: needinfo?(azasypkin)
Ok.

So I think that before bug 965826 landed you were connecting to wrong APN because it was different than the APN of comment 10.

As bug 965826 was requested by O2 people I am not sure that we should to do a backout in order to allow smartmobile.de to connect to O2 APN, we need to talk with O2 to clarify the way to proceed.

On the other hand, googling for smartmobile.de I see that customers configure manually the apn or using an OMA CP configuration message.

As Beatriz is on PTO until 8/25 and she is who is in contact with O2, I prepared a patch to fix the issue until she comes back.
Attached file Patch
Add smartmobile.de APN to local apn list.
Can you test if the attachment 8468336 [details] patch fixes the problem?
Flags: needinfo?(azasypkin)
(In reply to Albert [:albert] from comment #19)
> Can you test if the attachment 8468336 [details] patch fixes the problem?

Hmm, I can download MMS, but still unable to send it with "O2 MMS". Everything works with "o2 internet".

Maybe they have incorrect settings for "O2 MMS" at their website... Sent request to smartmobil.de support.
Flags: needinfo?(azasypkin)
(In reply to Oleg Zasypkin [:azasypkin] from comment #20)
> (In reply to Albert [:albert] from comment #19)
> > Can you test if the attachment 8468336 [details] patch fixes the problem?
> 
> Hmm, I can download MMS, but still unable to send it with "O2 MMS".
> Everything works with "o2 internet".
> 
> Maybe they have incorrect settings for "O2 MMS" at their website... Sent
> request to smartmobil.de support.

Any news?
Flags: needinfo?(azasypkin)
Sorry for the delay, here is what they replied (with auto translate from German :)):

Internet 
Name (Profile Name) Internet 
APN: internet.victorvox 
Username: not necessary 
Password: not required 
All other settings remain unchanged and it is not necessary that there registration occurs. 

MMS 
Name (Profile Name) MMS 
APN (Access Point) internet 
Username not necessary 
Password not required 
News Server (Home) http://10.81.0.7:8002 
WAP profile WAP 2.0 
MMS-C: http://10.81.0.7:8002 
MMS Proxy: 82.113.100.5:8080

So it looks similar to "o2 Internet" profile that works.
Flags: needinfo?(azasypkin)
Patch updated, please try again.
Flags: needinfo?(azasypkin)
(In reply to Albert [:albert] from comment #23)
> Patch updated, please try again.

Yes, with the latest patch I can send and receive MMS successfully.

Thanks!
Flags: needinfo?(azasypkin)
Attachment #8468336 - Flags: review?(josea.olivera)
QA Whiteboard: [2.0-signoff-need]
QA Whiteboard: [2.0-signoff-need] → [2.0-signoff-need+]
Comment on attachment 8468336 [details]
Patch

Removing review request in order to clarify with product team if this bug is valid.
Attachment #8468336 - Flags: review?(josea.olivera)
Flags: needinfo?(beatriz.rodriguezgomez)
Sorry for my delay.
We had checked O2 information and it seems that there is no agreement in place.

We need to close this bug as Invalid cause your provider is not covered by current APN list so you need to manually enter the settings or wait till your provider send a remote configuration message and accept it.

However, you can work in improving current situation by:
- Contact Android and add the APN to AOSP data base (https://android.googlesource.com/device/sample/+/master/etc/apns-full-conf.xml)
- After that, open a new bug here to ask for a new sync with AOSP, then your APN will be in FxOS list.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(beatriz.rodriguezgomez)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.