DOCSLIB.ORG

Project: Python Video Conferencing Client - Pyvcc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Project: Python Video Conferencing Client - Pyvcc Project: Python Video Conferencing Client - pyVCC Adrian Beutner1 and Christoph Kuhr2 Summer Semester 2013 [email protected] [email protected] Abstract In this document, the concept and design of the Python Video Conferencing Client (pyVCC) and it's development process is described. PyVCC utilizes the Session Initiation and Descrip- tion Protocols (SIP, SDP) to establish a session between two clients and a call server (CS). The two pyVCC clients share their audio and video (AV) data with the Realtime Transport Protocol (RTP). Python Video Conferencing Client Content Beutner - Kuhr Contents 1 Introduction 2 1.1 Workpackages and Schedueling . .2 1.2 Project Description . .3 2 Concept and Design 3 2.1 Communication Concept . .3 2.1.1 SIP and SDP - Kuhr . .3 2.1.2 RTSP and SDP- Kuhr . .5 2.1.3 RTP - Beutner . 10 2.2 Callserver and MCU - Beutner . 10 2.3 Software Design . 11 2.3.1 libVLC . 11 2.3.2 SIPSimple Client SDK . 12 2.3.3 UML . 13 2.4 Proof of Concept . 15 2.4.1 Virtualbox - Firewall - Beutner . 15 2.4.2 Callserver and MCU - Beutner . 15 2.4.3 libVLC RTSP Streaming . 15 2.4.4 SIP Simple SDK - Blink . 19 3 Discussion 21 3.1 Callserver and MCU - Beutner . 21 3.1.1 OpenVCS and Asterisk . 21 3.1.2 Medooze . 21 3.2 pyVLCC . 22 3.2.1 libVLC . 22 3.2.2 SIP Simple SDK . 22 3.2.3 RTSP SDP vs SIP SDP . 22 3.2.4 Python . 22 3.2.5 Performance . 23 pyVCC i Python Video Conferencing Client Content Beutner - Kuhr List of Figures 2.1 SIP Trapezoid [5, p. 4] . .3 2.2 SDP Body Scheme [4, p. 30] . .4 2.3 TEMP SIP Body Fields [4, p. 30] . .4 2.4 TEMP Field Values [4, p. 31] . .5 2.5 RTP Wireshark Capture . 11 2.6 Use Case Diagram . 13 2.7 Activity Diagram pyVCC . 14 2.8 Component Diagram pyVCC . 14 2.9 OpenVCS Communication . 15 2.10 pyVLCC GUI . 20 2.11 Blink GUI . 20 3.12 SIP Signaling Wireshark Capture . 23 3.13 RTSP Signaling Wireshark Capture . 23 3.14 SIP SDP Wireshark Capture . 23 3.15 RTSP SDP Wireshark Capture . 24 List of Tables 3.1 This table shows some data . 24 pyVCC 1 Python Video Conferencing Client Introduction Beutner - Kuhr 1 Introduction 1.1 Workpackages and Schedueling A list of single worksteps to perform: MS2 04/18/2013 Concept and Design: • Understand RTP (Beutner) • Understand SIP, RTSP, SDP, libVLC , SIPSimple Client SDK (Kuhr) • Develope communication concept (Beutner) • Design software (Kuhr) MS3 06/27/2013 Implementation and Verification: • Install call server(Beutner) • Implement software (Kuhr) • Install media control unit (Beutner) • Test software (Beutner, Kuhr) MS4 07/11/2013 Conclusions and Presentation: • Conclusions (Beutner, Kuhr) • Presentation (Beutner, Kuhr) pyVCC 2 Python Video Conferencing Client Introduction Beutner - Kuhr 1.2 Project Description PyVCC is a video conferencing client written with the Python programming language. The application script pyVCC.py is executed within the Python interpreter CLI. Thus, the inter- action and debugging iniformation is printed to the Python CLI. The required functionality for SIP sessions management shall be implemented with the SIPSimple Client SDK [?]. The SIPSimple Client SDK provides an interface for external codecs, called IMediaStream. The RTP AV data transport is implemented with the libVLC library and is called via the IMedi- aStream API by the SIP components. libVLC capture the local AV data, streams it to the remote client and plays back the AV data stream received by the remote client. With the Session Initiation and Description Protocols (SIP, SDP), two pyVCC Clients es- tablish a session, managed by a Call Server (CS). The Call Server shall be realized with the OpenSource Application openVCS. OpenVCS provides SIP functionaity along with a MCU (Multipoint Control Unit). The MCU manages RTP AV streams encoded with the h264 codec for video and the G711 codec for audio. 2 Concept and Design 2.1 Communication Concept 2.1.1 SIP and SDP - Kuhr SIP describes two types of communication, the most common way with the so called SIP trapezoid and communication which is forwarded to a Multipoint Control Unit (MCU). In the most commonly used case, Voice over IP, the user clients send and receive their SIP messages to and from their next SIP Proxy. The SIP Proxy forwards the SIP messages to the appropriate remote SIP Proxy to reach the remote URI. After the session is initialized with the SDP parameters, the audio data ist transported, via RTP, to the remote user client based on a peer-to-peer connection on different ports. Figure 2.1: SIP Trapezoid [5, p. 4] The second case is used for video conferencing environments, where different RTP AVC Profile streams, the amount depends on the users registered to the processed session, are pyVCC 3 Python Video Conferencing Client Introduction Beutner - Kuhr mixed to one RTP AVC Profile stream. The mixed stream is then return to each conference participant. This concept is described in detail in chapter 2.2 Callserver and MCU. The SDP part of a SIP INVITE message containes different lines of parameters to nego- tiate a RTP AVC Stream. Figure 2.2 shows the rule, by which each line of the SDP body is build. In figure 2.3, an example for a SDP body is given. Figure 2.2: SDP Body Scheme [4, p. 30] Figure 2.3: TEMP SIP Body Fields [4, p. 30] pyVCC 4 Python Video Conferencing Client Introduction Beutner - Kuhr The fields shown in figure 2.3 have the following meaning: Figure 2.4: TEMP Field Values [4, p. 31] 2.1.2 RTSP and SDP- Kuhr A RTSP stream uses HTTP like signaling to negotiate session parameters as well as SIP. But the signaling with RTSP is different. The mechanism to start a session uses a different data transport for signaling and media transmission, like with SIP signaling. For RTSP port 8554 is used over TCP and the ports 9000 and 9001 are used for RTP audio and video transport over UDP. Mandatory to start a presentation stream, which means a combination of for example audio and video streams, is a presentation description file. This presentation description file is provided as a SDP file. It has to be communicated, over a seperate channel like email or a webpage, before the actual start of the session. Once the servers presentation file is known, the requesting user client sends an OPTION request to the server. It contains information about the requested presentation stream by the preshared SDP file and the used user client. The server responses with a 200 OK message. In this message the server gives information about the server application that is providing the presentation stream. Also a field named PUBLIC is contained in the response. Th field PUBLIC is a list of the operations, which are implemented by the server. The most important operations, taken from the RTSP RFC2326 [7, p. 11f], are listed below: pyVCC 5 Python Video Conferencing Client Introduction Beutner - Kuhr SETUP: Causes the server to allocate resources for a stream and start an RTSP session. PLAY and RECORD: Starts data transmission on a stream allocated via SETUP. PAUSE: Temporarily halts a stream without freeing server resources. TEARDOWN: Frees resources associated with the stream. The RTSP session ceases to exist on the server. RTSP methods that contribute to state use the Session header field (Section 12.37) to identify the RTSP session whose state is being manipulated. The server generates session identifiers in response to SETUP requests (Section 10.4). The most important RTSP messages and their responses are listed below: DESCRIBE: The DESCRIBE method retrieves the description of a presentation or media object identified by the request URL from a server. It may use the Accept header to specify the description formats that the client understands. The server responds with a description of the requested resource. The DESCRIBE reply-response pair constitutes the media initialization phase of RTSP. Example: C->S: DESCRIBE rtsp://server.example.com/fizzle/foo RTSP/1.0 CSeq: 312 Accept: application/sdp, application/rtsl, application/mheg RESPONSE with SDP S->C: RTSP/1.0 200 OK CSeq: 312 Date: 23 Jan 1997 15:35:06 GMT Content-Type: application/sdp Content-Length: 376 v=0 o=mhandley 2890844526 2890842807 IN IP4 126.16.64.4 s=SDP Seminar i=A Seminar on the session description protocol u=http://www.cs.ucl.ac.uk/staff/M.Handley/sdp.03.ps [email protected] (Mark Handley) pyVCC 6 Python Video Conferencing Client Introduction Beutner - Kuhr c=IN IP4 224.2.17.12/127 t=2873397496 2873404696 a=recvonly m=audio 3456 RTP/AVP 0 m=video 2232 RTP/AVP 31 m=whiteboard 32416 UDP WB a=orient:portrait The DESCRIBE response MUST contain all media initialization information for the resource(s) that it describes. If a media client obtains a presentation description from a source other than DESCRIBE and that description contains a complete set of media initialization parameters, the client SHOULD use those parameters and not then request a description for the same media via RTSP. SETUP: The SETUP request for a URI specifies the transport mechanism to be used for the streamed media. A client can issue a SETUP request for a stream that is already playing to change transport parameters, which a server MAY allow. If it does not allow this, it MUST respond with error "455 Method Not Valid In This State". For the benefit of any intervening firewalls, a client must indicate the transport parameters even if it has no influence over these parameters, for example, where the server advertises a fixed multicast address.
Load more

Recommended publications
  • Copyrighted Material
    33_754935 bindex.qxp 11/7/05 10:09 PM Page 345 Index Applications Menu, 42–43, 68–71 • Symbols • Applixware Office package, 15 appointments, tracking, 210 * (asterisk), 249, 251 archives, packing and unpacking (tar), 20, \ (backslash), 248 337–338 - (dash), 94 arguments, command line, 247 . (dot), 92 asterisk (*), 249, 251 ! (exclamation point), 252–253 Asymmetric DSL (ADSL), 108–109 / (forward slash), 79, 81 attachments, e-mail, 154 > (greater-than sign), 249 audio CDs, playing, 221–223 - (hyphen), 95 authentication, 292 < (less-than sign), 249 automatic command completion, 250 . (period), 96 automatic login, 40, 318–319, 325 | (pipe), 248 ? (question mark), 251 " (quotation marks), 247 ; (semicolon), 248 • B • [] (square brackets), 252 backdoor, 292 .. (two dots or dot-dot), 92 background, desktop, 73–74, 75–76 backing up files, 20 backslash (\), 248 • A • base station, 129 bash (Bourne Again Shell) access point, wireless LAN, 129, 131 automatic command completion, 250 Adobe Portable Document Format. See PDF combining commands, 248 ADSL (Asymmetric DSL), 108–109 described, 47–48, 246 AES (Advanced Encryption Standard), 129 error messages, saving to file, 249–250 aggregator, RSS, 185 file, command input from, 249 AIM (America Online instant messaging output, saving to file, 249 service), 54, 161–162 repeating previously typed commands, Akregator news reader, 54, 185–186 252–253 amaroK music player, 224 syntax, 247–248 Apache Web server, 16 wildcards, 251–252 applets, 68, 75 bastion host, 293 application gateway, 292 bit bucket, 250 applications Blam RSS reader, 54 controlling, 18–19 block device, 94 development, 17 Bluetooth wireless, 20, 271 e-mail, 152–153 bookmark field, 200 GNOME Desktop, illustrated,COPYRIGHTED 64 boot menu MATERIAL items, installing, 27–28 GNU, 343 boot process, starting and stopping services, installing at setup, 32 263–264 KDE Desktop, illustrated, 64 booting, 26–27, 39–40 Linux packages, 11 Bourne Again Shell.
    [Show full text]
  • Cisco SCA BB Protocol Reference Guide
    Cisco Service Control Application for Broadband Protocol Reference Guide Protocol Pack #60 August 02, 2018 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Wiretapping End-To-End Encrypted Voip Calls Real-World Attacks on ZRTP
    Institute of Operating Systems and Computer Networks Wiretapping End-to-End Encrypted VoIP Calls Real-World Attacks on ZRTP Dominik Schürmann, Fabian Kabus, Gregor Hildermeier, Lars Wolf, 2017-07-18 wiretapping difficulty End-to-End Encryption SIP + DTLS-SRTP (SIP + Datagram Transport Layer Security-SRTP) End-to-End Encryption & Authentication SIP + SRTP + ZRTP Introduction Man-in-the-Middle ZRTP Attacks Conclusion End-to-End Security for Voice Calls Institute of Operating Systems and Computer Networks No End-to-End Security PSTN (Public Switched Telephone Network) SIP + (S)RTP (Session Initiation Protocol + Secure Real-Time Transport Protocol) 2017-07-18 Dominik Schürmann Wiretapping End-to-End Encrypted VoIP Calls Page 2 of 13 wiretapping difficulty End-to-End Encryption & Authentication SIP + SRTP + ZRTP Introduction Man-in-the-Middle ZRTP Attacks Conclusion End-to-End Security for Voice Calls Institute of Operating Systems and Computer Networks No End-to-End Security PSTN (Public Switched Telephone Network) SIP + (S)RTP (Session Initiation Protocol + Secure Real-Time Transport Protocol) End-to-End Encryption SIP + DTLS-SRTP (SIP + Datagram Transport Layer Security-SRTP) 2017-07-18 Dominik Schürmann Wiretapping End-to-End Encrypted VoIP Calls Page 2 of 13 wiretapping difficulty Introduction Man-in-the-Middle ZRTP Attacks Conclusion End-to-End Security for Voice Calls Institute of Operating Systems and Computer Networks No End-to-End Security PSTN (Public Switched Telephone Network) SIP + (S)RTP (Session Initiation Protocol + Secure Real-Time
    [Show full text]
  • Policy Options and Regulatory Mechanisms for Managing Radicalization on the Internet
    Policy options and regulatory mechanisms for managing radicalization on the Internet Paris, 30 September 2016 “[…] I firmly believe that in a free democratic society, freedom of speech and expression is one of the most prized freedoms which must be defended and upheld at any cost and this should be particularly so in the land of Voltaire. It is indeed unfortunate that in the world of today, when science and technology have advanced the frontiers of knowledge and mankind is beginning to realize that human happiness can be realized only through inter-dependence and cooperation, the threshold of tolerance should be going down. It is high time man should realize his spiritual dimension and replace bitterness and hatred by love and compassion, tolerance and forgiveness.” Justice Prafullachandra Bhagwati Dan Shefet (Individual Specialist) ACKNOWLEDGEMENTS The author wishes to thank the following for their support, valuable advice and input throughout the drafting of the Report: Dr. Indrajit Banerjee and his team in UNESCO’s Knowledge Societies Division The UNESCO Delegates and Ministries of Justice/Interior of countries that have participated in the Country Survey. Alexander Linden, Honorary advisor to the French Supreme Court Janice Duffy, Researcher, Australia Pavan Duggal, Supreme Court Lawyer, India Tom Høyem, Former Minister in Denmark under Poul Schlüter Francesca Musiani, Researcher at the CNRS Institute for Communication Sciences and Member of the French National Assembly’s Commission on the Law and Rights in the Digital Era Sami Mahbouli, Lawyer at The Tunisian Supreme Court and Columnist Sabine Leutheusser-Schnarrenberger, Former Minister of Justice under Angela Merkel Marc Randazza, First Amendment Attorney, United States Viswa Sadasivan, CEO of Strategic Moves (Consultancy agency in Singapore) and former member of the Singaporean Parliament Mr K.
    [Show full text]
  • Internet Telephony with Linphone WELLWELL CONNECTEDCONNECTED
    Linphone COVER STORY Internet telephony with Linphone WELLWELL CONNECTEDCONNECTED When you want to call your friends in distant countries, don’t pick up municate with the VoIP provider, so you will need to install the library first. To do the phone; just put on your headset and fire up Linphone. so, open a terminal window, then be- come root by typing su and supplying BY SIMONE SCHÄFER the root password. Unpack the archive by typing tar xzf libosip2-2.2.0.tar.gz, ne of the most popular methods wants to take incoming calls via Purtel. and then change to the new directory (cd for accessing Voice over IP tech- The procedures are similar for other pro- libosip2-2.2.0). The following commands Onology is through a so-called viders. will build and install the library: softphone. A softphone is simply a com- puter program running on your desktop Installation ./configure --prefix=/usr that handles call establishment and com- The source code for the 1.1.0 release, make munication. Linphone [1] is one of the and the libraries, are available on the most popular softphone applications for DVD with this issue below LinuxUser/ Phone Numbers and SIP Ids Linux. Linphone is optimized for the linphone/. In the simplest of all cases, the phone Gnome desktop, although that doesn’t Mandriva Linux 2006 has the current number will be a simple telephone num- mean you can’t run it on KDE. This arti- 1.1.0 version. Gentoo Linux users can ber followed by the SIP domain, such as cles describes how to install, configure, install Linphone 1.1.0 simply by running [email protected].
    [Show full text]
  • Protec3ng Messaging Other Than Email, Plus Network Link Protec3on
    Protec'ng Messaging Other Than Email, plus Network Link Protec'on Joe St Sauver, Ph.D. [email protected] or [email protected] M3AAWG Senior Technical Advisor Scien@st, Farsight Security, Inc. Gold Ballroom, 1st Floor M3AAWG 36, San Francisco, California Wednesday Feb 17th, 2016, 15:30-16:30 hPps://www.stsauver.com/joe/crypto-other-than-email/ 1 Introduc'on • Today's session has two parts: – The first part will consider cryptographic privacy protecon for messaging other than email. – The second part will focus on cryptographic protecon of high speed internal links. • The common link between the two topics is that in each case, your op@ons are constrained by what the market offers. Today's goal is to help you understand why you want protec@on for these points of exposure, and how to select a solu@on. • Both of these topics are the subject of pending dra documents in the Pervasive Monitoring SIG. 2 I. Messaging Other Than Email 3 Messaging Other Than Email • M3AAWG has been working hard on protec@ng email against pervasive monitoring. • That's very important work, and protec@ng email privacy is a totally appropriate goal for M3AAWG. • Although M3AAWG has always had a strong focus on email, our charter, as the an@-Pervasive Monitoring SIG of the Messaging, Malware, and Mobile An-Abuse Working Group, includes, or should include, protec@ng mobile voice telephony and mobile applicaons (such as tex@ng/chat), too. • Arguably, for many users, secure mobile voice and secure text/ chat is as important, or even more important than email.
    [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]
  • Linphone a Good Working Skype Voice Over IP Alternative
    Walking in Light with Christ - Faith, Computing, Diary Articles & tips and tricks on GNU/Linux, FreeBSD, Windows, mobile phone articles, religious related texts http://www.pc-freak.net/blog Linphone a good working Skype voice over IP alternative Author : admin If you never tried linphone I warmly recommend it. 2 days ago, with a friend of mine we tested a bunch of Linux softwares to find out what is the situation with possible alternatives to Skype to transmit Voice and Video. I've been interested into Skype Alternative programs since about 2 years, but so far I never found good and easy to set up working Linux alternative. We first tried Ekiga. Though it is said to be a good Linux SKype alternative, my ekiga client running on Debian Linux stable Squeeze ver. 3.2.7.2 failed to connect to SIP account I've created on ekiga.net. I've tried hard to make ekiga connect to account SIP created from ekiga.net but all time I was getting an error on connect: Ekiga did not manage to configure your network settings automatically. You can still use it, but you need to configure your network settings manually. Please see http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually for instructions After continously trying to follow instructions from above pointed URL and making proper settings on my DL-524 Wireless Router and all time ending up with the annoying error, we decided to finally completely abondoned it and try some other voice over IP clients. We tried Jitsi and few others which prooved to be unworking.
    [Show full text]
  • Modeling and Analysis of Next Generation 9-1-1 Emergency Medical Dispatch Protocols
    MODELING AND ANALYSIS OF NEXT GENERATION 9-1-1 EMERGENCY MEDICAL DISPATCH PROTOCOLS Neeraj Kant Gupta, BE(EE), MBA, MS(CS) Dissertation Prepared for the Degree of DOCTOR OF PHILOSOPHY UNIVERSITY OF NORTH TEXAS August 2013 APPROVED: Ram Dantu, Major Professor Kathleen Swigger, Committe Member Paul Tarau, Committee Member Sam G Pitroda Committee Member Barrett Bryant, Chair of the Department of Computer Science and Engineering Costas Tsatsoulis, Dean of the College of Engineering Mark Wardell, Dean of the Toulouse Graduate School Gupta, Neeraj Kant. Modeling and Analysis of Next Generation 9-1-1 Emergency Medical Dispatch Protocols. Doctor of Philosophy (Computer Science), August 2013, 192 pp., 12 tables, 72 figures, bibliography, 196 titles. In this thesis I analyze and model the emergency medical dispatch protocols for Next Generation 9-1-1 (NG9-1-1) architecture. I have identified various technical aspects to improve the NG9-1-1 dispatch protocols. The specific contributions in this thesis include developing applications that use smartphone sensors. The CPR application uses the smartphone to help administer effective CPR even if the person is not trained. The application makes the CPR process closed loop, i.e., the person who administers the CPR as well as the 9-1-1 operator receive feedback and prompt from the application about the correctness of the CPR. The breathing application analyzes the quality of breathing of the affected person and automatically sends the information to the 9-1-1 operator. In order to improve the human computer interface at the caller and the operator end, I have analyzed Fitts law and extended it so that it can be used to improve the instructions given to a caller.
    [Show full text]
  • By CARLTON A. THOMPSON a DISSERTATION
    A DESIGN AND PERFORMANCE STUDY OF A DISTRIBUTED IP-BASED TELECOMMUNICATION SYSTEM (D-IPTS) By CARLTON A. THOMPSON A DISSERTATION PRESENTED TO THE GRADUATE SCHOOL OF THE UNIVERSITY OF FLORIDA IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY UNIVERSITY OF FLORIDA 2016 © 2016 Carlton A. Thompson 2 To my mother Hyacinth Thompson and to the memory of my father Carlton Thompson, for always supporting me during my studies and work. 3 ACKNOWLEDGMENTS The path to PhD has been very challenging and I have achieved a milestone in my career. I learned a lot about the field of IP telecommunications, peformance analysis, and associated qualitative research methods. This dissertation would not have been written without the help of certain individuals. I would like to extend my gratitude towards my advisor Dr. Latchman and co-advisor Dr. McNair. They helped me with the selection of my topic and provided guidance during the writing of my dissertation. Their encouragement and insights have always been inspiring. In addition, none of this could have been possible without my family and loved ones providing their continuous support during my various course studies. Also, I would like to thank my friends and colleagues from the Electrical and Computer Engineering Department at the University of Florida. Finally, I would like to thank Texas Instruments ™ for providing financial support for this work. 4 TABLE OF CONTENTS page ACKNOWLEDGMENTS..................................4 LIST OF TABLES......................................9 LIST OF FIGURES..................................... 10 LIST OF ABBREVIATIONS ................................ 14 ABSTRACT......................................... 17 CHAPTER 1 INTRODUCTION .................................... 19 Motivation........................................ 20 Voice Networks..................................... 21 Traditional Telecommunications Networks..................
    [Show full text]
  • Volume 160 May, 2020
    Volume 160 May, 2020 Short Topix: Zoombombing Is A Crime, Not A Prank GIMP Tutorial: Photo Editing, Part 3 PCLinuxOS Magazine Friends & Family - jzakiya Champions Of Regnum On PCLinuxOS EBCDIC Handling Library, Part 2 PCLinuxOS Recipe Corner: Lemon Pepper Chicken ms_meme's Nook: The Linux Bounce Wallpaper Roundup, Revisited Finally! ShotCut Running On PCLinuxOS And more inside! PCLinuxOS Magazine Page 1 In This Issue... 3 From The Chief Editor's Desk... 5 Staying "Safe" While You Stream: DBD's Tips On Living DRM-Free During Quarantine The PCLinuxOS name, logo and colors are the trademark of 6 Screenshot Showcase Texstar. 7 PCLinuxOS Recipe Corner: Lemon Pepper Chicken The PCLinuxOS Magazine is a monthly online publication containing PCLinuxOS-related materials. It is published 8 Wallpaper Roundup, Revisited primarily for members of the PCLinuxOS community. The magazine staff is comprised of volunteers from the 13 Screenshot Showcase PCLinuxOS community. 14 ms_meme's Nook: I Want It That Way Visit us online at http://www.pclosmag.com 15 Short Topix: Zoombombing Is A Crime, Not A Prank This release was made possible by the following volunteers: 19 Screenshot Showcase Chief Editor: Paul Arnote (parnote) 20 GIMP Tutorial: Photo Editing, Part 3 Assistant Editor: Meemaw Artwork: Sproggy, Timeth, ms_meme, Meemaw 22 Better than Zoom: Magazine Layout: Paul Arnote, Meemaw, ms_meme HTML Layout: YouCanToo Try These Free Software Tools For Staying In Touch Staff: 25 PCLinuxOS Family Member Spotlight: jzakiya ms_meme CgBoy Meemaw YouCanToo 26 Screenshot Showcase Gary L. Ratliff, Sr. Pete Kelly Daniel Meiß-Wilhelm phorneker 27 Champions Of Regnum On PCLinuxOS daiashi Khadis Thok 32 Screenshot Showcase Alessandro Ebersol Smileeb 33 EBCDIC Handling Library, Part 2 Contributors: 44 PCLinuxOS Bonus Recipe Corner: jzakiya Mashed Potato Mac & Cheese Bake 45 Screenshot Showcase The PCLinuxOS Magazine is released under the Creative 46 Finally! ShotCut Running On PCLinuxOS! Commons Attribution-NonCommercial-Share-Alike 3.0 Unported license.
    [Show full text]
  • Digital Source Protection for Journalists
    3 Tow Center for Digital Journalism DIGITAL A Tow/Knight Report SECURITY AND SOURCE PROTECTION FOR JOURNALISTS SUSAN MCGREGOR Funded by the Tow Foundation and the John S. and James L. Knight Foundation 4 Acknowledgements This paper is the product of countless conversations, encounters, recommen- dations and insights provided to me over the past year by members of the digital security and journalism communities. Though it would be impossible to name everyone whose insight and exper- tise has informed this work, my deepest thanks go to Franzi Roesner, Carey Shenkman, Nabiha Syed, Seamus Tuohy, Chris Walker and Carol Waters for providing invaluable feedback and direction on early versions of this pa- per; your expertise and insight was invaluable. Also to Oktavia Jonsdottir, Scott Klein, Quinn Norton, Jeremy Singer-Vine and Jennifer Valentino- DeVries, who shared their ideas and work processes with me. And a very special thanks to Peter G. Neumann, who offered me the long view on digital security and directed me to essential resources and experts on the subject. This project would also not have been possible without the financial and intellectual support of my colleagues at Columbia Journalism School, and the Tow Center for Digital Journalism–particularly Emily Bell and Taylor Owen. Likewise, I am very grateful to both OpenITP and TacticalTech– organizations whose generosity in hosting me in the fall of 2013 made pos- sible so many enlightening interactions with the digital security community. Without the openness of these organizations and their associates, this work would not have been possible. And finally, many grateful thanks to my talented, enthusiastic, and insightful illustrator and collaborator, Matteo Farinella, for truly making the invisible, visible.
    [Show full text]