WO2000051299A1 - Telephone a navigateur numerique - Google Patents

Telephone a navigateur numerique Download PDF

Info

Publication number
WO2000051299A1
WO2000051299A1 PCT/US2000/005037 US0005037W WO0051299A1 WO 2000051299 A1 WO2000051299 A1 WO 2000051299A1 US 0005037 W US0005037 W US 0005037W WO 0051299 A1 WO0051299 A1 WO 0051299A1
Authority
WO
WIPO (PCT)
Prior art keywords
telephone
computer
link
telephony
server
Prior art date
Application number
PCT/US2000/005037
Other languages
English (en)
Other versions
WO2000051299A9 (fr
Inventor
Edwin M. Dylag
Robert Fritzinger
Original Assignee
Voice Technologies Group, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Voice Technologies Group, Inc. filed Critical Voice Technologies Group, Inc.
Priority to AU33830/00A priority Critical patent/AU3383000A/en
Priority to JP2000601795A priority patent/JP4494644B2/ja
Priority to EP00912030A priority patent/EP1157510A4/fr
Priority to CA002364680A priority patent/CA2364680C/fr
Publication of WO2000051299A1 publication Critical patent/WO2000051299A1/fr
Publication of WO2000051299A9 publication Critical patent/WO2000051299A9/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/247—Telephone sets including user guidance or feature selection means facilitating their use
    • H04M1/2473—Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface)
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/253—Telephone sets using digital voice transmission
    • H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42314—Systems providing special services or facilities to subscribers in private branch exchanges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6472—Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6486—Signalling Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42314—Systems providing special services or facilities to subscribers in private branch exchanges
    • H04M3/4234—Remote access to features of PBX or home telephone systems-teleworking in a PBX
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal

Definitions

  • This invention relates generally to telephone communication systems, and more particularly to a new and improved system wherein all the functions of a digital telephone are usable on a computer.
  • Digital computers in particular personal computers, are playing an ever increasing role in telephone systems.
  • the personal computer plays a central role in voice processing systems utilizing computer telephony integration wherein the personal computer is interposed functionally between the telephone switch such as a private branch exchange (PBX) and the telephone set.
  • PBX private branch exchange
  • the digital telephone itself represents an advance in the additional features and functions it provides over and above those provided by conventional telephones.
  • a PBX is connected through a computer telephony interface to a personal computer which, in turn, is connected through another interface to a telephone set, such as a digital telephone.
  • a telephone set such as a digital telephone.
  • a user could access and implement all digital telephone functions without the physical telephone set, the personal computer also providing the audio function.
  • a significant advantage of such a system is computer access to and utilization of digital telephone functions from a remote location with communication via internet, LAN, WAN, RAS or other mediums.
  • Fig. 1 is a block diagram of the system of the present invention
  • Fig. 2 is a schematic diagram illustrating operation of the system of the present invention
  • Fig. 3 is a schematic diagram further illustrating an aspect of the operation of the system of the present invention.
  • Fig. 4 is a schematic diagram further illustrating another aspect of the operation of the system of the present invention
  • Fig. 5 is a flow chart illustrating operation of the system of the present invention.
  • Figs. 6-9 are schematic block diagrams illustrating applications of the system of the present invention.
  • a system 10 according to the present invention is summarized briefly in Fig. 1.
  • a PBX or other standard telephone switch is represented at 12 and lines 14, 16 are standard interface lines which connect PBX 12 to a user's telephone network.
  • a standard personal computer (PC) 20 in the present illustration is operated by a mouse 22.
  • PC 20 in the system of the present invention can be operated by a keyboard or some other input device.
  • a graphical representation 26 of a digital telephone is provided on the display of PC 20.
  • Various telephone functions are accessed by manipulating mouse 22 to place the cursor (not shown) on a particular component of the phone image 26 and then clicking the mouse. For example, to place a call the first step is to remove the headset or receiver from the phone console.
  • the system of Fig. 1 further includes a phone server generally designated 30 which couples PBX 12 and PC 20. Lines 14 and 16 from PBX 12 are connected to server 30.
  • a communications link 32 connects server 30 and PC 20 and can be a LAN, WAN, RAS, internet or a modem accessed telephone line to mention a few.
  • the signals associated with PBX 12 and the signals on lines 14, 16 are characterized by synchronous timing which is a standard requirement of PBX operation.
  • server 30 makes possible communications between the synchronous operation of PBX 12 and the asynchronous operation of communications link 32 and PC 20.
  • Server 30 allows an asynchronous client such as a web browser operatively associated with PC 20 to communicate via link 32 with a synchronous device such as telephone switch, i.e. PBX, 12.
  • phone server 30 includes a digital phone emulation interface 34, an application program interface 36 and logic 38 which ties link 32 with the interfaces 34 and 36.
  • Interface 34 by way of example is commercially available from Voice Technologies Group, Inc. under the designation
  • Interface 34 provides a direct digital connection between various PBXs and computer telephony application computers, i.e. PC 20, and their processing cards and increases the amount of integration information that can be utilized from the PBX.
  • Application program interface 36 develops a command set from signals provided by interface 34 which the software in PC 20 can understand.
  • Logic 38 provides the synchronous/asynchronous conversion mentioned above.
  • logic 38 serves as an intermediary between synchronous switching on the PBX side of server 30 and asynchronous packet switching on the other side of server 30.
  • logic 38 will packetize a request from interface 34 so that it can travel over link 32 and be utilized by PC 20. This enables telephony events from interface 34 to be converted in a way that the object, i.e. the ActiveX program mentioned above, can utilize them in connection with phone image 26.
  • a preferred program is commercially available from Microsoft Corporation and known as ActiveX control.
  • ActiveX control enables one to develop sophisticated controls based on the common object model (COM) that can be installed in dialog boxes or any ActiveX control container application.
  • ActiveX control is a COM-based object that can draw itself in its own window, respond to events like mouse clicks, and be managed through an interface that includes certain properties and methods.
  • An ActiveX control is implemented as an in-process server, typically a small object, that can be used in a control container. The control container operates the ActiveX control by using the control's properties and methods, and receives notification from the ActiveX control in the form of events.
  • ActiveX is a means of implementing a control. While ActiveX is utilized in the present illustration of the invention, other graphical interface implementations can be employed such as JAVA-APPLET and even lower level software such as C or C++ to name a few.
  • Fig. 2 illustrates application of the principles of the system 10 of Fig. 1 to performing digital call control over internet protocol (IP).
  • IP internet protocol
  • PBX 12', PC 20', mouse 22', digital phone emulation interface 34' and application program interface 36' are similar to the corresponding components in the system 10 of Fig. 1.
  • some of the control components are actually the same C++ object, but behave differently based on whether the control is configured as the client or as the server. For this reason, the following description is separated into client and server sections.
  • the components within the broken line region 50 all reside within the same control which has methods, properties and events which will be described in further detail presently.
  • the server control object 54 is responsible for the following functions. Object 54 translates VoiceBridge light events and display updates from the VoiceBridge Thread 56 into graphical user interface (GUI) representations of these events for display on a server monitor 58.
  • GUI graphical user interface
  • the GUI representation 60 is a soft phone that looks like the actual digital station set that the VoiceBridge interface 34' emulates. In this implementation, the soft phone provides a mirror image of what the client is seeing on his/her PC 20'. The mirror image is a means to provide status of client activity.
  • Server control object 54 also translates key press and hook state commands from the TCP/IP Socket Thread 62 into GUI representations of these commands for display on the server monitor 58. This completes the mirror image described above.
  • Object 54 translates key press and hook state commands from the TCP/IP Socket Thread 62 into VoiceBridge API commands for execution and interaction with the PBX 12'. Object 54 also translates VoiceBridge light events and display updates from the VoiceBridge Event Thread 56 into a format suitable for subsequent packetization by the TCP/IP Socket Thread 62.
  • the TCP/IP Socket Thread 62 has the following responsibilities when the control 50 is acting as a server. It packetizes light events and display updates from the Server Control Object 54 for transmission over a socket to the client, and it accepts packetized key press and hook state commands from the client, unpacketizes these commands and submits them to the Server Control Object 54 for execution using VoiceBridge API Commands or display on the GUI .
  • the VoiceBridge Event Thread 56 is responsible for monitoring the
  • the VoiceBridge API 36' and the VoiceBridge Card 3 ' together provide a suitable interface to the PBX 12'.
  • the VoiceBridge Card 34' handles all low-level interactions with the PBX 12 ' over synchronous digital station links.
  • the VoiceBridge API 36' provides a means for the rest of the control 50 to interact with the PBX 12' using the VoiceBridge internal virtual phone.
  • the client control object 64 is responsible for the following functions. Object 64 translates mouse clicks and key strokes from the client machine 20' into the commands suitable for subsequent packetization by the TCP/IP Socket Thread 66. The mouse clicks and key strokes are input by the user from a GUI representation of a soft phone 68 as previously described. Similar to the server GUI 60, the client GUI 68 is a soft phone that looks like the actual digital station set that the VoiceBridge 34' emulates. Client control object 64 also translates light events and display updates from the
  • TCP/IP Socket Thread 66 into graphical representations on the client monitor 20. These events are displayed on the GUI soft phone 68 described above.
  • the TCP/IP Socket Thread 66 has the same responsibilities as described in the server section, but in reverse. That is to say, key press and hook state commands come from the client object and are packetized and sent to the server. Light updates and display updates are taken from the server, unpacketized and passed to the client object for further processing.
  • programming methods other than socket and threads, as well as protocols other than TCP, IP and H.323 can be utilized to implement the client and server control objects described herein.
  • Figs. 3 and 4 illustrate architectures of the control that include voice and digital control over internet protocol (IP) .
  • the control is used in a client/server environment to provide access over IP to digital station set features from a remote location.
  • the voice component of the control is handled in one of two ways.
  • the method of Fig. 3 uses a WAV interface available from Dialogic or Natural Microsystems (NMS) or other means in conjunction with the Microsoft NetMeeting version 2.1 SDK to provide an H.323 protocol stack with audio capabilities.
  • the method of Fig. 4 uses an H.323 protocol stack (middleware) provided by the Dialogic DM3 platform, NMS Fusion platform or other means. Both methods employ the NetMeeting version 2.1 SDK on the client side.
  • a PBX 80 is connected via digital lines collectively designated 82 to a digital phone emulation interface 84 in a manner similar to PBX 12, lines 14, 16 and interface 34 in the arrangements illustrated in Figs. 1 and 2.
  • Interface 84 is connected via a voice bus 86 to a digital signal processor (DSP) 88 included in the server control 90.
  • DSP digital signal processor
  • Control 90 also includes WAV interface 92 and protocol stack 94.
  • the client control 100 also includes a protocol stack 102, and the server and client controls 90 and 100, respectively, are connected by an IP communications link 106.
  • the voice over IP method of Fig. 3 uses a WAV interface provided by Dialogic, NMS or other means.
  • the controls 90 and 100 use NetMeeting version 2.1 API calls to handle all connection establishment and capabilities negotiation on both the server and the client side.
  • the audio channel is left open throughout the duration of the client/server session. Silence is transmitted until the VoiceBridge interface 84 opens an audio channel with the PBX 80 (i.e. when a phone call is made or answered). This provides the desired effect that audio is "cut through" when a call is initiated or answered.
  • the arrow 110 in Fig. 3 shows the audio path.
  • the PBX 80 provides audio to the VoiceBridge interface 84, which drives voice data onto the voice bus 86.
  • This voice data is taken from the voice bus by the DSP card 88 and provided to the server PC (not shown) through WAV interface 92.
  • the NetMeeting software 94, 102 utilizes this WAV interface 92 to implement the H.323 protocol which includes specifications for connection negotiation (H.245) and for voice packetization and transmission (Real Time Protocol - RTP) .
  • H.323 protocol which includes specifications for connection negotiation (H.245) and for voice packetization and transmission (Real Time Protocol - RTP) .
  • Fig. 4 which illustrates voice over IP using middleware, components similar to those of the architecture of Fig. 3 are identified by the same reference numerals provided with a prime designation.
  • Server control 120 includes middleware 122 and arrow 124 indicates audio path. The client implementation does not change for this method.
  • the server does change and now uses middleware 122 such as DM/3 IPLINK from Dialogic or Fusion from NMS to provide the interface on the client side.
  • middleware provides the H.323 protocol stack in place of the NetMeeting SDK.
  • the voice path indicated by arrow is very similar to that in the method of Fig. 3.
  • the system of Fig. 2 is illustrated further by the following example transactions.
  • the first illustrative example is establishing a client/server connection. Before the client can establish a connection with the server, the server must be waiting for a client connection.
  • a control method designated StartRemote () with a parameter of FALSE is executed to start the server waiting for a client connection. Start Remote and other control methods and parameters will be described in further detail presently.
  • the client control's RemoteHostName parameter is set to the IP address of the server (i.e. 204.242.28.197).
  • StartRemote () is executed with a parameter of TRUE. This will start the initial handshaking sequence between the client and the server.
  • the initial handshake sequence is outlined in Fig. 5.
  • the next illustrative example is a client key press transaction.
  • the following sequence describes an entire key press transaction, from the client machine to the PBX for execution in reference to the components of Fig. 2.
  • a hook state transaction is identical to the following sequence, only the data transmitted is different .
  • the client user presses a GUI phone key on image 68 using his/her mouse 22'.
  • the Client Control Object 64 is notified on the mouse press and determines the key number (ID) of the GUI phone key that was pressed and tells the TCP/IP Socket Thread 66 to transmit the key press command to the server.
  • the client's TCP/IP Socket Thread 66 builds a key press packet with the appropriate key number and supporting information and sends this data to the server via a socket command.
  • the server's TCP/IP Socket Thread 62 receives the key press command packet, un-packetizes the command and tells the Server Control Object 54 to press the key.
  • the Server Control Object 54 then issues a vb_ press_key () command to the VoiceBridge API 36'.
  • the press key command will be described in further detail presently.
  • the Server Control Object 54 shows the key press on the server GUI 60 for the purpose of activity trace.
  • the VoiceBridge API 36' passes the command to the VoiceBridge card 34', which sends the command along to the PBX 12' over the synchronous digital data link.
  • the PBX 12' then acts on the key press appropriately.
  • the next illustrative example is a light update sequence. The following describes an entire light update transaction. This sequence is very similar to the key press sequence described above, but this time is initiated by the PBX 12' and terminates on the client
  • GUI phone 68 Note also that a display update sequence is identical to the following sequence, only the data transmitted is different.
  • the PBX 12' sends a light update data packet over the digital data link to the VoiceBridge card 34'.
  • the VoiceBridge Event Thread 56 receives the light update via an event generated by the VoiceBridge card 34' and passed through by the VoiceBridge API 36'.
  • the VoiceBridge Event Thread 56 passes the light update event to the Server Control Object 54.
  • the server control tells the server's TCP/IP Socket Thread 62 to transmit the light event to the client.
  • the server's TCP/IP Socket Thread 62 packetizes the light event information, including the light number and new state, and transmits this information to the client via socket commands.
  • the client's TCP/IP Socket Thread 66 receives the light update packet, un-packetizes the update and notifies the Client Control Object 64 of the light update .
  • the Client Control Object 64 then displays the new light state on the lamp image in the GUI phone 68.
  • the various properties, methods and events of the control associated with the system of Figs. 2-4 now will be described.
  • the methods and properties of the control allow its container to press keys (using the mouse or a method) , set and get light states, set and get the hook state and set and get the display information for the phone.
  • multiple phone types and sizes can be configured.
  • the capability to interact with the VoiceBridge card 34 is provided inside the ActiveX control. This allows full control of a single
  • VoiceBridge channel from within a web page, Visual Basic program or even within a Power Point presentation.
  • Client/server capabilities are included in the control. This allows for complete remote operation (call control) of the ActiveX control over a TCP/IP socket.
  • a client computer i.e. a laptop
  • the server machine contains a VoiceBridge card that is connected to a PBX.
  • the server control accepts key press and hook state commands from the client, allowing a remote user to interact with the VoiceBridge channel.
  • the client accepts lamp updates, display updates and gain/loss of carrier events from the server, thereby providing full status of the VoiceBridge line from a remote location.
  • the custom methods of the control are set forth in Table II.
  • the parameters in the middle column indicate the actions to be taken.
  • the definitions in the right- hand column are part of the ActiveX definitions.
  • the container of the ActiveX control can interact with the methods set forth in Table II.
  • the StartActivePCMode method is used when the communications link is not IP.
  • the StartRemote method is used when the communications link is with IP.
  • the clientOrHost parameter To be a client, set the clientOrHost parameter to TRUE. The control will then try to establish a connection with a shot waiting at the IP address specified in the RemoteHostName property. If no host is waiting, or if another network error occurs, the error is reported to the application.
  • Client mode is supported under Windows NT and Windows 95.
  • the controlID of the client The custom events of the control are set forth in Table III. The events occur from the control to the container to indicate what happened, i.e. they provide a notification.
  • the six status events in Table III are related to the record/playback methods of Table II and tell the container what to do, i.e. enable or disable keys .
  • Fig. 6 illustrates utilizing the foregoing capability to provide full digital station features to telecommuters.
  • PBX 150 and phone server 152 are similar to PBX 12 and server 30 in the system of Fig. 1.
  • a remote access server (RAS) 154 is connected to a local area network (LAN) 156 which, in turn, is connected to phone server 152 of the present invention.
  • RAS 154 provides a dial- in connection to the LAN 156.
  • the personal computer 158 of the telecommuter is connected to RAS 154 via the respective modems 160 and 162 and the telephone network, 164.
  • a telecommuter can connect to the office Local Area Network (LAN) 156 using Remote Access
  • RAS Software
  • the control can be set up to ring when the office phone rings (i.e. the telecommuter's desk phone can be bridged onto the control). This allows callers to use the telecommuter's normal office number to reach the telecommuter when they are working at home.
  • the telecommuter can simultaneously access data (i.e. e-mail, file servers etc.) over his RAS line.
  • Fig. 7 shows an arrangement similar to Fig. 6 but wherein the telecommuter connects to the office LAN 156' via a web server 170 through internet access.
  • PBX 180 and phone server 182 are similar to PBX 12 and server 30 in the system of Fig. 1.
  • Dedicated lines 184 and 186 of a wide area network (WAN) connect branch office or location 188 and 190, respectively to the main office or location.
  • WAN wide area network
  • PBX 200 and phone server 202 are similar to PBX 12 and server 30 in the system of Fig. 1.
  • a web server 204 is operatively connected to phone server 202.
  • Vendors 206, 208 and 210 through their PCs 212, 214 and 216, respectively, and the internet 220 access web server 222 and ultimately phone server 202.
  • Vendors and customers can be given an extension on the PBX 200 by giving them a personal web page containing the control on the company's Intranet or Internet web site 222.
  • client applications are enabled through the client control such as a voice mail application and a telephone device.
  • the client control described above makes use of a mouse, keyboard or other input devices to direct commands to the server control.
  • a voice mail application is another input device that can be connected as a remote client control. As calls are directed from the PBX to the server control, these events are delivered to the voice mail client control. In response to these events, a voice mail application will typically answer the incoming call, take input from the calling party and record a message or redirect the call to another telephone extension. These actions taken by the voice mail application are presented as input to the client control which are then delivered to the server control as previously described.
  • the present invention thereby eliminates the need for the voice mail application to be located within the distance restrictions of the PBX, and furthermore enables alternate connection means to this PBX similar to link 32 in Fig. 1.
  • a telephone can also act as the input/output device of the client control. Key presses of the telephone are used as input by the client control and directed to the server control . Commands from the PBX are directed to the client control through the server control and presented to the telephone attached to the client control for interpretation by a user.

Abstract

L'invention concerne un système de téléphone (10) permettant l'accès aux fonctions d'un téléphone numérique et leur mise en application sur un ordinateur personnel (20) seul, de telle sorte qu'il n'est plus nécessaire d'avoir un combiné téléphonique. Au moyen d'un affichage informatique (26) et d'une souris (22), d'un clavier ou d'autres dispositifs de commande d'entrée/sortie, un utilisateur accède à toutes les fonctions téléphoniques numériques et les met en application sans combiné téléphonique physique, l'ordinateur personnel (20) fournissant également la fonction audio. Une représentation graphique d'un combiné téléphonique ou d'une autre forme de téléphone est fournie sur l'affichage informatique (26), l'accès s'effectuant par la souris (22), le clavier ou un autre dispositif de commande, les opérations s'effectuant par un programme informatique fournissant une mise en application d'interface graphique. Un avantage significatif du système (10) est l'accès informatique à l'utilisation des fonctions téléphoniques numériques à partir d'un emplacement distant avec une communication via l'Internet, un réseau local (LAN), un grand réseau (WAN), un serveur d'accès à distance (RAS) ou un autre support (32).
PCT/US2000/005037 1999-02-26 2000-02-25 Telephone a navigateur numerique WO2000051299A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
AU33830/00A AU3383000A (en) 1999-02-26 2000-02-25 Digital browser phone
JP2000601795A JP4494644B2 (ja) 1999-02-26 2000-02-25 デジタル・ブラウザ電話
EP00912030A EP1157510A4 (fr) 1999-02-26 2000-02-25 Telephone a navigateur numerique
CA002364680A CA2364680C (fr) 1999-02-26 2000-02-25 Telephone a navigateur numerique

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12175599P 1999-02-26 1999-02-26
US60/121,755 1999-02-26

Publications (2)

Publication Number Publication Date
WO2000051299A1 true WO2000051299A1 (fr) 2000-08-31
WO2000051299A9 WO2000051299A9 (fr) 2001-08-23

Family

ID=22398596

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/005037 WO2000051299A1 (fr) 1999-02-26 2000-02-25 Telephone a navigateur numerique

Country Status (6)

Country Link
EP (1) EP1157510A4 (fr)
JP (1) JP4494644B2 (fr)
CN (1) CN1213578C (fr)
AU (1) AU3383000A (fr)
CA (1) CA2364680C (fr)
WO (1) WO2000051299A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1180891A1 (fr) * 2000-08-17 2002-02-20 Samsung Electronics Co., Ltd. Systéme de programmation par un utilisateur d'un autocommutateur privé en utilisant un serveur WEB
US7522578B2 (en) 2000-02-17 2009-04-21 Sap Ag Packet network telecommunication system
WO2016085770A1 (fr) * 2014-11-26 2016-06-02 Microsoft Technology Licensing, Llc Commande d'un appel téléphonique dans un commutateur privé (pbx) par l'intermédiaire d'une application client
US9414417B2 (en) 2014-08-07 2016-08-09 Microsoft Technology Licensing, Llc Propagating communication awareness over a cellular network
US9787576B2 (en) 2014-07-31 2017-10-10 Microsoft Technology Licensing, Llc Propagating routing awareness for autonomous networks
US10254942B2 (en) 2014-07-31 2019-04-09 Microsoft Technology Licensing, Llc Adaptive sizing and positioning of application windows
US10324733B2 (en) 2014-07-30 2019-06-18 Microsoft Technology Licensing, Llc Shutdown notifications
US10592080B2 (en) 2014-07-31 2020-03-17 Microsoft Technology Licensing, Llc Assisted presentation of application windows
US10678412B2 (en) 2014-07-31 2020-06-09 Microsoft Technology Licensing, Llc Dynamic joint dividers for application windows

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003259405A (ja) 2002-02-28 2003-09-12 Nec Infrontia Corp 電話システム
CN1630246B (zh) * 2003-12-15 2011-04-27 联想(北京)有限公司 一种远程桌面获取数据的实现方法
JP5346193B2 (ja) * 2008-09-19 2013-11-20 ユニ・チャーム株式会社 着用物品
CN109151146A (zh) * 2017-06-28 2019-01-04 南宁富桂精密工业有限公司 电话机控制方法及电话机

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4763356A (en) * 1986-12-11 1988-08-09 AT&T Information Systems, Inc. American Telephone and Telegraph Company Touch screen form entry system
US5754636A (en) 1994-11-01 1998-05-19 Answersoft, Inc. Computer telephone system
US5764628A (en) * 1993-01-08 1998-06-09 Muti-Tech Systemns, Inc. Dual port interface for communication between a voice-over-data system and a conventional voice system
US5892764A (en) * 1996-09-16 1999-04-06 Sphere Communications Inc. ATM LAN telephone system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI955093A0 (fi) * 1995-10-25 1995-10-25 Finland Telecom Oy Datornaetelettelefonsystem och foerfarande foer styrning av det
SE506775C2 (sv) * 1996-06-04 1998-02-09 Ericsson Telefon Ab L M Sätt och anordning för samtidig telefon- och Internetförbindelse på en telefonlinje
AU4146797A (en) * 1996-08-08 1998-02-25 Intelligence At Large, Inc. Teleserver for interconnection of communications networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4763356A (en) * 1986-12-11 1988-08-09 AT&T Information Systems, Inc. American Telephone and Telegraph Company Touch screen form entry system
US5764628A (en) * 1993-01-08 1998-06-09 Muti-Tech Systemns, Inc. Dual port interface for communication between a voice-over-data system and a conventional voice system
US5754636A (en) 1994-11-01 1998-05-19 Answersoft, Inc. Computer telephone system
US5892764A (en) * 1996-09-16 1999-04-06 Sphere Communications Inc. ATM LAN telephone system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1157510A4

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7522578B2 (en) 2000-02-17 2009-04-21 Sap Ag Packet network telecommunication system
US7664025B2 (en) 2000-02-17 2010-02-16 Sap Ag Packet network telecommunication system
US7855965B2 (en) 2000-02-17 2010-12-21 Sap Ag Packet network telecommunication system
EP1180891A1 (fr) * 2000-08-17 2002-02-20 Samsung Electronics Co., Ltd. Systéme de programmation par un utilisateur d'un autocommutateur privé en utilisant un serveur WEB
US7321944B2 (en) 2000-08-17 2008-01-22 Samsung Electronics Co., Ltd User programming system using web server for private branch exchange
US10324733B2 (en) 2014-07-30 2019-06-18 Microsoft Technology Licensing, Llc Shutdown notifications
US10254942B2 (en) 2014-07-31 2019-04-09 Microsoft Technology Licensing, Llc Adaptive sizing and positioning of application windows
US9787576B2 (en) 2014-07-31 2017-10-10 Microsoft Technology Licensing, Llc Propagating routing awareness for autonomous networks
US10592080B2 (en) 2014-07-31 2020-03-17 Microsoft Technology Licensing, Llc Assisted presentation of application windows
US10678412B2 (en) 2014-07-31 2020-06-09 Microsoft Technology Licensing, Llc Dynamic joint dividers for application windows
US9860321B2 (en) 2014-08-07 2018-01-02 Microsoft Technology Licensing, Llc Propagating communication awareness over a cellular network
US9414417B2 (en) 2014-08-07 2016-08-09 Microsoft Technology Licensing, Llc Propagating communication awareness over a cellular network
WO2016085770A1 (fr) * 2014-11-26 2016-06-02 Microsoft Technology Licensing, Llc Commande d'un appel téléphonique dans un commutateur privé (pbx) par l'intermédiaire d'une application client

Also Published As

Publication number Publication date
CN1375145A (zh) 2002-10-16
EP1157510A4 (fr) 2005-04-06
JP2002538667A (ja) 2002-11-12
CN1213578C (zh) 2005-08-03
CA2364680A1 (fr) 2000-08-31
JP4494644B2 (ja) 2010-06-30
EP1157510A1 (fr) 2001-11-28
AU3383000A (en) 2000-09-14
CA2364680C (fr) 2008-07-08

Similar Documents

Publication Publication Date Title
US20080219240A1 (en) Digital browser phone
EP1240777B1 (fr) Reseau client-serveur servant a gerer des paquets vocaux de protocole internet
US6259692B1 (en) Internet call waiting
US6707811B2 (en) Internet telephony for ecommerce
US5889845A (en) System and method for providing a remote user with a virtual presence to an office
US6791974B1 (en) Universal internet based telephony system that provides ubiquitous access for subscribers from any terminal device
JP4804600B2 (ja) マルチメディア電気通信自動コール分配システム
CA2308157C (fr) Acces a distance, emulation et commande d'equipement de bureau, dispositifs et services
AU727702B2 (en) Point-to-point internet protocol
US20030095644A1 (en) System and method for remote access to a telephone
US5657446A (en) Local area communications server
JP2000032146A (ja) 自動呼び出し分配システムおよび通信ネットワ―ク
CA2364680C (fr) Telephone a navigateur numerique
WO2000051299A9 (fr) Telephone a navigateur numerique
WO2005062594A1 (fr) Systeme de teleconference a gestion informatique
US7372822B2 (en) Computer-based telephone call conferencing
US9054910B1 (en) Apparatus and method for providing status information telecommunication
JPH07131486A (ja) Ｌａｎ通信装置用ターミナルアダプタ
EP1062794A2 (fr) Systeme de communication

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 00806840.2

Country of ref document: CN

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)

Free format text: (EXCEPT MA)

COP Corrected version of pamphlet

Free format text: PAGES 1/6-6/6, DRAWINGS, REPLACED BY NEW PAGES 1/8-8/8; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

ENP Entry into the national phase

Ref document number: 2364680

Country of ref document: CA

Ref document number: 2364680

Country of ref document: CA

Kind code of ref document: A

Ref document number: 2000 601795

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2000912030

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2000912030

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642