DOCSLIB.ORG

An Analysis of Instant Messaging and E- Mail Access Protocol Behavior in Wireless Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Analysis of Instant Messaging and E- Mail Access Protocol Behavior in Wireless Environment An Analysis of Instant Messaging and E- mail Access Protocol Behavior in Wireless Environment IIP Mixture Project Simone Leggio Tuomas Kulve Oriana Riva Jarno Saarto Markku Kojo March 26, 2004 University of Helsinki - Department of Computer Science i TABLE OF CONTENTS 1 Introduction ..................................................................................................................................... 1 PART I: BACKGROUND AND PROTOCOL ANALYSIS ............................................................. 1 2 Instant Messaging............................................................................................................................ 1 3 ICQ.................................................................................................................................................. 3 3.1 Overview ................................................................................................................................. 3 3.2 Protocol Operation .................................................................................................................. 4 3.2.1 Client to Server................................................................................................................4 3.2.2 Client to Client ................................................................................................................5 3.2.3 Normal Operation............................................................................................................ 5 3.2.4 Abnormal Operation........................................................................................................ 5 3.3 Discussion ............................................................................................................................... 6 3.3.1 Advantages of ICQ.......................................................................................................... 6 3.3.2 Disadvantages of ICQ ..................................................................................................... 6 4 AOL/Oscar ...................................................................................................................................... 7 4.1 Overview ................................................................................................................................. 7 4.2 Protocol Operation .................................................................................................................. 7 5 MSN Messenger.............................................................................................................................. 9 5.1 Overview ................................................................................................................................. 9 5.2 Protocol Operation ................................................................................................................ 10 5.3 Discussion ............................................................................................................................. 11 6 Yahoo ............................................................................................................................................ 12 7 IRC ................................................................................................................................................ 13 7.1 Overview ............................................................................................................................... 13 7.2 Protocol Operation ................................................................................................................ 13 7.3 Discussion ............................................................................................................................. 15 8 SILC .............................................................................................................................................. 15 8.1 Overview ............................................................................................................................... 15 8.2 Protocol Operation ................................................................................................................ 16 8.3 Discussion ............................................................................................................................. 17 9 Jabber ............................................................................................................................................ 17 9.1 Overview ............................................................................................................................... 17 9.2 Protocol Operation ................................................................................................................ 18 9.3 Discussion ............................................................................................................................. 20 10 Other Protocols.......................................................................................................................... 21 ii 10.1 TOC....................................................................................................................................... 21 10.2 Napster .................................................................................................................................. 22 10.3 Zephyr ................................................................................................................................... 24 11 The Internet Message Access Protocol...................................................................................... 25 11.1 The mail access paradigms.................................................................................................... 26 11.2 Description of IMAP features ............................................................................................... 27 11.3 Discussion on IMAP ............................................................................................................. 28 11.4 The IMAP state machine....................................................................................................... 29 12 Detailed analysis of the selected protocols................................................................................ 31 12.1 Detailed analysis of IRC........................................................................................................31 12.2 Detailed analysis of SILC...................................................................................................... 33 12.3 Detailed analysis of Jabber.................................................................................................... 34 12.3.1 Discussion on the deployment of XMPP in a wireless link .......................................... 40 12.3.2 Analysis of session establishment sequence.................................................................. 42 12.3.3 Behaviour in disconnected environments and in case of packets losses ....................... 46 12.4 Detailed analysis of the Internet Message Access Protocol .................................................. 46 12.4.1 Discussion on the deployment of IMAP in a wireless link ........................................... 50 12.4.2 Behaviour in disconnected environments and in case of packet losses......................... 52 13 Protocols Comparison ............................................................................................................... 52 PART II: JABBER TEST REPORT................................................................................................. 55 14 Test environment....................................................................................................................... 55 14.1 Best-case scenario ................................................................................................................. 57 15 Test case 1: Delay in the downlink direction ............................................................................ 58 16 Test case 2: Delay in the uplink direction ................................................................................. 65 17 Test case 3: Reconnection of a client ........................................................................................ 69 18 Test case 4: Delay in reconnection. Downlink direction........................................................... 70 19 Test case 5: Delay in reconnection. Uplink direction................................................................ 74 19.1 Connection of the fixed client after message delivery to the server...................................... 75 19.2 Reconnection of the fixed client during message delivery to the server ............................... 77 20 Other test cases.......................................................................................................................... 80 20.1 Tests with the older server version........................................................................................ 80 20.2 Preliminary tests with the Jabberd2 server............................................................................ 82 20.3 Tests with two source clients................................................................................................. 83 21 Discussion on Jabber experiments............................................................................................. 84 21.1 The pacing of message sending............................................................................................
Load more

Recommended publications
  • Uila Supported Apps
    Uila Supported Applications and Protocols updated Oct 2020 Application/Protocol Name Full Description 01net.com 01net website, a French high-tech news site. 050 plus is a Japanese embedded smartphone application dedicated to 050 plus audio-conferencing. 0zz0.com 0zz0 is an online solution to store, send and share files 10050.net China Railcom group web portal. This protocol plug-in classifies the http traffic to the host 10086.cn. It also 10086.cn classifies the ssl traffic to the Common Name 10086.cn. 104.com Web site dedicated to job research. 1111.com.tw Website dedicated to job research in Taiwan. 114la.com Chinese web portal operated by YLMF Computer Technology Co. Chinese cloud storing system of the 115 website. It is operated by YLMF 115.com Computer Technology Co. 118114.cn Chinese booking and reservation portal. 11st.co.kr Korean shopping website 11st. It is operated by SK Planet Co. 1337x.org Bittorrent tracker search engine 139mail 139mail is a chinese webmail powered by China Mobile. 15min.lt Lithuanian news portal Chinese web portal 163. It is operated by NetEase, a company which 163.com pioneered the development of Internet in China. 17173.com Website distributing Chinese games. 17u.com Chinese online travel booking website. 20 minutes is a free, daily newspaper available in France, Spain and 20minutes Switzerland. This plugin classifies websites. 24h.com.vn Vietnamese news portal 24ora.com Aruban news portal 24sata.hr Croatian news portal 24SevenOffice 24SevenOffice is a web-based Enterprise resource planning (ERP) systems. 24ur.com Slovenian news portal 2ch.net Japanese adult videos web site 2Shared 2shared is an online space for sharing and storage.
    [Show full text]
  • Webrtc and XMPP
    webRTC and XMPP Philipp Hancke, XMPP Summit 2013 What is this webRTC thing … …and why should XMPP developers care? . I assume you know what XMPP is… . … you might have heard of Jingle . the XMPP framework for establishing P2P sessions . used for VoIP, filesharing, … . … you might have also heard about this webRTC thing . doing VoIP in the browser . without plugins . „no more flash“ . Do you want to know how it relates to XMPP ? Philipp Hancke © ESTOS GmbH 2013 2 What is webRTC? . P2P sessions between browsers . no servers involved in media transfer . using open standards . Javascript API in the browser . also an BSD-licensed C++ library from Google . Want to know more? . Listen to the evangelists! . Justin Uberti http://www.youtube.com/watch?v=E8C8ouiXHHk . Jose de Castro http://vimeo.com/52510068 . Cullen Jennings http://vimeo.com/cullenfluffyjennings/rtcwebexplained Philipp Hancke © ESTOS GmbH 2013 3 Initiating P2P sessions . initiate a P2P session between two browsers . negotiate media codecs, NAT traversal, etc . media is sent P2P . you need a session initiation protocol . SIP? . JSEP? . H.323? . Jingle! . webRTC does not mandate a signalling protocol . WG decision Philipp Hancke © ESTOS GmbH 2013 4 Call Flow - JSEP Philipp Hancke © ESTOS GmbH 2013 5 Jingle . You can use Jingle as signalling protocol . together with BOSH or XMPP over websockets in the browser . Demo later . But… . webRTC uses the Session Description Protocol as an API . Jingle does not use SDP . You need a mapping SDP -> Jingle -> SDP . Complicated, but doable . Topic for breakout Philipp Hancke © ESTOS GmbH 2013 6 Call Flow - Jingle Philipp Hancke © ESTOS GmbH 2013 7 webRTC-Jingle usecases .
    [Show full text]
  • SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst
    ISSN (Print) : 2320 – 3765 ISSN (Online): 2278 – 8875 International Journal of Advanced Research in Electrical, Electronics and Instrumentation Engineering Vol. 2, Issue 5, May 2013 SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst. Prof, Dept. of ECE, Siliguri Institute of Technology, Sukna, Siliguri, West Bengal, India 1 Network Engineer, Network Dept, Ericsson Global India Ltd, India2 Abstract:-. The Secure Internet Live Conferencing (SILC) protocol, a new generation chat protocol provides full featured conferencing services, compared to any other chat protocol. Its main interesting point is security which has been described all through the paper. We have studied how encryption and authentication of the messages in the network achieves security. The security has been the primary goal of the SILC protocol and the protocol has been designed from the day one security in mind. In this paper we have studied about different keys which have been used to achieve security in the SILC protocol. The main function of SILC is to achieve SECURITY which is most important in any chat protocol. We also have studied different command for communication in chat protocols. Keywords: SILC protocol, IM, MIME, security I.INTRODUCTION SILC stands for “SECURE INTERNET LIVE CONFERENCING”. SILC is a secure communication platform, looks similar to IRC, first protocol & quickly gained the status of being the most popular chat on the net. The security is important feature in applications & protocols in contemporary network environment. It is not anymore enough to just provide services; they need to be secure services. The SILC protocol is a new generation chat protocol which provides full featured conferencing services; additionally it provides security by encrypting & authenticating the messages in the network.
    [Show full text]
  • Universidad Pol Facultad D Trabajo
    UNIVERSIDAD POLITÉCNICA DE MADRID FACULTAD DE INFORMÁTICA TRABAJO FINAL DE CARRERA ESTUDIO DEL PROTOCOLO XMPP DE MESAJERÍA ISTATÁEA, DE SUS ATECEDETES, Y DE SUS APLICACIOES CIVILES Y MILITARES Autor: José Carlos Díaz García Tutor: Rafael Martínez Olalla Madrid, Septiembre de 2008 2 A mis padres, Francisco y Pilar, que me empujaron siempre a terminar esta licenciatura y que tanto me han enseñado sobre la vida A mis abuelos (q.e.p.d.) A mi hijo icolás, que me ha dejado terminar este trabajo a pesar de robarle su tiempo de juego conmigo Y muy en especial, a Susana, mi fiel y leal compañera, y la luz que ilumina mi camino Agradecimientos En primer lugar, me gustaría agradecer a toda mi familia la comprensión y confianza que me han dado, una vez más, para poder concluir definitivamente esta etapa de mi vida. Sin su apoyo, no lo hubiera hecho. En segundo lugar, quiero agradecer a mis amigos Rafa y Carmen, su interés e insistencia para que llegara este momento. Por sus consejos y por su amistad, les debo mi gratitud. Por otra parte, quiero agradecer a mis compañeros asesores militares de Nextel Engineering sus explicaciones y sabios consejos, que sin duda han sido muy oportunos para escribir el capítulo cuarto de este trabajo. Del mismo modo, agradecer a Pepe Hevia, arquitecto de software de Alhambra Eidos, los buenos ratos compartidos alrrededor de nuestros viejos proyectos sobre XMPP y que encendieron prodigiosamente la mecha de este proyecto. A Jaime y a Bernardo, del Ministerio de Defensa, por haberme hecho descubrir las bondades de XMPP.
    [Show full text]
  • CCIA Comments in ITU CWG-Internet OTT Open Consultation.Pdf
    CCIA Response to the Open Consultation of the ITU Council Working Group on International Internet-related Public Policy Issues (CWG-Internet) on the “Public Policy considerations for OTTs” Summary. The Computer & Communications Industry Association welcomes this opportunity to present the views of the tech sector to the ITU’s Open Consultation of the CWG-Internet on the “Public Policy considerations for OTTs”.1 CCIA acknowledges the ITU’s expertise in the areas of international, technical standards development and spectrum coordination and its ambition to help improve access to ICTs to underserved communities worldwide. We remain supporters of the ITU’s important work within its current mandate and remit; however, we strongly oppose expanding the ITU’s work program to include Internet and content-related issues and Internet-enabled applications that are well beyond its mandate and core competencies. Furthermore, such an expansion would regrettably divert the ITU’s resources away from its globally-recognized core competencies. The Internet is an unparalleled engine of economic growth enabling commerce, social development and freedom of expression. Recent research notes the vast economic and societal benefits from Rich Interaction Applications (RIAs), a term that refers to applications that facilitate “rich interaction” such as photo/video sharing, money transferring, in-app gaming, location sharing, translation, and chat among individuals, groups and enterprises.2 Global GDP has increased US$5.6 trillion for every ten percent increase in the usage of RIAs across 164 countries over 16 years (2000 to 2015).3 However, these economic and societal benefits are at risk if RIAs are subjected to sweeping regulations.
    [Show full text]
  • Daniel Nashed "CSI Domino" Diagnostic Collection & NSD Analysis
    "CSI Domino" Diagnostic Collection & NSD Analysis Daniel Nashed AdminCamp 2016 – Sept. 19-21 in Gelsenkirchen About the presenter ● Nash!Com – German IBM® Business Partner/ISV – Member of The Penumbra group -- an international consortium of selected Business Partners pooling their talent and resources ● Focused on Cross-Platform C-API, IBM® Domino® Infrastructure, Administration, Integration, Troubleshooting and IBM® Traveler – Platform Focus: Microsoft® Windows® 32/64, Linux® and IBM AIX® ● Author of the Domino on Linux®/UNIX® Start Script – Note: Working on RHEL7 + SLES 12 “systemd” support Agenda ● Introduction – What is „Serviceability“ ● Automatic Data Collection (ADC), Configuration Collector ● NSD, Memcheck – Server Crashes, Hangs, Annotation of NSDs ● Memory Management ● Advanced Methods – Semaphore Debugging – Memory Dumps ● Performance Troubleshooting ● Q&A – Any time Useful Software & Tools ● Software – Notes Peek – Lotus Notes Diagnostics (LND) – 7Zip – open source ZIP tool – Ultraedit (commerical but great) or Notepad++ (free) – NashCom Tools ● nshcrash ● Nshmem ● C-API Toolkit – Great source of information What is Serviceability? ● RAS = Reliability Availability Serviceability ● RAS is the effort to improve the Domino Product suite so that: – Client/Server doesn’t crash or hang as often (Reliability) – Client/Server performs well, Server is available to clients (Availability) – The ability to quickly pin-point and fix problems (Serviceability) ● Ongoing effort in each incremental release – Some features are even back-ported
    [Show full text]
  • Cheat Sheet – Common Ports (PDF)
    COMMON PORTS packetlife.net TCP/UDP Port Numbers 7 Echo 554 RTSP 2745 Bagle.H 6891-6901 Windows Live 19 Chargen 546-547 DHCPv6 2967 Symantec AV 6970 Quicktime 20-21 FTP 560 rmonitor 3050 Interbase DB 7212 GhostSurf 22 SSH/SCP 563 NNTP over SSL 3074 XBOX Live 7648-7649 CU-SeeMe 23 Telnet 587 SMTP 3124 HTTP Proxy 8000 Internet Radio 25 SMTP 591 FileMaker 3127 MyDoom 8080 HTTP Proxy 42 WINS Replication 593 Microsoft DCOM 3128 HTTP Proxy 8086-8087 Kaspersky AV 43 WHOIS 631 Internet Printing 3222 GLBP 8118 Privoxy 49 TACACS 636 LDAP over SSL 3260 iSCSI Target 8200 VMware Server 53 DNS 639 MSDP (PIM) 3306 MySQL 8500 Adobe ColdFusion 67-68 DHCP/BOOTP 646 LDP (MPLS) 3389 Terminal Server 8767 TeamSpeak 69 TFTP 691 MS Exchange 3689 iTunes 8866 Bagle.B 70 Gopher 860 iSCSI 3690 Subversion 9100 HP JetDirect 79 Finger 873 rsync 3724 World of Warcraft 9101-9103 Bacula 80 HTTP 902 VMware Server 3784-3785 Ventrilo 9119 MXit 88 Kerberos 989-990 FTP over SSL 4333 mSQL 9800 WebDAV 102 MS Exchange 993 IMAP4 over SSL 4444 Blaster 9898 Dabber 110 POP3 995 POP3 over SSL 4664 Google Desktop 9988 Rbot/Spybot 113 Ident 1025 Microsoft RPC 4672 eMule 9999 Urchin 119 NNTP (Usenet) 1026-1029 Windows Messenger 4899 Radmin 10000 Webmin 123 NTP 1080 SOCKS Proxy 5000 UPnP 10000 BackupExec 135 Microsoft RPC 1080 MyDoom 5001 Slingbox 10113-10116 NetIQ 137-139 NetBIOS 1194 OpenVPN 5001 iperf 11371 OpenPGP 143 IMAP4 1214 Kazaa 5004-5005 RTP 12035-12036 Second Life 161-162 SNMP 1241 Nessus 5050 Yahoo! Messenger 12345 NetBus 177 XDMCP 1311 Dell OpenManage 5060 SIP 13720-13721
    [Show full text]
  • Secure Internet Live Conferencing
    Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Secure Internet Live Conferencing Frank Benkstein <[email protected]> 26.10.2007, 19:12:23h Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Übersicht I Einführung I SILC vs. IRC vs. XMPP I Architektur I Protokoll Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Geschichte Geschichte 1996 Idee und Entwurf durch Pekka Riikonen 1997 erster Code 1998 Rewrite in C++ 1999 Rewrite in C 2000 erste Veröffentlichung der Quelltexte Einreichung der Spezifikationen bei der IETF 2003 SILC-Client 1.0 Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Design Ziele I Echtzeit-Text-Kommunikation I Viele-Zu-Viele (ähnlich IRC) I Eins-Zu-Eins (Instant Messaging) I Multimedia-Fähigkeit I Datei-Transfer I Sicherheit I Modularität Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Protokoll-Eigenschaften I Verschlüsselung I gesamte Kommunikation verschüsselt und authentifiziert I unverschlüsselte Kommunikation unmöglich* I Signatur von Nachrichten I Unicode (UTF-8) statt ASCII I Nicknames I Channel-Namen I Nachrichten I Peer-to-Peer für Dateitransfer I alles andere über Server Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Clients I eindeutige Client-ID I Nicknamen I nicht eindeutig* I UTF-8 I bis zu 128 Bytes (!) lang I gleicher Public-Key möglich Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs.
    [Show full text]
  • Viral Triggers
    Viral Triggers Instant Messaging Ilia Mirkin [email protected] January 26, 2005 Instant Messaging ! Talk: Communications between terminals ! Zephyr: Developed at MIT; little use outside ! ICQ: First popular IM service ! AIM: At first for AOL members only, later free service to all, but with ads for non-AOL members ! Jabber: Open IM architecture, though similar to AIM in most respects ! MSN/Yahoo/etc: Proprietary but free services similar to AIM ! Rendezvous: Can be used for messaging in LANs ! Skype: Peer-to-peer application for both voice and text Talk ! Originally developed for Multics, in 1973 ! Became a standard UNIX command with 4.2BSD ! Further enhancements to connect terminals over a network, and later, to be able to connect more than 2 parties (Ytalk - 1990) ! Was popular amongst UNIX users since its existence, though no concrete usage statistics are available ! Has become marginalized by other IM systems that do not require people to be logged in on terminals Zephyr Developed at MIT under Project Athena Designed to run under Unix, there are few clients available, as well as few users outside universities Started in the 1980's, has not gained widespread acceptance. However it does provide various security enhancements, such as interoperability with Kerberos Protocol specifications available freely, open source clients ICQ (“I Seek You”) Created by Mirabilis, Inc., in 1996 First IM service to gain wide acceptance, mostly via member- driven advertising Used numbers to identify members (much like Compuserve) Allowed messages to be stored on server and delivered them when the target user would log on Overtaken in popularity by AIM, which allowed people to pick any username Currently accepts new users, but the service has become very similar to AIM, and uses the same servers AOL IM AOL bought up Mirabilis, and recreated ICQ as AIM Two protocols: OSCAR and TOC OSCAR included all the features of AIM, but was closed.
    [Show full text]
  • Sir Charles Poised for Comms Vision
    Bahman Rahimi: An Node4 channel chief entrepreneur with his outlines strategy for mind on growth p32 mid-market push p46 VOL 22 ISSUE 5 OCTOBER 2017 www.comms-dealer.com Call recording for PCI, FCA and MiFID ll compliance. oak.co.uk ADVERTISEMENT ADVERTISEMENT THE HEARTBEAT OF THE UK COMMS INDUSTRY THINK For Reliable & Scaleable Recording Solutions, MiFIDII, FCA & PCI Compliance e: [email protected] t: 020 3488 1498 w: www.vidicodeuk.com 3-22 Industry News Fully white labelled Catch up with hosted telephony events in comms solution from £2.75 Take Control of Your PBX Deploy24 on Windows, Linux or in the Cloud Business Matters Q3 dominated by fibre-fest and M&A CD_commcloud.pdf 1 24/04/2017 12:24 www.channeltelecom.com www.channeltelecom.com 26 Experience the Interview Sir Charles poisedC Thirkill and the rise M of3CX GCI People PhoneCloud System Y CM Communications Cloud • Easy to install & managefor Comms VisionMY 34 CY We get your • Inexpensive to buy and expand Case study SIR Charles Dunstone, one of the UK’s most successful ICT entrepreneurs, willCMY employees, outline his vision for the future of the industry at Gleneagles next month. • VirtualizeApprenticeships or run in and the cloud (Windows / Linux) K customers and why they matter apps talking • Halve your phone bill with SIPEXCLUSIVE Trunks ing a culture to drive growth’, In June 2012 Dunstone rec- TalkTalk Executive Chairman eived a Knighthood for his ser- • Increase48 mobility with smartphoneComms Vision Conference clients org- Sir Charles will take part in vices to the telecommunications aniser Comms Dealer has con- an exclusive conversation and industry and his charitable work.
    [Show full text]
  • Messages End-To-End Encryption Overview
    Messages End-to-End Encryption Overview Technical Paper Emad Omara Communications Security Lead November 2020 Version 1.0 A high-level technical overview of end-to-end encryption in Messages Introduction ​2 Background & RCS Ecosystem ​3 Threat Model ​3 Goals ​4 UI Changes ​4 SMS/MMS Fallback ​5 Identity Verification ​6 E2EE in Messages ​7 Signal Protocol ​7 Key Server ​8 Messages Encryption ​9 Attachment Encryption ​10 Session Recovery ​10 Web Client ​10 Storage & Access ​11 Android Messages Database ​11 Notifications ​11 Limitations ​11 Third Party RCS Client ​11 Conclusion ​12 Introduction Rich Communication Services (RCS) is designed to improve users’ experience and security over Short Message Service (SMS)/Multimedia Messaging Service (MMS), and we’ve invested in making Messages by Google a modern and globally available RCS & SMS/MMS messaging app for Android phones. While RCS messages are already a big security improvement over SMS/MMS, we wanted to take it a step further and add end-to-end encryption (E2EE) to Messages, so no one else – including 2 Messages E2EE Overview​ Google servers or third-party servers – can access your conversations as they travel between your phone and the phone you message. Background & RCS Ecosystem RCS uses a set of standard internet protocols like Session Initiation Protocol (SIP)​[1] ​ to establish a connection between two clients through a central messaging server. This connection is then used to exchange the messages using Message Session Relay Protocol (MSRP)​[2].​ In some RCS deployments this server is hosted by the carrier, and in other deployments the server is hosted by Jibe Mobile from Google.
    [Show full text]
  • A Survey of Open Source Products for Building a SIP Communication Platform
    Hindawi Publishing Corporation Advances in Multimedia Volume 2011, Article ID 372591, 21 pages doi:10.1155/2011/372591 Research Article A Survey of Open Source Products for Building a SIP Communication Platform Pavel Segec and Tatiana Kovacikova Department of InfoCom Networks, University of Zilina, Univerzitna 8215/1, 010 26 Zilina, Slovakia Correspondence should be addressed to Tatiana Kovacikova, [email protected] Received 29 July 2011; Revised 31 October 2011; Accepted 15 November 2011 Academic Editor: T. Turletti Copyright © 2011 P. Segec and T. Kovacikova. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. The Session Initiation Protocol (SIP) is a multimedia signalling protocol that has evolved into a widely adopted communication standard. The integration of SIP into existing IP networks has fostered IP networks becoming a convergence platform for both real- time and non-real-time multimedia communications. This converged platform integrates data, voice, video, presence, messaging, and conference services into a single network that offers new communication experiences for users. The open source community has contributed to SIP adoption through the development of open source software for both SIP clients and servers. In this paper, we provide a survey on open SIP systems that can be built using publically available software. We identify SIP features for service deve- lopment and programming, services and applications of a SIP-converged platform, and the most important technologies support- ing SIP functionalities. We propose an advanced converged IP communication platform that uses SIP for service delivery.
    [Show full text]