cannot receive MMS using AT+T
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
messaging-app |
Fix Released
|
High
|
Tiago Salem Herrmann | ||
mobile-broadband-provider-info (Ubuntu) |
Invalid
|
High
|
Mathieu Trudel-Lapierre | ||
network-manager (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
nuntium (Ubuntu) |
Fix Released
|
Undecided
|
Sergio Schvezov | ||
ofono (Ubuntu) |
Fix Released
|
High
|
Tony Espy |
Bug Description
using build 51
MMS recv support is enabled but I cannot receive any attachments with At+t as my service provider. I tried with both wifi enabled and disabled
Here are the logs and contexts
phablet@
[ /ril_0 ]
[ /ril_0/context1 ]
Protocol = ip
Name = ATT Phone
Username =
Active = 0
Settings = { }
Password =
Type = internet
[ /ril_0/context2 ]
Protocol = ip
Name = ATT WAP
Username =
Active = 0
Settings = { }
Password =
Type = internet
[ /ril_0/context3 ]
Protocol = ip
Name = TracFone
Username =
Active = 0
Settings = { }
Password =
Type = internet
[ /ril_0/context4 ]
Protocol = ip
Name = LaptopConnect (data cards)
Username =
Active = 1
Settings = { Address=
Password =
Type = internet
[ /ril_0/context5 ]
Protocol = ip
Name = Data Connect (old)
Username =
Active = 0
Settings = { }
Password =
Type = internet
[ /ril_0/context6 ]
Protocol = ip
Name = LTE
Username =
Active = 0
Settings = { }
Password =
Type = internet
[ /ril_0/context7 ]
Protocol = ip
Name = Internet
Username =
Active = 0
Settings = { }
Password =
Type = internet
nuntium.log:
phablet@
2014/05/28 09:25:49 Received ReceiveNotifica
2014/05/28 09:25:49 Push data
00000000 01 06 27 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76 |..'application/v|
00000010 6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61 |nd.wap.mms-messa|
00000020 67 65 00 af 84 8d 01 81 b4 84 8c 82 98 43 44 30 |ge...........CD0|
00000030 35 32 38 31 33 32 35 34 35 34 30 30 30 33 38 30 |5281325454000380|
00000040 30 30 30 30 30 30 30 30 00 8d 90 89 18 80 2b 31 |00000000......+1|
00000050 36 31 37 36 39 39 30 36 35 35 2f 54 59 50 45 3d |6176990655/TYPE=|
00000060 50 4c 4d 4e 00 96 02 ea 00 8a 80 8e 02 80 00 88 |PLMN............|
00000070 05 81 03 05 46 00 83 68 74 74 70 3a 2f 2f 31 36 |....F..http://
00000080 36 2e 32 31 36 2e 32 33 30 2e 35 3a 38 30 31 35 |6.216.230.5:8015|
00000090 2f 30 35 32 38 31 33 32 35 34 35 34 30 30 30 33 |/052813254540003|
000000a0 38 30 30 30 30 30 30 30 30 30 00 |8000000000.|
Setting HeaderLength to 39
Setting ContentType to application/
Setting ApplicationId to 4
Setting TransactionId to CD0528132545400
Setting Version to 0x10 == 16
Setting From to +16176990655/
Next string encoded with: utf-8
Setting Subject to
Setting Class to 0x80 == 128
Setting Size to 32768
Expiry token: 81
Message Expiry 197958, 0
Setting ContentLocation to http://
2014/05/28 09:25:49 Context type: internet MessageCenter: http://
2014/05/28 09:25:49 Context type: internet MessageCenter: http://
2014/05/28 09:25:49 Context type: internet MessageCenter: http://
2014/05/28 09:25:49 Context type: internet MessageCenter: MessageProxy: Active: true
2014/05/28 09:25:49 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:25:49 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:25:49 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:25:49 Cannot activate ofono context: No mms contexts found
2014/05/28 09:29:16 Received ReceiveNotifica
2014/05/28 09:29:16 Push data
00000000 01 06 27 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76 |..'application/v|
00000010 6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61 |nd.wap.mms-messa|
00000020 67 65 00 af 84 8d 01 81 b4 84 8c 82 98 41 36 30 |ge...........A60|
00000030 35 32 38 31 33 32 39 31 31 35 30 30 30 31 38 30 |5281329115000180|
00000040 30 30 30 35 30 30 30 30 00 8d 90 89 18 80 2b 31 |00050000......+1|
00000050 36 31 37 36 39 39 30 36 35 35 2f 54 59 50 45 3d |6176990655/TYPE=|
00000060 50 4c 4d 4e 00 96 02 ea 00 8a 80 8e 02 80 00 88 |PLMN............|
00000070 05 81 03 05 46 00 83 68 74 74 70 3a 2f 2f 31 36 |....F..http://
00000080 36 2e 32 31 36 2e 31 39 38 2e 35 3a 38 30 30 38 |6.216.198.5:8008|
00000090 2f 30 35 32 38 31 33 32 39 31 31 35 30 30 30 31 |/052813291150001|
000000a0 38 30 30 30 30 35 30 30 30 30 00 |8000050000.|
Setting HeaderLength to 39
Setting ContentType to application/
Setting ApplicationId to 4
Setting TransactionId to A60528132911500
Setting Version to 0x10 == 16
Setting From to +16176990655/
Next string encoded with: utf-8
Setting Subject to
Setting Class to 0x80 == 128
Setting Size to 32768
Expiry token: 81
Message Expiry 197958, 0
Setting ContentLocation to http://
2014/05/28 09:29:16 Context type: internet MessageCenter: http://
2014/05/28 09:29:16 Context type: internet MessageCenter: http://
2014/05/28 09:29:16 Context type: internet MessageCenter: http://
2014/05/28 09:29:16 Context type: internet MessageCenter: MessageProxy: Active: true
2014/05/28 09:29:16 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:29:16 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:29:16 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:29:16 Cannot activate ofono context: No mms contexts found
2014/05/28 09:55:20 Received ReceiveNotifica
2014/05/28 09:55:20 Push data
00000000 01 06 27 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76 |..'application/v|
00000010 6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61 |nd.wap.mms-messa|
00000020 67 65 00 af 84 8d 01 81 b4 84 8c 82 98 43 37 30 |ge...........C70|
00000030 35 32 38 31 33 35 34 35 39 34 30 30 30 32 31 30 |5281354594000210|
00000040 30 30 30 36 30 30 30 30 00 8d 90 89 18 80 2b 31 |00060000......+1|
00000050 36 31 37 36 39 39 30 36 35 35 2f 54 59 50 45 3d |6176990655/TYPE=|
00000060 50 4c 4d 4e 00 96 02 ea 00 8a 80 8e 02 80 00 88 |PLMN............|
00000070 05 81 03 05 46 00 83 68 74 74 70 3a 2f 2f 31 36 |....F..http://
00000080 36 2e 32 31 36 2e 32 33 30 2e 35 3a 38 30 30 39 |6.216.230.5:8009|
00000090 2f 30 35 32 38 31 33 35 34 35 39 34 30 30 30 32 |/052813545940002|
000000a0 31 30 30 30 30 36 30 30 30 30 00 |1000060000.|
Setting HeaderLength to 39
Setting ContentType to application/
Setting ApplicationId to 4
Setting TransactionId to C70528135459400
Setting Version to 0x10 == 16
Setting From to +16176990655/
Next string encoded with: utf-8
Setting Subject to
Setting Class to 0x80 == 128
Setting Size to 32768
Expiry token: 81
Message Expiry 197958, 0
Setting ContentLocation to http://
2014/05/28 09:55:20 Context type: internet MessageCenter: http://
2014/05/28 09:55:20 Context type: internet MessageCenter: http://
2014/05/28 09:55:20 Context type: internet MessageCenter: http://
2014/05/28 09:55:20 Context type: internet MessageCenter: MessageProxy: Active: true
2014/05/28 09:55:20 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:55:20 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:55:20 Context type: internet MessageCenter: MessageProxy: Active: false
2014/05/28 09:55:20 Cannot activate ofono context: No mms contexts found
phablet@
phablet@
phablet@
tags: | added: rtm14 |
Changed in messaging-app: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in ofono (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in nuntium (Ubuntu): | |
status: | New → Invalid |
Changed in network-manager (Ubuntu): | |
status: | New → Triaged |
no longer affects: | ofono |
Changed in messaging-app: | |
status: | Confirmed → Invalid |
description: | updated |
Changed in mobile-broadband-provider-info (Ubuntu): | |
status: | Triaged → Invalid |
Changed in ofono (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in nuntium (Ubuntu): | |
status: | New → Invalid |
Changed in messaging-app: | |
status: | Confirmed → Fix Released |
Changed in nuntium (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in network-manager (Ubuntu): | |
status: | Triaged → Fix Released |
The cause of this bug is that our current GPRS/MMS provisioning strategy is over-ambitious in that it attempts to provision from both mobile- broadband- provider- info ( /usr/share/ mobile- broadband- provider/ serviceprovider s.xml ) and apns-conf.xml ( located in /system/etc, and part of our android package ).
A couple of points...
1. Our provisioning plugin is part of the Ubuntu ofono package. It's called android-provision, it's source code can be found here:
https:/ /github. com/rilmodem/ ofono/blob/ master/ plugins/ android- provision. c
It first queries apns-conf, then queries mbpi and will only add results from mbpi if their no collision with an already added APN from apns-conf that has the same value for "apn".
2. The second point is that provisioning works by grabbing all of the APNs that match a particular set of criteria pulled from the SIM card ( mobile- country- code, mobile- network- code, servic- provider- name, ... ). It's then NetworkManager's responsibility to try each in sequence and when it finds one that works, mark that APN/connection with a "last-connected -time".
3. Some operators define stand-alone APNs for MMS usage. These APNs are not affected by this problem. Unfortunately AT&T uses the mixed context type.
4. With our current logic, it's possible that more than one context is provisioned that is valid for Internet/GPRS usage by a particular subscriber. In your case, both "ATT Phone" and "Laptop Connect (data cards)" are valid. If "ATT Phone" had been the context activated, everything would have worked, but in this case NM chose "Laptop Connect (data cards)" which doesn't support MMS, so this is why MMS doesn't work.
5. The mbpi APN was used for one of two reasons.... a) there used to be a bug in NM where it didn't walk thru the APNs in sequence or b) NM tried to activate "ATT Phone", failed, and thus moved on to "Laptop Connect (data cards)". My guess is that the latter happened, but without the syslog, it's hard to tell. My guess though is that it's case (b), as I'm pretty sure (a) was fixed before image #51 was released.