summaryrefslogtreecommitdiffstats
path: root/notFinishedCode
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-27 16:22:32 +0200
committerRefik Hadzialic2011-10-27 16:22:32 +0200
commitfc77bf21defd2cac48dd21d7dbf3d022c51afe98 (patch)
tree6213720810516e771c42ace5db404a906b622f42 /notFinishedCode
parentReport writing, describing the tests (Tri's part) (diff)
downloadgsm-selftest-fc77bf21defd2cac48dd21d7dbf3d022c51afe98.tar.gz
gsm-selftest-fc77bf21defd2cac48dd21d7dbf3d022c51afe98.tar.xz
gsm-selftest-fc77bf21defd2cac48dd21d7dbf3d022c51afe98.zip
Report writing
Diffstat (limited to 'notFinishedCode')
-rw-r--r--notFinishedCode/Report/test.aux8
-rw-r--r--notFinishedCode/Report/test.log10
-rw-r--r--notFinishedCode/Report/test.pdfbin1537592 -> 1539394 bytes
-rw-r--r--notFinishedCode/Report/test.tex14
-rw-r--r--notFinishedCode/Report/test.tex.backup64
-rw-r--r--notFinishedCode/Report/test.tex~10
-rw-r--r--notFinishedCode/Report/test.toc6
7 files changed, 81 insertions, 31 deletions
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index d97a02b..de2e619 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -100,9 +100,9 @@
\@writefile{toc}{\contentsline {subsection}{\numberline {9.3}Location of the files}{36}}
\@writefile{toc}{\contentsline {subsection}{\numberline {9.4}Setting up the parameters}{36}}
\@writefile{toc}{\contentsline {subsection}{\numberline {9.5}Test descriptions}{36}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {9.6}Using the software}{36}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {9.7}Error description}{36}}
-\@writefile{toc}{\contentsline {section}{\numberline {10}Conclusion}{37}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {9.6}Using the software}{37}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {9.7}Error description}{37}}
+\@writefile{toc}{\contentsline {section}{\numberline {10}Conclusion}{38}}
\bibcite{network}{1}
\bibcite{python}{2}
\bibcite{mysqlManual}{3}
@@ -116,4 +116,4 @@
\bibcite{beagleDataSheet}{11}
\bibcite{proctitle}{12}
\bibcite{pjsip}{13}
-\newlabel{LastPage}{{}{38}}
+\newlabel{LastPage}{{}{39}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index edc0917..1ea3e82 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 27 OCT 2011 15:41
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 27 OCT 2011 16:22
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -421,8 +421,8 @@ LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
<resultsImage.png, id=144, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
-[32 <./resultsImage.png (PNG copy)>] [33] [34] [35] [36] [37]
-AED: lastpage setting LastPage [38] (./test.aux) )
+[32 <./resultsImage.png (PNG copy)>] [33] [34] [35] [36] [37] [38]
+AED: lastpage setting LastPage [39] (./test.aux) )
Here is how much of TeX's memory you used:
4976 strings out of 495061
69340 string characters out of 1182621
@@ -445,9 +445,9 @@ ur/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/te
xmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive
/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (38 pages, 1537592 bytes).
+Output written on test.pdf (39 pages, 1539394 bytes).
PDF statistics:
- 770 PDF objects out of 1000 (max. 8388607)
+ 774 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
121 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 9c58bb1..2d18f1d 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index ba42fa7..2cf41ec 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -993,8 +993,18 @@ of problems they can identify. There are five types of tests:
Each test will be described in the few next paragraphs.
\par The \emph{smart} test is not called smart without a reason. It tries automatically to identify
problems inside of the telecommunication network. The user is not required to define what kind
-of tests have to be performed. In the first part it communicates with the database to see what
-is avai
+of tests have to be performed. In the first part the test software communicates with the
+database to see what systems are available. In the next step it performs a call from the
+University telephone system to a random local cell phone\footnote{Local cell phone or
+local GSM network means our University GSM Network or RZ GSM.}
+inside of our University GSM network.
+While executing this task, automatically the Asterisk server, OpenBSC and a random nanoBTS
+(or the one cell phone in RZ) are tested. The next task to be performed in the smart test,
+a randomly selected cell phone inside of our local GSM network will try to call: a random
+cell phone within the external (O2, Vodaphone,E-Plus or T-Mobile) or local GSM network.
+This might test the external network and will test it with high probability, however the
+probability exists to make a local to local GSM test call. In the third task, we perform
+a test where we call from the landline to a random cell phone inside of our local GSM network.
\subsection{Using the software}
\subsection{Error description}
\newpage
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index b94282d..d2a5768 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -454,19 +454,19 @@ keep in mind it works like a well defined state machine.}.
\begin{figure}[ht!]
\centering
- \includegraphics[width=130mm]{protocolCommunicationHandler.png}
+ \includegraphics[width=147mm]{protocolCommunicationHandler.png}
\caption[]{Flowchart of the protocol on the handler side without the state representation}
\end{figure}
\begin{figure}[ht!]
\centering
- \includegraphics[width=130mm]{protocolCommunicationcControllerReceiver.png}
+ \includegraphics[width=147mm]{protocolCommunicationcControllerReceiver.png}
\caption[]{Flowchart of the protocol on the controller side for the caller without the state representation}
\end{figure}
\begin{figure}[ht!]
\centering
- \includegraphics[width=130mm]{protocolCommunicationcControllerCaller.png}
+ \includegraphics[width=147mm]{protocolCommunicationcControllerCaller.png}
\caption[]{Flowchart of the protocol on the controller side for the receiver without the state representation}
\end{figure}
@@ -484,7 +484,11 @@ We modeled both sides, server and client side. As well as the server side being
and a callee. It was important to find out if our protocol is deadlock or delayed state free.
For more details our model can be found on our wiki project page with the PROMELA source code \cite{wiki}.
We had built in a 50\% random probability that the call test will not be successful, to make the model even more
-realistic. Our protocol idea was deadlock free and the verification results prove it:
+realistic. Our protocol idea was deadlock free and the verification results prove it.
+After we had modeled the basic idea we had written the code that implements our idea. The Python code
+resembles some kind of a state machine which remembers the last state and what the next state should be in case
+of receiving corresponding message. Otherwise it enters the exit state and then the start state.
+
\begin{lstlisting}
(Spin Version 6.1.0 -- 2 May 2011)
+ Partial Order Reduction
@@ -508,9 +512,6 @@ unreached in proctype Client
(0 of 67 states)
pan: elapsed time 0 seconds
\end{lstlisting}
-After we had modeled the basic idea we had written the code that implements our idea. The Python code
-resembles some kind of a state machine which remembers the last state and what the next state should be in case
-of receiving corresponding message. Otherwise it enters the exit state and then the start state.
\clearpage
\newpage
@@ -569,7 +570,6 @@ After we have created the public and private keys, and coppied the public key on
\begin{lstlisting}
refik@ubuntu:$ ssh remote-host
-Last login: Sun Nov 16 17:22:33 2008 from 192.168.1.2
[Note: SSH did not ask for password.]
refik@remote-host:$ [Note: You are on remote-host here]
@@ -725,7 +725,8 @@ sudo /etc/init.d/apache2 reload
\end{lstlisting}
The next step is to go to the directory where our test software web page is located
(e.g. \emph{/var/www-ssl/testsoftware}) and to create a file called \emph{.htaccess}.
-Please insert the following code segment inside the created \emph{.htaccess} file:
+Please insert the following code segment inside the created \emph{.htaccess} file where
+\emph{/var/www-ssl/testsoftware/.htpasswd} is your full path address to \emph{.htpasswd}:
\begin{lstlisting}
AuthUserFile /var/www-ssl/testsoftware/.htpasswd
AuthName "Authorization Required"
@@ -743,13 +744,25 @@ Afterwards, you will be required to type twice the same password for the usernam
you want to create, in this case \emph{konrad}. ``The -c flag is used only when you
are creating a new file. After the first time, you will omit the -c flag,
when you are adding new users to an already-existing password file. Otherwise you
-will overwrite the file!'' \cite{htaccess}.
-
-
-
-
-
-
+will overwrite the file!'' \cite{htaccess}. You can add as many users as you wish,
+do not forget to remove the -c flag when you do it.
+In the last step, we have to modify the \emph{/etc/apache2/apache2.conf} file and
+to add at the end of it the following code segment where \emph{/vaw/www-ssl/testsoftware}
+is the full path to your web page directory where you put the \emph{.htpasswd} file:
+\begin{lstlisting}
+<Directory /vaw/www-ssl/testsoftware>
+AllowOverride All
+</Directory>
+\end{lstlisting}
+We are done with editing. All we have to do now is to restart the Apache web server. We
+can do that by typing:
+\begin{lstlisting}
+sudo /etc/init.d/apache2 restart
+\end{lstlisting}
+You can test it now by opening a new browser tab and navigating to \emph{https://localhost/\\testsoftware}
+(keep in mind to replace \emph{testsoftware} with your name of the folder where the web page
+is located). If you configured everything properly, you should get a dialog where you can
+enter your created username and password and try to login.
\newpage
\section{Web page}
@@ -968,6 +981,25 @@ commands since some cell phone manufacturers do not use the standardized \emph{A
\subsection{Location of the files}
\subsection{Setting up the parameters}
\subsection{Test descriptions}
+In the following section we will describe the tests that can be performed and what kind
+of problems they can identify. There are five types of tests:
+\begin{itemize}
+\item Smart test
+\item SIP test
+\item GSM test
+\item Everything test
+\item Manual test
+\end{itemize}
+Each test will be described in the few next paragraphs.
+\par The \emph{smart} test is not called smart without a reason. It tries automatically to identify
+problems inside of the telecommunication network. The user is not required to define what kind
+of tests have to be performed. In the first part the test software communicates with the
+database to see what systems are available. In the next step it performs a call from the
+University telephone system to a random local cell phone inside of our University GSM network.
+While executing this task, automatically the Asterisk server, OpenBSC and a random nanoBTS
+(or the one cell phone in RZ) are tested. The next task to be performed in the smart test,
+a randomly selected cell phone inside of our local GSM network will try to call: a random
+cell phone within the external (O2, Vodaphone,E-Plus or T-Mobile) or local GSM network; or
\subsection{Using the software}
\subsection{Error description}
\newpage
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index c174acd..bae58e5 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -993,7 +993,15 @@ of problems they can identify. There are five types of tests:
Each test will be described in the few next paragraphs.
\par The \emph{smart} test is not called smart without a reason. It tries automatically to identify
problems inside of the telecommunication network. The user is not required to define what kind
-of tests have to be performed.
+of tests have to be performed. In the first part the test software communicates with the
+database to see what systems are available. In the next step it performs a call from the
+University telephone system to a random local cell phone inside of our University GSM network.
+While executing this task, automatically the Asterisk server, OpenBSC and a random nanoBTS
+(or the one cell phone in RZ) are tested. The next task to be performed in the smart test,
+a randomly selected cell phone inside of our local GSM network will try to call: a random
+cell phone within the external (O2, Vodaphone,E-Plus or T-Mobile) or local GSM network.
+This might test the external network and will test it with high probability, however the
+probability exists to make a local to local GSM test call.
\subsection{Using the software}
\subsection{Error description}
\newpage
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 9d99748..7047774 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -46,6 +46,6 @@
\contentsline {subsection}{\numberline {9.3}Location of the files}{36}
\contentsline {subsection}{\numberline {9.4}Setting up the parameters}{36}
\contentsline {subsection}{\numberline {9.5}Test descriptions}{36}
-\contentsline {subsection}{\numberline {9.6}Using the software}{36}
-\contentsline {subsection}{\numberline {9.7}Error description}{36}
-\contentsline {section}{\numberline {10}Conclusion}{37}
+\contentsline {subsection}{\numberline {9.6}Using the software}{37}
+\contentsline {subsection}{\numberline {9.7}Error description}{37}
+\contentsline {section}{\numberline {10}Conclusion}{38}