From 1334316844c85709e71b21979f0003ffb55c4be9 Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Fri, 16 Apr 2021 07:04:56 +0200 Subject: manuals: fix wrong VTY node for 'gsmtap-sapi' command Change-Id: Ifcf1cf9cdbad40862d48415e004865a91a61d1b1 --- doc/manuals/chapters/configuration.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'doc/manuals') diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc index 772d8daf..107fcfdc 100644 --- a/doc/manuals/chapters/configuration.adoc +++ b/doc/manuals/chapters/configuration.adoc @@ -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 -- cgit v1.2.3