Osmocom Media Gateway (RTP proxy and RTP/E1 gateway) https://osmocom.org/projects/osmo-mgw
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|2 months ago|
|contrib||8 months ago|
|debian||2 months ago|
|doc||8 months ago|
|include||3 months ago|
|m4||7 months ago|
|src||2 months ago|
|tests||4 months ago|
|.clang-format||9 months ago|
|.gitignore||11 months ago|
|.gitreview||5 years ago|
|.mailmap||6 years ago|
|AUTHORS||5 years ago|
|COPYING||5 years ago|
|Makefile.am||2 years ago|
|README||4 years ago|
|README.vty-tests||2 months ago|
|TODO-RELEASE||3 months ago|
|configure.ac||2 months ago|
|git-version-gen||4 years ago|
|libosmo-mgcp-client.pc.in||5 years ago|
|osmoappdesc.py||3 years ago|
OsmoMGW 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.
OsmoMGW was one of the parts split off from the old openbsc.git. It originated
as a solution to merely navigate RTP streams through a NAT, but has since
matured to a Media Gateway implementation that is capable of streaming RTP for
2G (AoIP) and 3G (IuCS) GSM networks as well as (still not implemented at time
of writing) transcoding between TRAU, various RTP payloads and IuUP.
The OsmoMGW program exposes an MGCP interface towards clients like OsmoMSC and
OsmoBSC, and receives and sends RTP streams as configured via MGCP.
The libosmo-mgcp-client library exposes utilities used by e.g. OsmoMSC (found
in osmo-msc.git) to instruct OsmoMGW via its MGCP service.
Find OsmoMGW issue tracker and wiki online at