diff options
| author | Daniel Willmann <daniel@totalueberwachung.de> | 2018-10-23 18:20:02 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-11-27 18:30:23 +0100 |
| commit | 96481c8d3f72711b218c62df4879df76366f5c7b (patch) | |
| tree | 5f7d828ff57cfecbfc5847a76662cb2dc70a91da | |
| parent | 2eeddee1323ea5f92667c689ca9a0c0bd6a88c17 (diff) | |
Change OpenBSC mentions to OsmoBSC where applicable
Change-Id: I4cc6874302b6089a54d44b09f08660a25e46d4dc
| -rw-r--r-- | doc/manuals/gb/bssgp.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manuals/gb/bssgp.adoc b/doc/manuals/gb/bssgp.adoc index fe30d847..18f1842d 100644 --- a/doc/manuals/gb/bssgp.adoc +++ b/doc/manuals/gb/bssgp.adoc @@ -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 |