|author||Daniel Willmann <email@example.com>||2018-10-23 18:20:02 +0200|
|committer||Harald Welte <firstname.lastname@example.org>||2018-11-18 20:06:00 +0000|
Change OpenBSC mentions to OsmoBSC where applicable
2 files changed, 2 insertions, 2 deletions
diff --git a/OsmoPCU/gb/bssgp.adoc b/OsmoPCU/gb/bssgp.adoc
index fe30d84..18f1842 100644
@@ -490,7 +490,7 @@ The BSSGP initialization directly follows NS connection establishment
described in <<ns_init>>.
OsmoPCU allocates a BVC context for the BVCI given by OsmoBTS, which
-in turn receives it from OpenBSC via OML procedures.
+in turn receives it from OsmoBSC or OsmoNITB via OML procedures.
In addition to the BVCI identifying the OsmoPCU side of BSSGP
connection, there is also special BVCI which is accepted by OsmoPCU in
diff --git a/common/chapters/bts.adoc b/common/chapters/bts.adoc
index 2e11db1..eb28497 100644
@@ -3,7 +3,7 @@
The main functionality of the BSC component is to manage BTSs. As such,
provisioning BTSs within the BSC is one of the most common tasks during
-BSC operation. Just like about anything else in OpenBSC, they are
+BSC operation. Just like about anything else in OsmoBSC, they are
configured using the VTY.
BTSs are internally numbered with integer numbers starting from "0" for