DOCSLIB.ORG

(12) United States Patent (10) Patent No.: US 8,000,316 B2 Kobayashi Et Al

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
(12) United States Patent (10) Patent No.: US 8,000,316 B2 Kobayashi Et Al USOO8000316B2 (12) United States Patent (10) Patent No.: US 8,000,316 B2 Kobayashi et al. (45) Date of Patent: * Aug. 16, 2011 (54) IPTELEPHONE APPARATUS, ENUM 6,347,085 B2 * 2/2002 Kelly ............................ 370,352 6,349,324 B1 2/2002 Tokoro SERVER, TERMINAL APPARATUS AND IP 6,359.880 B1* 3/2002 Curry et al. ................... 370,352 TELEPHONE SYSTEM 6,373,817 B1 * 4/2002 Kung et al. ................... 370,217 6,498,797 B1 12/2002 Anerousis et al. (75) Inventors: Kazuto Kobayashi, Kawasaki (JP); 6,567,122 B1 5/2003 Anderson et al. 6,917,612 B2 * 7/2005 Foti et al. ...................... 370,352 Akira Miyajima, Yokohama (JP) 7,243,151 B2 7/2007 Sekiguchi (73) Assignee: PANASONIC Corporation, Osaka (JP) (Continued) (*) Notice: Subject to any disclaimer, the term of this FOREIGN PATENT DOCUMENTS patent is extended or adjusted under 35 EP 106.1728 12/1999 U.S.C. 154(b) by 1149 days. (Continued) This patent is Subject to a terminal dis claimer. OTHER PUBLICATIONS Network Working Group M. Mealling R. Daniel Request for Com (21) Appl. No.: 11/249,715 ments: 2915 Updates: 2168 Sep. 2000.* (22) Filed: Oct. 14, 2005 (Continued) (65) Prior Publication Data Primary Examiner — Joe Cheng Assistant Examiner — Wutchung Chu US 2006/0092922 A1 May 4, 2006 (74) Attorney, Agent, or Firm — Greenblum & Bernstein, (30) Foreign Application Priority Data P.L.C. Nov. 2, 2004 (JP) ................................. 2004-319898 (57) ABSTRACT An IP telephone apparatus is connected to an ENUM server (51) Int. Cl. and a Web server via an IP network. The ENUM server has a H04L 2/66 (2006.01) database that stores an IP telephone URI as terminal infor (52) U.S. Cl. ........ 370/352; 370/353; 370/354; 370/355; mation of the IP telephone apparatus and a Web server URI 370/356; 370/465; 709/201: 709/202; 709/203; corresponding to the IP telephone apparatus. The Web server 709/204 stores image data captured by a camera. The IP telephone (58) Field of Classification Search ............. 370/395.54, apparatus transmits to the ENUM server a query on terminal 370/352,351,353,354, 355, 356,357, 465; information of a destination IP telephone apparatus; receives 709/201, 202, 203, 204 from the ENUM server the terminal information of the des See application file for complete search history. tination IP telephone apparatus; acquires from the received terminal information a Web server URI corresponding to the (56) References Cited destination IP telephone apparatus and performs visual com munication with the Web server based on the Web server URI: U.S. PATENT DOCUMENTS and displays captured image data received from the Web 6,157,636 A * 12/2000 Voit et al. ...................... 370,353 server in the visual communication. 6,292.478 B1* 9/2001 Farris ............................ 370,352 6,324.264 B1 * 1 1/2001 Wiener et al. .............. 379.8822 12 Claims, 19 Drawing Sheets 100 103 y 104 --------- -----4---- 10A Camera 105 4 -4 103B- web ENUM Callagent web -104B server Sewer apparatus - server : - - - - -r - - - - IP telephone IP telephone 107 US 8,000,316 B2 Page 2 U.S. PATENT DOCUMENTS Conroy et al. JPRSL. “ENUM Implementation Issues and Experi ences.” IETF Standard-Working-Draft, Internet Engineering Task 7.350.224 B2 * 3/2008 Creamer et al. .............. 725/105 Force, IETF, CH, vol. enum, (Jul. 2004), XPO15018179. 7,453,827 B2 * 1 1/2008 Toyoda ....... 370,260 Stastny, "Scenarios for ENUM and ENUM-like Systems <draft 2001/0055299 A1* 12/2001 Kelly ............................ 370,352 stantny-enum-scenarios-00.txt>.” IETF Standard-working-draft, 2002.009983.0 A1 7/2002 Viechter Internet Engineering Task Force, IETF, CH, pp. 1-18, (Jun. 2002), 2002/0156899 A1 10/2002 Sekiguchi XPO15005.364. 2002fO165969 A1* 11/2002 Gallant ......................... 709,227 2002fO196746 A1 12, 2002 Allen “Report of the Department of State ITAC-T Advisory Committee 2003/0058805 A1* 3/2003 Meyerson et al. ............ 370,260 Study Group A Ad Hoc on ENUM." chaired by G. Richenaker, 2003/0058806 A1* 3/2003 Meyerson et al. ... 370,260 ENUM, pp. 1-39, (Jun. 6, 2001), XP002238.095. 2003/0058844 A1* 3/2003 Sojka et al. ........ 370,352 Kaspch Carriercom AG: “ENUM Trial.” online (Dec. 28, 2003), 2003/0059002 A1* 3/2003 Meyerson et al. 379.88.13 XP002363054, Retrieved from the Internet <URL: http://web. 2003/019348.6 A1* 10/2003 Estrop ................ ... 345.204 archive.org/web/2003122820 1931/http://www.kapsch.net/Car 2003/0212758 A1* 11/2003 Anderson et al. ............. 709/217 rierCom/defa627 DEU HTMLExtranetCD.html D on Jan. 10, 2003/021494.0 A1 11, 2003 Takken 2005, in English and German. 2004/005.7421 A1 3f2004 Kawabata et al. ............ 370,352 English Language Abstract of JP 2004-248086. 2004/0068574 A1* 4/2004 Costa Requena et al. ... 709/230 English Language Abstract of JP 8-130594. 2005/0057644 A1* 3/2005 Huang ....................... 348, 14.01 ENUM Trial Japan, “ENUM Trial Japan First Report.” May 2004, 2005/O182781 A1 8, 2005 Bouvet together with an English language translation of the same. Sinnreich et al., “Mastering TCP/IP SIP, Chapter 14 (DVS and 2008, 0291263 A1 11/2008 Tokoro ENUM)” together with an English language translation of the same. 2009/0252302 A1* 10, 2009 Monroe .......................... 379/37 U.S. Appl. No. 1 1/150,119 to Kobayashi et al., which was filed Jun. FOREIGN PATENT DOCUMENTS 13, 2005. JP 8-130594 5, 1996 U.S. Appl. No. 1 1/235,217 to Miyajima et al., which was filed Sep. JP 11-234.642 8, 1999 27, 2005. JP 2002-319956 10, 2002 U.S. Appl. No. 1 1/235.275 to Miyajima, which was filed Sep. 27. JP 2003-209634 T 2003 2005. JP 2004-24.8069 9, 2004 U.S. Appl. No. 1 1/235,156 to Miyajima et al., which was filed Sep. JP 2004-248086 9, 2004 27, 2005. JP 2005-323.172 11, 2005 U.S. Appl. No. 1 1/235.273 to Miyajima et al., which was filed Sep. WO O3/107627 12/2003 27, 2005. WO 2004/O19592 3, 2004 U.S. Appl. No. 1 1/235,154 to Miyajima, which was filed Sep. 27. 2005. OTHER PUBLICATIONS English Language Abstract of JP 2004-248086, publication date unknown. Falstrom et al., “The E. 164 to Uniform Resource Identifier (URI) English Language Abstract of JP 8-130594, publication date Dynamic Delegation Discovery System (DDDS) Application unknown. (ENUM).” IETF Standard, Internet Engineering Task Force, IETF, Sinnreigh et al., “Mastering TCP/IP SIP, Chapter 14 (DVS and ENUM).” Oct. 25, 2002, together with an English language transla CH, (Apr. 2004), XPO15009541. tion of the same. Falstrom, “E. 164 number and DNS, IETF Standard, Internet Engi neering Task Force, IETF, CH, (Sep. 2000), XPO15008699. * cited by examiner U.S. Patent Aug. 16, 2011 Sheet 1 of 19 US 8,000,316 B2 870|| ?70|| |4 --------- 001, 90|| que6e||eo sn?euedde /01, 90?. -------- U.S. Patent Aug. 16, 2011 Sheet 2 of 19 US 8,000,316 B2 Fig.2 107 IP network U.S. Patent Aug. 16, 2011 Sheet 3 of 19 US 8,000,316 B2 S S. S S S - - - - - - - - - - - - - - - - e 8 U.S. Patent Aug. 16, 2011 Sheet 4 of 19 US 8,000,316 B2 Fig.4 input/output device 4O1 107 IP network U.S. Patent Aug. 16, 2011 Sheet 5 Of 19 US 8,000,316 B2 9Seqe?epWONE U.S. Patent Aug. 16, 2011 Sheet 6 of 19 US 8,000,316 B2 Kjenb(J.LdWN101euO?de|º}di119S 9:61 U.S. Patent Aug. 16, 2011 Sheet 7 Of 19 US 8,000,316 B2 Fig.7 S701 N IP telephones 101 and 102 turned on S702 IP telephones 101 and 102 register terminal information in CA 106 S703 IP telephones 101 and 102 process a Call S704 IP telephones 101 and 102 Start a Call IP telephone 101 acquires S705 IP telephone 102 NAPTR from ENUM Server 105 Web Server 104B URL available? S707 IP telephone 101 accesses Web Server 104B URL IP telephone 102 acquires S708 IP telephone 101 NAPTR from ENUM Server 105 S709 Web Server 103B URL available? S710 IP telephone 102 accesses Web Server 103B URL S711 IP telephones 101 and 102 establish visual Communication U.S. Patent Aug. 16, 2011 Sheet 8 of 19 US 8,000,316 B2 Z0), ?uO?d????di U.S. Patent Aug. 16, 2011 Sheet 10 of 19 US 8,000,316 B2 | OL-61-I 900),S U.S. Patent Aug. 16, 2011 Sheet 11 of 19 US 8,000,316 B2 Fig.11 S1101 Dials IP telephone 102 telephone number S1102 Acquires IP telephone 102 NAPTR from ENUM Server 105 S1103 Acquires IP telephone 102 P address from DNS Server 901 S1 104 Calls IP telephone 102 (transmits INVITE) S1105 N Starts a call with IP telephone 102 S1106 Web Server 104B URL available? S1107 ACCeSSes Web Server 104B URL S1108 Establishes visual Communication with IP telephone 102 U.S. Patent Aug. 16, 2011 Sheet 12 of 19 US 8,000,316 B2 Fig.12 S1201 S1202 s1203 || Aquilipping.from ENUM Server 105 PRI S1204 Web Server 103B URL available? S1205 ACCeSSes Web Server 103B URL S12O6 Establishes visual Communication with IP telephone 101 U.S. Patent Aug. 16, 2011 Sheet 13 Of 19 US 8,000,316 B2 euO?da???di ?70|| 007), --------- CL-61-I ?04. ?UO?da???di U.S. Patent Aug. 16, 2011 Sheet 14 of 19 US 8,000,316 B2 ?07), U.S. Patent Aug. 16, 2011 Sheet 15 Of 19 US 8,000,316 B2 -gogus-?(T?d?JssÐIÐp?JINo..----/09?SELIANI U.S.
Load more

Recommended publications
  • RFC 2168 Resolution of Uris Using the DNS June 1997
    Network Working Group R. Daniel Request for Comments: 2168 Los Alamos National Laboratory Category: Experimental M. Mealling Network Solutions, Inc. June 1997 Resolution of Uniform Resource Identifiers using the Domain Name System Status of this Memo =================== This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Abstract: ========= Uniform Resource Locators (URLs) are the foundation of the World Wide Web, and are a vital Internet technology. However, they have proven to be brittle in practice. The basic problem is that URLs typically identify a particular path to a file on a particular host. There is no graceful way of changing the path or host once the URL has been assigned. Neither is there a graceful way of replicating the resource located by the URL to achieve better network utilization and/or fault tolerance. Uniform Resource Names (URNs) have been hypothesized as a adjunct to URLs that would overcome such problems. URNs and URLs are both instances of a broader class of identifiers known as Uniform Resource Identifiers (URIs). The requirements document for URN resolution systems[15] defines the concept of a "resolver discovery service". This document describes the first, experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR), that provides rules for mapping parts of URIs to domain names. By changing the mapping rules, we can change the host that is contacted to resolve a URI. This will allow a more graceful handling of URLs over long time periods, and forms the foundation for a new proposal for Uniform Resource Names.
    [Show full text]
  • DNS/ENUM Guidelines for Service Providers & GRX/IPX
    GSM Association Non Confidential Official Document IR.67 IR.67 - DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers 6.0 1 December 2011 This is a non-binding permanent reference document of the GSM Association. Security Classification – NON-CONFIDENTIAL GSMA Material Copyright Notice Copyright © 2011 GSM Association Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V6.0 Page 1 of 78 GSM Association Non Confidential Official Document IR.67 Table of Contents IR.67 - DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers .......... 1 6.0 ............................................................................................................................... 1 1 December 2011 ....................................................................................................... 1 1 Introduction ...................................................................................................... 5 1.1 Overview ..................................................................................................... 5 1.2 Scope .......................................................................................................... 5 1.3 Definition of Acronyms and Abbreviations ................................................... 5 1.4 Definition of Terms ...................................................................................... 6 1.5 Document Cross-References ...................................................................... 7 2 DNS
    [Show full text]
  • Technical Realization of Communication Networks
    TECHNISCHE UNIVERSITAT ••• WIEN • • • institute of Vienna University of Technology • e • telecommunications Lecture Notes Technical Realization of Communication Networks Course Number: 388.031 Part : Networking o. Univ. Prof. Dr. Hannen R. van As Institute of Telecommunications Vienna University of Technology 2011 2 CONTENTS 1.5.14 Adrnii;sion control 59 l.5.15 Flow control .... 60 1.5.16 Congestion control 61 1.6 Mobility 62 1. 7 Security . .. 63 Contents 2 Source and transmission coding 65 2.1 Introduction . 66 2.2 Source coding . 67 2.3 Linc coding aJJd modulation . 68 2.3.1 Binary coding . 69 1 Networking 1 2.3.2 I3lock <.'Oding .... 70 1.1 Network architecture . 2 2.3.3 Convolution coding . 71 1.1.1 Network planes . .. 2 2.4 Modulation . 72 1.1.2 Wired and wireless media 3 2.4.l OFDM ....... 73 1.1.3 Transmission . 3 2.4.2 CMSK .. .. ... 74 1.1.4 Switching . 9 2.5 System-related coding and tra.nsrnh;sion 75 1.1.5 Signaling and control . 13 2.5.1 PCM .......... .... 76 1.1.6 Network intelligence 14 1.1.7 Network management 14 3 Tuansmission 77 1.1.8 Service transport . 14 3.1 Introduction . 78 1.1.9 Communication and content services 14 3.2 Transmission media . 82 1.1.10 Technological layering 14 3.2.l CoaxiaJ cable 82 1.1.11 Geographical areas 15 3.2.2 Copper twisted pair 82 1.2 Protocol Architecture 19 3.2.3 Fiber . 83 1.3 Network protocols 23 3.2.4 Free-space optic link 83 1.4 Network availability 27 3.2.5 Frequency spcctmrn 83 1.5 Network control .
    [Show full text]
  • March 22, 2006 Marlene H. Dortch Federal Communications Commission Office of the Secretary 445 12Th Street, SW Washington, DC 2
    1875 K Street, NW Washington, DC 20006 Tel: 202 303 1000 Fax: 202 303 2000 March 22, 2006 Marlene H. Dortch Federal Communications Commission Office of the Secretary 445 12th Street, SW Washington, DC 20554 Re: In re Telecommunications Relay Services and Speech-to-Speech Services for Individuals with Hearing and Speech Disabilities; Petition for Declaratory Ruling on Video Relay Service Interoperability, CG Docket No. 03-123 Dear Ms. Dortch: On March 20, 2006, representatives of Snap Telecommunications, Inc. (“Snap”), Aequus Technologies Corp. (“Aequus”), and WorldGate Communications, Inc. (“WorldGate”) met with Tom Chandler, Chief, Disability Rights Office; Jay Keithley, Deputy Bureau Chief, Consumer & Governmental Affairs Bureau; Greg Hlibok, Disability Rights Office; and Sharon Diskin, Office of the General Counsel. Also attending the meeting were David Dinin, President, Aequus; Daryl Crouse, President and Founder, Snap; Randy Gort, General Counsel, WorldGate; Richard Westerfer, Chief Operating Officer and Senior Vice-President, WorldGate; and the undersigned. During the meeting, the parties supported the petition in the above-captioned proceeding and opposed restrictive marketing practices, IP blocking, or other techniques by a VRS provider designed to prevent a hearing-impaired individual from placing a VRS call to a different VRS provider. However, the parties also cautioned the Commission to avoid the adoption of requirements in this proceeding that could have the inadvertent effect of impeding the ability of new or existing VRS providers from introducing VRS equipment and services implementing the newer and more robust open standard called Session Initiation Protocol (“SIP”). The parties described the benefits of SIP in providing functionally equivalent service for the hearing-impaired community, the fact that SIP is increasingly being embraced as the standard of choice in the video phone and VoIP arenas, and that SIP is the focus of significant efforts by various industry players to establish E-911 solutions for VoIP and VRS.
    [Show full text]
  • Dns Applications and Resource Records
    10 DNS APPLICATIONS AND RESOURCE RECORDS 10.1 INTRODUCTION DNS inherently lends itself well to “translating” a given piece of information into another related piece of information. This resolution process is the very reason for DNS’s invention, and it has been extended beyond resolving hostnames into IP addresses and vice versa to support a broad variety of applications. Virtually any service or application that requires translation of one form of information into another can leverage DNS. Each resource record configured in DNS enables this lookup function, returning a resolution answer for a given query. The DNS server parses the query from the Question section of the DNS message,* seeking a match within the corresponding domain’s zone file for the query’s QNAME, QCLASS, and QTYPE. Each resource record has a Name (aka Owner) field, Class (Internet class is assumed if not specified), and Type field. The RData field contains the corresponding answer to the query. The resource record type defines the type and format of the question (owner/name field) and corresponding answer (RData field). In some instances, multiple resource records may match the queried name, type, and class. In such cases, all matching records, called a Resource Record Set (RRSet), are returned in the Answer section of the response message. * Refer to Figure 9.12. IP Address Management: Principles and Practice, by Timothy Rooney Copyright Ó 2011 the Institute of Electrical and Electronics Engineers, Inc. 10.1 INTRODUCTION 177 Most, but not all, new applications require new resource record types to enable definition of application-specific information, and these new resource record types are standardized via the IETF RFC process.
    [Show full text]
  • ENUM Guidelines for Service Providers and IPX Providers
    GSM Association Non-confidential Official Document NG.105 - ENUM Guidelines for Service Providers and IPX Providers ENUM Guidelines for Service Providers and IPX Providers Version 1.1 28 May 2018 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice (Test) Copyright © 2018 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V1.1 Page 1 of 55 GSM Association Non-confidential Official Document NG.105 - ENUM Guidelines for Service Providers and IPX Providers Table of Contents 1 Introduction
    [Show full text]
  • Vitalqip® DNS/DHCP & IP Management Software ENUM
    VitalQIP® DNS/DHCP & IP Management Software ENUM Manager Release 1.2 User’s Guide 190-409-067R7.1 Issue 1 August 2007 Alcatel-Lucent - Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright © 2007 Alcatel-Lucent. Unpublished and not for publication. All rights reserved. Copyright © 2007 Alcatel-Lucent. All Rights Reserved. This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material. This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material. Trademarks All trademarks and service marks specified herein are owned by their respective companies. Licenses Apache This product includes software developed by the Apache Software Foundation (http:// www.apache.org/). Alcatel-Lucent - Proprietary See notice on first page. Contents About this document 1 ENUM
    [Show full text]
  • IP Telephony Cookbook
    IP Telephony Cookbook Dr. Margit Brandl, Dimitris Daskopoulos, Erik Dobbelsteijn, Dr. Rosario Giuseppe Garroppo, Jan Janak, Jiri Kuthan, Saverio Niccolini, Dr. Jorg¨ Ott, Stefan Prelle, Dr. Sven Ubik, Egon Verharen March 9, 2004 Contents 1 Introduction 11 1.1 Goal . 11 1.2 Reasons for writing this document . 11 1.3 Contents . 11 1.4 How to read this document . 12 1.5 Techno-economic aspect of moving from classic telephony to VoIP . 12 2 Technology Background 15 2.1 Components . 15 2.1.1 Terminal . 15 2.1.2 Server . 15 2.1.3 Gateway . 15 2.1.4 Conference Bridge . 16 2.1.5 Addressing . 16 2.2 Protocols . 16 2.2.1 H.323 . 16 2.2.1.1 Scope . 17 2.2.1.2 Signaling protocols . 18 2.2.1.3 Gatekeeper Discovery and Registration . 20 2.2.1.4 Signaling models . 21 2.2.1.5 Communication Phases . 24 2.2.1.6 Locating zone external targets . 28 2.2.1.7 Sample Call Scenario . 29 2.2.1.8 Additional (Call) Services . 29 2.2.1.9 H.235 Security . 30 2.2.1.10 Protocol Profiles . 31 2.2.2 SIP . 31 2.2.2.1 Purpose of SIP . 31 2.2.2.2 SIP Network Elements . 32 2.2.2.3 SIP Messages . 34 2.2.2.4 SIP Transactions . 38 2.2.2.5 SIP Dialogs . 38 2.2.2.6 Typical SIP Scenarios . 40 2.2.3 Media Gateway Control Protocols . 43 2.2.4 Proprietary Signaling Protocols . 45 2.2.5 Real Time Protocol (RTP) and Real Time Control Protocol (RTCP) .
    [Show full text]
  • Rewriting Dns for the Semantic Network with Ruby and Rails
    anchoring trust r e w r i t i n g d n s f o r t h e s e m a n t i c n e t w o r k w i t h r u b y a n d r a i l s http://slides.games-with-brains.nethttp://slides.games-with-brains.net// introduction we are scientists romek szczesniak eleanor mchugh cryptographer physicist [email protected] [email protected] we do science! applied research semantic DNS infrastructure identity & access management Rails-abuse, Ruby-fu, vapourware the wraith network packet sniffer the rindr DNS application server the weasel words danger! experimental code and concepts ahead all such code is provided for entertainment purposes only and should be used with extreme caution, under adult supervision, blah blah blah... any resemblance to actual code & conceptsTM, living or dead, is purely coincidental the semantic network today’s internet packet switched network based on Internet Protocol each node has an IANA-allocated IP address some IP addresses map to domain names all domains ultimately map to IP addresses nominally application agnostic the dns system defined in RFC 1034-1035 (November 1987) resolves IP addresses from domain names predominantly a static system ISC BIND 9 is the base implementation alternatives: NSD; MaraDNS; djbdns a dns lookup the following is the output of querying the domain spikyblackcat.co.uk using dig ; <<>> DiG 9.3.4 <<>> spikyblackcat.co.uk ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30042 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;spikyblackcat.co.uk.
    [Show full text]
  • Oracle Communications Network Charging and Control ENUM Control Agent User's and Technical Guide
    Oracle® Communications Network Charging and Control ENUM Control Agent User's and Technical Guide Release 12.0.0 December 2017 Copyright Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • Dns & Bind Ge-Packt
    DNS & BIND GE-PACKT Johannes Franken DNS & BIND GE-PACKT Bibliografische Information Der Deutschen Bibliothek Die Deutsche Bibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.ddb.de abrufbar. ISBN 3-8266-1502-6 1. Auflage 2005 Alle Rechte, auch die der Übersetzung, vorbehalten. Kein Teil des Werkes darf in irgendeiner Form (Druck, Kopie, Mikrofilm oder einem anderen Verfahren) ohne schriftliche Genehmi- gung des Verlages reproduziert oder unter Verwendung elektronischer Systeme verarbeitet, vervielfältigt oder verbreitet werden. Der Verlag übernimmt keine Gewähr für die Funktion einzelner Programme oder von Teilen derselben. Insbesondere übernimmt er keinerlei Haf- tung für eventuelle, aus dem Gebrauch resultierende Folgeschäden. Die Wiedergabe von Gebrauchsnamen, Handelsnamen, Warenbezeichnungen usw. in diesem Werk berechtigt auch ohne besondere Kennzeichnung nicht zu der Annahme, dass solche Namen im Sinne der Warenzeichen- und Markenschutz-Gesetzgebung als frei zu betrachten wären und daher von jedermann benutzt werden dürften. Printed in Germany © Copyright 2005 by mitp-Verlag/Bonn, ein Geschäftsbereich der verlag moderne industrie Buch AG & Co. KG/Landsberg Lektorat: Gunnar Jehle Sprachkorrektorat: Petra Heubach-Erdmann Satz und Layout: G&U e.Publishing Services GmbH, Flensburg Druck: Kösel, Krugzell I Inhaltsverzeichnis V Vorwort . 15 E Über diese Referenz . 17 E.1 Abgrenzung . 17 E.2 Zielgruppe . 17 E.3 Aufbau . 18 E.4 Schreibweisen . 18 E.5 Die RFCs . 20 E.6 Beispiele . 21 E.7 Feedback und Errata . 21 E.8 Danksagungen. 21 Teil I Konzepte und Einsatz von DNS und BIND . 23 1 Das Domain Name System . 25 1.1 Motivation . 25 1.2 Entstehung.
    [Show full text]
  • (54) METHODS.SYSTEMSAND.COMPETEB. E.R. 39 Style Alm 573
    US00839 1273B2 (12) United States Patent (10) Patent No.: US 8,391,273 B2 Ku (45) Date of Patent: Mar. 5, 2013 (54) METHODS.SYSTEMSAND.COMPETEB.PROGRAMI PRODUCTS FOR PROVIDING 2007/0061397E.R. A1 3/200739 GregoratStyleacket al.et al.................... alm 573. INTRA-CARRIER P-BASED CONNECTIONS 2007/0133574 A1 6/2007 Tejani et al. USINGA COMMON TELEPHONE NUMBER 2007/0165613 A1* 7/2007 Soo et al. ...................... 370,356 MAPPING ARCHITECTURE 2007/0286379 A1* 12/2007 Wiatrowski et al. ..... 379,201.01 2008.0002665 A1 1/2008 Soo et al. .... 370,352 2008/00 19356 A1 1/2008 Marsico ........................ 370,352 (75) Inventor: Bernard Ku, Austin, TX (US) 2008.0025492 A1* 1/2008 Heinze et al. ............ 379,220.01 2008. O198997 A1* 8, 2008 Sterman et al. .......... 379,220.01 (73) Assignee: AT&T Intellectual Property I, L.P., 2009/0227276 A1* 9/2009 Agarwal et al. ............... 455,466 Reno, NV (US) 2010/0158201 A1* 6/2010 Vijay Marathe et al. ....... 379,36 2011/0038468 A1 2/2011 Hannan et al. ........... 379,112.01 (*) Notice: Subject to any disclaimer, the term of this 2011/0149956 A1*ck 6, 2011 Alt et al. ....................... 370,352 patent is extended or adjusted under 35 FOREIGN PATENT DOCUMENTS U.S.C. 154(b) by 1111 days. JP 2007243564 A * 9, 2007 (21) Appl. No.: 12/338,259 OTHER PUBLICATIONS Lind, “ENUMOverview”, CC1 ENUM LLCPETPAC, 6 pages, Jun. (22) Filed: Dec. 18, 2008 13, 2006. (65) Prior Publication Data (Continued) US 2010/O157977 A1 Jun. 24, 2010 Primary Examiner — Chi Pham (51) Int. Cl Assistant Examiner — Ahmed Elallam H04L 2/28 (2006.01) SEg: Agent, or Firm — Myers Bigel Sibley & H04L 2/64 (2006.01) s H04L 2/66 (2006.01) (57) ABSTRACT 52) U.S.
    [Show full text]