From 2262916e0c9422f93315044a47382aadbce31402 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sat, 9 Mar 2024 20:00:13 +0100 Subject: [PATCH] doc: Mention the `gb-dialect` vty option, as it is quite essential We should have introduced this documentation snipped years ago, when first introducing IP-SNS support in libosmogb/osmo-pcu. Change-Id: I83709b7231c2a3930e1b3f09b737319fb7d7e741 --- doc/manuals/chapters/overview.adoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc index 69d0672f..45aea537 100644 --- a/doc/manuals/chapters/overview.adoc +++ b/doc/manuals/chapters/overview.adoc @@ -106,6 +106,19 @@ in turn part of the libosmocore software package. This allows the same Gb implementation to be used from OsmoPCU, OsmoGbProxy as well as OsmoSGSN. +The Gb Implementation supports two different dialects: + +* `classic` dialect, which implements a non-standard dialect from the days + where Frame Relay was the default and no IP transport had yet been + specified by 3GPP. +* `ip-sns` dialect, which implements the 3GPP standard for NS-over-IP, + including the IP-SNS protocol. + +In case of doubt, and assuming you are directly interfacing to a +modern 3rd party SGSN, use the `ip-sns` dialect. + +Selection of the dialect is done using the `gb-dialect` VTY option at the `pcu` node. + [[pcu_sock_iface]] ==== `pcu_sock` Interface to OsmoBTS/OsmoBSC