The timer "mgw X2" (RTP stream establishing timeout) is set by default to 30 seconds. When an MT call is ringing and remains unanswered, it is this timer that will expire, and the call is terminated. Up to now this results in a CC_CAUSE of Resource Unavailable and if osmo-sip-connector is in use, the SIP agent will get 503 Service Unavailable. While "resource unavailable" may be technically correct, in that the MGW did not return an rtp stream in time, returning "No User Responding" (resulting in SIP 480) is probably a more accurate description of what actually happened, allowing the switch to inform the caller. Change-Id: I4a9cfc388ec9ecb743d154a114a6db638eac4701
|2 days ago|
|contrib||1 month ago|
|debian||3 months ago|
|doc||11 months ago|
|include||3 days ago|
|m4||9 months ago|
|src||2 days ago|
|tests||3 weeks ago|
|.gitignore||2 months ago|
|.gitreview||5 years ago|
|.mailmap||6 years ago|
|AUTHORS||5 years ago|
|COPYING||5 years ago|
|Makefile.am||2 years ago|
|README.md||4 months ago|
|README.vty-tests||4 months ago|
|TODO-RELEASE||3 months ago|
|configure.ac||2 months ago|
|git-version-gen||4 years ago|
|osmoappdesc.py||3 years ago|
osmo-msc - Osmocom MSC Implementation
This repository contains a C-language implementation of a GSM Mobile Switching Centre (MSC) for 2G (GSM) and 3G (UMTS). It is part of the Osmocom Open Source Mobile Communications project.
- A over IP towards BSCs (e.g. OsmoBSC): 3GPP AoIP or SCCPlite
- IuCS over IP towards RNCs / HNBGW (e.g. osmo-hnbgw)
- The Osmocom typical telnet VTY and CTRL interfaces.
- The Osmocom typical statsd exporter.
- 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)
You can clone from the official osmo-msc.git repository using
git clone https://gitea.osmocom.org/cellular-infrastructure/osmo-msc
There is a web interface at https://gitea.osmocom.org/cellular-infrastructure/osmo-msc
User Manuals and VTY reference manuals are [optionally] built in PDF form as part of the build process.
Discussions related to osmo-msc are happening on the firstname.lastname@example.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.
Please observe the Osmocom Mailing List Rules when posting.
Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards
We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details
The current patch queue for osmo-msc can be seen at https://gerrit.osmocom.org/#/q/project:osmo-msc+status:open
OsmoMSC originated from the OsmoNITB project, which started as a minimalistic all-in-one implementation of the GSM Network. In 2017, OsmoNITB 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.