User Story: As an OEM, I want to be able to specify which messaging APN, Identifer, Password, HTTP proxy host, HTTP proxy port, MMS proxy, MMS port and MMSC should be used on the device based on the MNC/MCC setting from the SIM card inserted in order to target customizations to locales without needing to use separate builds. Acceptance Criteria: 1. If a certain messaging settings (including APN, Identifier, Password, HTTP proxy host, HTTP proxy port, MMS proxy, MMS post and MMSC) are specified to be included for an MNC/MCC combination, and a SIM card with that MNC/MCC combination is inserted into the device the messaging settings used by the device are those specified. 2. If no SIM card is inserted, the specified default messaging settings are used by the device. Note: this functionality should already exists - this user story is just to ensure the inclusion of integration tests and QA test verification.

Ghislain 'Aus' Lacroix changed story state to started in Pivotal Tracker

Fixed: https://github.com/mozilla-b2g/gaia/commit/cfcea746250d7c6ea01a389c3d7714c471f28641

Ghislain 'Aus' Lacroix changed story state to accepted in Pivotal Tracker

Ghislain 'Aus' Lacroix changed story state to accepted in Pivotal Tracker

Ghislain 'Aus' Lacroix changed story state to accepted in Pivotal Tracker

Reopening this, see bug 898409 comment 13 for the details.

Landed as part of pull request for Bug 891725, which also contained revert revert and fix. A sad mess I will try not to repeat. https://github.com/mozilla-b2g/gaia/pull/12121

Aus - Can you provide a sample customization showcasing how this could work?

See https://github.com/mozilla-b2g/gaia/tree/master/shared/resources/apn for the README.md See https://github.com/mozilla-b2g/gaia/blob/master/shared/resources/apn.json#L3179 for what is the final output file that we actually load and parse at run-time. I pointed you to the test data we use. The MMS settings are the ones of interest for this bug.