Revision: 15531
Author: baranowb
Date: Mon Nov 29 01:04:13 2010
Log: Upate Issue 1616
xxx
http://code.google.com/p/mobicents/source/detail?r=15531
Modified:
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Design_Overview.xml
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Introduction.xml
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Protocol.xml
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Setup.xml
=======================================
---
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Design_Overview.xml
Tue Jul 6 00:46:08 2010
+++
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Design_Overview.xml
Mon Nov 29 01:04:13 2010
@@ -11,29 +11,26 @@
<important>
- <para>Be
- aware, &THIS.PLATFORM; &THIS.APPLICATION;
- is subject to changes as it is under active development!
+ <para>
+ &THIS.PLATFORM; &THIS.APPLICATION;
+ is subject to changes as it is under active development.
</para>
</important>
<para>
- <acronym>SCCP</acronym>
- resides on top of
- <acronym>mtp</acronym>
- layer. Top overview is depicted on diagram below:
+ SCCP
+ resides on top of the
+ mtp
+ layer. The diagram below depicts the top overview:
</para>
- <mediaobject id="ss7_design_sccp_overview_1">
- <imageobject>
- <imagedata width="300px" align="center"
- fileref="images/ss7-sccp-design-overview1.png"
format="PNG" />
- </imageobject>
- <caption>
- <para>&THIS.PLATFORM; &THIS.APPLICATION;
- SCCP
- </para>
- </caption>
- </mediaobject>
-
+ <figure>
+ <title>&THIS.PLATFORM; &THIS.APPLICATION; SCCP</title>
+ <mediaobject id="ss7_design_sccp_overview_1">
+ <imageobject>
+ <imagedata width="300px" align="center"
+ fileref="images/ss7-sccp-design-overview1.png" format="PNG" />
+ </imageobject>
+ </mediaobject>
+ </figure>
</chapter>
=======================================
---
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Introduction.xml
Mon Jul 12 08:58:48 2010
+++
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Introduction.xml
Mon Nov 29 01:04:13 2010
@@ -13,23 +13,23 @@
<para>
SCCP provides connectionless and connection-oriented network
services and global title translation (GTT) capabilities above
- <acronym>MTP</acronym>
- Level 3. SCCP provides also extended routing, flow control, segmentation
and reassembly of data service.
+ MTP
+ Level 3. SCCP also provides extended routing, flow control, segmentation
and reassembly of data services.
</para>
- <para> A global title is an address (e.g., a dialed 800 number,
+ <para>A global title is an address (for example, a dialed 800
number,
calling card number, or mobile subscriber identification number)
- which is translated by SCCP into a destination point code and
+ that is translated by SCCP into a destination point code and
subsystem number. A subsystem number uniquely identifies an
application at the destination signaling point.
- <acronym>SCCP</acronym>
+ SCCP
is used as the
transport layer for
- <acronym>TCAP</acronym>
+ TCAP
-based services
</para>
<para>
- <acronym>SCCP</acronym>
- data is sent between peers by means of Data Units (UDs)
+ SCCP
+ data is sent between peers by means of Data Units (UDs).
</para>
</chapter>
=======================================
---
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Protocol.xml
Thu Oct 7 07:51:07 2010
+++
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Protocol.xml
Mon Nov 29 01:04:13 2010
@@ -13,10 +13,10 @@
<section>
<title>Stack</title>
<para>
- <acronym>SCCP</acronym>
+ SCCP
stack relies on
- <acronym>MTP</acronym>
- to provide transport. Stack interface is
defined as follows:
+ MTP
+ to provide transport. The stack interface is
defined as follows:
</para>
<programlisting language="Java" role="JAVA">
package org.mobicents.protocols.ss7.sccp;
@@ -86,11 +86,11 @@
</programlisting>
</section>
<section>
- <title>Provider </title>
+ <title>Provider</title>
<para>
- Stack declares provider which allows user to
access stack
+ Stack declares the provider that allows the
user to access stack
facilities,
- send messages statelesly and register listener.
Provider
+ send messages statelessly and register a
listener. The provider
is defined
as follows:
</para>
@@ -145,11 +145,11 @@
}
</programlisting>
<para>
- Provider allows to register listener per
address. Listener will
- be called whenever stack receives message which
called
- party equals
+ The provider allows the user to register a listener per address. The
listener will
+ be called whenever the stack receives a message
that called the
+ party equal
to that address.
- Listener is defined as follows:
+ The listener is defined as follows:
</para>
<programlisting language="Java" role="JAVA">
package org.mobicents.protocols.ss7.sccp;
@@ -174,7 +174,7 @@
<section>
<title>Example</title>
<para>
- Below is simple example how to use
+ Below is a simple example for how to use
<literal>SCCP</literal>.
</para>
<programlisting language="Java" role="JAVA">
=======================================
---
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Setup.xml
Thu Oct 7 07:51:07 2010
+++
/trunk/protocols/ss7/sccp/docs/sources/src/main/resources/en-US/Chapter-Setup.xml
Mon Nov 29 01:04:13 2010
@@ -10,13 +10,13 @@
<section id="preinstall_requirements_and_prerequisites">
<title>Pre-Install Requirements and Prerequisites</title>
- <para>Ensure that the following requirements have been met before
continuing with the install.</para>
+ <para>Ensure that the following requirements have been met before
continuing with the installation process.</para>
<section id="hardware_requirements">
<title>Hardware Requirements</title>
- <para>The Stack doesn't change the &THIS.PLATFORM; Hardware
Requirements, however it requires <acronym>SS7</acronym> card.</para>
+ <para>The Stack doesn't change the &THIS.PLATFORM; Hardware
Requirements, however it does require an <acronym>SS7</acronym> card.</para>
<note>
<!-- Is this proper statement ? -->
- <para>Desired is high performance machine to process voice and data
channels.</para>
+ <para>A high performance machine is desired to process voice and data
channels.</para>
</note>
</section>
<section id="software_prerequisites">
@@ -46,9 +46,9 @@
<step>
<title>Downloading the source code</title>
<important>
- <para>Subversion is used to manage its source code. Instructions
for using Subversion, including install, can be found at <ulink
url="http://svnbook.red-bean.com" /></para>
+ <para>Subversion is used to manage its source code. Instructions
for using Subversion, including installation, can be found at <ulink
url="http://svnbook.red-bean.com" /></para>
</important>
- <para>Use SVN to checkout a specific release source, the base URL
is &THIS.RELEASE_SOURCE_CODE_URL;, then add the specific release version,
lets consider &THIS.VERSION;.</para>
+ <para>Use SVN to checkout a specific release source. The base URL
is &THIS.RELEASE_SOURCE_CODE_URL;. Then add the specific release version,
for example &THIS.VERSION;.</para>
<programlisting>[usr]$ svn co
&THIS.RELEASE_SOURCE_CODE_URL;/&THIS.VERSION;
&THIS.APPLICATION.DIRNAME;-&THIS.VERSION;</programlisting>
</step>
<step>
@@ -68,7 +68,7 @@
<section id="trunk_source_building">
<title>Development Trunk Source Building</title>
- <para>Similar process as for <xref linkend="release_source_building"/>,
the only change is the SVN source code URL, which is
&THIS.TRUNK_SOURCE_CODE_URL;.</para>
+ <para>A similar process as <xref linkend="release_source_building"/>.
The only change is the SVN source code URL, which is
&THIS.TRUNK_SOURCE_CODE_URL;.</para>
</section>
</section>