Cannot receive MMS from some devices

Bug #1336146 reported by Martti Piirainen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nuntium (Ubuntu)
Fix Released
High
Sergio Schvezov

Bug Description

I tested receiving a simple MMS (a picture + a short text) that were sent from three different phones. Reception was successful only in one of the three cases.

Attached are nuntium logs + nuntium store, contains these three attempts:
1. From a Jolla device (Sailfish OS 1.0.7.16). The message is not visible in the UI, although I can't spot any error in the nuntium logs (timestamp 07:49).
2. From a Nexus 4 device (Android 4.2.2). The message is successfully shown (timestamp 07:53).
3. From a Nokia C6-01 device (Symbian OS 111.030.0609). There is an "Unable to decode m-retrieve.conf: Unhandled length" error in the nuntium logs (timestamp 08:13).

In all cases, the same SIM card was used in the sending device. Information on the receiving device:
system-image-cli -i
current build number: 105
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-06-30 08:30:08
version version: 105
version ubuntu: 20140630
version device: 20140625

Related branches

Revision history for this message
Martti Piirainen (piiramar) wrote :
Revision history for this message
Martti Piirainen (piiramar) wrote :
Revision history for this message
Tony Espy (awe) wrote :

I just tried sending a MMS where I took a photo specifically for the MMS and sent it by itself on a Nexus 5 running KitKat.

I failed to receive the MMS on mako running image #107.

@Sergio, let me know if you'd like me to attach my nuntium store. Also how do I enable/retrieve the nuntium log messages?

Changed in nuntium (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Sergio Schvezov (sergiusens)
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

@martti for case 1 there's not much I can do to figure this out; it may be telepathy-ofono since I see this <!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 1.0//EN" "http://www.w3.org/TR/REC-smil/SMIL10.dtd">

can you rerun in any case with a dbus monitor running like:

dbus-monitor sender=org.ofono.mms

I'm interested in the MessageAdded signal (which nuntium logs if it fails to send and I'm not seeing that here); telepathy-ofono then picks that up and does it's magic

Good for 2! :-P

For 3 I'll be checking that tonight or tomorrow.

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

needless to say, 1 and 3 are different bugs ;-)

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

@tony; please attach the logs and if there is a decode failure; provide the store data. A word of warning; if the payload gets modified by the backend you might be out of luck. Sometimes when I send an image from Android I don't get the MMS all the way to the UI since we don't support operator messages like there:

The operator can do this with the attachments:
- "Excess message size - part was removed: image/jpeg; name=image.jpg"
- "Part with unsupported media type was stripped from the message: application/ogg; name=Aquila.ogg"

There are also some radius errors that can happen and I'm still debating with Tiago how to manage rinse and repeat downloads for messages.

Revision history for this message
Martti Piirainen (piiramar) wrote :

> @martti for case 1 there's not much I can do to figure this out
I added some extra logging in nuntium. Some sort of parsing failure seems to happen in this line http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/nuntium/utopic/view/head:/telepathy/service.go#L152 , the GetSmil() call returns "Cannot find SMIL data part". Not sure what that means, as the content type 'application/smil' and the actual SMIL XML are printed in the log earlier. As a result, the MMS is not signalled to tp-ofono.

Revision history for this message
Martti Piirainen (piiramar) wrote :

Tested with nuntium 0.1+14.10.20140621sergiusens9-0ubuntu1 from the phablet-team/telephony PPA. Both cases 1 (Jolla) and 3 (Nokia C6) are fixed, MMS messages are successfully received in the UI. Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nuntium - 0.1+14.10.20140702.2-0ubuntu1

---------------
nuntium (0.1+14.10.20140702.2-0ubuntu1) utopic; urgency=low

  [ CI bot ]
  * Upload support while moving udm to it's new package namespace
  * SendMessage telepathy service support with necessary encoder fixes.

  [ Sergio Schvezov ]
  * Improving incoming dbus method call handling for the mms service
    interface
  * Waiting for calls to GetServices on the proper interface
  * Adding a minimal telepathy message interface
  * Fixing recv for multiple recipients.
  * Making decoding less verbose and logging information on errors only
  * Adding encode -> decode tests for the cases where decoding is the
    inverse function of encoding.
  * Relaxing matching for smil media type
  * Length bound checks fix (LP: #1336146)
  * Sending MessageAdded with draft Status for new outgoing messages
 -- Ubuntu daily release <email address hidden> Wed, 02 Jul 2014 21:15:22 +0000

Changed in nuntium (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Kalpesh Bafna (kalpeshb84) wrote :

I am seeing a similar bug mentioned in case 1 in android 4.2.2 , but i am getting this bug only at specific location and for specific mobile operator and for the specific audio file format i.e ogg

I am using the Android 4.2.2 at the warsaw location with the T-mobile operator, whenever anybody send the an audio file of type ogg, the MMS attachment is not deliver to the UI instead i get the below msg

"Part with unsupported media type was stripped from the message: application/ogg name=Bollywood.ogg"

Please find the attached screen shot of the error msg
Please let me know whether it is an operator issue or it is an android bug.

Regards,
Kalpesh Bafna

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.