GNOME Bugzilla – Bug 639953
austrian provider bob reports as roaming in its "own" network
Last modified: 2014-03-10 18:38:16 UTC
Hello dear maintainer as said in the below bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608966 Austrian provider bob reports as roaming always and wont connect if " roaming only " is enabled in some cases More details on the above bug link regards
just a small update: recent Ubuntu update manager versions rely on the "roaming" information to show big warnings when downloading package updates over roaming connections (the "this could turn out to be expensive" type) -- this issue gets slightly more imporant the more often the provider database is queried.
The modem reports to be 'roaming' when it is not in its own home network, and that is the information ModemManager exposes. Now, being 'roaming' (not in home network) doesn't necessarily mean that the user will get charged more. It may just be that the modem is connected to one of the networks in the SPDI list (list of networks allowed to automatically connect to when home network is not around). I do have this same exact issue with my operator (Yoigo) which relies on another network (Movistar) when using plain GPRS/EDGE. Phones will usually show your own home network name both when you're in your own home network and when you're camping in a network listed in the SPDI list. That's why in my example my phone always tells me "Yoigo" even when I'm sitting in Movistar's 2G network, while MM tells me "Movistar". We don't do this yet in ModemManager, but we have some unmerged bits to manage this information: http://cgit.freedesktop.org/ModemManager/ModemManager/log/?h=display-rules But again, the display rules only affect which is the Operator Name to show in the UI; not the real roaming status. We could use the info in the SPDI list to say whether the current network is in there or not, but not sure if that's the best option. Maybe there's some other standard way to handle that situation w.r.t. roaming status, will try to look for it.
Handling this in the new bug 726052. *** This bug has been marked as a duplicate of bug 726052 ***