Closed
Bug 862263
Opened 12 years ago
Closed 12 years ago
[MMS][User Story] Support sending retry for MMS
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:leo+, b2g18 fixed)
People
(Reporter: khu, Assigned: vicamo)
References
()
Details
(Keywords: feature)
Should we need to support sending retry for MMS? Thanks!
Reporter | ||
Updated•12 years ago
|
blocking-b2g: --- → leo?
Flags: needinfo?(ffos-product)
Updated•12 years ago
|
Blocks: mms-userstories
Summary: Support sending retry for MMS → [MMS][User Story] Support sending retry for MMS
Comment 1•12 years ago
|
||
Checking our specs:
Message Reattempt Policy: If sending fails the device will retry based on a retry schema if the error is considered temporary (Examples of temporary errors are: device resources not available, WAP Gateway not reached, MMSC not available etc)
The vendor must give the report of reattempting period that is supported by the handset for the downloading of the MMS message pending notifications.
It has, minimum, TWO reattempts of the MMS message pending notifications.
Comment 2•12 years ago
|
||
Over to vicamo to start - please reassign as you see fit.
Assignee: nobody → vyang
blocking-b2g: leo? → leo+
Updated•12 years ago
|
Flags: needinfo?(ffos-product)
Assignee | ||
Comment 3•12 years ago
|
||
Retry send has been resolved in bug 842235.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-b2g18:
--- → fixed
Assignee | ||
Comment 5•12 years ago
|
||
no, it's no related to commercial ril, and no interface changed.
Flags: needinfo?(vyang)
Updated•12 years ago
|
Flags: in-moztrap?
Updated•12 years ago
|
Flags: in-moztrap? → in-moztrap+
You need to log in
before you can comment on or make changes to this bug.
Description
•