DOCSLIB.ORG

NENA Voip Technical Committee Voip Characteristics Technical Information Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
NENA Voip Technical Committee Voip Characteristics Technical Information Document NENA VoIP Technical Committee VoIP Characteristics Technical Information Document NENA 08-503 - VoIP Characteristics Technical Information Document (TID) Issue 0, June 10, 2004 Prepared by: National Emergency Number Association (NENA) VoIP Technical Committee - VoIP Characteristics Working Group Published by NENA Printed in USA NENA VoIP Characteristics Technical Information Document NENA 08-503 June 10, 2004 (Original) NENA TECHNICAL INFORMATION DOCUMENT NOTICE This Technical Information Document (TID) is published by the National Emergency Number Association (NENA) as an information source for the designers and manufacturers of systems that are used for the purpose of processing emergency calls. It is not intended to provide complete design specifications or parameters or to assure the quality of performance for systems that process emergency calls. NENA reserves the right to revise this TID for any reason including, but not limited to, conformity with criteria or standards promulgated by various agencies, utilization of advances in the state of the technical arts or to reflect changes in the design of network interface or services described herein. It is possible that certain advances in technology will precede these revisions. Therefore, this TID should not be the only source of information used. NENA members are advised to contact their Telecommunications Carrier representative to ensure compatibility with the 9-1-1 network. Patents may cover the specifications, techniques or network interface/system characteristics disclosed herein. No license expressed or implied is hereby granted. This document is not to be construed as a suggestion to any manufacturer to modify or change any of its products, nor does this document represent any commitment by NENA or any affiliate thereof to purchase any product whether or not it provides the described characteristics. This document has been prepared solely for the voluntary use of E9-1-1 Service System Providers, network interface and system vendors, participating telephone companies, etc. By using this document, the user agrees that NENA will have no liability for any consequential, incidental, special, or punitive damages arising from use of the document. NENA’s Technical Committee has developed this document. Recommendations for change to this document may be submitted to: National Emergency Number Association 4350 N. Fairfax Dr, Suite 750 Arlington, VA 22203 800-332-3911 Page ii of 28 NENA VoIP Characteristics Technical Information Document NENA 08-503 June 10, 2004 (Original) Acknowledgments: This document has been developed by the National Emergency Number Association (NENA) VoIP Technical Committee. The following industry experts and their companies are recognized for their contributions in development of this document. Members: Company Henning Schulzrinne Columbia University Jonathan Flack Cox Communications Deborah Stone Intrado Lawrence Gowin Level 3 Communications Brian Rosen Marconi Mike Aprile – WG Leader Red Sky Technologies, Inc. Nate Wilcox – VTC Chair Vermont Enhanced 9-1-1 Greg Welenson Vonage Holdings, Inc. Larry Short Page iii of 28 NENA VoIP Characteristics Technical Information Document NENA 08-503 June 10, 2004 (Original) TABLE OF CONTENTS 1 EXECUTIVE OVERVIEW ..............................................................................................................................1 1.1 PURPOSE AND SCOPE OF DOCUMENT ...............................................................................................................1 1.2 REASON FOR ISSUE...........................................................................................................................................1 1.3 REASON FOR REISSUE ......................................................................................................................................1 1.4 RECOMMENDATION FOR STANDARDS DEVELOPMENT WORK ...........................................................................1 1.5 COSTS FACTORS...............................................................................................................................................1 1.6 ACRONYMS/ABBREVIATIONS...........................................................................................................................1 2 TECHNICAL DESCRIPTION.........................................................................................................................2 2.1 TCP/IP PRIMER................................................................................................................................................2 2.1.1 What is TCP/IP made of?...........................................................................................................................2 2.1.2 Application layer ........................................................................................................................................3 2.1.3 Transport layer...........................................................................................................................................3 2.1.4 Internet layer ..............................................................................................................................................3 2.1.5 Physical layer .............................................................................................................................................4 2.2 DECENTRALIZED IMPLEMENTATION.................................................................................................................4 2.3 PHYSICAL MEDIA INDEPENDENCE....................................................................................................................5 2.4 NETWORK REQUIREMENTS...............................................................................................................................5 2.4.1 Latency .......................................................................................................................................................5 2.4.2 Jitter............................................................................................................................................................5 2.4.3 Packet Loss.................................................................................................................................................5 2.4.4 General Guidelines.....................................................................................................................................5 2.4.5 Quality of Service (QoS).............................................................................................................................6 2.5 MEDIA TYPES...................................................................................................................................................7 2.5.1 Data............................................................................................................................................................7 2.5.2 Voice...........................................................................................................................................................7 2.5.3 Video...........................................................................................................................................................7 2.6 SEPARATION OF CALL CONTROL AND MEDIA TRANSPORT...............................................................................8 2.7 VIRTUAL LOCATIONS AND MOBILITY ..............................................................................................................8 2.8 IP TELEPHONY ARCHITECTURE OPTIONS .........................................................................................................8 2.8.1 Trunk Replacement.....................................................................................................................................9 2.8.2 Hybrid (hop-on/hop-off).............................................................................................................................9 2.8.3 Direct, end-to-end IP connection .............................................................................................................10 2.9 METHODS OF USAGE......................................................................................................................................10 2.9.1 Replacing the PBX....................................................................................................................................10 2.9.2 Extending the PBX....................................................................................................................................10 2.9.3 IP Centrex.................................................................................................................................................11 2.9.4 Residential Service ...................................................................................................................................11 2.10 HARDWARE COMPONENTS .............................................................................................................................12 2.10.1 IP End-Points (i.e. phones, PCs, etc.) .................................................................................................12 2.10.2 Access Gateways..................................................................................................................................13 2.10.3 Integrated Access Devices ...................................................................................................................13
Load more

Recommended publications
  • Voip): SIP and Related Protocols Fall 2013, Period 1 Lecture Notes of G
    IK2554 Practical Voice Over IP (VoIP): SIP and related protocols Fall 2013, Period 1 Lecture notes of G. Q. Maguire Jr. For use in conjunction with: Henry Sinnreich and Alan B. Johnston, Internet Communications Using SIP: Delivering VoIP and Multimedia KTH Information and Services with Session Initiation Protocol, 2nd Edition, Wiley, Communication Technology August 2006, ISBN: 0-471-77657-2. © 2004-2013 G.Q.Maguire Jr. All rights reserved. No part of this course may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission of the author. Last modified: 2013.08.30:12:51 Maguire Cover.fm Total pages: 1 [email protected] 2013.08.30 Module 1: Introduction........................................................................... 35 Welcome to the course! .......................................................................... 36 Staff Associated with the Course............................................................ 37 Instructor (Kursansvarig) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37 Goals, Scope and Method....................................................................... 38 Goals of the Course - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38 Scope and Method - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [Show full text]
  • A Telephone Domain Name System (T-DNS) for Internet Telephony Service at All IP Network
    A Telephone Domain Name System (T-DNS) for Internet Telephony Service at All IP Network oMi-Ryong Park, Chang-Min Park, and Jong-Hyup Lee Router Technology Department, Network Research Lab., ETRI 161 Kajong-Dong, Yusong-Gu, Taejon, 305-350, Korea Tel: +82-42-860-1211, Fax: +82-42-860-5213 Abstract: - Lately, Internet is generally accepted as a principle communication protocol for voice and data networks. Moreover data and voice is converging with one network over the Internet. Each node has its own IP address for existing packet data on the Internet. Even multi-media terminals including Internet phone, Internet fax, and Internet-enabled electric devices, are transferring variable-sized packets. There are several working groups for studying converged data and voice communication in Internet. Such converged network services especially for Internet telephony as Voice over IP (VoIP) or SoftSwitch have already been suggested. We believe that the VoIP service become a killer application on the Internet for the future. Many protocols such as Session Initiation Protocol (SIP), Media Gateway Control Protocol (MGCP), MEGACO, SIGTRAN of Internet Engineering Task Force (IETF) and H.323 series of International Telecommunication Unit (ITU-T), are accepted as standards required for the VOIP service. In this paper, we suggest a Telephone-Domain Name System (T-DNS) architecture for detecting simply the destination IP address at the converged network. T-DNS is based on a Client and Server and an original Internet Domain Name Service (DNS) model. But it expands the DNS architecture for detecting destination IP address by querying the Uniform Resource Locator (URL) of telephone numbers.
    [Show full text]
  • ENUM: an Enabler for Voip and Next Generation Services
    ITU Workshop on “Origin Identification and Alternative Calling Procedures” (Geneva, Switzerland, 19-20(AM) 2012) ENUM: an Enabler for VoIP and Next Generation Services Steven D. Lind Senior Member of the Technical Staff, AT&T [email protected] Geneva, Switzerland, 19-20 March(AM) 2012 What is ENUM? Provides mapping from E.164 numbers to IP resources Telephone number as domain name Built on top of DNS Number “holder” needs to opt-in Example: +1-973-236-6787 Lookup 7.8.7.6.6.3.2.3.7.9.1.e164.arpa sip:[email protected] DNS sip: [email protected] mailto:[email protected] mailto:[email protected] Geneva, Switzerland, 19-20 March(AM) 2012 2 Assumption Use of standard telephone numbers (ITU-T Recommendation E.164) is not going away PSTN/analog terminals are going to be around IP phones will use 12-button keypad Globally unique identifier that has established familiarity with end users Geneva, Switzerland, 19-20 March(AM) 2012 3 Types of ENUM End-User ENUM used to discover IP endpoints where data is placed in a public ENUM tree by end-users (or their agents) Provider ENUM (aka Carrier or Infrastructure ENUM) used to discover IP-based points of interconnection where data is placed in a private ENUM tree by carriers of record Geneva, Switzerland, 19-20 March(AM) 2012 4 Why is ENUM Important? ENUM will enable VoIP interoperability E.164 addresses will be used as names in VoIP networks ENUM enables call routing between VoIP service providers E.164 addresses are not directly routable in an IP/VoIP network Use ENUM to map E.164 number to an Internet address that can be used to setup communication (e.g.
    [Show full text]
  • ENUM & DNS Principles for an Interoperator IP Backbone Network
    ETSI TS 184 010 V3.1.1 (2011-08) Technical Specification Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); ENUM & DNS Principles for an Interoperator IP backbone network 2 ETSI TS 184 010 V3.1.1 (2011-08) Reference DTS/TISPAN-04015-NGN-R3 Keywords DNS, ENUM ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Itu-T Supplement to Rec. E.164 Operational and Administrative Issues Associated with National Implementations of the Enum Functi
    ITU-T SUPPLEMENT TO REC. E.164 (CLEAN VERSION) OPERATIONAL AND ADMINISTRATIVE ISSUES ASSOCIATED WITH NATIONAL IMPLEMENTATIONS OF THE ENUM FUNCTIONS DRAFT # 11.2 STATUS: REVISED DRAFT #11.2 UPDATED DURING THE 7-16 MAY 2002 STUDY GROUP 2 MEETING IMPORTANT NOTE on the STATUS of ITU-T SUPPLEMENTS: Supplements are only informative and are, therefore, not considered to be an integral part of any Recommendation(s). They do not imply any agreement on the part of the ITU-T (Recommendation A.13, 10/2000, Section 2.4) - 2 - ENUM supplement to ITU-T Rec. E.164 OPERATIONAL AND ADMINISTRATIVE ISSUES ASSOCIATED WITH NATIONAL IMPLEMENTATIONS OF THE ENUM FUNCTIONS Table of Contents 1 Introduction ............................................................................................................................... 2 2 Scope ........................................................................................................................................... 2 3 References .................................................................................................................................. 2 3.1 IETF .................................................................................................................................... 2 3.2 ITU ...................................................................................................................................... 2 4 Definitions .................................................................................................................................. 2 4.1 General
    [Show full text]
  • TRIP, ENUM and Number Portability
    TRIP, ENUM and Number Portability Nicklas Beijar Networking Laboratory, Helsinki University of Technology P.O. Box 3000, FIN-02015 HUT, Finland [email protected] order to make connectivity between all IP- and PSTN- Abstract terminals possible, the problem of terminal and gateway location must be solved. In these problems, addressing is This paper describes the problem of locating terminals central. Number portability allows users to change using E.164 numbers, and the problem of selecting a operators and locations without changing the telephone suitable gateway for calls from an IP telephony network number. To smoothen the transition to an IP-based to the public switched telephone network (PSTN). telephone network, number portability is also required Generally, these are the problems of mapping the name between PSTN and IP-networks. of a destination into an address, and to find the best route to the destination in a combined IP and PSTN network. The main signaling protocols for IP telephony are Number portability is closely related to these problems. Session Initiation Protocol (SIP) [1] and H.323 [2]. The Due to number portability the address of a destination is architectures that they define are similar, although changed without changing its name. Number portability different names are used for the network elements. Calls may also change the optimal route to a destination. can be established between IP telephony terminals directly, but usually the call setup signaling passes Two protocols are being developed by the Internet through a gatekeeper (in H.3232) or signaling server (in Engineering Task Force (IETF) to solve these problems.
    [Show full text]
  • TR 184 007 V2.1.1 (2008-08) Technical Report
    ETSI TR 184 007 V2.1.1 (2008-08) Technical Report Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Naming/Numbering Address Resolution (NAR) 2 ETSI TR 184 007 V2.1.1 (2008-08) Reference DTR/TISPAN-04011-NGN-R2 Keywords addressing, enum, DNS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
    [Show full text]
  • MAGIC: a Collaboration Project to Globally Connect Researchers and Academics
    MAGIC: A collaboration project to globally connect researchers and academics Leandro Marcos de O. GUIMARÃES1, María José LÓPEZ2 1RNP, Rua Lauro Müller, 116, sala 1103 - Botafogo, Rio de Janeiro - RJ - 22290-906, Brazil Tel: + 55 21 2102-9660, Fax: + 55 21 2279-3731, Email: [email protected] 2RedCLARA, Av. El Parque 4680-A, Oficina 108, Santiago, Chile Tel: + 56 2 584 86 18 , Email: [email protected] Abstract Building on the success of the ELCIRA project, RedCLARA - with partners from Latin America, Europe, the Caribbean, West and Central Africa, Eastern and Southern Africa, North Africa and the Middle East, Central Asia and Asia-Pacific is leading MAGIC (Middleware for collaborative Applications and Global vIrtual Communities), a cooperation project that aims to significantly improve the ability of researchers and academics around the world to collaborate together. MAGIC might be the first really global collaborative project in the REN environment. But which are the benefits of the project to its partner institutions’ (UbuntuNet and WACREN) members? How can the African researchers and academics benefit from MAGIC? By fostering and easing collaboration and mobility, MAGIC is fostering intra-regional and global collaboration, helping to reduce the technological gap, and as a consequence, in the long term, to reduce the brain drain. Keywords Collaboration, identity federations, eduroam, eduGAIN, scientific communities, researchers, academics, RENs, NRENs. Introduction A collaboration project to globally connect researchers and academics - aims to establish a set of agreements for all the participating world regions, aimed at consolidating and completing the building blocks of middleware necessary for the establishment of a marketplace of services and real-time applications which will facilitate mobility and the work of global science communities.
    [Show full text]
  • IMS Interconnect: Peering, Roaming and Security – Part One
    TECHNOLOGY WHITE PAPER IMS Interconnect: Peering, Roaming and Security – Part One IMS interconnection promises to enable greater reach and richer offerings for the providers that establish successful peering arrangements. This paper provides an introduction to IMS interconnection and identifies security considerations that carriers must address in order to achieve the proper balance of providing access while maintaining security. The paper is organized into two parts – Part One introduces key concepts and definitions related to network interconnections and interconnect models, while Part Two addresses the security mechanisms within the IMS standards and identifies potential security threats that face IMS carriers looking to interconnect their networks. Introduction While service providers are rushing to bring their initial IMS service offerings into commercial service, a number of them are also beginning to look beyond their basic IMS architectures to explore the potential for connecting to other carrier’s networks. By interconnecting their networks, carriers are looking to extend their reach and to leverage opportunities to explore new business models with partner providers. These types of provider-to-provider connections are not a new phenomena, there are examples of interconnected carriers in the PSTN world, the mobile telephone environment, and in the IP service provider industry. The Internet is a perfect example of a fully interconnected network – subscribers can interact with other subscribers and services, regardless of which service provider they belong to. The advantages of creating interconnected IMS networks include: • Carriers can provide services to their IMS subscribers while those subscribers visit geographies, regions, or networks where that carrier does not have a physical presence.
    [Show full text]
  • The .Tel Application Fails to Take Into Account National and International Regulations and the Need for Consensus on Key Aspects Amongst the International Community
    COMMENTS ON THE PULVER.COM APPLICATION ON THE NEW SPONSORED TOP LEVEL DOMAIN .TEL Madrid, 28 April 2004 CONTENTS 1. The .tel application does not satisfy the requirements laid down by ICANN to be a “sponsored Top Level Domain”. 2. The .tel/Pulver.com application is not a simple application on a new TLD. In view of its content and objectives, its approval goes beyond the purpose, function, role and competence of ICANN. 3. The .tel application fails to take into account national and international regulations and the need for consensus on key aspects amongst the international community. 4. Shortcomings of the application as regards intellectual property. 5. Shortcomings of the application as regards data, privacy and consumer protection. 6. Shortcomings of the application as regards competition. 7. Conclusion. 2 1. THE .TEL APPLICATION DOES NOT SATISFY THE REQUIREMENTS LAID DOWN BY ICANN TO BE A “SPONSORED TOP LEVEL DOMAIN”. Unlike gTLD, which are open to any individual, sTLD are for exclusive use by a specific "community", and are proposed and managed by one or more authorised members of that community with its backing. 1.1.- The following are the ICANN requirements as regards the meaning of “Community”: “The proposed sTLD must address the needs and interests of a clearly defined community (the Sponsored TLD Community)… and the applicants must demonstrate that the sponsored TLD Community is precisely defined, so it can readily be determinated which persons or entities make up that community and comprised of persons that have needs and interests in common but which are differentiated from those of the general global Internet community” 1.
    [Show full text]
  • TR 184 003 V3.1.1 (2010-06) Technical Report
    ETSI TR 184 003 V3.1.1 (2010-06) Technical Report Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Portability of telephone numbers between operators for Next Generation Networks (NGNs) 2 ETSI TR 184 003 V3.1.1 (2010-06) Reference DTR/TISPAN-04008-NGN-R3 Keywords NP, portability ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Challenges and Achievements During Integration of IMS Platform Into OSS/NMS Environment
    Challenges and achievements during integration of IMS platform into OSS/NMS environment S. Nesti ć, N. Peki ć and M. Tutman Hrvatski Telekom d.d./Service Management and Network Operations Sector, Zagreb, Croatia {sanjin.nestic|nikolina.pekic|mihaela.tutman}@t.ht.hr Abstract - IP Multimedia Subsystem (IMS) is a core experience, no matter where he is or what device he is network architecture standard for mobile, fixed and cable using. networks that defines a collection of functional entities and concepts for delivering multimedia services based on IP As IMS is not merely replica of the existing voice and protocol and next generation telecommunications network data platforms, all services from existing platforms cannot model. It was developed through collaboration of few be directly migrated to IMS, hence new or adapted leading standardization societies, such as 3GPP, services have to be developed from existing ones. After ETSI/TISPAN and IETF, so it represents a strong guideline implementation of new services, existing customers have of future development. Along with the implementation in to be migrated to new platform and to new or modified the network, IMS has to be integrated into operator’s services. Operations Support Systems / Network Management Systems environment in order to fulfill expectations of Although the prioritization and speed for adopting having cost-effective service provisioning and assurance, IMS architecture is still in some cases matter of system Fault and Performance management and efficient discussions, most incumbent operators will have to decide device and subscriber management. Besides problems and to implement IMS at some point. solutions already solved and implemented, this paper Along with the implementation in the network, IMS describes plans and challenges which are yet to be researched and developed in near future.
    [Show full text]