From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: provisioning APN using mbpi plugin
Date: Wed, 08 Feb 2017 10:54:18 -0600 [thread overview]
Message-ID: <96d52c22-bfde-7618-4ffc-1477a80686b3@gmail.com> (raw)
In-Reply-To: <1fdc62d3-5bb4-baec-39f6-ea0345f010ff@kerlink.fr>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hi Christophe,
> With this change, provisionning using plugins provision.c and mbpi.c
> works. It creates 9 contexts for my SIM, 4 of them are internet type
> contexts.
> In connman (I use connman above ofono), I see 4 services and I am able
> to connect at least 2 of them. So I wonder why duplicate context is
> considered an error by these plugins. Does anybody know ?
This is done on purpose. oFono & ConnMan are designed with the
assumption that the user will see what is being exposed by the D-Bus
API. The UI is just a thin client which simply renders the state of
ConnMan / oFono. Think of the D-Bus API as being user-visible. Thus it
makes no sense for us to expose services that the user cannot use.
There are a couple of ways to get around this:
- Use a more up-to-date database
- Have a provisioning UI that detects that provisioning has failed, and
guides the user through picking the right combination of operator / plan
/ etc and configures the context settings accordingly
There really should only be a single internet context configured for a
given SIM for the vast majority of users in the world.
Regards,
-Denis
next prev parent reply other threads:[~2017-02-08 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d9dfde3c-2b28-197f-f257-a7451d9871ed@kerlink.fr>
2017-02-08 12:24 ` provisioning APN using mbpi plugin Christophe Ronco
2017-02-08 16:54 ` Denis Kenzior [this message]
2017-02-16 16:46 ` Christophe Ronco
2017-02-16 18:02 ` Denis Kenzior
2017-02-17 14:44 ` [PATCH 0/2] Add provisioning plugin from configuration file Christophe Ronco
2017-02-17 14:44 ` [PATCH 1/2] provision: add plugin to provision from config file Christophe Ronco
2017-02-17 14:44 ` [PATCH 2/2] plugins: support for provisioning " Christophe Ronco
2017-02-21 17:12 ` [PATCH 0/2] Add provisioning plugin from configuration file Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96d52c22-bfde-7618-4ffc-1477a80686b3@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox