| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 1 | About OsmoBSC |
| Harald Welte | d94ee1e | 2008-12-29 04:50:01 +0000 | [diff] [blame] | 2 | ============= |
| 3 | |
| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 4 | OsmoBSC originated from the OpenBSC project, which started as a minimalistic |
| 5 | all-in-one implementation of the GSM Network. In 2017, OpenBSC had reached |
| 6 | maturity and diversity (including M3UA SIGTRAN and 3G support in the form of |
| 7 | IuCS and IuPS interfaces) that naturally lead to a separation of the all-in-one |
| 8 | approach to fully independent separate programs as in typical GSM networks. |
| Harald Welte | d94ee1e | 2008-12-29 04:50:01 +0000 | [diff] [blame] | 9 | |
| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 10 | OsmoBSC was one of the parts split off from the old openbsc.git. Before, it |
| 11 | worked as a standalone osmo-bsc binary as well as a combination of libbsc and |
| 12 | libmsc, i.e. the old OsmoNITB. Since the standalone OsmoMSC with a true A |
| 13 | interface (and IuCS for 3G support) is available, OsmoBSC exists only as a |
| 14 | separate standalone entity. |
| Harald Welte | 3f015f0 | 2015-12-05 23:13:35 +0100 | [diff] [blame] | 15 | |
| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 16 | OsmoBSC exposes |
| 17 | - A over IP towards an MSC (e.g. OsmoMSC); |
| 18 | - Abis interfaces towards various kinds of BTS; |
| 19 | - The Osmocom typical telnet VTY and CTRL interfaces. |
| Harald Welte | d94ee1e | 2008-12-29 04:50:01 +0000 | [diff] [blame] | 20 | |
| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 21 | Find OsmoBSC issue tracker and wiki online at |
| 22 | https://osmocom.org/projects/osmobsc |
| 23 | https://osmocom.org/projects/osmobsc/wiki |
| Harald Welte | 61b4232 | 2010-03-09 12:38:31 +0100 | [diff] [blame] | 24 | |
| Neels Hofmeyr | 538635a | 2017-09-04 03:25:24 +0200 | [diff] [blame] | 25 | OsmoBSC-NAT is a specialized solution to navigating RTP streams through a NAT. |
| 26 | (Todo: describe in more detail) |