blob: 29883b8fdadff27a2fa78678d1724d74eab2daac [file] [log] [blame]
Neels Hofmeyrd049a662017-09-04 02:34:20 +02001About OsmoMGW
Harald Welted94ee1e2008-12-29 04:50:01 +00002=============
3
Neels Hofmeyrd049a662017-09-04 02:34:20 +02004OsmoMGW originated from the OpenBSC project, which started as a minimalistic
5all-in-one implementation of the GSM Network. In 2017, OpenBSC had reached
6maturity and diversity (including M3UA SIGTRAN and 3G support in the form of
7IuCS and IuPS interfaces) that naturally lead to a separation of the all-in-one
8approach to fully independent separate programs as in typical GSM networks.
Harald Welted94ee1e2008-12-29 04:50:01 +00009
Neels Hofmeyrd049a662017-09-04 02:34:20 +020010OsmoMGW was one of the parts split off from the old openbsc.git. It originated
11as a solution to merely navigate RTP streams through a NAT, but has since
12matured to a Media Gateway implementation that is capable of streaming RTP for
132G (AoIP) and 3G (IuCS) GSM networks as well as (still not implemented at time
14of writing) transcoding between TRAU, various RTP payloads and IuUP.
Harald Welte3f015f02015-12-05 23:13:35 +010015
Neels Hofmeyrd049a662017-09-04 02:34:20 +020016The OsmoMGW program exposes an MGCP interface towards clients like OsmoMSC and
17OsmoBSC, and receives and sends RTP streams as configured via MGCP.
Harald Welted94ee1e2008-12-29 04:50:01 +000018
Neels Hofmeyrd049a662017-09-04 02:34:20 +020019The libosmo-mgcp-client library exposes utilities used by e.g. OsmoMSC (found
20in osmo-msc.git) to instruct OsmoMGW via its MGCP service.
Harald Welte61b42322010-03-09 12:38:31 +010021
Neels Hofmeyrd049a662017-09-04 02:34:20 +020022Find OsmoMGW issue tracker and wiki online at
23https://osmocom.org/projects/osmo-mgw
24https://osmocom.org/projects/osmo-mgw/wiki