1146739 - [HOMO][TMO 63339][MMS]Device device does not acknowledges download of MMS

Status: RESOLVED DUPLICATE of bug 1150368

(Firefox OS Graveyard :: RIL, defect, P1)

Description

[sync-1]

Mozilla Build ID: 20141019000201  
 Description:
 Device device does not acknowledges download of MMS by sending an "M-acknowledge-ind" message
 Trace attached.
 
 steps to reproduce:
 1)set auto retrieve of MMS to off
 2)send MMS to device
 3)device notifies user about received MMS, but do not download it
 4)download MMS
 5)packet which contains "M-acknowledge-ind" is not sent
 
 Expected Behaviour:
 Terminal acknowledges download of MMS by sending a MMSE packet  "M-acknowledge-ind" with status "Retrieved" back to MMSC.
 		
 
  DEFECT DESCRIPTION:
 
  REPRODUCING PROCEDURES:
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: From this picture, we can see the "m-acknowledge-ind"

Comment 2

[sync-1]

Attachment: How to use tcpdump to grap mms package?

Comment 3

[sync-1]

Attachment: From this picture, we can see the "m-acknowledge-ind"

Comment 4

[sync-1]

Attachment: How to use tcpdump to grap mms package?

Comment 5

[sync-1]

Attachment: From this picture, we can see the "m-acknowledge-ind"

Comment 6

[sync-1]

Attachment: How to use tcpdump to grap mms package?

Comment 7

[sync-1]

Attachment: From this picture, we can see the "m-acknowledge-ind"

Comment 9

[Wesly Huang (EPM)]

Hi [e-mail]:

quickly discussed with RD, would you help clarify the problem or request here? Per comment#0 the problem is "M-acknowledge-ind" not sent. But you can actually see it in attachment?

So what's the issue we are trying to solve, would you help clarify? Thanks.

Comment 10

[田旻]

(In reply to Wesly Huang from comment #9)
> Hi [e-mail]:
> 
> quickly discussed with RD, would you help clarify the problem or request
> here? Per comment#0 the problem is "M-acknowledge-ind" not sent. But you can
> actually see it in attachment?
> 
> So what's the issue we are trying to solve, would you help clarify? Thanks.

Some attachments come from Shanghai validation center, they can't reproduce this bug either. So you can see the M-acknowledge-ind in it. Actually, we can't reproduce this bug all the time. But our customer just propose this kind of bug again and again in a block status. We are still waiting for their logs about this problem. Please refer bug#1150368, they are the same one.

Comment 11

[Wesly Huang (EPM)]

(In reply to 田旻 from comment #10)
> (In reply to Wesly Huang from comment #9)
> > Hi [e-mail]:
> > 
> > quickly discussed with RD, would you help clarify the problem or request
> > here? Per comment#0 the problem is "M-acknowledge-ind" not sent. But you can
> > actually see it in attachment?
> > 
> > So what's the issue we are trying to solve, would you help clarify? Thanks.
> 
> Some attachments come from Shanghai validation center, they can't reproduce
> this bug either. So you can see the M-acknowledge-ind in it. Actually, we
> can't reproduce this bug all the time. But our customer just propose this
> kind of bug again and again in a block status. We are still waiting for
> their logs about this problem. Please refer bug#1150368, they are the same
> one.

Thanks, I see. Then I propose to duplicate this one to 1150368 since they are the same, and more discussion is made there already.

Also in latest status of 1150368, more log with error symptom will be needed to proceed further analysis, please help attached it there once available, thanks.

Comment 12

[田旻]

(In reply to Wesly Huang from comment #11)
> (In reply to 田旻 from comment #10)
> > (In reply to Wesly Huang from comment #9)
> > > Hi [e-mail]:
> > > 
> > > quickly discussed with RD, would you help clarify the problem or request
> > > here? Per comment#0 the problem is "M-acknowledge-ind" not sent. But you can
> > > actually see it in attachment?
> > > 
> > > So what's the issue we are trying to solve, would you help clarify? Thanks.
> > 
> > Some attachments come from Shanghai validation center, they can't reproduce
> > this bug either. So you can see the M-acknowledge-ind in it. Actually, we
> > can't reproduce this bug all the time. But our customer just propose this
> > kind of bug again and again in a block status. We are still waiting for
> > their logs about this problem. Please refer bug#1150368, they are the same
> > one.
> 
> Thanks, I see. Then I propose to duplicate this one to 1150368 since they
> are the same, and more discussion is made there already.
> 
> Also in latest status of 1150368, more log with error symptom will be needed
> to proceed further analysis, please help attached it there once available,
> thanks.
> 
> *** This bug has been marked as a duplicate of bug 1150368 ***

OK.