laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/31996 )
Change subject: doc: overview: replace section TRAU mapper / E1 sub-channel muxer
......................................................................
doc: overview: replace section TRAU mapper / E1 sub-channel muxer
The manual contains a section about a TRAU mapper / E1 sub-channel
muxer. This section seems to be copied from the OsmoNITB manual. In
OsmoNITB everything was integrated in one binary, now dealing with TRAU
frames is the task of the MGW. Let's remove the section but still leave
a word about how Speech traffic is handled/relayed by OsmoBSC.
Change-Id: If33589feb80e1b29b4f841b678fe5329b8c06a76
---
M doc/manuals/chapters/overview.adoc
1 file changed, 24 insertions(+), 7 deletions(-)
Approvals:
Jenkins Builder: Verified
pespin: Looks good to me, but someone else must approve
laforge: Looks good to me, approved
diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc
index a27b0bf..aca0c98 100644
--- a/doc/manuals/chapters/overview.adoc
+++ b/doc/manuals/chapters/overview.adoc
@@ -135,11 +135,13 @@
For more information, see <<net>>, <<bts>> and <<bts-examples>>.
-==== TRAU mapper / E1 sub-channel muxer
+==== Speech traffic
-Unlike classic GSM networks, OsmoBSC does not perform any transcoding.
-Rather, a compatible codec is selected for both legs of a call, and
-codec frames are passed through transparently. In order to achieve this
-with E1 based BTS, OsmoBSC contains a E1 sub-channel de- and
-re-multiplexer as well as a TRAU mapper that can map uplink to downlink
-frames and vice versa.
+OsmoBSC, by itself, does not perform any transcoding or relaying of user plane
+speech traffic. This task is handled entirely by a BSC co-located media gateway,
+such as OsmoMGW, which will take care of relaying the RTP traffic from the BTS
+into the core network.
+
+In case classic E1 based BTSs are used, OsmoBSC will instruct the MGW to
+convert between TRAU frames on the E1 side and RTP frames on the IP based core
+network side.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/31996
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: If33589feb80e1b29b4f841b678fe5329b8c06a76
Gerrit-Change-Number: 31996
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: merged
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32009 )
Change subject: common/chapters: http -> https
......................................................................
common/chapters: http -> https
Change-Id: Idf88e6141aad37d731a1955ad8b30f956c44a417
---
M common/chapters/osmux/osmux.adoc
M common/chapters/preface.adoc
2 files changed, 11 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/09/32009/1
diff --git a/common/chapters/osmux/osmux.adoc b/common/chapters/osmux/osmux.adoc
index a727e2e..6862d9c 100644
--- a/common/chapters/osmux/osmux.adoc
+++ b/common/chapters/osmux/osmux.adoc
@@ -9,7 +9,7 @@
reduction.
Full reference document for the osmux protocol can be found here:
-http://ftp.osmocom.org/docs/latest/osmux-reference.pdf
+https://ftp.osmocom.org/docs/latest/osmux-reference.pdf
In Osmocom satellite based GSM networks, the satellite link is envisioned to be
in between the BSS and the core network, that is, between the BSC and the MSC
diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc
index b9a32d6..7dad998 100644
--- a/common/chapters/preface.adoc
+++ b/common/chapters/preface.adoc
@@ -293,7 +293,7 @@
If you don't have a support package / contract, you have the option of
using the resources put together by the Osmocom community
-at http://projects.osmocom.org/, checking out the wiki and
+at https://projects.osmocom.org/, checking out the wiki and
the mailing-list for community-based assistance. Please always
remember, though: The community has no obligation to help you, and you
should address your requests politely to them. The information (and
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32009
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: Idf88e6141aad37d731a1955ad8b30f956c44a417
Gerrit-Change-Number: 32009
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32007 )
Change subject: chapters/logging: Expand documentation on GSMTAP logging
......................................................................
chapters/logging: Expand documentation on GSMTAP logging
Change-Id: I9d7a15fd81bb0f3bc89b97ebfd35e9efc48c94e2
---
M common/chapters/logging.adoc
1 file changed, 28 insertions(+), 3 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/07/32007/1
diff --git a/common/chapters/logging.adoc b/common/chapters/logging.adoc
index a832ca4..0b31211 100644
--- a/common/chapters/logging.adoc
+++ b/common/chapters/logging.adoc
@@ -200,9 +200,16 @@
==== Logging via gsmtap
-When debugging complex issues it's handy to be able to reconstruct exact chain of events. This is enabled by using GSMTAP
-log output where frames sent/received over the air are intersperced with the log lines. It also simplifies the bug handling
-as users don't have to provide separate .pcap and .log files anymore - everything will be inside self-contained packet dump.
+GSMTAP is normally a pseudo-header format that enables the IP-transport of GSM (or other telecom) protocols
+that are not normally transported over IP. For example, the most common situation is to enable GSMTAP in
+OsmoBTS or OsmoPCU to provide GSM-Um air interface capture files over IP, so they can be analyzed in
+wireshark.
+
+GSMTAP logging is now a method how Osmocom software can also encapsulate its own log output in GSMTAP frames.
+We're not trying to re-invent rsyslog here, but this is very handy When debugging complex issues. It enables
+the reader of the pcap file containing GSMTAP logging together with other protocol traces to reconstruct exact
+chain of events. A single pcap file can then contain both the log output of any number of Osmocom programs in
+the same timeline of the messages on various interfaces in and out of said Osmocom programs.
It's configured as follows:
----
@@ -230,6 +237,15 @@
OsmoBSC(config-log)# logging level force-all fatal
----
+NOTE: Every time you generate GSMTAP messages and send it to a unicast (non-broadcast/multicast) IP address,
+please make sure that the destination IP address actually has a socket open on the specified port, or drops
+the packets in its packet filter. If unicast GSMTAP messages arrive at a closed destination UDP port, the
+operating system will likely generate ICMP port unreachable messages. Those ICMP messages in turn will, when
+arriving at the source (the host on which you run the Osmocom software sending GSMTAP), suppress generation
+of further GSMTAP messages for some time, resulting in incomplete files. In case of doubt, either send GSMTAP
+to multicast IP addresses, or run something like `nc -l -u -p 4729 > /dev/null` on the destination host to
+open the socket at the GSMTAP port and discard anything arriving at it.
+
==== Logging to a file
As opposed to Logging to the VTY, logging to files is persistent and
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32007
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: I9d7a15fd81bb0f3bc89b97ebfd35e9efc48c94e2
Gerrit-Change-Number: 32007
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32008 )
Change subject: chapters/preface: Thank NLnet and WaveMobile
......................................................................
chapters/preface: Thank NLnet and WaveMobile
Change-Id: Ib887489fce522981df298594931100b9e553c291
---
M common/chapters/preface.adoc
1 file changed, 13 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/08/32008/1
diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc
index 272f84a..b9a32d6 100644
--- a/common/chapters/preface.adoc
+++ b/common/chapters/preface.adoc
@@ -79,6 +79,10 @@
* Jan Luebbe, Stefan Schmidt, Daniel Willmann, Pablo Neira, Nico Golde,
Kevin Redon, Ingo Albrecht, Alexander Huemer, Alexander Chemeris, Max
Suraev, Tobias Engel, Jacob Erlbeck, Ivan Kluchnikov
+* NLnet Foundation, for providing funding for a number of individual work items
+ within the Osmocom universe, such as LTE support in OsmoCBC or GPRS/EGPRS
+ support for Ericsson RBS6000.
+* WaveMobile Ltd, for many years of sponsoring.
May the source be with you!
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32008
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: Ib887489fce522981df298594931100b9e553c291
Gerrit-Change-Number: 32008
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32010 )
Change subject: preface: indicate where to ask for commercial support
......................................................................
preface: indicate where to ask for commercial support
Change-Id: I386d9bd31afe363677f23751d9ffe99f14800484
---
M common/chapters/preface.adoc
1 file changed, 14 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/10/32010/1
diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc
index 7dad998..f102aea 100644
--- a/common/chapters/preface.adoc
+++ b/common/chapters/preface.adoc
@@ -300,3 +300,8 @@
software) provided at osmocom.org is put together by volunteers for
free. Treat them like a friend whom you're asking for help, not like a
supplier from whom you have bought a service.
+
+If you would like to obtain professional/commercial support on Osmocom
+CNI, you can always reach out to sales(a)sysmocom.de to discuss your
+support needs. Purchasing support from sysmocom helps to cover the
+ongoing maintenance of the Osmocom CNI software stack.
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32010
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: I386d9bd31afe363677f23751d9ffe99f14800484
Gerrit-Change-Number: 32010
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange