Osmocom Serving GPRS Support Node for 2G(GPRS) and 3G(UMTS)
https://osmocom.org/projects/osmosgsn
The MS notifies movement to GMM SUSPEND state because it is for instance handling a call and cannot use PDCH anymore. Once it releases the TCH it will ASAP move to either dedicated mode or trigger RAU, which means it will get out of SUSPEND state. So it doesn't make sense to try paging the MS when in that state. Related: OS#4616 Change-Id: Ia245899eb9f16c7f839785def4ceb721a1c3a11b |
||
---|---|---|
contrib | ||
debian | ||
doc | ||
include | ||
m4 | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README | ||
README.vty-tests | ||
TODO-RELEASE | ||
configure.ac | ||
git-version-gen | ||
osmoappdesc.py |
README
About OsmoSGSN ============== OsmoSGSN originated from the OpenBSC project, as a separate program within openbsc.git. In 2017, OpenBSC was split in separate repositories, and hence OsmoSGSN was given its own separate git repository. OsmoSGSN exposes - GSUP towards OsmoHLR (or a MAP proxy); - GTP towards a GGSN (e.g. OsmoGGSN); - Gb towards a BSS (e.g. OsmoPCU); - IuPS towards an RNC or HNB-GW (e.g. OsmoHNBGW) for 3G data; - The Osmocom typical telnet VTY and CTRL interfaces. Find OsmoSGSN issue tracker and wiki online at https://osmocom.org/projects/osmosgsn https://osmocom.org/projects/osmosgsn/wiki