Change in osmo-gsm-manuals[master]: fix missing and/or non-existent linked references

laforge gerrit-no-reply at
Mon Apr 12 08:09:03 UTC 2021

laforge has submitted this change. ( )

Change subject: fix missing and/or non-existent linked references

fix missing and/or non-existent linked references

Change-Id: I5fe6263ac666e41cbe34407f09e9023aafa57d2c
M common/chapters/bibliography.adoc
M common/chapters/control_if.adoc
M common/chapters/rf.adoc
3 files changed, 5 insertions(+), 3 deletions(-)

  Jenkins Builder: Verified
  laforge: Looks good to me, approved

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 @@
+- [[[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
@@ -160,7 +162,7 @@
   system for telecommunication application providers
-- [[[ietf-rfc768]]] IETF RFC 768: Internet Protocol
+- [[[ietf-rfc791]]] IETF RFC 791: Internet Protocol
 - [[[ietf-rfc793]]] IETF RFC 793: Transmission Control Protocol
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 @@
 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 `` 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 @@
 . 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

To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: I5fe6263ac666e41cbe34407f09e9023aafa57d2c
Gerrit-Change-Number: 23695
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge at>
Gerrit-Reviewer: pespin <pespin at>
Gerrit-MessageType: merged
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list