Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Problems provisioning APN from SIMs
Date: Thu, 04 Jun 2015 17:16:14 -0500	[thread overview]
Message-ID: <5570CE2E.4020305@gmail.com> (raw)
In-Reply-To: <5570CA31.6070002@dynamicdevices.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Hi Alex,

 > As I come to investigate this, I find I am concerned about using the
> Service Provider Name as I can't see any registry for those names, it's
> free text for display purposes, so I assume it is at least possible it
> might change without warning,
> whereas there does seem to be a registry for MCC/MNC (e.g.
> http://www.mcc-mnc.com/)

In theory MCC/MNC should be unique even for MVNOs.  But some have not 
followed that properly.  SPN is free-form, but it probably doesn't 
change all that often.  The provisioning database would have to be 
updated frequently.

If you know you will only need a subset of particular providers, it 
might be easier to develop your own provisioning db.

>
> I am thinking it may be preferable to use the registered IIN number from
> the ICCID - http://www.controlf.net/iccid/
>
> This seems a more controlled way of providing the uniqueness needed to
> me and presumably it's easy enough to read the ICCID out, if it's not
> already being read out.
>

I don't recall that any provisioning (proprietary or otherwise) database 
used ICCID as an identifier.  Not saying it won't work, so feel free to 
investigate what is possible.

Regards,
-Denis


  parent reply	other threads:[~2015-06-04 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 12:07 Problems provisioning APN from SIMs Alex J Lennon
2015-06-04 19:52 ` Denis Kenzior
2015-06-04 20:23   ` Alex J Lennon
2015-06-04 21:03     ` Denis Kenzior
2015-06-04 21:59       ` Alex J Lennon
2015-06-04 22:05         ` Alex J Lennon
2015-06-04 22:16         ` Denis Kenzior [this message]
2015-06-04 22:30         ` Marcel Holtmann
2015-06-04 22:50         ` Marcel Holtmann
2015-06-04 23:48           ` Denis Kenzior
2015-06-05  8:29             ` Alex J Lennon
2015-06-12 13:09               ` Alex J Lennon

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=5570CE2E.4020305@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