Closed
Bug 1007542
Opened 10 years ago
Closed 10 years ago
Add Phone Number into FROM Field of MMS Header when transmitting MMS PDU to network.
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(tracking-b2g:backlog, firefox30 wontfix, firefox31 wontfix, firefox32 fixed, b2g-v1.4 fixed, b2g-v2.0 fixed)
People
(Reporter: bevis, Assigned: bevis)
References
Details
(Whiteboard: [caf priority: p2][p=1] [cr 654132])
Attachments
(1 file)
2.44 KB,
patch
|
vicamo
:
review+
praghunath
:
approval-mozilla-b2g30+
|
Details | Diff | Splinter Review |
*** This is a duplicated bug to Bug 995486 *** I'd like describe the handling of FROM field in MMS header more specifically in this bug. According to the |From| field defined in |6.1.1 Send Request| & |6.7.2 PDU Read Report | of OMA MMS Encapsulation Protocol [2]: " The originator MMS Client MUST send either its address or an |Insert-address-token|. In case of token, the MMS Proxy-Relay MUST insert the correct address of the originator MMS Client. " In current FFOS implementation, we choose to fill |Insert-address-token| to leave this to MMS Proxy-Relay. However, Some Operator not allow to have |Insert-address-token| specified, which didn't obey the OMA requirement: "In case of token, the MMS Proxy-Relay MUST insert the correct address of the originator MMS Client" (See Bug 995486 for the error reported from VzW network.) After comparing the implementation in AOSP, we found that in AOSP implementation, the line number will be used to replaced |Insert-address-token| if available. [1][2] The solution for this bug is to specified the phone number into FROM field to increase the compatibility of more carrier. [1] http://androidxref.com/4.3_r2.1/xref/packages/apps/Mms/src/com/android/mms/transaction/SendTransaction.java#108 [2] http://androidxref.com/4.3_r2.1/xref/packages/apps/Mms/src/com/android/mms/transaction/ReadRecTransaction.java#84
Assignee | ||
Comment 1•10 years ago
|
||
Verify Pass with following UICC: CHT(Empty MSISDN), TMO(MSISDN without international TON), CU (MSISDN with international TON).
Attachment #8419235 -
Flags: review?(vyang)
Updated•10 years ago
|
blocking-b2g: --- → backlog
Updated•10 years ago
|
Attachment #8419235 -
Flags: review?(vyang) → review+
Assignee | ||
Updated•10 years ago
|
Whiteboard: [p=1]
Target Milestone: --- → 2.0 S1 (9may)
Comment 2•10 years ago
|
||
This feature have to apply to v1.4 for commercialization.
Assignee | ||
Comment 3•10 years ago
|
||
update try server result: https://tbpl.mozilla.org/?tree=Try&rev=5cc71598af23
status-b2g-v1.4:
--- → affected
Keywords: checkin-needed
Assignee | ||
Comment 4•10 years ago
|
||
Comment on attachment 8419235 [details] [diff] [review] Patch v1 - Add Phone Number into FROM Field of MMS Header when transmitting MMS PDU to network. r=vyang. NOTE: This flag is now for security issues only. Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): N/A. This is because some carrier didn't follow the OMA standard when FROM in MMS header is equal to insert-address-token. According to OMA standard, MMS client can either fill the address or the insert-address-token. To be more compatible with more carriers, we filled the address proactively if it's already available in inserted UICC. User impact if declined: can not get the certificate from carrier. Testing completed: Yes. Risk to taking this patch (and alternatives if risky): No String or UUID changes made by this patch:No
Attachment #8419235 -
Flags: approval-mozilla-b2g30?
Updated•10 years ago
|
Attachment #8419235 -
Flags: approval-mozilla-b2g30? → approval-mozilla-b2g30+
Comment 5•10 years ago
|
||
Approved for 1.4
Updated•10 years ago
|
blocking-b2g: 1.4? → backlog
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/9c0299e910bf
Keywords: checkin-needed
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9c0299e910bf
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 9•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/d017bbb0fd61
status-b2g-v2.0:
--- → fixed
status-firefox30:
--- → wontfix
status-firefox31:
--- → wontfix
status-firefox32:
--- → fixed
Updated•10 years ago
|
Whiteboard: [p=1] [cr 654132] → [caf priority: p2][p=1] [cr 654132]
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•