Bug 85010

Summary:	Treat registrations to operators in the SPDI list as non-roaming
Product:	ModemManager	Reporter:	Aleksander Morgado <aleksander>
Component:	general	Assignee:	ModemManager bug user <modemmanager>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Aleksander Morgado 2014-10-14 16:31:22 UTC

Originally reported at:
  https://bugzilla.gnome.org/show_bug.cgi?id=726052

There are multiple virtual operators which don't have their own networks, and
re-use networks from other providers. When using a SIM card from one of these
virtual operators, ModemManager will show in the 3GPP registration info the
service provider network (i.e. the operator name/MCCMNC of the network in which
the device is registered), and it will also show the registration as roaming.
It technically is roaming; but logicaly isn't, as the network to which the
device is registered is to be treated as 'home'.

So, registrations to networks available in the SPDI list of the SIM card (list
which provides home-like networks) shouldn't be marked as roaming; and the User
Interface should follow the rules marked by the SIM card to decide which
Operator Name to show in the interface (either the name of the operator which
issued the SIM card or the name of the SPN).

Work to start handling this is already available in the 'aleksander/display-rules' in git,
see:
http://cgit.freedesktop.org/ModemManager/ModemManager/log/?h=aleksander/display-rules

Comment 1 GitLab Migration User 2018-06-10 09:04:45 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/58.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.