Browse > Article
http://dx.doi.org/10.6109/jkiice.2008.12.6.1022

Secure Framework for SIP-based VoIP Network  

Han, Kyong-Heon (조선대학교 정보통신학과)
Choi, Dong-You (조선대학교 정보통신학과)
Bae, Yong-Guen (조선대학교 컴퓨터공학부)
Abstract
Session Initiation Protocol (SIP) has become the call control protocol of choice for Voice over IP (VoIP) networks because of its open and extensible nature. However, the integrity of call signaling between sites is of utmost importance, and SIP is vulnerable to attackers when left unprotected. Currently a herby-hop security model is prevalent, wherein intermediaries forward a request towards the destination user agent sewer (UAS) without a user agent client (UAC) knowing whether or not the intermediary behaved in a trusted manner. This paper presents an integrated security model for SIP-based VoIP network by combining hop-by-hop security and end-to-end security.
Keywords
SIP; hop by hop; end to end; VoIP; SIP;
Citations & Related Records
연도 인용수 순위
  • Reference
1 K. Ono and S. Tachimoto, 'Requirements for End- to-Middle Security for the Session Initiation Protocol (SIP),' IETF draft-ietf-sipping-e2m-sec-reqs-06, March 2005
2 K. Ono and S. Tachimoto, 'SIP signaling security for end-to-end communication,' Proc. of 9th Asia-Pacific Conference on Communications, APCC 2003, Sept. 2003
3 S. Salsano, L. Veltri, and D. Papalilo, 'SIP Security Issues: The SIP Authentication Procedure and its Processing Load,' IEEE Network, 16(6): 38-44, Nov/Dec 2002
4 B. Ramsdell, 'Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification,' IETF RFC 3851, July 2004
5 S. Kent, R. Atkinson 'Security Architecture for the Internet Protocol', Request for Comments: 2401, November 1998
6 J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, and E. Schooler, 'SIP: Session Initiation Protocol,' IETF RFC 3261, June 2002
7 M. Handley and V. Jacobson, 'SDP: Session Description Protocol,' IETF RFC 2327, April 1998
8 T. Dierks and C. Allen, 'The TLS Protocol Version 1.0,' IETF RFC 2246, Jan. 1999