\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Voip End-To-End Security using S/MIME and a Security Toolbox},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2014-01-15 (revised: 15 January 2014)}
\def\TheID{\makeatother }
\def\TheDate{2014-01-15}
\title{Voip End-To-End Security using S/MIME and a Security Toolbox}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Md. Shahidul  Islm}

             \affil[1]{  }

\renewcommand\Authands{ and }

\date{\small \em Received: 12 December 2013 Accepted: 5 January 2014 Published: 15 January 2014}

\maketitle


\begin{abstract}
        


Voice Over Internet Protocol (VOIP) is a rapidlygrowing Internet service for telephone communication. However, while it offers a number of cost advantages over traditional telephone service, it can pose a security threat, especially when used over public networks. In the absence of sufficient security, users of public networks are open to threats such as identity theft, man-in-the-middle attack, interception of messages/eavesdropping, DOS attacks, interruption of service and spam. S/MIME adds security to the message itself and can be used to provide end-to-end security to SIP. S/MIME can also offer confidentiality or integrity, or both, but it does not provide any anti-replay protection. However, we propose to use a unified architecture for the implementation of security protocols in the form of a security toolbox system. It will prevent an attack against anti-replay.

\end{abstract}


\keywords{S/MIME, SIP, IPSEC, replay attack, SDP .}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ow can a client be sure that his message will not be intercepted by someone? This is the most important and urgent question that security professionals have to answer when dealing with VoIP systems.\par
Voice over Internet Protocol is a rapidly growing Internet service. Voice over IP (VoIP) has been developed in order to provide access to voice communication anywhere in the world. VoIP is simply the transmission of voice conversations over IP-based networks. Although IP was originally planned for data networking, now it is also commonly used for voice networking. While VoIP (Voice over Internet Protocol) offers a number of cost advantages over traditional telephoning, it can also pose a security threat. So watertight security is needed when using VoIP, end-toend, especially when used on a public network. There is, however, no standard for VoIP and no general solution for VoIP security. The security of VoIP systems today is often non-existent or, in the best case, weak. As a result, hackers can easily hack. 
\section[{II.}]{II.} 
\section[{Review}]{Review}\par
Several writers have taken on this or similar problems. Gupta and Shmatikov \hyperref[b0]{[1]} investigated the security of the VoIP protocol stack, as well as SIP, SDP, ZRTP, MIKEY, SDES, and SRTP. Their investigation found a number of flaws and opportunity for replay Author: Rajshahi University of Engineering \& Technology (RUET) DEP: ETE, Rajshahi, Bangladesh. e-mail: sohidsakir@gmail.com attacks in SDES that could completely smash content protection. They showed that a man-in-the-middle attack was possible using ZRTP. They also found a weakness in the key derivation process used in MIKEY.\par
Niccolini et al. \hyperref[b1]{[2]} designed an intrusion prevention system architecture for use with SIP. They evaluated the effectiveness of legitimate SIP traffic in the presence of increasing volumes of malformed SIP INVITE messages in an attack scenario.\par
Fessi et al. \hyperref[b2]{[3]} proposed extensions to P2P SIP and developed a signaling protocol for P2P SIP that uses two different Kademlia-based overlay networks for storing information and forwarding traffic. Their system requires a centralised authentication server, which provides verifiable identities at the application/SIP layer.\par
Palmieri and Fiore \hyperref[b3]{[4]} describe an adaptation of SIP to provide end-to-end security using digital signatures and efficient encryption mechanisms. The authors developed a prototype implementation and conducted a performance analysis of their scheme. However, one weakness of this system is that it is open to man-in-the-middle attacks.\par
Syed Abdul and Mueed Mohd Salman \hyperref[b4]{[5]} developed Android driven security in SIP based VoIP systems using ZRTP on GPRS network. It communicated securely, using the GPRS data channel encrypted by using ZRTP technique. As it relies on ZRTP, it is probably vulnerable to man-in-the-middle attacks too.\par
Chirag Thaker, Nirali Soni and Pratik Patel \hyperref[b5]{[6]} developed a new Performance Analysis and Security Provisions for VoIP Servers. This paper provided a performance analysis of VoIP-based servers providing services like IPPBX, IVR, Voice-Mail, MOH, Video Call and also considered the security provisions for securing VoIP servers. 
\section[{III.}]{III.} 
\section[{Related Work}]{Related Work}\par
This paper considers a different solution, presenting a structure to assure end-to-end security by using the key management protocol S/MIME with the security toolbox system. S/MIME (Secure/Multipurpose Internet Mail Extensions) is a standard for public key encryption and signing of MIME data. S/MIME provides end-to-end integrity, confidentiality protection and does not require the intermediate proxies to be trusted. However, S/MIME does not provide any anti-replay protection. To protect against a replay attack, we use Year 2014 the security toolbox system. Toolbox system is a protocol as a single package comprised of two layers: control and a library of algorithms.\par
IV. 
\section[{Parameters' of a Solution}]{Parameters' of a Solution}\par
SIP is an application-layer protocol standardized by the Internet Engineering Task Force (IETF), and is designed to support the setup of bidirectional communication sessions for VoIP calls. The main SIP entities are endpoints (softphones or physical devices), a proxy server, a registrar, a redirect server, and a location server.\par
However, TLS (Transport Layer Security) can be used to introduce integrity and confidentiality to SIP between two points. Although it uses SIP signaling to secure, it has some limitations. Each proxy needs the SIP header in clear text to be able to route the message properly. All proxies in use in a connection must be trusted, as messages are decrypted and encrypted in each node. There will be no assurance that an SIP message cannot be intercepted by someone in the network.\par
IPSec can also be used to provide confidentiality, integrity, data origin authentication and even replay protection to SIP. It cannot be used in endto end security. Proxy servers need to read from SIP headers and sometimes write to them. It can be used in protecting data flows between a pair of hosts (host-tohost), between a pair of security gateways (network-tonetwork), or between a security gateway and a host (network-to-host). IPSec assumes, however, that a preestablished trust relationship has been introduced between the communicating parties, making it most suited for SIP hosts in a VPN scenario. Further, the SIP specification does not describe how IPSec should be used; neither does it describe how key management should be operated.\par
S/MIME is a set of specifications for securing electronic mail and can also be used to secure other applications such as SIP. S/MIME provides security services such as authentication, non-repudiation of origin, message integrity, and message privacy. Other security services include signed receipts, security labels, secure mailing lists, and an extended method of identifying the signer's certificate(s) etc.\par
S/MIME provides open, interoperable protocols that allow compliant software to exchange messages that are protected with digital signatures and encryption. S/MIME requires that each sender and recipient have an X.509-format digital certificate, so public-key infrastructure (PKI) design and deployment is a major part of S/MIME deployment.\par
The same mechanisms can be applied for SIP. The MIME security mechanism is referred to as S/MIME and is specified in RFC 2633. S/MIME adds security to the message itself and can be used to provide end-toend security to SIP.\par
Suppose two clients are trying to communicate each other. One client wants to send a message to the other client.\par
Figure  {\ref 1} shows how to send the message in secure way. Before S/MIME can be used to encrypt the message, one needs to obtain a key/certificate, either from one's in-house certificate authority (CA) or from a public CA.\par
The client uses S/MIME to sign and/or encrypt a SIP message. S/MIME combines public-key and secretkey cryptography. To encrypt the message, the sender obtains certificates from the certificate authority (CA) and generates a strong, random secret key. The message is then signed with the private key of the sender.\par
The encryption of the message is a bit trickier. It requires that the public key of the recipient is known to the sender. This key must be fetched in advance or be fetched from some kind of central repository. The secret key is used to encrypt the message, and then the public key of the recipient is used to encrypt the key for the  recipient. When the recipient gets the message, he uses the private key to decrypt his copy of the secret key, and the secret key is used to decrypt the original message. 
\section[{V.}]{V.}\par
The Security Risk S/MIME does not provide any anti-replay protection. The most serious attack is a replay attack on SDES, which causes SRTP to repeat the key stream used for media encryption, thus completely breaking transport-layer security. To protect against a replay attack, we use the security toolbox. How to use it to prevent an attack on SRTP, when used in combination with an SDES key exchange, is described below.\par
Suppose two users, Alice and Bob are trying to communicate with each other. Bob is the initiator in this session, and SDES is used to transport SRTP key material. To provide confidentiality for the SDES message, S/MIME is used to encrypt the payload. S/MIME does not provide any anti-replay protection. Suppose an attacker, Charles, is trying to attack the call. Charles sends the copy of Bob's original INVITE message to Alice, containing an S/MIMEencrypted SDP attachment, with the SDES key transfer message. Since Alice does not maintain any state for SDP, she will not be able to detect the replay. Charles will effectively, for Alice, become Bob! This is why it is proposed to use security toolbox: to prevent such a personation attack. Since anti-replay tools will be maintained all states for SDP, at all times, all messages will be filtered through anti-replay tools. Anti-replay tools will be able to detect the replay. S/MIME provides the security at the document level and IPSec performs the same function at the packet level. This configuration should become common whenever an application uses S/MIME as a document-level protection. 
\section[{VI.}]{VI.} 
\section[{A Security Toolbox}]{A Security Toolbox}\par
Ibrahim S. Abdullah and Daniel A. Menasce \hyperref[b8]{[9]} designed a security toolbox. In the toolbox, every tool carries out a specific function such as: encryption, decryption, random number generation, integrity protection, anti-replay, and header processing.   \hyperref[fig_2]{2} shows the major components of such a toolbox. The template is a set of specifications that define the required security services. The template database takes the necessary steps from the database for overall protection.\par
The toolbox architecture consists of two parts: one that must be secured as part of the trusted domain of the operating system (CBT) and another that may be part of the user domain.\par
The secure part consists of the following components:\par
1. Databases: store information about different operations of the toolbox, such as: private and secret keys, templates, registry for the tools and template names, alert messages, authorization information, policies, and the toolbox configuration information. 2. Interpretation engine: interprets protocol templates. \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}H}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-4.png}
\caption{\label{fig_3}Figure 2 :}\end{figure}
   			\footnote{© 2014 Global Journals Inc. (US)Abstract-Voice Over Internet Protocol (VOIP) is a rapidlygrowing Internet service for telephone communication. However, while it offers a number of cost advantages over traditional telephone service, it can pose a security threat, especially when used over public networks. In the absence of sufficient security, users of public networks are open to threats such as identity theft, man-in-the-middle attack, interception of messages/eavesdropping, DOS attacks, interruption of service and spam. S/MIME adds security to the message itself and can be used to provide end-to-end security to SIP. S/MIME can also offer confidentiality or integrity, or both, but it does not provide any anti-replay protection. However, we propose to use a unified architecture for the implementation of security protocols in the form of a security toolbox system. It will prevent an attack against anti-replay.} 			\footnote{© 2014 Global Journals Inc. (US)Voip End-To-End Security using S/Mime and a Security Toolbox} 		 		\backmatter  			 \par
attack. This happens because S/MIME does not identify the source of the messages coming into the system. This article suggests a solution to this problem by combining the S/MIME with a security toolbox, using IPSec to monitor IP packet. The toolbox monitors the IP packet of message originators and, where a new IP address enters from the same source, denies access to the message. Such a solution guarantees complete end-to-end user security for VoIP messages at minimal cost. Thus S/MIME, with this solution, maximizes effectiveness, given the technology of the moment, in protecting the user.			 			  				\begin{bibitemlist}{1}
\bibitem[Abdullah and Menasce ()]{b8}\label{b8} 	 		‘A unified architecture for the implementation of security protocols’.  		 			Ibrahim S Abdullah 		,  		 			Daniel A Menasce 		.  	 	 		\textit{the Proc. of Computer Applications in Industry and Engineering (CAINE03)},  				 (Las Vegas, Nevada USA)  		2003. p. .  	 
\bibitem[Syed Abdul Mueed and Salman ()]{b6}\label{b6} 	 		‘Android driven security in SIP based VoIP systems using ZRTP on GPRS network’.  		 			Mohd Syed Abdul Mueed 		,  		 			Salman 		.  	 	 		\textit{International Journal of Computer Networks and Wireless Communications (IJCNWC)},  				2012. 2.  	 
\bibitem[Fessi et al. ()]{b3}\label{b3} 	 		‘Pr2-P2PSIP: Privacy Preserving P2P Signaling for VoIP and IM’.  		 			N Fessi 		,  		 			H Evans 		,  		 			R Niedermayer 		,  		 			Holz 		.  	 	 		\textit{Proceedings of the 4th Annual ACM Conference on Principles, Systems and Applications of IP Telecommunications (IPTCOMM)},  				 (the 4th Annual ACM Conference on Principles, Systems and Applications of IP Telecommunications (IPTCOMM))  		2010. p. .  	 
\bibitem[Palmieri and Fiore ()]{b4}\label{b4} 	 		‘Providing True Endto-End Security in Converged Voice over IP Infrastructures’.  		 			F Palmieri 		,  		 			U Fiore 		.  	 	 		\textit{Computers \& Security}  		2009. 28 p. .  	 
\bibitem[Gupta and Shmatikov ()]{b0}\label{b0} 	 		‘Security Analysis of Voice-over-IP Protocols’.  		 			P Gupta 		,  		 			V Shmatikov 		.  	 	 		\textit{Proceedings of the 20th IEEE Computer Security Foundations Symposium (CSFW)},  				 (the 20th IEEE Computer Security Foundations Symposium (CSFW))  		2007. p. .  	 
\bibitem[Petraschek et al. ()]{b1}\label{b1} 	 		‘Security and Usability Aspects of Man-in-the-Middle Attacks on ZRTP’.  		 			M Petraschek 		,  		 			T Hoeher 		,  		 			O Jung 		,  		 			H Hlavacs 		,  		 			W N Ganstere 		.  	 	 		\textit{Journal of Universal Computer Science}  		2008. 14  (5)  p. .  	 
\bibitem[Niccolini et al. ()]{b2}\label{b2} 	 		‘SIP Intrusion Detection and Prevention: Recommendations and Prototype Implementation’.  		 			S Niccolini 		,  		 			R G Garroppo 		,  		 			S Giordano 		,  		 			G Risi 		,  		 			S Ventura 		.  	 	 		\textit{Proceedings of the 1st IEEE Workshop on VoIP Management and Security (VoIP MaSe)},  				 (the 1st IEEE Workshop on VoIP Management and Security (VoIP MaSe))  		2006. p. .  	 
\bibitem[Murphy ()]{b5}\label{b5} 	 		\textit{Toll Fraud Challenges and Prevention in a VoIP Environment (President of Phone Power)},  		 			Jim Murphy 		.  		2013.  	 
\bibitem[Zar et al. ()]{b7}\label{b7} 	 		 			Jonathan Zar 		,  		 			David Endler 		,  		 			Dipak Ghosal 		.  		\textit{VoIP Security and Privacy Threat Taxonomy (VIOPSA)},  				2005.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
