Osmocom Mobile Switching Centre
Go to file
Pau Espin 017ba1fa30 vlr_sgs: Balance use_count incremented in vlr_sgs_loc_update
During a recent pcap trace, it was spotted that subscriber coming from
SGs had a use count with 16 "SGs" items, and later it incremented to 17.
Further investigation shows that the related use_count item was never
decreased, meaning every time an SGs-LU was sent by the MME, the item
was incremented further and never decremented.

Let's rename the item to be referenced while in LU, and then decremented
when LU is done. At that time, either the LU was accepted and the
subscriber object has a use_count item "attached", or it was rejected
and we already sent the reject messages, so we are fine deleting it if
needed.

Related: SYS#5337
Change-Id: I22c386f02ffa57428f700b003cc2cf23133598d0
2021-08-24 14:59:27 +02:00
contrib contrib/osmo-msc.spec.in: depend on dbd-sqlite3 2021-03-09 14:48:59 +01:00
debian Bump version: 1.6.1.98-cad22-dirty → 1.7.0 2021-02-23 20:22:34 +01:00
doc running.adoc: add section about MGCP configuration 2021-08-03 11:36:25 +02:00
include vlr_sgs: Balance use_count incremented in vlr_sgs_loc_update 2021-08-24 14:59:27 +02:00
m4 move openbsc/* to repos root 2017-07-12 23:17:10 +00:00
src vlr_sgs: Balance use_count incremented in vlr_sgs_loc_update 2021-08-24 14:59:27 +02:00
tests msc_a.c: Allow MSC_A_EV_CN_CLOSE in state MSC_A_ST_RELEASING 2021-07-12 16:37:24 +02:00
.gitignore .gitignore: Ignore new autofoo tmp files 2021-02-04 12:51:41 +01:00
.gitreview update .gitreview to new repo url 2017-08-08 17:26:28 +02:00
.mailmap add .mailmap file for mapping git author name/mail in shortlog 2016-08-08 17:40:28 +00:00
AUTHORS move openbsc/* to repos root 2017-07-12 23:17:10 +00:00
COPYING move openbsc/* to repos root 2017-07-12 23:17:10 +00:00
Makefile.am manuals: generate vty reference xml at build time 2020-07-12 12:30:28 +00:00
README README update. Explain more what it is than just the history 2021-01-06 13:13:46 +01:00
README.vty-tests Remove obsolete ./configure option 2017-11-29 14:24:54 +00:00
TODO-RELEASE support A5/4 in inter-BSC handover 2021-06-24 01:44:17 +02:00
configure.ac configure.ac: Depend on newer libosmo-ranap 2021-02-23 20:47:57 +01:00
git-version-gen git-version-gen: Don't check for .git directory 2018-07-24 18:05:46 +02:00
osmoappdesc.py osmoappdesc.py, tests: switch to python 3 2019-12-12 09:29:19 +00:00

README

About OsmoMSC
=============

OsmoMSC is an implementation of the 3GPP MSC (Mobile Switching Centre)
network element.  It implements the following core functionality within
the 2G (GSM) and 3G (UMTS) networks:

* mobility management
* call control (either via built-in MNCC handler or external osmo-sip-connector)
* USSD (exposed via GSUP)
* SMS (either via built-in SMSC or external via GSUP)

Historically, OsmoMSC originated from the OpenBSC project, which started
as a minimalistic all-in-one implementation of the GSM Network. In 2017,
OpenBSC had reached maturity and diversity (including M3UA SIGTRAN and
3G support in the form of IuCS and IuPS interfaces) that naturally lead
to a separation of the all-in-one approach to fully independent separate
programs as in typical GSM networks.

OsmoMSC was one of the parts split off from the old openbsc.git. Before,
it was the libmsc part of the old OsmoNITB. Since a true A interface and
IuCS for 3G support is available, OsmoMSC exists only as a separate
standalone entity.

OsmoMSC exposes
- GSUP towards OsmoHLR (or a MAP proxy);
- A over IP towards a BSC (e.g. OsmoBSC);
- IuCS towards an RNC or HNB-GW (e.g. OsmoHNBGW) for 3G voice;
- MNCC (Mobile Network Call Control derived from GSM TS 04.07);
- SMPP 3.4 (Short Message Peer-to-Peer);
- The Osmocom typical telnet VTY and CTRL interfaces.

Find OsmoMSC issue tracker and wiki online at
https://osmocom.org/projects/osmomsc
https://osmocom.org/projects/osmomsc/wiki