summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--common/chapters/abis.adoc4
-rw-r--r--common/chapters/control_if.adoc2
-rw-r--r--common/chapters/gb.adoc2
-rw-r--r--common/chapters/gsup.adoc6
-rw-r--r--common/chapters/mncc.adoc2
-rw-r--r--common/chapters/oap.adoc2
-rw-r--r--common/chapters/osmux/mgcp_extension_osmux.adoc2
-rw-r--r--common/chapters/sigtran-osmocom.adoc18
-rw-r--r--common/chapters/sigtran.adoc12
-rw-r--r--common/chapters/smpp.adoc4
10 files changed, 27 insertions, 27 deletions
diff --git a/common/chapters/abis.adoc b/common/chapters/abis.adoc
index 7524661..a46abfa 100644
--- a/common/chapters/abis.adoc
+++ b/common/chapters/abis.adoc
@@ -82,11 +82,11 @@ A tool called ipaccess-config can be used to configure a new ip.access nanoBTS.
==== ipaccess-config
This program is very helpful tool which is used to configure Unit ID and
-Primarly OML IP. You can find this tool in the OsmoBSC repository under:
+Primary OML IP. You can find this tool in the OsmoBSC repository under:
'./src/ipaccess'
-.Example: using ipaccess-config to configure Unit ID and Primarly OML IP of
+.Example: using ipaccess-config to configure Unit ID and Primary OML IP of
nanoBTS
----
$ ./ipaccess-config -u 1801/0/0<1> 10.9.1.195<2> -o 10.9.1.154<3>
diff --git a/common/chapters/control_if.adoc b/common/chapters/control_if.adoc
index cd639c7..67ac045 100644
--- a/common/chapters/control_if.adoc
+++ b/common/chapters/control_if.adoc
@@ -169,7 +169,7 @@ The rate counter group name have to be prefixed with interval
specification which can be any of "*per_sec*", "*per_min*", "*per_hour*", "*per_day*"
or "*abs*" for absolute value.
-The old-style counters available via "+counter.*+" variables are superceeded by "+rate_ctr.abs+"
+The old-style counters available via "+counter.*+" variables are superseded by "+rate_ctr.abs+"
so its use is discouraged.
There might still be some applications not yet converted to rate_ctr.
diff --git a/common/chapters/gb.adoc b/common/chapters/gb.adoc
index 6a6f65c..3e33eea 100644
--- a/common/chapters/gb.adoc
+++ b/common/chapters/gb.adoc
@@ -91,7 +91,7 @@ NSEI 101, NS-VC 101, Remote: BSS, ALIVE UNBLOCKED, UDP 10.9.1.119:23000
ALIVE ACK missing count : 0 (0/s 0/m 0/h 0/d)
RESET ACK missing count : 0 (0/s 0/m 0/h 0/d)
NSVC Peer Statistics:
- ALIVE reponse time : 0 ms
+ ALIVE response time : 0 ms
----
.Example: Inspecting BSSGP state
diff --git a/common/chapters/gsup.adoc b/common/chapters/gsup.adoc
index c67dfca..e0034f9 100644
--- a/common/chapters/gsup.adoc
+++ b/common/chapters/gsup.adoc
@@ -363,7 +363,7 @@ Direction: SGSN / VLR => HLR
|===
The conditional 'AUTS' and 'RAND' IEs are both present in case the SIM
-(via UE) requests an UMTS AKA re-synchronization procedure. Eiter
+(via UE) requests an UMTS AKA re-synchronization procedure. Either
both optional IEs are present, or none of them.
==== Send Authentication Info Error
@@ -1181,7 +1181,7 @@ tuple.
|27|RES|<<gsup-ie-res>>|C|TLV|2-18
|===
-The conditional IEs 'IK', 'CK', 'AUTN' and 'RES' are onl present in
+The conditional IEs 'IK', 'CK', 'AUTN' and 'RES' are only present in
case the subscriber supports UMTS AKA.
[[gsup-ie-rand]]
@@ -1197,7 +1197,7 @@ The 4-byte Authentication Result of the GSM Authentication Algorithm.
[[gsup-ie-kc]]
==== Kc
-The 8-byte Encryption Key of the GSM Authentication and Key Agreemnt
+The 8-byte Encryption Key of the GSM Authentication and Key Agreement
Algorithm.
[[gsup-ie-ik]]
diff --git a/common/chapters/mncc.adoc b/common/chapters/mncc.adoc
index 3adbf7f..15c9982 100644
--- a/common/chapters/mncc.adoc
+++ b/common/chapters/mncc.adoc
@@ -68,7 +68,7 @@ depending on the signaling direction. A mobile originated DTMF tone is
signaled using START/STOP DTMF messages which are hauled through various
protocols upwards into the core network.
-Contrary to that, a mobile terminated DTMF tone is not transfered as an out of
+Contrary to that, a mobile terminated DTMF tone is not transferred as an out of
band message. Instead, in-band signaling is used, which means a tone is injected
early inside a PBX or MGW.
diff --git a/common/chapters/oap.adoc b/common/chapters/oap.adoc
index 3c5ad35..ad91f36 100644
--- a/common/chapters/oap.adoc
+++ b/common/chapters/oap.adoc
@@ -209,7 +209,7 @@ Not used.
[options="header",cols="15%,85%"]
|===
-|0x04|Register Requst
+|0x04|Register Request
|0x05|Register Error
|0x06|Register Result
|0x08|Challenge Request
diff --git a/common/chapters/osmux/mgcp_extension_osmux.adoc b/common/chapters/osmux/mgcp_extension_osmux.adoc
index c12e9ef..e2b0947 100644
--- a/common/chapters/osmux/mgcp_extension_osmux.adoc
+++ b/common/chapters/osmux/mgcp_extension_osmux.adoc
@@ -98,7 +98,7 @@ writing this document.
In OmoMGW, Osmux support is managed through VTY.
-.Example: Sample config file section with Osmux configuation
+.Example: Sample config file section with Osmux configuration
----
mgcp
...
diff --git a/common/chapters/sigtran-osmocom.adoc b/common/chapters/sigtran-osmocom.adoc
index 1f2bb1e..3fbaac2 100644
--- a/common/chapters/sigtran-osmocom.adoc
+++ b/common/chapters/sigtran-osmocom.adoc
@@ -14,7 +14,7 @@ This is despite the fact that ETSI/3GPP mandated the use of SCCP over
MTP over E1/T1 TDM lines for the A interface at that time.
Instead of going down to the TDM based legacy physical layers, OsmoBSC
-implemented someting called an IPA multiplex, which apparently some
+implemented something called an IPA multiplex, which apparently some
people also refer to as SCCPlite. We have never seen any
specifications for this interface, but implemented it from scratch
using protocol traces.
@@ -152,8 +152,8 @@ SS7/SIGTRAN stack, there are the following options:
. implement SCCP connection coupling. This is something like a proxy
for connection-oriented SCCP, and is what is used in SS7 to route
- beyond a given MTP netwokr (e.g. at gateways between different MTP
- networks)
+ beyond a given MTP network (e.g. at gateways between different MTP
+ networks).
. consider all SCCP messages to be destined for the local point code
of the receiver. This then means that the SG functionality must be
@@ -197,7 +197,7 @@ STP is performing some routing function. Compares this to your web
browser not knowing about IP routers, it just establishes an http
connection to a web server.
-This is also why most GSM nework architecture diagrams will not
+This is also why most GSM network architecture diagrams will not
explicitly show an STP. It is not part of the cellular network.
Rather, one or many STPs are part of the underlying SS7 signaling
transport network, on top of which the cellular network elements are
@@ -231,7 +231,7 @@ All you need to make sure is:
* to point all BSCs and the MSC to connect to the IP+Port of the STP
* to configure the point code of the MSC in the BSCs
-==== A minimaal 3G configuration to get started
+==== A minimal 3G configuration to get started
You will be running the following programs:
@@ -252,7 +252,7 @@ include::sigtran-simple-3g.dot[]
----
You can use the OsmoSTP fully dynamic registration feature, so the
-HNBGWs, the SMC and the SGSNwill simply register with their point
+HNBGWs, the MSC and the SGSN will simply register with their point
codes to the STP, and the STP will create most configuration on the
fly.
@@ -345,7 +345,7 @@ An AS has the following properties:
|Description|More verbose description (for human user only)
|Protocol|Protocol (M3UA, SUA, IPA) to be operated by this server
|Routing Key|Routing Key (mostly Point Code) routed to this AS
-|Traffic Mode|Theoretically Bradcast, Load-Balance. Currently only Ovverride
+|Traffic Mode|Theoretically Broadcast, Load-Balance. Currently only Override
|Recovery Timeout|Duration of the AS T(r) recovery timer. During this time,
outgoing messages are queued. If the AS is ACTIVE
before timer expiration, the queue is drained. At
@@ -398,7 +398,7 @@ Application Servers are identified by their name.
=== Osmocom SCCP Instances
-An Osmocom SS7 Instance can be bound to an Osmocom SS7 Instance. It
+An Osmocom SCCP Instance can be bound to an Osmocom SS7 Instance. It
will register/bind for the ITU-standard Service Indicator (SI).
=== Osmocom SCCP User
@@ -419,7 +419,7 @@ corresponding SSNs.
This is how Osmocom represents each individual connection of
connection-oriented SCCP.
-To illustrate the practical applicaiton: For the common use case of
+To illustrate the practical application: For the common use case of
the A or Iu interfaces, this means that every dedicated radio channel
that is currently active to any UE/MS has one SCCP connection to the
MSC and/or SGSN.
diff --git a/common/chapters/sigtran.adoc b/common/chapters/sigtran.adoc
index fd7d3cc..9e02f38 100644
--- a/common/chapters/sigtran.adoc
+++ b/common/chapters/sigtran.adoc
@@ -89,9 +89,9 @@ isolated MTP networks, each with their own MTP dialect and addressing.
SCCP provides both connectionless (datagram) and connection-oriented
services. Both are used in the context of cellular networks.
-==== SCCP Adresses
+==== SCCP Addresses
-SCCP Adresses are quite complex. This is due to the fact that it is
+SCCP Addresses are quite complex. This is due to the fact that it is
not simply one address format, but in fact a choice of one or multiple
different types of addresses.
@@ -136,11 +136,11 @@ as well as the _Nature of Address Indication_.
|NAI|Nature of Address Indicator|Exists in GTI=1 and is sort of a mixture of TON + NPI
|TT|Translation Type |Used as a look-up key in Global Title Translation Tables
|NP|Numbering Plan |Indicates ITU Numbering Plan, such as E.164, E.212, E.214
-|ES|Encoding Scheme |Just a peculiar way to idicate the length of the digits
+|ES|Encoding Scheme |Just a peculiar way to indicate the length of the digits
|- |Signals |The actual "phone number digits"
|====
-For more information about SCCP Adresses and Global Titles, please
+For more information about SCCP Addresses and Global Titles, please
refer to <<itu-t-q713>>
@@ -189,7 +189,7 @@ connection is established.
This means that connection-oriented SCCP can not be routed across MTP
network boundaries the same way as connectionless SCCP messages.
-Instead, an STP would have to perform _connection coupling_, whic is
+Instead, an STP would have to perform _connection coupling_, which is
basically the equivalent of an application-level proxy between two
SCCP connections, each over one of the two MTP networks.
@@ -233,7 +233,7 @@ them. For more information, please see the related IETF RFCs.
===== Signaling Gateway (SG)
-The Signaling Gateway (SG) interconnects the SS7 network wit external
+The Signaling Gateway (SG) interconnects the SS7 network with external
applications. It translates (parts of) the SS7 protocol stack into an
IP based SIGTRAN protocol stack. Which parts at which level of the
protocol stack are translated to what depends on the specific SIGTRAN
diff --git a/common/chapters/smpp.adoc b/common/chapters/smpp.adoc
index e62a844..4efb46d 100644
--- a/common/chapters/smpp.adoc
+++ b/common/chapters/smpp.adoc
@@ -128,7 +128,7 @@ TLVs to each SMPP DELIVER PDU:
|===
All of the above values reflect the *last measurement report* as
-recieved vi A-bis RSL from the BTS. It is thus a snapshot value (of
+received vi A-bis RSL from the BTS. It is thus a snapshot value (of
the average within one 480ms SACCH period), and not an average over
all the SACCH periods during which the channel was open or the SMS was
received. Not all measurement reports contain all the values. So you
@@ -143,5 +143,5 @@ to each SMPP DELIVER PDU:
[options="header", cols="3,1,1,5"]
|===
| TLV | IEI | Length | Purpose
-| TLVID_osmo_imei | 0x2306 | variable | IMEI of the subscibers phone (ME)
+| TLVID_osmo_imei | 0x2306 | variable | IMEI of the subscribers phone (ME)
|===