Freeswitch 1.2 Second Edition
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Microsoft Skype for Business Deployment Guide
Microsoft Skype for Business Deployment Guide Multimedia Connector for Skype for Business 8.5.0 3/8/2020 Table of Contents Multimedia Connector for Skype for Business Deployment Guide 4 Architecture 6 Paired Front End Pools 9 Federation Platform with Microsoft Office 365 Cloud 12 Managing T-Server and UCMA Connectors 14 Prerequisites 16 Provisioning for UCMA Connectors 22 Using Telephony Objects 24 Managing UCMA Connectors 28 Managing T-Server 33 Upgrading Multimedia Connector for Skype For Business 36 Configuring Skype for Business Application Endpoints 37 Configuring Skype for Business User Endpoints 38 High-Availability Deployment 39 Performance 45 Managing Workspace Plugin for Skype for Business 46 Using Workspace Plugin for Skype for Business 51 Handling IM Transcripts 60 Supported Features 61 Alternate Routing 62 Call Monitoring 63 Call Supervision 64 Calling using Back-to-Back User Agent 70 Conference Resource Pools 77 Disable Lobby Bypass 80 Emulated Agents 82 Emulated Ringing 85 Handling Direct Calls 86 Handling Pass-Through Calls 89 Hiding Sensitive Data 91 IM Treatments 93 IM Suppression 94 Music On Hold 97 No-Answer Supervision 98 Presence 99 Remote Recording 103 Remote Treatments 110 Transport Layer Security 112 UTF-8 Encoding 114 Supported Media Types 116 T-Library Functionality 120 Attribute Extensions 124 Hardware Sizing Guidelines and Capacity Planning 130 Error Messages 132 Known Limitations and Workarounds 134 Multimedia Connector for Skype for Business Deployment Guide Multimedia Connector for Skype for Business Deployment Guide Welcome to the Multimedia Connector for Skype for Business Deployment Guide. This Deployment Guide provides deployment procedures and detailed reference information about the Multimedia Connector for Skype for Business as a product, and its components: T-Server, UCMA Connector, and Workspace Plugin. -
IM Security Documentation on Page Vi
Trend Micro Incorporated reserves the right to make changes to this document and to the product described herein without notice. Before installing and using the product, review the readme files, release notes, and/or the latest version of the applicable documentation, which are available from the Trend Micro website at: http://docs.trendmicro.com/en-us/enterprise/trend-micro-im-security.aspx Trend Micro, the Trend Micro t-ball logo, Control Manager, MacroTrap, and TrendLabs are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners. Copyright © 2016. Trend Micro Incorporated. All rights reserved. Document Part No.: TIEM16347/140311 Release Date: September 2016 Protected by U.S. Patent No.: Pending This documentation introduces the main features of the product and/or provides installation instructions for a production environment. Read through the documentation before installing or using the product. Detailed information about how to use specific features within the product may be available at the Trend Micro Online Help Center and/or the Trend Micro Knowledge Base. Trend Micro always seeks to improve its documentation. If you have questions, comments, or suggestions about this or any Trend Micro document, please contact us at [email protected]. Evaluate this documentation on the following site: http://www.trendmicro.com/download/documentation/rating.asp Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this data is considered personal in certain jurisdictions and under certain regulations. -
Ozgur Ozturk's Introduction to XMPP 1 XMPP Protocol and Application
Software XMPP Protocol Access to This Tutorial that you will need to repeat exercises with me and • Start downloads now Application Development using • Latest version of slides available on – In the break you will have time to install – http://DrOzturk.com/talks • Visual C# 2008 Express Edition Open Source XMPP Software • Also useful for clicking on links – http://www.microsoft.com/express/downloads/ and Libraries • Eclipse IDE for Java Developers (92 MB) – http://www.eclipse.org/downloads/ Ozgur Ozturk Openfire & Spark Code: [email protected] • – http://www.igniterealtime.org/downloads/source.jsp Georgia Institute of Technology, Atlanta, GA – TortoiseSVN recommended for subversion check out Acknowledgement: This tutorial is based on the book “XMPP: The • http://tortoisesvn.net/downloads Definitive Guide, Building Real-Time Applications with Jabber Technologies” with permission from Peter Saint-Andre. • JabberNet code: 1 2 – http://code.google.com/p/jabber-net/ 3 What is XMPP Samples from its Usage • Extensible Messaging and Presence Protocol • IM and Social Networking platforms – open, XML-based protocol – GTalk, and Facebook Part 1 – aimed at near-real-time, extensible • Collaborative services – Google Wave, and Gradient; • instant messaging (IM), and • Geo-presence systems • presence information. Introduction to XMPP – Nokia Ovi Contacts • Extended with features such as Voice over IP • Multiplayer games and file transfer signaling – Chesspark – and even expanded into the broader realm of • Many online live customer support and technical -
Design of a Handset for the IP Multimedia Subsystem a Case Study
Design of a Handset for the IP Multimedia Subsystem A Case Study James Sunil Selvam ITTIAM Systems [email protected] IMS Architecture OSA AS GSM SCF Application Layer OSA-SCS SIP AS IM-SSF Session Control CSCF Layer HSS GPRS, CDMA MGCF 802.11, DSL SIP Media Transport Layer Gateway EndPoint PSTN PTT, IM, VVoIP VoIP PTT, IM, VVoIP Hardware Block Diagram MIC LCD / Audio TOUCH Codec Speaker/ SCREEN Headphone GSM/ Keypad GPRS JTAG PROCESSOR WLAN Serial Board Control Flash/ Power SDRAM USB Reg TI Innovator Kit based on OMAP1510 Customised Hardware Based on OMAP™ Innovator Kit WLAN NOISE SUPRESSOR R O USB1 USB DWL-G122 T C TRANSCEIVER WLAN E 3.3V N N 5V O C GSM/ SIM E C GPRS CARD A F R E UART2 GM47 T LEVEL GSM/ N I SHIFTER GPRS R O T A MIC V O SPEAKER N N I POWER 2.75V (LEVEL SHIFTER) 5V POWER CONVERTERS 3.6V (GM47) Implementation Hardware Software Block Level SIP : oSIP Linux 2.6.16 RTP/RTCP : oRTP Circuit Design Audio Codec : Kernel Dep. G711, SPEEX, GSM Artwork Driver Management of SIM Test Programs Air Interface : GM47 TI Innovator Device + Custom Hardware Kernel Related Application Services VoIP : Linphone UA GUI Ergonomics Packaging ID Test Setup SIP Proxy & Registrar Ethernet Linphone UA Linphone UA IMS Handset Test Setup Integrated Product IMS Handset Design of a Handset for the IP Multimedia Subsystem - A Case Study James Selvam ITTIAM Systems (Pvt) Ltd Part 1: IMS Why IMS? • Internet – Ease of service creation & provision – Open protocols & large professional talent – Wealth of information • Cellular World – Service on the move -
How Secure Is Textsecure?
How Secure is TextSecure? Tilman Frosch∗y, Christian Mainkay, Christoph Badery, Florian Bergsmay,Jorg¨ Schwenky, Thorsten Holzy ∗G DATA Advanced Analytics GmbH firstname.lastname @gdata.de f g yHorst Gortz¨ Institute for IT-Security Ruhr University Bochum firstname.lastname @rub.de f g Abstract—Instant Messaging has gained popularity by users without providing any kind of authentication. Today, many for both private and business communication as low-cost clients implement only client-to-server encryption via TLS, short message replacement on mobile devices. However, until although security mechanisms like Off the Record (OTR) recently, most mobile messaging apps did not protect confi- communication [3] or SCIMP [4] providing end-to-end con- dentiality or integrity of the messages. fidentiality and integrity are available. Press releases about mass surveillance performed by intelli- With the advent of smartphones, low-cost short-message gence services such as NSA and GCHQ motivated many people alternatives that use the data channel to communicate, to use alternative messaging solutions to preserve the security gained popularity. However, in the context of mobile ap- and privacy of their communication on the Internet. Initially plications, the assumption of classical instant messaging, fueled by Facebook’s acquisition of the hugely popular mobile for instance, that both parties are online at the time the messaging app WHATSAPP, alternatives claiming to provide conversation takes place, is no longer necessarily valid. secure communication experienced a significant increase of new Instead, the mobile context requires solutions that allow for users. asynchronous communication, where a party may be offline A messaging app that claims to provide secure instant for a prolonged time. -
Chat Server Administration Guide
Chat Server Administration Guide Rich Messaging Support 9/24/2021 Contents • 1 Rich Messaging Support • 1.1 Overview • 1.2 How to deploy and use structured messages • 1.3 Chat Widget support Chat Server Administration Guide 2 Rich Messaging Support Rich Messaging Support Overview Genesys chat solution provides the ability to use structured messages (in other words, Rich Messaging) across various chat channels, including: Channel Components Channel name Genesys Mobile Services (GMS) (min version required 8.5.201.04) and Web chat Chat Widget (for supported elements, genesys-chat see Rich Messaging in the Genesys Widgets Deployment Guide) Digital Messaging Server (DMS) and ABC driver (see Deploying Apple Apple Business Chat (ABC) applebc-session Business Chat in the Apple Business Chat Guide) DMS and Genesys Driver for use with WhatsApp Genesys Hub (see Deploying genesys-chat WhatsApp in the WhatsApp Guide) Important Support for Rich Messaging varies by channel based on what each channel service provider supports and what is implemented in Genesys Engage. Not every Rich Messaging element is supported in all channels. Additionally, the following components are also involved: Component Purpose Chat Server Conduct chat session. Min version required 8.5.109.06. An authoring tool for creating standard responses which can contain structured messages. Graphical editing eServices Manager capabilities are provided for some channels together with the ability to provide raw (for example JSON) representation of a structured message. A chat bot deployment platform that provides an API for bots to use either standard responses with structured Bot Gateway Server messages, or send Rich Messaging containing native or normalized JSON format. -
Tech Note: Integrating CPM with Other PRPC Applications
Technical Note Installing and Configuring OpenFire for PegaCHAT™ 18 December 2009 Copyright 2009 Pegasystems Inc., Cambridge, MA All rights reserved. This document and the software describe products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. This information should not be disclosed to third parties without the prior written consent of Pegasystems Inc. This document and the software are protected by federal copyright law, international laws and/or applicable treaties. This document is current as of the date of publication only. Changes in the document may be made from time to time at Pegasystems’ discretion. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services provided. This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems services consultant. Other brand or product names are trademarks or registered trademarks of their respective holders. This document is the property of: Pegasystems Inc. 101 Main Street Cambridge, MA 02142-1590 (617) 374-9600, fax: (617) 374-9620 www.pega.com Contents Introduction .......................................................................................................... 1 Installing & Configuring OpenFire and FastPath to Work with PegaCHAT . 2 1. -
What Is Open Source?
Putting OPen SOurce tO WOrk in the enterPriSe: A guide tO riSkS And OPPOrtunitieS © Copyright 2007 SAP AG. All rights reserved. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, No part of this publication may be reproduced or transmitted in Massachusetts Institute of Technology. any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed Java is a registered trademark of Sun Microsystems, Inc. without prior notice. JavaScript is a registered trademark of Sun Microsystems, Inc., Some software products marketed by SAP AG and its distributors used under license for technology invented and implemented contain proprietary software components of other software by Netscape. vendors. MaxDB is a trademark of MySQL AB, Sweden. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, mentioned herein as well as their respective logos are trademarks MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, or registered trademarks of SAP AG in Germany and in several xSeries, zSeries, System i, System i5, System p, System p5, System x, other countries all over the world. All other product and service System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, names mentioned are the trademarks of their respective compa- Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, nies. Data contained in this document serves informational OpenPower and PowerPC are trademarks or registered purposes only. -
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. -
Atme Documentation
PatetLex19117 1 AtMe Documentation INDEX INTRODUCTION - 1 GETTING STARTED - 1-2 INSIDE WORKSPACE - 3-4 TERMS - 5 IMAGES - 5 EXAMPLE VIDEO - 6 Documentation Information - 6 INTRODUCTION AtMe is intended to be a simple software to create Discord bots (1) with graphical programming (2). AtMe aims to reduce the level of skill required to make Discord bots. Grasping external functions, AtMe generates inerrant javascript code. It is important to note that AtMe does not depend on Discord and can run separately. Please view the one minute example video (EXAMPLE VIDEO) to gather a simple visual and example of AtMe functions (Note: All functions aren’t shown in the video to reduce lengthy content). GETTING STARTED On launch, the user is granted with image A. The plus button (+) creates a new workspace, the path of the workspace defaults to \%USER_HOME%\AtMeWorkspaces\. CREATION: There are five values that should be set before creating the bot. ● Name - This defines the name of the bot (4), may be referred to as the id. This value is often condensed and spaces may be removed. (Note: This value is unchangeable) ● Description - This defines the description of the bot and is only used in the manifest. PatetLex19117 2 ● Token - This defines a value that is severely important and is used to connect AtMe/Discord-bot to Discord. A token can be granted from Discord Developer Portal. (Note: This value is not shared and is only saved remotely in “index.js”) ● Prefix - This defines a constant value. ● Author - This defines the author of bot and is only used in the manifest. -
Deniable Key Exchanges for Secure Messaging
Deniable Key Exchanges for Secure Messaging Nik Unger Ian Goldberg Cheriton School of Computer Science Cheriton School of Computer Science University of Waterloo, University of Waterloo, Waterloo, ON, Canada Waterloo, ON, Canada [email protected] [email protected] ABSTRACT the lack of security and privacy in our messaging tools and spurred In the wake of recent revelations of mass government surveillance, demand for better solutions [20]. A widespread weakness in cur- secure messaging protocols have come under renewed scrutiny. A rent secure messaging tools is the lack of strong deniability proper- widespread weakness of existing solutions is the lack of strong ties [28]. Deniable secure messaging schemes allow conversation deniability properties that allow users to plausibly deny sending participants to later plausibly deny sending messages, or even par- messages or participating in conversations if the security of their ticipating in a conversation, while still providing authentication to communications is later compromised. Deniable authenticated key the participants at the time of the conversation. This notion was exchanges (DAKEs), the cryptographic protocols responsible for popularized in the secure messaging context with the release of providing deniability in secure messaging applications, cannot cur- Off-the-Record Messaging (OTR) a decade ago [3]. Unfortunately, rently provide all desirable properties simultaneously. the OTR protocol is not well suited to modern settings such as mo- We introduce two new DAKEs with provable -
Oracle® Communications Session Border Controller – SCZ730 - S-CZ7.3.0
Oracle® Communications Session Border Controller – SCZ730 - S-CZ7.3.0 Program Documentation – License Document First Edition October 2015 Contents Copyright Notices ......................................................................................................... 3 License Restrictions Warranty/Consequential Damages Disclaimer .............................................. 3 Warranty Disclaimer ........................................................................................................................ 3 Restricted Rights Notice .................................................................................................................. 3 Hazardous Applications Notice ....................................................................................................... 3 Trademark Notice ............................................................................................................................ 4 Alpha and Beta Draft Documentation Notice................................................................................... 4 Revenue Recognition Notice ........................................................................................................... 4 Beta Program Notice ....................................................................................................................... 5 Documentation Accessibility ............................................................................................................ 5 Access to Oracle Support ...............................................................................................................