APN Editor: Issues with 'Same APN as for Internet' checkbox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-system-settings (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
ubuntu-system-settings (Ubuntu RTM) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
ofono on Ubuntu currently supports three distinct APN types:
* Internet
* MMS
* Combined Internet/MMS
The value of the 'Type' property for Internet and MMS is just lower-cased versions of each. A combined Internet/MMS APN is of type 'internet', but has the additional MMS properties 'MessageCenter' and 'MessageProxy'. Here's an example for ATT:
[context1]
Name=ATT Phone
AccessPointName
Username=
Password=
Type=internet
Protocol=ip
MessageProxy=
MessageCenter=http://
The current APN Editor doesn't allow a user any way to view the current MessageCenter ( aka MMSC ) or MessageProxy ( aka Proxy & Port ) of an existing APN ( ie. provisioned by ofono ). There's a bit of overlap with bug #1388222. The only way a user can even tell that an APN is combined currently is if the APN is active; in this case the "Same APN as for Internet" will show a checkmark.
<https:/
Also, there's no way for a user to extend an existing APN by adding MMS parameters to it. The Networking specification states that the "Same APN as for Internet" should be on the Custom MMS page, but it's currently a list item in the MMS APN list.
Futhermore, if the checkbox were to move to the Custom MMS page, it could only be used in the existing model if there was an active Internet APN. Finally, the editor would need to ensure that it added the new attributes to the existing Internet APN vs. creating a brand new Custom MMS APN. If the checkmark moves, then it makes it hard to identify combined APNs from the top-level lists ( see above ).
<https:/
Finally, we also will need to protect against a user selecting a Custom MMS APN when the current active Internet APN already supports MMS. This would lead to undefined behavior.
This bug is being reported against vivid-devel on mako, image #136, but also exists in RTM.
Status changed to 'Confirmed' because the bug affects multiple users.