Nuntium assumes a single MMS context

[Antti Kaijanmäki]

due to early architectural decisions our platform is only capable of dealing with one actual MMS context in the system (type="mms"). This is unfortunate as it makes creating a custom MMS in APN editor harder.

It also is unfortunate as with the Internet contexts, there might be different MMS contexts for operator and MVO's. Currently we are not able to show any of the options.

I will make APN editor to have two choices with MMS. Either "Same as Internet APN" if the internet APN is a dual context. Or "Custom".

[Tony Espy (awe)]

This is not an "architectural" problem. We made a design decision based on the fact that none of the operators defined in apns-conf.xml specify more than a single MMS context. As such, we didn't feel the need at the time to build some kind of settings mechanism for nuntium to allow a settings application to tell nuntium which context to use. I will add a nuntium task, as it wouldn't be that difficult to add ( ie. a simple DBus call like SetPreferredContext ).

My guess is that the current nuntium behavior is to use the first MMS context it finds.

Furthermore, we probably need to handle this anyways there's no guarantee that an operator might specify more then one MMS context in the future, and I also believe that the customization provisioning mechanism ( eg. /custom/etc/apns-conf.xml is searched if found on disk ) also could be used to force this to happen as well ( it'd be stupid, but it could happen ).

MVNO APNs are handled specially, if an APN context is found based on MVNO-matching, then all non-MVNOs from the query are thrown out.

[Antti Kaijanmäki (kaijanmaki)]

Thanks tony for your comments.

Actually this also affects ofono. After nuntium can deal with multiple MMS contexts, ofono provision plugin must remove it's limit of max. 1 MMS APN being provisioned.

[Antti Kaijanmäki (kaijanmaki)]

settings as Medium as this is clearly post RTM work.

[Tony Espy (awe)]

@Antti

I'm not sure why you're focusing on the provisioning plugin. I reviewed the code and it looks like I was incorrect about there being an internal limit. None of the operators define more than one MMS context, so this is something could never happen up until the customization hooks were added to the provisioning plugin.

[Tony Espy (awe)]

Marked ofono task as Invalid.

Assigned nuntium task to Sergio. This probably should just be marked a duplicate of nuntium bug #1370659.