manuals: fix wrong VTY node for 'gsmtap-sapi' command

Change-Id: Ifcf1cf9cdbad40862d48415e004865a91a61d1b1
This commit is contained in:
Vadim Yanitskiy 2021-04-16 07:04:56 +02:00 committed by fixeria
parent f88f539c77
commit 1334316844
1 changed files with 2 additions and 3 deletions

View File

@ -137,8 +137,7 @@ node of the OsmoBTS VTY.
OsmoBTS> enable
OsmoBTS# configure terminal
OsmoBTS(config)# bts 0
OsmoBTS(bts)# trx 0
OsmoBTS(trx)# gsmtap-sapi sdcch
OsmoBTS(bts)# gsmtap-sapi sdcch
OsmoBTS(trx)# write <1>
----
<1> the `write` command will make the configuration persistent in the
@ -146,7 +145,7 @@ configuration file. This is not required if you wish to enable GSMTAP
only in the current session of OsmoBTS.
De-activation can be performed similarly by using the `no gsmtap-sapi
sdcch` command at the `trx` node of the OsmoBTS VTY.
sdcch` command at the `bts` node of the OsmoBTS VTY.
From the moment they are enabled via VTY, GSMTAP messages will be
generated and sent in UDP encapsulation to the IANA-registered UDP port