From lynxis at fe80.eu  Fri Jan  1 16:41:44 2021
From: lynxis at fe80.eu (Alexander 'lynxis' Couzens)
Date: Fri, 1 Jan 2021 17:41:44 +0100
Subject: set a c/c++ standard for all osmocom core network projects
Message-ID: <20210101174144.14468335@lazus.yip>

Hi,

I would like to start a discussion to set for all osmocom core
network projects a language standard (could be also set for other
osmocom projects).
The current state is the code is compiled with the compilers choice of
c/c++. This produce unexpected build failures on newer or older system.

I would like to start setting it to c11/c++11 + gnu extensions. This is
a more random choice of standard. I would argue to have at least c99
for c.

Any feedback?

Best,
lynxis


-- 
Alexander Couzens

mail: lynxis at fe80.eu
jabber: lynxis at fe80.eu
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210101/abe1d026/attachment.bin>

From laforge at osmocom.org  Sat Jan  2 15:55:18 2021
From: laforge at osmocom.org (Harald Welte)
Date: Sat, 2 Jan 2021 16:55:18 +0100
Subject: set a c/c++ standard for all osmocom core network projects
In-Reply-To: <20210101174144.14468335@lazus.yip>
References: <20210101174144.14468335@lazus.yip>
Message-ID: <X/CXZuJ3yLU2u9bF@nataraja>

Hi Lynxis,

On Fri, Jan 01, 2021 at 05:41:44PM +0100, Alexander 'lynxis' Couzens wrote:
> I would like to start setting it to c11/c++11 + gnu extensions. This is
> a more random choice of standard. I would argue to have at least c99
> for c.

In general I don't have much of an opinion on the specofics, just as
long as whatever is chosen is supported by the toolchains of Debian 8,
which is currently the oldest platform we officially support.

Regards,
	Harald
-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From sonny.lafuente at entropysolution.com  Wed Jan  6 07:53:18 2021
From: sonny.lafuente at entropysolution.com (Sonny Lafuente)
Date: Wed, 6 Jan 2021 07:53:18 +0000
Subject: OsmoBSC - SCCP Connection to Nokia MSC
In-Reply-To: <FBD8ABB3-E05B-4137-A7AD-6C7989DF3ABE@entropysolution.com>
References: <FBD8ABB3-E05B-4137-A7AD-6C7989DF3ABE@entropysolution.com>
Message-ID: <FF9819FB-9AD3-47C3-9375-C05238CF2460@entropysolution.com>

Hi Community,

Happy New Year!

Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I?ve red some documentations in OSMO but I don?t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured.


BSC Point code - 2262
Nokia Point code - 7039




Logs Below:


<001f> sccp_scrc.c:420 sccp_scrc_rx_sclc_msg:  HDR=(CL:CLDT,V=0,LEN=0),
PART(T=Routing Context,L=4,D=00000000),
PART(T=Protocol Class,L=4,D=00000000),
PART(T=Source Address,L=20,D=0002000380020008000008d680030008000000fe),
PART(T=Destination Address,L=20,D=000200038002000800001b7f80030008000000fe),
PART(T=Sequence Control,L=4,D=00000000),
PART(T=Data,L=6,D=000430040120)
<001f> osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=7039=3.111.7 not local, message is for routing
<001f> osmo_ss7_hmrt.c:227 Found route for dpc=7039=3.111.7: pc=0=0.0.0 mask=0x0=0.0.0 via AS nokia_msc proto=m3ua
<001f> osmo_ss7_hmrt.c:233 rt->dest.as proto is M3UA for dpc=7039=3.111.7
<001f> m3ua.c:507 XUA_AS(nokia_msc)[0x11886f0]{AS_ACTIVE}: Received Event AS-TRANSFER.req
<0007> a_reset.c:110 A-RESET(msc-0)[0x1194c80]{DISC}: state_chg to DISC
<0007> fsm.c:189 A-RESET(msc-0)[0x1194c80]{DISC}: Timeout of T4
<0007> a_reset.c:106 A-RESET(msc-0)[0x1194c80]{DISC}: (re)sending BSSMAP RESET message...
<0007> osmo_bsc_sigtran.c:93 Sending RESET to MSC: RI=SSN_PC,PC=3.111.7,SSN=BSSAP
<001f> sccp_scrc.c:420 sccp_scrc_rx_sclc_msg:  HDR=(CL:CLDT,V=0,LEN=0),
PART(T=Routing Context,L=4,D=00000000),
PART(T=Protocol Class,L=4,D=00000000),
PART(T=Source Address,L=20,D=0002000380020008000008d680030008000000fe),
PART(T=Destination Address,L=20,D=000200038002000800001b7f80030008000000fe),
PART(T=Sequence Control,L=4,D=00000000),
PART(T=Data,L=6,D=000430040120)
<001f> osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=7039=3.111.7 not local, message is for routing
<001f> osmo_ss7_hmrt.c:227 Found route for dpc=7039=3.111.7: pc=0=0.0.0 mask=0x0=0.0.0 via AS nokia_msc proto=m3ua
<001f> osmo_ss7_hmrt.c:233 rt->dest.as proto is M3UA for dpc=7039=3.111.7
<001f> m3ua.c:507 XUA_AS(nokia_msc)[0x11886f0]{AS_ACTIVE}: Received Event AS-TRANSFER.req
<0007> a_reset.c:110 A-RESET(msc-0)[0x1194c80]{DISC}: state_chg to DISC




OSMOBSC Version:

OsmoBSC# show version
OsmoBSC 1.3.0.132-bcbc5 (OsmoBSC).
Copyright (C) 2008-2018 Harald Welte, Holger Freyther
Contributions by Daniel Willmann, Jan L?bbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr

License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

OsmoBSC#


Regards,

Sonny Lafuente | Systems Engineer | Entropy Solution Philippines
Mobile: +639985365206 | Office: 028931781 | Email: sonny.lafuente at entropysolution.com<mailto:sonny.lafuente at entropysolution.com>
Office Address: Unit 2103 Antel Corporate  Centre 121 Valero St. Salcedo Village Makati City Philippines 1227

[cid:907cda3a-190d-48c4-bd09-a9b05bf0c799 at apcprd04.prod.outlook.com]

Singapore * Philippines
Products:
Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development
This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

On 6 Jan 2021, at 8:41 AM, Sonny Lafuente <sonny.lafuente at entropysolution.com<mailto:sonny.lafuente at entropysolution.com>> wrote:

Hi Community,

Happy New Year!

Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I?ve red some documentations in OSMO but I don?t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured.


BSC Point code - 2262
Nokia Point code - 7039













Regards,
Sonny
<PastedGraphic-1.tiff><PastedGraphic-2.tiff><PastedGraphic-3.tiff><sccp captured nokia MSC.pcap>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Entropy Logo Email.png
Type: image/png
Size: 32853 bytes
Desc: Entropy Logo Email.png
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sccp captured nokia MSC.pcap
Type: application/octet-stream
Size: 2748 bytes
Desc: sccp captured nokia MSC.pcap
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.obj>

From laforge at gnumonks.org  Fri Jan  8 22:53:51 2021
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 8 Jan 2021 23:53:51 +0100
Subject: WIP / RFC for pysim 'next generation;' aka pysim-shell
Message-ID: <X/jif2C1BF3RfY9w@nataraja>

Dear Osmocom community,

pySim-prog was nice when there were only 5 parameters on a SIM that we
could program, and where the use case was pretty limited.  Today, we
have SIM/USIM/ISIM cards with hundreds of files and even more parameters
to program.  We cannot add a command line argument for each file to
pySim-prog.

Instead, this introduces an interactive command-line shell / REPL,
in which one can navigate the file system of the card, read and update
files both in raw format and in decoded/parsed format.

The idea is primarily inspired by Henryk Ploetz' venerable
cyberflex-shell, but implemented on a more modern basis using
the cmd2 python module.

You can see the very first prototype in the laforge/shell branch of pysim.git

You can do things with it like this:

===> Start-up and authenticate with adm pin
----------------------------------------------------------------------
$ ./pysim-shell.py -p 0
Using PC/SC reader interface
Autodetected card type: sysmoISIM-SJA2
AIDs on card: ['a0000000871002ffffffff8907090000', 'a0000000871004ffffffff8907090000']
Welcome to pySim-shell!
pySIM-shell (3f00)> verify_adm 92990895
----------------------------------------------------------------------

===> interactive help
----------------------------------------------------------------------
pySIM-shell (3f00)> help

Documented commands (use 'help -v' for verbose/'help <topic>' for details):

ISO7816 Commands
================
read_binary  select_adf  select_file  update_binary  update_record  verify_chv

pySim Commands
==============
intro  verify_adm

USIM Commands
=============
read_ehplmn  ust_service_activate  ust_service_deactivate

pySim-shell built-in commands
=============================
alias  help     macro  quit          run_script  shell
edit   history  py     run_pyscript  set         shortcuts

----------------------------------------------------------------------


===> more interactive help
----------------------------------------------------------------------
pySIM-shell (3f00)> help read_binary
usage: read_binary [-h] [--file-id FILE_ID] [--offset OFFSET] [--length LENGTH] [--record-nr RECORD_NR]

Read binary data from a transparent EF

optional arguments:
  -h, --help            show this help message and exit
  --file-id FILE_ID     File ID
  --offset OFFSET       Byte offset for start of read
  --length LENGTH       Number of bytes to read
  --record-nr RECORD_NR
                        Number of record to read
----------------------------------------------------------------------


===> navigating the FS and reading files
----------------------------------------------------------------------
pySIM-shell (3f00)> select_file 7f20
['622c8202782183027f20a509800171830400018d088a01058b032f0601c60f90017083010183018183010a83010b']
pySIM-shell (3f00/7f20)> read_binary --file-id 6f07
089910070000400310
----------------------------------------------------------------------


===> interaction with local filesystem, i.e. I/O redirect + shell commands
----------------------------------------------------------------------
pySIM-shell (3f00)> select_adf a0000000871002
pySIM-shell (a0000000871002)> select_file 5f3b
pySIM-shell (a0000000871002/5f3b)> read_binary --file-id 4f20 > /tmp/f
pySIM-shell (a0000000871002/5f3b)> !cat /tmp/f
ffffffffffffffff07
----------------------------------------------------------------------

===> piping output through shell tools like grep
----------------------------------------------------------------------
pySIM-shell (3f00)> read_ust  | grep 86
        Service 86 - Allowed CSG Lists and corresponding indications
----------------------------------------------------------------------


===> enabling/disabling services
----------------------------------------------------------------------
pySIM-shell (3f00/7f20)> ust_service_activate 123
pySIM-shell (3f00/7f20)> ust_service_deactivate 123
----------------------------------------------------------------------

It's a very first prototype, but it is really promising.

The major tasks I see to make this go anywhere is:

* have "File" class with encoder/decoder methods, which are registered
  automatically with a 'file system' layer that knows about the DF/ADF
  hierarchy
** this allows us to have a "read-decoded" command, which will
   call the decode method of the file, automatically resolved by the
   selected FID/path
* automatic mapping of file-name -> FID and FID -> file name
** when printing (like in the path), use the human-readable names
** allow users to use human-readable names in SELECT
* decode + display the TLVs / FCPs after a SELECT (like cyberflex-shell
* ability to enable/disable APDU trace
* dynamically register/deregster commands based on the path, i.e. offer
  USIM commands only when in ADF_USIM

We have quite a bit of that infrastructure in the c-language libosmosim,
(part of libosmocore.git), but unfortunately not in python :/

Let me know if anyone is interested in joining this effort.

Regards,
	Harald
-- 
- 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)


From bryancoxwell at gmail.com  Sat Jan  9 15:00:58 2021
From: bryancoxwell at gmail.com (bryan coxwell)
Date: Sat, 9 Jan 2021 10:00:58 -0500
Subject: WIP / RFC for pysim 'next generation;' aka pysim-shell
In-Reply-To: <X/jif2C1BF3RfY9w@nataraja>
References: <X/jif2C1BF3RfY9w@nataraja>
Message-ID: <CAAESu2mLjjyQzK0WehY9F+nKDinStq-6eMUD_sAGVZwkstot1w@mail.gmail.com>

Harald,

I think this is a great idea and I'd love to help out, but I'm new to
working on open source projects. What's the best way for me to get started
in a way that would be helpful?

Best,

Bryan

On Fri, Jan 8, 2021 at 5:54 PM Harald Welte <laforge at gnumonks.org> wrote:

> Dear Osmocom community,
>
> pySim-prog was nice when there were only 5 parameters on a SIM that we
> could program, and where the use case was pretty limited.  Today, we
> have SIM/USIM/ISIM cards with hundreds of files and even more parameters
> to program.  We cannot add a command line argument for each file to
> pySim-prog.
>
> Instead, this introduces an interactive command-line shell / REPL,
> in which one can navigate the file system of the card, read and update
> files both in raw format and in decoded/parsed format.
>
> The idea is primarily inspired by Henryk Ploetz' venerable
> cyberflex-shell, but implemented on a more modern basis using
> the cmd2 python module.
>
> You can see the very first prototype in the laforge/shell branch of
> pysim.git
>
> You can do things with it like this:
>
> ===> Start-up and authenticate with adm pin
> ----------------------------------------------------------------------
> $ ./pysim-shell.py -p 0
> Using PC/SC reader interface
> Autodetected card type: sysmoISIM-SJA2
> AIDs on card: ['a0000000871002ffffffff8907090000',
> 'a0000000871004ffffffff8907090000']
> Welcome to pySim-shell!
> pySIM-shell (3f00)> verify_adm 92990895
> ----------------------------------------------------------------------
>
> ===> interactive help
> ----------------------------------------------------------------------
> pySIM-shell (3f00)> help
>
> Documented commands (use 'help -v' for verbose/'help <topic>' for details):
>
> ISO7816 Commands
> ================
> read_binary  select_adf  select_file  update_binary  update_record
> verify_chv
>
> pySim Commands
> ==============
> intro  verify_adm
>
> USIM Commands
> =============
> read_ehplmn  ust_service_activate  ust_service_deactivate
>
> pySim-shell built-in commands
> =============================
> alias  help     macro  quit          run_script  shell
> edit   history  py     run_pyscript  set         shortcuts
>
> ----------------------------------------------------------------------
>
>
> ===> more interactive help
> ----------------------------------------------------------------------
> pySIM-shell (3f00)> help read_binary
> usage: read_binary [-h] [--file-id FILE_ID] [--offset OFFSET] [--length
> LENGTH] [--record-nr RECORD_NR]
>
> Read binary data from a transparent EF
>
> optional arguments:
>   -h, --help            show this help message and exit
>   --file-id FILE_ID     File ID
>   --offset OFFSET       Byte offset for start of read
>   --length LENGTH       Number of bytes to read
>   --record-nr RECORD_NR
>                         Number of record to read
> ----------------------------------------------------------------------
>
>
> ===> navigating the FS and reading files
> ----------------------------------------------------------------------
> pySIM-shell (3f00)> select_file 7f20
>
> ['622c8202782183027f20a509800171830400018d088a01058b032f0601c60f90017083010183018183010a83010b']
> pySIM-shell (3f00/7f20)> read_binary --file-id 6f07
> 089910070000400310
> ----------------------------------------------------------------------
>
>
> ===> interaction with local filesystem, i.e. I/O redirect + shell commands
> ----------------------------------------------------------------------
> pySIM-shell (3f00)> select_adf a0000000871002
> pySIM-shell (a0000000871002)> select_file 5f3b
> pySIM-shell (a0000000871002/5f3b)> read_binary --file-id 4f20 > /tmp/f
> pySIM-shell (a0000000871002/5f3b)> !cat /tmp/f
> ffffffffffffffff07
> ----------------------------------------------------------------------
>
> ===> piping output through shell tools like grep
> ----------------------------------------------------------------------
> pySIM-shell (3f00)> read_ust  | grep 86
>         Service 86 - Allowed CSG Lists and corresponding indications
> ----------------------------------------------------------------------
>
>
> ===> enabling/disabling services
> ----------------------------------------------------------------------
> pySIM-shell (3f00/7f20)> ust_service_activate 123
> pySIM-shell (3f00/7f20)> ust_service_deactivate 123
> ----------------------------------------------------------------------
>
> It's a very first prototype, but it is really promising.
>
> The major tasks I see to make this go anywhere is:
>
> * have "File" class with encoder/decoder methods, which are registered
>   automatically with a 'file system' layer that knows about the DF/ADF
>   hierarchy
> ** this allows us to have a "read-decoded" command, which will
>    call the decode method of the file, automatically resolved by the
>    selected FID/path
> * automatic mapping of file-name -> FID and FID -> file name
> ** when printing (like in the path), use the human-readable names
> ** allow users to use human-readable names in SELECT
> * decode + display the TLVs / FCPs after a SELECT (like cyberflex-shell
> * ability to enable/disable APDU trace
> * dynamically register/deregster commands based on the path, i.e. offer
>   USIM commands only when in ADF_USIM
>
> We have quite a bit of that infrastructure in the c-language libosmosim,
> (part of libosmocore.git), but unfortunately not in python :/
>
> Let me know if anyone is interested in joining this effort.
>
> Regards,
>         Harald
> --
> - 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)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210109/71c3ebf5/attachment.htm>

From laforge at gnumonks.org  Mon Jan 11 13:04:26 2021
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 11 Jan 2021 14:04:26 +0100
Subject: WIP / RFC for pysim 'next generation;' aka pysim-shell
In-Reply-To: <CAAESu2mLjjyQzK0WehY9F+nKDinStq-6eMUD_sAGVZwkstot1w@mail.gmail.com>
References: <X/jif2C1BF3RfY9w@nataraja>
 <CAAESu2mLjjyQzK0WehY9F+nKDinStq-6eMUD_sAGVZwkstot1w@mail.gmail.com>
Message-ID: <X/xM2oOpYNZHzsDq@nataraja>

Hi Bryan,

On Sat, Jan 09, 2021 at 10:00:58AM -0500, bryan coxwell wrote:
> I think this is a great idea and I'd love to help out, but I'm new to
> working on open source projects. What's the best way for me to get started
> in a way that would be helpful?

thanks for reaching out.  By now most of the APIs/architecture is sorted
out, so you could

a) make sure that ts_51_011.py (sim) / ts_31_102.py (usim) / ts_31_103.py (isim)
   contain class definitions for all of the files specified in the latest Release 16
   3GPP specifications

b) write encoder and decoder methods within the EF classes for the various files
   of interest.  See the EF_IMSI() as an example. The Decoder method should return
   a python dict (possibly a hierarchy of dicts) and return the binary representation,
   while the encoder method should take the dict and produce the binary representation.

Regards,
	Harald
-- 
- 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)


From sonny.lafuente at entropysolution.com  Wed Jan  6 00:41:17 2021
From: sonny.lafuente at entropysolution.com (Sonny Lafuente)
Date: Wed, 6 Jan 2021 00:41:17 +0000
Subject: OsmoBSC - SCCP Connection to Nokia MSC
Message-ID: <FBD8ABB3-E05B-4137-A7AD-6C7989DF3ABE@entropysolution.com>

Hi Community,

Happy New Year!

Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I?ve red some documentations in OSMO but I don?t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured.


BSC Point code - 2262
Nokia Point code - 7039













Regards,
Sonny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/6d1f568b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.tiff
Type: image/tiff
Size: 819894 bytes
Desc: PastedGraphic-1.tiff
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/6d1f568b/attachment.tiff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.tiff
Type: image/tiff
Size: 854146 bytes
Desc: PastedGraphic-2.tiff
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/6d1f568b/attachment-0001.tiff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-3.tiff
Type: image/tiff
Size: 907218 bytes
Desc: PastedGraphic-3.tiff
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/6d1f568b/attachment-0002.tiff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sccp captured nokia MSC.pcap
Type: application/octet-stream
Size: 2748 bytes
Desc: sccp captured nokia MSC.pcap
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/6d1f568b/attachment.obj>

From keith at rhizomatica.org  Wed Jan 13 07:25:12 2021
From: keith at rhizomatica.org (Keith)
Date: Wed, 13 Jan 2021 01:25:12 -0600
Subject: SMPP Alert Notifications
Message-ID: <6b82e406-b9d7-b63c-5b72-b1d6691a67c9@rhizomatica.org>

Hi Osmocom Community.

I'd like to extend the SMPP protocol alert notifications to be able to
differentiate between IMSI_ATTACH, NORMAL and PERIODIC LURs

The reason is to be able to react to an initial attach by sending a
"Welcome" SMS.

SMPP specifies only three status possibilities:

0 = Available

1 = Disabled

2 = Not Available (Detaching)

I've added 3 for IMSI_ATTACH - Actually I ended up using != PERIODIC
because not all phones send an ATTACH after a DETACH, some send NORMAL LUR.

With this the ESME can respond to an alert notification that has status
3 by looking up the IMSI to see if it's known/autorised etc (this is
outside of osmo-hlr in my use case, although I guess it could also be
done by checking what the HLR says inside the MSC)

Anyway.. I'm wondering if anybody else ever did this, and do we
want/accept this functionality in master osmo-msc?

Or.. any better ideas on how to do it?

Thanks

k/




From laforge at osmocom.org  Thu Jan 14 14:53:14 2021
From: laforge at osmocom.org (Harald Welte)
Date: Thu, 14 Jan 2021 15:53:14 +0100
Subject: SMPP Alert Notifications
In-Reply-To: <6b82e406-b9d7-b63c-5b72-b1d6691a67c9@rhizomatica.org>
References: <6b82e406-b9d7-b63c-5b72-b1d6691a67c9@rhizomatica.org>
Message-ID: <YABa2oybjkr+rHNV@nataraja>

Hi Keith,

On Wed, Jan 13, 2021 at 01:25:12AM -0600, Keith wrote:
> SMPP specifies only three status possibilities:
> 
> 0 = Available
> 
> 1 = Disabled
> 
> 2 = Not Available (Detaching)
> 
> I've added 3 for IMSI_ATTACH - Actually I ended up using != PERIODIC
> because not all phones send an ATTACH after a DETACH, some send NORMAL LUR.

I think it might make sense to add a new IE/TLV as a sub-type of "Available",
this way I would think it's more compatible to other implementations as
additional IEs are typically simply ignored.

Furthermore, I'm not convinced your !=PERIODIC will do what you want, as NORMAL
will also happen between location areas, so neither ATTACH nor PERIODIC.

One idea is to add logic to osmo-msc to distinguish whether this really
was a new subscriber that was previously unknown to the MSC (and Then send "Available"),
or simply send no SMPP notifiation at all if the subscriber was previously already
known to osm-msc.  This way no protocol changes need to be introduced at all.

The alternative would be to add a new, non-standard IE whihc just passes the LU type
transparently through.

> do we want/accept this functionality in master osmo-msc?

I think either of the two ideas I outlined above could go master.

Regards,
	Harald
-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From bryancoxwell at gmail.com  Fri Jan 15 00:59:04 2021
From: bryancoxwell at gmail.com (bryan coxwell)
Date: Thu, 14 Jan 2021 19:59:04 -0500
Subject: WIP / RFC for pysim 'next generation;' aka pysim-shell
In-Reply-To: <X/xM2oOpYNZHzsDq@nataraja>
References: <X/xM2oOpYNZHzsDq@nataraja>
Message-ID: <803E01D5-2235-4210-9989-EF040B86CE12@gmail.com>

Sounds good to me. 51.011 looks to be unchanged, which I guess is expected. Working on updating 31.102 now.

Thanks,

Bryan Coxwell

> On Jan 11, 2021, at 8:10 AM, Harald Welte <laforge at gnumonks.org> wrote:
> 
> ?Hi Bryan,
> 
>> On Sat, Jan 09, 2021 at 10:00:58AM -0500, bryan coxwell wrote:
>> I think this is a great idea and I'd love to help out, but I'm new to
>> working on open source projects. What's the best way for me to get started
>> in a way that would be helpful?
> 
> thanks for reaching out.  By now most of the APIs/architecture is sorted
> out, so you could
> 
> a) make sure that ts_51_011.py (sim) / ts_31_102.py (usim) / ts_31_103.py (isim)
>   contain class definitions for all of the files specified in the latest Release 16
>   3GPP specifications
> 
> b) write encoder and decoder methods within the EF classes for the various files
>   of interest.  See the EF_IMSI() as an example. The Decoder method should return
>   a python dict (possibly a hierarchy of dicts) and return the binary representation,
>   while the encoder method should take the dict and produce the binary representation.
> 
> Regards,
>    Harald
> -- 
> - 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)


From northmirko at gmail.com  Thu Jan 28 09:52:41 2021
From: northmirko at gmail.com (Mirko Kovacevic)
Date: Thu, 28 Jan 2021 10:52:41 +0100
Subject: OsmoHNBGW M3UA IPSP mode
Message-ID: <CAMYWRL-KD-6t61eHycMT25rctJnWBkimZe3YDS_b8Xj+cSr-PQ@mail.gmail.com>

 Hello,
not many discussions found  on OsmoHNBGW topic.

1. Can we connect O' HNBGW directly to SGSN without STP (IPSP mode)?
2. If not, I am wondering do OSMOCOM have development support for IPSP M3UA
mode in SIGTRAN development files or elsewhere?

Thank you in advance, and keep shaking mobile development world.

Mirko K.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210128/7768d05c/attachment.htm>

From laforge at osmocom.org  Thu Jan 28 15:50:49 2021
From: laforge at osmocom.org (Harald Welte)
Date: Thu, 28 Jan 2021 16:50:49 +0100
Subject: OsmoHNBGW M3UA IPSP mode
In-Reply-To: <CAMYWRL-KD-6t61eHycMT25rctJnWBkimZe3YDS_b8Xj+cSr-PQ@mail.gmail.com>
References: <CAMYWRL-KD-6t61eHycMT25rctJnWBkimZe3YDS_b8Xj+cSr-PQ@mail.gmail.com>
Message-ID: <YBLdWc9UjKfLT7pQ@nataraja>

Hi Mirko,

On Thu, Jan 28, 2021 at 10:52:41AM +0100, Mirko Kovacevic wrote:
> not many discussions found  on OsmoHNBGW topic.

Indeed, it became in general very quite here on many osmocom mailing list,
which is probably caused by:

* less community / volunteer interest in 2G and 3G technologies

* the professional/commercial user base has been growing significatnly, but
  they mostly don't want to discuss topics on public mailing lists, at least
  in the telecom operator/vendor industry

* less ability/willingnes to use mailing lists for communication

> 1. Can we connect O' HNBGW directly to SGSN without STP (IPSP mode)?

No, IPSP is generally not supported by lbiosmo-sigtran.  We only support
ASP and SGW roles, but not IPSP.  This has so far not been requested/required
by anyone.  All the third party equipment we interoperatd with typically supports
non-IPSP modes.

> 2. If not, I am wondering do OSMOCOM have development support for IPSP M3UA
> mode in SIGTRAN development files or elsewhere?

No such development has been done.  Both OsmoSTP and OSmoHNBGW use the same
libosmo-sigtran library, which only support ASP and SGW mode.

If IPSP were to be developed, it would immediately be available both in OsmoSTP
and all applications like OsmoHNBGW, OsmoMSC, OsmoSGSN, ...

We always appreciate contributions, whether in form of patches or in form of
funding of development.

> Thank you in advance, and keep shaking mobile development world.

thanks :)

Regards,
	Harald

-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)