From 923fb05cbff83e07798a8ee9d7fbb987c472c09e Mon Sep 17 00:00:00 2001
From: Refik Hadzialic
Date: Fri, 28 Oct 2011 15:25:28 +0200
Subject: Report writing

---
 notFinishedCode/Report/test.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'notFinishedCode/Report/test.tex')

diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 7ae54a9..1233416 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -175,7 +175,7 @@ The key point in the design of our database was the simplicity and speed of acce
 \par The \emph{PingResultTable} table has six attributes (\emph{taskNo, sipServer, sipGate, unisip, gsmBox1, gsmBox2}), all of integer type. 
 The \emph{taskNo} attribute identifies the test number but not a single test (e.g. an operator user has selected three different tests to be executed, all of the three tests will have the same \emph{taskNo} to identify them together as belonging to one test group and \emph{taskId} identifies each single test and will be explained later). 
 \emph{sipServer} represents the Asterisk server ping result. \emph{sipGate} is used to represent the SIP Gate server for the landline calls (\url{http://www.sipgate.de}). \emph{uniSip} represents the ping results for our local University telephone network SIP server. 
-\emph{gsmBox1} and \emph{gsmBox2} are the two single-chip Linux computers (BeagleBoard), that controll two cell phones each one (i.e. they are also known under the name of \emph{nanoBTSx}).
+\emph{gsmBox1} and \emph{gsmBox2} are the two single-chip Linux computers (BeagleBoard), that controll two cell phones each one (i.e. they are also known under the name of \emph{nanoBTSx controller}).
 \emph{taskNo} is the primary and unique key in the table \emph{PingResultTable}. Rest of the attributes (i.e. \emph{sipServer, sipGate, uniSip, gsmBox1, gsmBox2}) are used to insert the ping results, if the assigned servers are reachable or not.
 Before any test attempt is made, our test software first tries to ping the servers. These results are then stored in the \emph{PingResultTable}.
 
@@ -373,7 +373,7 @@ the communication between the handlers and the main test software (controller).
   \includegraphics[width=60mm]{controllerclass.png}
   \caption[]{Controller class}
 \end{figure}
-If the callee or the caller are nanoBTS control boxes (i.e. BeagleBoards outside 
+If the callee or the caller are nanoBTS controller boxes (i.e. BeagleBoards outside 
 the Rechenzentrum), it will first create an SSH connection to make a tunnel before 
 the local socket connection is created. Then the controller class sends all the 
 required data regarding the test tasks to the handlers. 
@@ -1075,7 +1075,7 @@ problems on the Asterisk server and our University telephone network, including
 outgoing calls from the SIP side. 
 \subsubsection{GSM test}
 In the \emph{GSM} test both GSM networks get tested, the local and the external GSM netwrok. 
-We test the nanoBTS boxes (i.e. BeagleBoards) as well. Using this test, both incoming 
+We test the nanoBTS controller boxes (i.e. BeagleBoards) as well. Using this test, both incoming 
 and outgoing calls are performed, we can detect possible errors on the OpenBSC and the nanoBTS.
 \subsubsection{All test}
 The \emph{All} test selects all the given tests and executes them step-by-step. It is the test
-- 
cgit v1.2.3-55-g7522

