Personal Desktop Router

• US 20080043977A1
• Filed: 10/29/2007
• Published: 02/21/2008
• Est. Priority Date: 02/10/1997
• Status: Active Grant

• Current Assignee: Alec Miloslavsky, Alexander Volguin, Alex Smelik, Andrei Petrov, Boris Livshits, Hamid Dadgar, Igor Neyman, Michail Barskiy, Oleg Bondarenko, Paul Karpenko, Valeriy Issayev, Yuri Ostapchuk
• Original Assignee: Alec Miloslavsky, Alexander Volguin, Alex Smelik, Andrei Petrov, Boris Livshits, Hamid Dadgar, Igor Neyman, Michail Barskiy, Oleg Bondarenko, Paul Karpenko, Valeriy Issayev, Yuri Ostapchuk
• Inventors: Smelik, Alex, Karpenko, Paul, Dadgar, Hamid, Ostapchuk, Yuri, Volguin, Alexander, Barskiy, Michail, Livshits, Boris, Bondarenko, Oleg, Miloslavsky, Alec, Petrov, Andrei, Neyman, Igor, Issayev, Valeriy
• Granted Patent: US 8,358,769 B2
• Time in Patent Office: Days
• US Class Current: 379/220.01
• CPC Class Codes: H04M 1/2473 Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) details of API H04M7/0021
• CPC Class Codes: H04M 2201/40 using speech recognition speech recognition per se G10L15/00
• CPC Class Codes: H04M 2201/42 Graphical user interfaces
• CPC Class Codes: H04M 2203/408 Customer-specific call routing plans
• CPC Class Codes: H04M 2242/22 Automatic class or number identification arrangements
• CPC Class Codes: H04M 3/323 for the arrangements providing the connection (test connection, test call, call simulation)
• CPC Class Codes: H04M 3/42042 Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42059 Making use of the calling party identifier
• CPC Class Codes: H04M 3/42102 Making use of the called party identifier
• CPC Class Codes: H04M 3/42127 Systems providing several special services or facilities from groups H04M3/42008 - H04M3/58
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/42161 via computer interface
• CPC Class Codes: H04M 3/42221 Conversation recording systems at the subscriber's set H04M1/656
• CPC Class Codes: H04M 3/5183 Call or contact centers with computer-telephony arrangements
• CPC Class Codes: H04M 3/5191 interacting with the Internet
• CPC Class Codes: H04M 3/523 with call distribution or queueing
• CPC Class Codes: H04M 3/5235 Dependent on call type or called number [DNIS]
• CPC Class Codes: H04M 7/00 Arrangements for interconnection between switching centres
• CPC Class Codes: H04M 7/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 H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A client-server telephone call router system as part of a customer premises system has a client-server router adapted to execute on a telephony switch, such as a public branch exchange (PBX) or other telephony switch, or on a processor connected by CTI link to a telephony switch. The telephony switch or processor executing the router is connected to a local area network (LAN) that also interconnects computer workstations proximate to telephones connected to the telephony switch. Client user interface applications run on the computer workstations, allowing clients to edit routing rules for the router, which has a list of routing rules keyed to users and workstations of the customer premises system. The editing rules are kept by the router in portions dedicated to individual users. With this system a user can edit at a workstation on the LAN his\her own routing rules, and transmit the edits to the client-server router where the rules will be followed to route calls for that user and protocol.

Claims

1. (canceled)

2. A method for routing interactions to a plurality of individuals, comprising the steps of:

(a) receiving an interaction at a media server coupled to a network;

(b) broadcasting identifying data associated with the call on the network;

(c) receiving routing responses from one or more individuals over the network;

(e) determining routing instructions for the interaction based at least in part on the responses received; and

(f) executing the routing instructions in the media server.