This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi Oliver,
On Tue, Feb 05, 2019 at 10:34:04AM +0100, Oliver Smith wrote:
> On 1/14/19 3:03 AM, Neels Hofmeyr wrote:
> > I placed the draft in osmo-msc/doc/interMSC_HO_GSUP_msgs.txt on my branch neels/ho:
> > http://git.osmocom.org/osmo-msc/tree/doc/interMSC_HO_GSUP_msgs.txt?h=neels/ho
>
> In your draft, you describe the handover_number IE like this:
>
> > handover_number: (MSC-A <-- MSC-B, Handover Request Ack)
> > extension: [Extension=0|NoExtension=1] (1 bit; should currently always be == 1)
> > nature_of_nr: [GSM340_TYPE_NATIONAL|GSM340_TYPE_INTERNATIONAL|...] (3 bit)
> > number_plan: GSM340_PLAN_ISDN (4 bit)
> > msisdn: BCD
>
> GSUP already has a msisdn IE:
>
> https://git.osmocom.org/libosmocore/tree/include/osmocom/gsm/gsup.h?id=ae7966d145965452a325a33ca6334b6d6fe061a6#n244
> Can we use that, and simplify the handover_number to only have
> extension, nature_of_nr and number_plan?
I would argue we should introduce a new "global title" IE which contains
* BCD digits
* nature of address / type of number
* numbering plan indicator
This would basically correspond to a SCCP global title, see osmo_sccp_gt in sccp_sap.h
This is the most flexible way to encode any MSISDN, IMSI, ...
just my thoughts...
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)