aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVadim Yanitskiy <vyanitskiy@sysmocom.de>2021-04-10 05:30:43 +0200
committerVadim Yanitskiy <vyanitskiy@sysmocom.de>2021-04-10 05:31:07 +0200
commit0a5a50b67bd3f8aafb554f05e004d597e20ab2ac (patch)
treef64d91dd8cb585d405d2ae5600f976de212b995f
parenta137f4a47cb18016e6e8d44cd77d15f229f91569 (diff)
fix missing and/or non-existent linked references
-rw-r--r--common/chapters/bibliography.adoc4
-rw-r--r--common/chapters/control_if.adoc2
-rw-r--r--common/chapters/rf.adoc2
3 files changed, 5 insertions, 3 deletions
diff --git a/common/chapters/bibliography.adoc b/common/chapters/bibliography.adoc
index e447325..67f0cb9 100644
--- a/common/chapters/bibliography.adoc
+++ b/common/chapters/bibliography.adoc
@@ -81,6 +81,8 @@
https://ftp.osmocom.org/docs/latest/osmotrx-lms-vty-reference.pdf
https://ftp.osmocom.org/docs/latest/osmotrx-ipc-vty-reference.pdf
https://ftp.osmocom.org/docs/latest/osmotrx-usrp1-vty-reference.pdf
+- [[[3gpp-ts-23-041]]] 3GPP TS 23.041: Technical realization of
+ Cell Broadcast Service (CBS)
- [[[3gpp-ts-23-048]]] 3GPP TS 23.048: Security mechanisms for the
(U)SIM application toolkit; Stage 2
https://www.3gpp.org/DynaReport/23048.htm
@@ -160,7 +162,7 @@
system for telecommunication application providers
https://www.etsi.org/deliver/etsi_ts/101200_101299/101220/12.00.00_60/ts_101220v120000p.pdf
-- [[[ietf-rfc768]]] IETF RFC 768: Internet Protocol
+- [[[ietf-rfc791]]] IETF RFC 791: Internet Protocol
https://tools.ietf.org/html/rfc791
- [[[ietf-rfc793]]] IETF RFC 793: Transmission Control Protocol
https://tools.ietf.org/html/rfc793
diff --git a/common/chapters/control_if.adoc b/common/chapters/control_if.adoc
index 67ac045..e64f661 100644
--- a/common/chapters/control_if.adoc
+++ b/common/chapters/control_if.adoc
@@ -188,7 +188,7 @@ Another implementation is in `scripts/osmo_rate_ctr2csv.py` which will retrieve
for a given Osmocom program and output it in csv format. This can be used to periodically (using systemd timer
for example) retrieve data to build KPI and evaluate how it changes over time.
-Internally it uses "+rate_ctr.*+" variable described in <<ctrl_common_var>> to get the list of counter groups
+Internally it uses "+rate_ctr.*+" variable described in <<ctrl_common_vars>> to get the list of counter groups
and than request all the counters in each group. Applications interested in individual metrics can request it
directly using `rate_ctr2csv.py` as an example.
diff --git a/common/chapters/rf.adoc b/common/chapters/rf.adoc
index f3f6dd9..637fb5e 100644
--- a/common/chapters/rf.adoc
+++ b/common/chapters/rf.adoc
@@ -45,7 +45,7 @@ So in order to estimate the loss of a coaxial cable, you need to
. determine the frequency at which you will use the cable, as determined
by the GSM frequency band of your BTS. Make sure you use the highest
frequency that might occur, which is typically the upper end of the
- transmit band, see <<gsm-bands>>
+ transmit band, see <<rf-gsm-bands>>
. determine the attenuation of your cable per 100m at the given
frequency (check the cable data sheet)
. scale that value by the actual length of the cable