Osmocom Open Build Service

commit_59d031823d3c07325f6226096cc4778ed7170e32.txt Deleted

commit_832258a471d8f72494dbdbb904b6ab3b158d18ec.txt Added

osmo-gsm-manuals-dev_1.4.0.4.59d0.dsc -> osmo-gsm-manuals-dev_1.4.0.5.8322.dsc Changed

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/.tarball-version -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/.tarball-version Changed

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/common/chapters/cell-broadcast.adoc -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/common/chapters/cell-broadcast.adoc Changed

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/common/chapters/preface.adoc -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/common/chapters/preface.adoc Changed

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/common/chapters/sigtran-osmocom.adoc -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/common/chapters/sigtran-osmocom.adoc Changed

@@ -38,7 +38,7 @@
 ==== The present (2017)
 
 In 2017, sysmocom was tasked with implementing a 3GPP AoIP compliant A
-interface.  This meant that lot of things had to change in the
+interface.  This meant that a lot of things had to change in the
 existing code:
 
 * removal of the existing hard-wired SCCPlite/IPA code from OsmoBSC
@@ -112,7 +112,7 @@
 `accept-asp-connections dynamic-permitted`.
 
 To enable dynamic registration of routing keys via RKM, the
-corresponding SS7 Instance (<<ss7-instance>>) must be confgured with
+corresponding SS7 Instance (<<ss7-instance>>) must be configured with
 `xua rkm routing-key-allocation dynamic-permitted`.
 
 This is of course highly insecure and can only be used in trusted,
@@ -349,7 +349,7 @@
 |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
-                  expriation, the queue is flushed.
+                  expiration, the queue is flushed.
 |State|Application Server State (Down, Inactive, Active, Pending)
 |ASPs|Which ASPs are permitted to transfer traffic for this AS
 |====
@@ -360,7 +360,7 @@
 connection.  From the STP/SG (Server) point-of-view, those are
 incoming connections from Application Servers such as the BSCs.  From
 the ASP (Client) Point of view, it has one `osmo_ss7_asp` object for
-each outbound SIGTARN connection.
+each outbound SIGTRAN connection.
 
 An ASP has the following properties:

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/common/chapters/sigtran.adoc -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/common/chapters/sigtran.adoc Changed

@@ -33,7 +33,7 @@
 === Message Transfer Part (MTP)
 
 MTP is the lower layer of the SS7 protocol stack.  It is comprised of
-two sub-layes, called MTP2 and MTP3.
+two sub-layers, called MTP2 and MTP3.
 
 Nodes in a MTP network are addressed by their unique PC (Point Code).
 
@@ -54,7 +54,7 @@
 ==== Point Codes
 
 The length of point codes depends on the particular MTP dialect that
-is used.  In the 1980ies, when international telephony signaling
+is used.  In the 1980s, when international telephony signaling
 networks were established, most countries had their own national
 dialects with certain specifics.
 
@@ -210,7 +210,7 @@
 SS7 backbone by means as SUA and M3UA.  Over time, even the links of
 the actual network backbone networks became more and more IP based.
 
-In order to replace existing TDM-based SS7 links/liksets with SIGTRAN,
+In order to replace existing TDM-based SS7 links/linksets with SIGTRAN,
 the M2UA or M2PA variants are used as a kind of drop-in replacement
 for physical links.
 
@@ -334,7 +334,7 @@
 underlying IP transport is transparent to the SS7/SCCP applications,
 there is no restriction on whether to use SIGTRAN over IPv4 or IPv6.
 
-==== SCTP multi-homing in SIGTARN
+==== SCTP multi-homing in SIGTRAN
 
 SCTP, unlike more traditional IP L4 protocols (TCP, UDP) doesn't work
 based on a _connection_ between source IP:port and Destination IP:port.

osmo-gsm-manuals-dev_1.4.0.4.59d0.tar.xz/debian/changelog -> osmo-gsm-manuals-dev_1.4.0.5.8322.tar.xz/debian/changelog Changed

Changes of Revision 15