US20030091028A1 - Apparatus and method for integrated voice gateway - Google Patents

Apparatus and method for integrated voice gateway Download PDF

Info

Publication number
US20030091028A1
US20030091028A1 US10/086,602 US8660202A US2003091028A1 US 20030091028 A1 US20030091028 A1 US 20030091028A1 US 8660202 A US8660202 A US 8660202A US 2003091028 A1 US2003091028 A1 US 2003091028A1
Authority
US
United States
Prior art keywords
gateway
network
call
telephone
caller
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US10/086,602
Inventor
Gordon Chang
Robert Harbison
Richard Barry
Ming Lo
Stephen Raab
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
DKR SOUNDSHORE OASIS HOLDING FUND Ltd (65%)
DKR SOUNDSHORE OASIS HOLDING FUND Ltd WITH COPIES OF NOTICES TO ITS INVESTMENT MANAGER DKR OASIS MANAGEMENT Co LP
TRINAD CAPITAL MASTER FUND Ltd (35%)
Starvox Communications Inc
Original Assignee
Chang Gordon K.
Harbison Robert W.
Barry Richard J.
Lo Ming C.
Raab Stephen R.
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 Chang Gordon K., Harbison Robert W., Barry Richard J., Lo Ming C., Raab Stephen R. filed Critical Chang Gordon K.
Priority to US10/086,602 priority Critical patent/US20030091028A1/en
Publication of US20030091028A1 publication Critical patent/US20030091028A1/en
Assigned to STARVOX COMMUNICATIONS INC. reassignment STARVOX COMMUNICATIONS INC. DOCUMENT PREVIOUSLY RECORDED AT REEL 018419 FRAME 0045 CONTAINED ERRORS IN APPLICATION NUMBER 10/086628. DOCUMENT RERECORDED TO CORRECT ERRORS ON STATED REEL. Assignors: STARVOX, INC.
Assigned to STARVOX COMMUNICATIONS, INC. reassignment STARVOX COMMUNICATIONS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: STARVOX, INC.
Assigned to DKR SOUNDSHORE OASIS HOLDING FUND LTD. (65%), TRINAD CAPITAL MASTER FUND LTD. (35%), DKR SOUNDSHORE OASIS HOLDING FUND LTD. WITH COPIES OF NOTICES TO ITS INVESTMENT MANAGER DKR OASIS MANAGEMENT COMPANY LP reassignment DKR SOUNDSHORE OASIS HOLDING FUND LTD. (65%) ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.
Assigned to TRINAD CAPITAL MASTER FUND LTD. (35%), DKR SOUNDSHORE OASIS HOLDING FUND LTD. (65%) reassignment TRINAD CAPITAL MASTER FUND LTD. (35%) ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/0024Services and arrangements where telephone services are combined with data services
    • H04M7/0057Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/20Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2022Path replacement
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/54Arrangements for diverting calls for one subscriber to another predetermined subscriber
    • H04M3/545Arrangements for diverting calls for one subscriber to another predetermined subscriber with loop avoiding arrangements
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S379/00Telephonic communications
    • Y10S379/90Internet, e.g. Internet phone, webphone, internet-based telephony

Definitions

  • This invention relates to an integrated voice gateway system.
  • PC to PC telephone technology is limited by the need to be logged on to a PC and the Internet to place or receive a call.
  • Software incorporating proprietary algorithms limit the ability to call to others having the same or similar software.
  • the sound quality is often degraded because of packet loss and delays in forwarding packets from the sender to the receiver over the Internet, operation in a half-duplex mode, and the use of low quality PC speakers and microphones.
  • PBX private branch exchange
  • IP Internet protocol
  • company e.g., intranet, wide area network (WAN), Internet
  • PST Network public switched telephone network
  • the PST NETWORK includes both public and private networks. This can result in significant cost savings and can also help to improve communication within and between companies by providing a variety of related services which are not available via the PST NETWORK.
  • current voice gateway systems are capable of only routing a nominal telephone call from a calling party at point A to a called party at point B.
  • current voice gateway systems do not provide important additional services to facilitate making a connection between the calling party and the called party at a later time or at another location or by an alternative method.
  • current voice gateway networks have no information regarding the calling party's name, telephone number, or status of the called party, e.g., busy or idle. It is this information about the calling and called parties which is not readily available, but which is necessary to provide important additional services.
  • the integrated voice gateway system should have the ability to route telephone calls between parties at two different locations over the IP network as well as the PST NETWORK, and to automatically select which of the IP network and PST NETWORK overwhich to route telephone calls.
  • the integrated voice gateway system should have the means to obtain, store, update and retrieve information about calling and called parties. For example, in instances in which a calling party is unsuccessful in making a connection to a called party, the integrated voice gateway system should have the means to use information about the calling and called parties to provide services which facilitate making an alternate or subsequent connection between the calling party and the called party.
  • ITU-T Recommendation H.323 Packet-based multimedia communications systems
  • ITU-T Recommendation X.500 Open systems interconnection—The directory: Overview of concepts, models and services; and
  • a voice telephone call from a caller telephone to a called telephone, the call carried via an IP network is referred to as a VoIP call.
  • a fax call from a caller fax machine to a called fax machine, the call carried via an IP network is referred to as an FoIP call.
  • an object of the invention to provide an integrated voice gateway system for use within a company which can route a voice telephone call between parties at two different locations over an IP network as well as the PST NETWORK and to automatically select which of the IP network and PST NETWORK over which to route the calls. It is a further object of the invention to provide a system which can route a voice telephone call between a calling party using a telephone at a first location within the system to a second location within the system via an IP network, and then from the second location to a called party at a third location via the PST NETWORK.
  • IVR interactive voice response
  • the invention provides a communication system comprising a public switched telephone (PST) network; an IP network; a PBX coupled to the PST network for routing a telephone call over the PST network; a telephone coupled to the PBX; a voice gateway coupled to the PBX through a call status-call control link and a trunk, and coupled to the IP network for routing a telephone call over the IP network; selection means for selecting which of the PST network or the IP network to route a telephone call; and call status means for the gateway server to monitor events associated with incoming calls to the telephone and outgoing calls from the telephone.
  • PST public switched telephone
  • the invention provides a communication system comprising a PST network; an IP network; a PBX coupled to the PST network for routing a telephone call over the PST network; a telephone coupled to the PBX; a voice gateway coupled to the PBX through a call status-call control link and a trunk, and coupled to the IP network for routing a telephone call over the IP network; a desktop workstation coupled to the voice gateway; selection means for selecting which of the PST network or the IP network to route a telephone call; and PC call control means for controlling the telephone from the desktop workstation.
  • the invention provides, in a communication system comprising a PST network, an IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, fallback to PST NETWORK means for rerouting a telephone call connected over the IP network to the PST network.
  • the invention provides, in a communication system comprising a PST network, an IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, a method of automatically rerouting an in process telephone call from the IP network to the PST network when the quality of the telephone call over the IP network falls below a predetermined quality level, the method comprising the steps of (a) establishing a connection for the telephone call over the PST network while the telephone call is still connected over the IP network; (b) switching the parties to telephone call over the PST network; and (c) breaking the connection for the telephone call over the IP network while maintaining the telephone call over the PST
  • the invention provides, in a communication system comprising a PST network, an IP network, a plurality of private branch exchanges (PBX) at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, fallback during call setup means to automatically route a telephone call over the PST network if, during call setup, the telephone call cannot be setup over the IP network.
  • PBX private branch exchanges
  • the invention provides a method of configuring an enterprise directory for IP telephony, the method comprising the steps of (a) providing an X.500 compatible directory; and (b) including in the schema of the directory at least one of GateKeeper, Gateway, Multipoint Control Unit (MCU), GateKeeper Exchange, and a desktop user object and attribute.
  • a providing an X.500 compatible directory
  • MCU Multipoint Control Unit
  • GateKeeper Exchange a desktop user object and attribute.
  • the invention provides a computer telephony integration (CTI) system comprising a PBX, a telephone coupled to the PBX, a local area network (LAN), a voice gateway coupled to the LAN, a CTI server coupled to the PBX and coupled to the LAN, a web server coupled to the LAN, a desktop workstation coupled to the LAN, the desktop workstation comprising a web browser.
  • CTI computer telephony integration
  • the invention provides a communication system comprising a PST network, an IP network, a PBX coupled to the PST network for routing a telephone call over the PST network, a voice gateway coupled to the PBX and the IP network for routing a telephone call over the IP network, and selection means for selecting which of the PST network or the IP network to route a telephone call, and for a telephone call placed from a first telephone at a first location, over the IP network to a second telephone at a second location, path replacement means for transferring the telephone call from the second telephone at the second location to a third telephone at a third location, the path replacement means routing the telephone call from the first telephone at the first location over the IP network to the third telephone.
  • the invention provides a communication system comprising a PST network, IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX through a call status and call control link and a trunk, and coupled to the IP network for routing telephone calls over the IP network, coupled to a plurality of voice gateways, selection means for selecting which of the PST network or the IP network to route telephone calls, and feature networking means for providing PBX features among the plurality of locations over the IP network.
  • the integrated voice gateway system includes a gateway server which serves as an Intranet/internet telephony gateway.
  • the gateway server routes intra-company voice or facsimile (fax) calls, made from user's desktop phones or fax machines/servers, over the company's intranet or the public Internet.
  • the gateway server provides an alternate voice network to the PST NETWORK for a company. This alternate network carries voice and fax calls at a much lower cost. This is because an intranet is built to support bursty data traffic and the bandwidth is underutilized most of the time.
  • the gateway server takes advantage of the underutilized bandwidth when such bandwidth is available to transmit voice.
  • the gateway server is a combination of hardware and software components which reside on a workstation server platform.
  • the gateway server is coupled to a customer premise telephone system, i.e. a PBX via a T1 or E1 trunk for larger systems, or an analog trunk for smaller systems.
  • the gateway server is coupled to the company's intranet via industry standard connections (e.g., ethernet, frame relay or asynchronous transfer mode (ATM)).
  • ATM asynchronous transfer mode
  • the gateway server is a gateway between the PBX/PST NETWORK and the company's intranet.
  • the gateway servers in a multi-site company are therefore coupled together via the company's intranet or wide area network (WAN) into a gateway network.
  • WAN wide area network
  • the gateway server uses call status and call control integration with the PBX to provide many unique and useful features which are otherwise unavailable.
  • the gateway server supports a variety of call status/call control PBX links including T1 inband ANI, PRI, QSIG (global DSS1 based signaling system for corporate networks, not an acronym, known at the international level as Private Signaling System No. 1 (PSS1)) and CTI.
  • PSS1 Private Signaling System No. 1
  • PSS1 Private Signaling System No. 1
  • API industry standard CTI applications programming interfaces
  • TSAPI AT&T/Novell Telephony Services Application Programming Interface
  • TAPI Microsoft Telephony Application Programming Interface
  • ECMA European Computer Manufacturers Association
  • CSTA Computer Supported Telephony Applications
  • the gateway server is also equipped with a database of user and gateway objects and attributes.
  • This database provides many unique features including providing caller's name based on caller phone number, address translation, gateway network routing information, user authentication, etc.
  • This database is stored in the server but can be integrated with industry standard enterprise directory services systems including Novell Directory Services (NDS), Microsoft Active Directory Services (ADS), Domain NT and any directory which supports the Lightweight Directory Access Protocol (X.500) (LDAP) interface.
  • NDS Novell Directory Services
  • ADS Microsoft Active Directory Services
  • Domain NT any directory which supports the Lightweight Directory Access Protocol (X.500) (LDAP) interface.
  • LDAP Lightweight Directory Access Protocol
  • a gateway network in a company essentially connects a company's PBXs, which are often geographically dispersed, into a single intelligent virtual PBX (VPBX).
  • VPBX virtual PBX
  • a company-wide VPBX provides advanced end-user features across the company. These features would otherwise be available only within the scope of a single PBX, or would require expensive PBX features interworking products which require expensive PBX resident software and expensive data connections, e.g. dedicated voice tie lines between sites.
  • the gateway server offers PBX features interworking, at a lower cost, over a network of mixed PBXs from different vendors and over a single converged network (data tie line or data VPN).
  • the gateway server works with existing telephone systems, and with the mixed networks of telephone systems commonly found in large companies.
  • the gateway server provides feature interworking using the combination of the desktop telephone and desktop workstation.
  • Current PBX systems provide such internetworking capabilities only between desktop telephones. With the gateway server, however, a worker using a desktop telephone can be notified of an important call via the desktop workstation.
  • the unique ability of the gateway server to control both the desktop telephone and the desktop workstation for calls between remote workers provides many new VPBX features not available with current PBX to PBX solutions, and provides an alternative method for current PBX networking features that is not limited to only sites with the same vendor PBX models. These consistent features across the network substantially improve communications and enhance productivity by making employees at multiple sites feel like they are part of a single community.
  • the gateway server also offers benefits such as intelligent routing (using automatic configuration) and increases network performance.
  • the gateway server supports routing of telephone and fax calls made from desktop telephones or stand alone fax machines, or workstation integrated fax servers over a company's intranet or the public Internet. By configuring a selection table in the server, the gateway server can route real-time fax calls over either the intranet or Internet to minimize the cost of the fax call.
  • the gateway server supports computer-based fax as well as stand-alone fax machines.
  • the gateway server By integrating CTI and enterprise directory service with IP telephony, the gateway server provides many more features in a user-friendly way than current Internet/intranet telephony to IP voice gateways.
  • Current voice gateways connect only to a telephone system's voice lines, e.g., analog, ISDN BRI, ISDN PRI, or T1. This provides only for carrying voice or fax calls over IP.
  • the gateway server is unique in that the server also provides a call control and call status link to the telephone system.
  • current voice gateways do not store user telephone information such as telephone number and associated user name.
  • the gateway server is unique in that it stores extensive user telephone information and also integrates with industry standard enterprise directory services. The use of extensions to the enterprise directory services to implement IP telephony services is a new concept introduced by the gateway server of the invention.
  • the gateway server can route long distance calls among multiple company locations and do so in a manner which is transparent to the users, except perhaps for possible differences in the quality of voice transmission. However, the users dial the same way that they currently dial to make calls whether over public or private networks.
  • the routing table of the PBX automatically routes designated calls to the voice gateway and the gateway then decides whether to route the call over the company's intranet or the Internet.
  • the gateway server In addition to integrating CTI and enterprise directory service with IP telephony, the gateway server also provides many unique IP telephony features in addition to the VPBX features.
  • the gateway network of the invention can continue to maintain a call over the IP network as long as the quality of the call is above a predetermined quality level. If the quality of a voice call over the intranet or Internet falls below a predetermined quality level, e.g. due to network congestion, the gateway server can automatically “fall back” to the PST NETWORK. The gateway server can automatically set up a call over the PST NETWORK between the caller and called party's desktop telephones and switch the parties to the PST NETWORK call. The gateway server can then drop the IP portion of the call such that the caller and called party are then talking over the PST NETWORK.
  • the integrated voice gateway system of the invention provides the capability to fallback to PST NETWORK during call setup in which only calls directed to a non-accessible gateway are routed over the PST NETWORK, while still allowing other calls to be routed via the gateway and IP network. If a remote gateway is not accessible, a voice call would not necessarily be rerouted over the PST NETWORK as would be done by current voice gateways.
  • FIG. 1 is a block diagram of an overview of the top-level architecture of an embodiment of an integrated voice gateway system according to a first aspect of the invention.
  • FIG. 2 is a block diagram of the top-level architecture of a gateway network according to a first aspect of the invention.
  • FIG. 3 is a block diagram illustrating major software and hardware components of an embodiment of a gateway network according to a first aspect of the invention.
  • FIG. 3A illustrates the distributed architecture of the enterprise directory.
  • FIG. 4 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in setting up a basic PST NETWORK call.
  • FIG. 5 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in setting up a basic VoIP call.
  • FIGS. 6 - 7 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a first method for setting up a hop-off to PST NETWORK call.
  • FIGS. 8 - 12 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a second method for setting up a hop-off to PST NETWORK call.
  • FIGS. 13 - 14 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a third method for setting up a hop-off to PST NETWORK call.
  • FIG. 15 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a common method for setting up a hop-on to VoIP call.
  • FIG. 16 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a first scenario for setting up a hop-on to VoIP call.
  • FIG. 17 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a third scenario for setting up a hop-on to VoIP call.
  • FIG. 18 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a fourth scenario for setting up a hop-on to VoIP call.
  • FIGS. 19 - 22 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a first method for setting up a fallback to PST NETWORK call.
  • FIGS. 23 - 29 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a second method for setting up a fallback to PST NETWORK call.
  • FIGS. 30 - 33 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a third method for setting up a fallback to PST NETWORK call.
  • FIGS. 34 - 38 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a fourth method for setting up a fallback to PST NETWORK call.
  • FIGS. 39 - 46 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a fifth method for setting up a fallback to PST NETWORK call.
  • FIG. 47 is a block diagram illustrating a prior art approach to providing a CTI-workstation interface.
  • FIG. 48 is a block diagram illustrating the computer architecture supporting a PC Call Control feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 49 illustrates the operation of a virtual desktop feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 50 illustrates the operation of a caller name display feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 51 illustrates the operation of a call log feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 52 illustrates the operation of an embodiment of an integrated voice gateway system of the invention when a called telephone is busy.
  • FIG. 53 illustrates the operation of a callback on busy feature in an embodiment of an integrated voice gateway system of the invention.
  • FIGS. 54 - 55 illustrate the operation of a call alert feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 56 illustrates the operation of a ring through feature in an embodiment of an integrated voice gateway system of the invention.
  • FIGS. 57 - 58 illustrate the setup and operation of a follow me feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 1 is a block diagram of an overview of the top-level architecture of an embodiment of an integrated voice gateway system 2 according to a first aspect of the invention.
  • the block diagram depicts three gateway networks 4 , 6 , 8 of a multi-site company.
  • such gateway networks may be located, e.g. in different buildings of a large plant, such as in an industrial park or campus setting, in different locations within the same city, or may be located at geographically distant locations, including world-wide.
  • the gateway networks may also be located in different companies. In the particular example depicted in FIG.
  • first and second gateway networks 4 , 6 may be within a large industrial park or at different locations within a city as they are both coupled to a first telephone company central office (CO) CO 1 12 .
  • the third gateway network 8 is geographically distant from both the first and second gateway networks 4 , 6 and is coupled to a second CO, CO 2 14 .
  • CO 1 12 and CO 2 14 are part of a PST NETWORK 16 .
  • the PST NETWORK 16 may include many COs.
  • Each of the gateway networks 4 , 6 , 8 is coupled to the company's IP network 18 .
  • the IP network 18 may include an intranet, the Internet, and the like.
  • FIG. 2 In the description of FIG. 2 and subsequent FIGS., a generic embodiment of a gateway network according to the invention will be described with reference to the first gateway network 4 depicted in FIG. 1.
  • FIG. 2 is a block diagram of the top-level architecture of an embodiment of a gateway network 4 (represented by the dashed box) according to a first aspect of the invention.
  • the gateway network 4 includes a local area network (LAN) 22 . Coupled to the LAN 22 are one or more workstations 24 , a gateway server 26 , a directory server 28 , and a router 32 . The gateway server 26 is also coupled to the PBX 34 via a call status-call control link.
  • the call status-call control link can comprise a CTI link 98 , a PRI interface 36 , a QSIG interface 36 or an analog driver 33 . These interfaces are individually illustrated and described below in reference to FIG. 3.
  • the PBX 34 is coupled to CO 1 12 .
  • One or more telephones 38 are coupled to the PBX 34 .
  • the telephones 38 may be any telephone device connecting to a PBX, e.g. analog (POTS), proprietary digital, or standards-based digital (ISDN BRI).
  • POTS analog
  • ISDN BRI standards-based digital
  • Each telephone 38 may be logically associated with and may be co-located with a respective workstation 24 .
  • the gateway server 26 is also coupled to the PBX 34 via an industry standard telephone station interface 33 .
  • the CTI interface 98 between the gateway server 26 and the PBX 34 uses an industry standard CTI API, e.g., TSAPI, TAPI and CT Connect. Both TSAPI and TAPI focus on call control.
  • the CTI interfaces enable computer control of dialing, answering, transferring and conferencing, and provide status. In PBX environments, the CTI interfaces also support control of advanced features of digital telephones (TAPI) and the switches to which those station sets connect (TSAPI).
  • TAPI digital telephones
  • TSAPI switches to which those station sets connect
  • the directory server 28 may reside in separate hardware or may be co-located with the gateway server 26 in the same hardware.
  • FIG. 3 is a block diagram illustrating major software and hardware components of an embodiment of a gateway server 26 according to a first aspect of the invention.
  • the gateway server 26 includes software modules which communicate among themselves and have interconnections to other components through either software drivers supporting interfacing hardware elements, or communication links to other components.
  • the gateway engine 50 is the central logic coordinating element of the gateway server 26 .
  • the gateway engine 50 directs and oversees the activities of the other components of the gateway server 26 and gateway network 4 (FIG. 2).
  • the gateway engine 50 accesses routing information from a gateway gatekeeper 53 and directs a communication subsystem 58 .
  • the gateway engine 50 also contains the feature logic for VPBX capabilities.
  • the gateway engine 50 also creates logging and statistical data.
  • the enterprise directory 90 is a company-wide general purpose directory or global database of named objects including users, network devices (e.g. routers, gateways), and network services (e.g. print servers), etc.
  • the enterprise directory 90 is a distributed system with replication and synchronization among its nodes, and has an extensible object schema.
  • the implementation of the enterprise directory 90 in the integrated voice gateway system of the invention includes the extension of the directory schema to support IP telephony.
  • the enterprise directory 90 is implemented using a general purpose directory such as NDS.
  • the invention introduces schema extensions in NDS.
  • the schema extensions enhance the NDS base schema so that it supports the Directory Services requirements for an H.323 Recommendation based IP telephony network.
  • the schema extension enables the H.323 gatekeepers in an H.323 IP telephony network to automatically find each other. This capability is not currently specified and supported by the ITU H.323 Recommendation v.1.
  • the schema extensions also enable the invention to provide many of its unique features, e.g. caller ID, follow me with call filtering, etc.
  • FIG. 3A illustrates the distributed architecture of the enterprise directory 90 .
  • the logical organization of the enterprise directory 90 is illustrated by the large ellipse with NDS at its center and surrounded by a series of pie-shaped logical partitions P 1 , P 2 , P 3 , P 4 , P 5 , P 6 .
  • the number of partitions illustrated in FIG. 3A is arbitrary, as the actual number of partitions in a particular gateway network will depend on the needs of the particular enterprise.
  • gateway servers 26 - 1 , 26 - 2 , 26 - 3 , 26 - 4 , 26 - 5 , 26 - 6 each gateway server coupled to a respective physical partition P 1 ′, P 2 ′, P 3 ′, P 4 ′, P 5 ′, P 6 ′ of the enterprise directory 90 .
  • the dashed curved lines indicate the correspondence of the physical partitions P 1 ′, P 2 ′, P 3 ′, P 4 ′, P 5 ′, P 6 ′ with the logical partitions P 1 , P 2 , P 3 , P 4 , P 5 , P 6 of the enterprise directory 90 .
  • Each physical partition P 1 ′, P 2 ′, P 3 ′, P 4 ′, P 5 ′, P 6 ′ comprises the portion of the respective enterprise directory 90 applicable to the respective location served by a gateway server 26 - 1 , 26 - 2 , 26 - 3 , 26 - 4 , 26 - 5 , 26 - 6 in the enterprise's gateway network.
  • the enterprise directory 90 at an individual location may include a replica of a partition from another location in the network. This can be done, for example, to facilitate set up of calls between locations which have a high volume of telephone calls.
  • the arrows in FIG. 3A indicate the locations of replicas of partitions which are included in the enterprise directories at other locations.
  • a replica of the partition P 1 ′ at the first location is included in the enterprise directory 90 - 2 at the second location.
  • both the third and sixth locations have replicas R 3 ′, R 6 ′ of each other's partitions.
  • the replicas of the partitions are automatically synchronized, whereby changes to entries in a partition at one location, are sent to other locations having a replica of the respective partition.
  • the gateway database 51 is an open database connectivity (ODBC) compatible database.
  • the gateway database 51 contains enterprise white pages, frequent contact information, gateway routing tables, individual user follow me records, and a call log.
  • the gateway database 51 records are fully indexed to provide necessary real-time performance.
  • the enterprise directory 90 is the source of the white pages, and frequent contact and raw routing tables. This information is separately maintained in the gateway database because commercially available implementations of an enterprise directory, e.g. NDS, are not indexed, and are therefore not easily searchable.
  • the gateway database 51 is indexed to facilitate the availability of the data. The data is obtained from the enterprise directory 90 and passed to the gateway database 51 by the dredger 107 .
  • the gateway database 51 also includes an operational routing table, user follow me and call log data which are created within the gateway server 26 .
  • the gateway database 51 runs on an ODBC compliant database application. Suitable database applications include, for example, Jet, which is included with Windows NT 4.0, and Oracle 8.
  • the preferred embodiment of the invention includes the X.500 compatible enterprise directory.
  • the alternative embodiments of the gateway network of the invention may include other database configurations.
  • one alternate embodiment may be used in systems which have an SQL Server database.
  • the schema extensions may be added to the existing data structures in the SQL database, or a new, comprehensive schema may be established.
  • the enterprise directory includes a database designated the master database at a first location, and duplicate databases, designated slave databases at the remaining locations in the gateway network. In this master-slave configuration, all database administration is performed on the master database. Updates to the master database are exported to a file which is sent to the other locations and imported into the slave databases.
  • the dredging and synchronization process would be the same as for an X.500 compatible enterprise directory.
  • the database cache 108 is a repository of information contained in RAM in the gateway server 26 .
  • the database cache includes data duplicated from the gateway database 51 which data is required to be in RAM to support the performance of the gateway server, and also transient/dynamically changing data, e.g. idle/busy status of users' telephones. Much of the data in the database cache 108 is indexed for rapid retrieval.
  • the gatekeeper agent 52 is the equivalent of an H.323 gatekeeper client.
  • the gatekeeper agent 52 interacts with the gateway gatekeeper 53 for address translation, e.g. PST NETWORK telephone number to IP address of a remote destination gateway server or H.323 telephone.
  • the gateway gatekeeper 53 is an embedded equivalent of an H.323 gatekeeper.
  • the gateway gatekeeper 53 services the request for address translation received from the gatekeeper agent 52 .
  • This module uses data within the gateway database 51 for performing address translations.
  • the fax gateway 54 sends and receives faxes to and from an external fax server (not illustrated).
  • the fax gateway 54 also translates faxes into printable files and transfers the files to a print server (not illustrated) for printing.
  • the gateway web server application 55 supports the components of the web client server applications in the gateway network 4 .
  • a suitable web server application 55 is the Microsoft NT IIS server application which uses ActiveX server components and Active Server Pages technologies.
  • the user web server application 56 is a server application component which supports user clients by responding to HTTP user requests by the user clients.
  • the administrator web server application 57 is a server application component which supports system administrator clients by responding to HTTP user requests by administrator clients.
  • the web server 92 is a Microsoft NT IIS Server.
  • the web server 92 provides the client/server communication mechanism between browser-based clients, e.g. a user client 95 and an administrative client 96 , and the gateway web server application 55 , the user web application 56 and the administrator web application 57 .
  • the web server 92 may be co-located on the same server hardware as the gateway server 26 or may be on separate server hardware.
  • the user client 95 (also referred to herein as “browser”) is a browser-based graphical user interface (GUI) application which resides in a desktop workstation 24 .
  • GUI graphical user interface
  • Java and HTML are used to provide the user interface.
  • This application interface is used to deliver integrated gateway user features.
  • the administrator client 96 is also a browser-based GUI application, which resides in a desktop workstation 24 .
  • the communications subsystem 58 presents to the gateway engine 50 an abstract appearance of telephony capabilities and activities in the system.
  • the communications system 58 merges information from separate modules (e.g., the telephone network 65 and CTI 76 modules) to present a single logical PBX representation.
  • the communications subsystem 58 also allows calls to be managed in a similar manner by the higher systems, whether telephone network or IP telephony in nature during initiation, while active and at completion.
  • the IP telephony module 59 is an object oriented abstraction of IP telephony. This module permits hardware from different vendors to be used, thereby isolating their differences from the higher level components of the system.
  • the VoIP submodule 60 is an object oriented abstraction of an H.323 implementation including H.323 call control and H.323 voice transmission over an IP network.
  • the FoIP submodule 61 is an object oriented abstraction of T.IFAX2 implementation including the fax interaction and transmission protocol over an IP network.
  • the VoIP/FoIP driver 62 is the software layer supplied with IP telephony hardware to support the gateway server 26 application.
  • a network interface card (NIC) 63 connection (e.g., ethernet 10baseT) provides the IP connection to the data network (not illustrated) used to transmit and receive IP telephony communications.
  • a digital signal processor (DSP) 64 includes a microprocessor which is specialized to manage real-time digitally encoded signals. For IP telephony, the DSP 64 may include coder/decoder (codec) algorithms to compress and decompress voice signals.
  • the telephone network module 65 is an object oriented abstraction of switched circuit telephone network connections. These connection types are the foundations of today's telephone network. Elements controlled in the telephone network module 65 include station interfaces 73 , trunk interfaces 66 , and resources to interact with the media stream (e.g. record and playback voices, detect and generate touch tones, etc.). The telephone network module 65 represents all the call processing information and call status.
  • the trunk interface submodule 66 is an object oriented abstraction of telephone network trunk connections. Several telephone trunk types may be 5 supported including, e.g., analog trunks (Loop Start and Ground Start), T1/E1 E&M trunks, ISDN PRI trunks (T1/E1), and ISDN QSIG (T1/E1).
  • the trunk interface submodule 66 can interface with a variety of hardware specific software drivers, e.g. analog driver 67 , T1/E1E&M driver 69 , PRI driver 70 , and QSIG driver 71 .
  • the analog trunk hardware 68 supports connecting analog trunk lines 35 .
  • the analog trunk hardware 68 provides the physical connection of this trunk type to the gateway server 26 and, in some cases, provides a connection to an internal time division multiplexing (TDM) bus 84 .
  • Suitable analog trunk hardware 68 includes the QuickNet Technologies LineJack card.
  • the DS-1 hardware (T1/E1) 72 supports connecting DS-1 trunk lines (T1/E1 E&M) 37 , (PRI) 39 , (QSIG) 41 .
  • the DS-1 hardware 72 provides the physical connection of this trunk type to the server and, in some cases, provides a connection to the internal TDM bus 84 .
  • the DS-1 hardware 72 card may be a T1 card which supports 24 channels (domestic US) or an E1 card which supports 30 channels (European).
  • a suitable DS-1 hardware 72 card is the Dialogic D240.SC card.
  • the analog station hardware 75 supports connecting analog station lines 33 .
  • the analog station hardware 75 provides the physical connection to the gateway server 26 and, in some cases, provides a connection to the internal TDM bus 84 .
  • a suitable analog station hardware 75 is the Dialogic DIALOG/4 card.
  • the TDM bus 84 is an internal bus which provides a switching matrix for circuit switched telephone connections.
  • the TDM bus 84 is used to transport voice signals or other call content from one hardware device (e.g., analog trunk 68 , DS-1 H/W (T1/E1) 72 , and analog station H/W 75 ) to another within the system.
  • the TDM bus 84 may exist both internal to a single card as well as providing a physical connection where multiple cards may be interconnected. Suitable implementations of a TDM bus 84 include the Dialogic SC-Bus and the Natural Microsystems MVIP bus.
  • the station interface submodule 73 is an object oriented abstraction of telephone network station connections.
  • the interactions embodied in the station interface submodule 73 represent the operation of a telephone device connected to a telephone system PBX or public network.
  • the station interface submodule 73 is implemented using analog station connections (POTS telephone), however the station interface submodule 73 may also be implemented using digital telephone connections, e.g. ISDN BRI emulation.
  • the station interface submodule 73 interfaces with a variety of station hardware specific software drivers, illustrated in FIG. 3 as an analog station driver 74 .
  • the CTI module 76 provides an object oriented abstraction of a CTI link connection to a PBX.
  • the CTI module 76 supports the delivery of events received and the receipt of call control commands in an abstract sense for processing and subsequent handoff for delivery to the PBX 34 over the CTI link 98 .
  • the CTI module 76 can support the requirements of industry standard CTI links, e.g. TSAPI, TAPI and CT Connect.
  • the TSAPI submodule 77 supports all communications with the TSAPI driver 80 .
  • the TSAPI submodule 77 normalizes any TSAPI differences which exist among various PBX implementations into a common TSAPI abstraction, and presents this abstraction to the CTI module 76 .
  • the TAPI submodule 78 supports all communications with the TAPI driver 81 .
  • the TAPI submodule 78 normalizes any TAPI differences which exist among the various PBX implementations into a common TAPI abstraction and presents this abstraction to the CTI module 76 .
  • the CT Connect submodule 79 supports all communications with the CT Connect driver 82 .
  • the CT Connect submodule 79 normalizes any CT Connect differences which exist among the various PBX implementations into a common CT Connect abstraction and presents this abstraction to the CTI module 76 .
  • the CTI server 97 is a client/server application which controls the flow of information between the gateway server 26 and the PBX 34 over the PBX CTI link 98 .
  • the core CTI server module 102 provides the central logic for the application.
  • the CTI client driver 99 manages logical link connectivity to client applications.
  • the CTI client driver 99 also manages a communications link 106 to the CT Connect driver 82 , and brokers the information flow to and from the CT Connect driver 82 .
  • the PBX-specific driver 101 interfaces with the CTI server core module 102 , translates the CTI server's 97 standard messaging to/from the particular protocol used by the specific PBX 34 , and delivers the information to/from the physical connection to the PBX 34 .
  • the physical connection to the PBX 34 may be an ethernet NIC, or a dedicated physical link with a protocol, e.g. X.25 or ISDN BRI.
  • Suitable client/server CTI implementations include Novell TSAPI, Microsoft TAPI2.1 and Dialogic CT Connect.
  • the CTI server 97 may be a stand alone application on separate server hardware or may reside in the same server hardware as the gateway server 26 .
  • the gateway server 26 integrates with telecommunications customer premises equipment (CPE), in particular PBXs for large sites and hybrid/key systems at smaller locations.
  • CPE customer premises equipment
  • PBX is used herein interchangeably to refer to all such systems.
  • the automatic route selection (ARS) 103 is a functional capability that the PBX 34 employs to select the preferred trunk for placing a call.
  • PBXs may have a variety of trunks attached, including local lines, direct lines to a long distance provider, private leased lines interconnecting with other company PBXs, and virtual private networks.
  • the ARS 103 sometimes also called least cost routing (LCR), reviews the number dialed, and identifies a preferred trunk. If the preferred trunk is busy, the ARS 103 will proceed to a subsequent choice. The ARS 103 then adds or deletes digits to condition the number dialed and transmit the call over the selected line. This feature is also available on some hybrid/key systems.
  • the ARS 103 is configured to route calls destined across the gateway network to the gateway server as the preferred first choice.
  • the PBX 34 uses trunks to connect to the PST NETWORK CO and to interconnect to other PBXs. Various types of trunks may be used, including analog, T1, E1, ISDN PRI, and QSIG.
  • the gateway server 26 can support all the trunk types listed.
  • a PBX station line is a connection for a telephone device.
  • PBXs may support several types of telephone devices, including analog (POTS), proprietary digital stations, and ISDN terminals.
  • POTS analog
  • the gateway server 26 may use analog station lines 33 to interface with the PBX.
  • the integrated computer telephone system introduces schema extensions in industry standard enterprise directory services systems to support IP telephony. While the description of the schema extensions will be presented in terms of NDS, it is understood that the schema extensions are applicable to other industry standard directory systems.
  • the schema extensions enhance the NDS base schema so that the schema supports the Directory Services requirement for an ITU H.323 Recommendation based IP telephony network.
  • the schema extensions enable the H.323 gatekeepers in an H.323 IP telephony network to automatically find each other. This capability is not currently specified and supported by ITU H.323 Recommendation v.1.
  • the schema extensions also enable the gateway server to provide additional features, e.g. caller ID and call filtering.
  • the schema extension includes additional NDS objects and additional NDS attributes.
  • the schema enhancement defines the relationships among the additional NDS objects and attributes.
  • the additional NDS objects for H.323 include H.323 Gateway, H.323 Gatekeeper, and H.323 Multipoint Control Unit (MCU).
  • the additional NDS attributes are applicable to the additional H.323 objects and existing NDS objects.
  • Table 1 lists the attributes which are included in the NDS enterprise directory schema extensions in a preferred embodiment of the invention.
  • Table 1 includes the name of each attribute added to the schema, a brief definition of each attribute, and an indication as to whether the attribute is added to support the use of the enterprise directory to support IP telephony or to support the advanced features TABLE 1 New Attributes Included in the Enterprise Directory Schema Extension Attribute Definition Supports
  • Attendant Specifies the telephone number for a gateway Advanced Number server for Finder activation/deactivation, Features HopOn from PST NETWORK, etc.
  • Auto Attendant Specifies the dialing string for the auto Advanced Prefix attendant preceding the extension number Features (null value if no autoattendant and Direct Inward Dialing is available for the PBX).
  • CallAlert Specifies the time-out period, in seconds, Advanced Timeout for Call Alert inaction for a gateway server.
  • Features Call Log Specifies the duration, in days, of the call Advanced Configuration log parameters for a gateway server, Features including Call Log Duration, Call Log Type 1, Call Log Type 2, . . . (where Call Log Type i specifies the event logging level for a gateway server. There can be multiple event logging levels.).
  • WhitePages Specifies the scope of the whirte pages in Advanced Subtree the context of the enterprise directory.
  • the Features gateway server catalog contains WhitePages and other information derived from the enterprise directory. This attribute establishes the directory contents that the WhitePages contain.
  • Cellular Specifies the user's cellular phone number.
  • CTI Specifies the CTI link between the gateway Advanced server and the PBX, including CTI Type, Link Features Name, and Server Name.
  • CTN Access Specifies the special trunk access code to Advanced Code the Corporate Telephony Network, e.g. “8” Features (null value if the PBX does not support CTN dialing).
  • CTNLocation Specifies the location ID(s) for the gateway Advanced ID network in the Corporate Telephony Network Features numbering plan.
  • CTN Numbers Specifies the Corporate Telephony Network Advanced Table numbers (or number patterns) represented by Features the gateway network for its PBX and its satellite PBXs (i.e.
  • CTN Trunk Specifies the translation table for Advanced Translation converting from the PBX numbering format to Features CTN canonical format, including Trunk Group ID, Trunk ID Range, Number of Digits to Delete, Digit to Prepend, and Trunk Card ID, and Comments.
  • FallBack Specifies the fallback number for a gateway Advanced Number server. This is the PST NETWORK number Features that the gateway servers use to call each other for fallback to PST NETWORK.
  • GateKeeper Specifies the default GateKeeper with which IP an entity such as Gateway and H.323 Terminal Telephony should register. Entities are allowed to register with GateKeeper for the H.323 Zone to which the entity belongs.
  • GatekKeeper Identifies the GateKeeper Exchange with IP Exchange which a GateKeeper is associated.
  • Telephony Gateway Specifies the gateway associated with a IP gateway network entity, e.g. a user.
  • Telephony Gateway List Specifies the gateway servers associated with IP a GateKeeper.
  • Telephony Home Phone Specifies the user's home phone number. Advanced Features HopOff Specifies whether Hop-Off to PST NETWORK Advanced Enabled is enabled for a gateway server.
  • HopOff PST Specifies the PST NETWORK number patterns Advanced NETWORK for hop-off to PST NETWORK for the gateway Features Patterns server. Only PST NETWORK numbers which match these patterns can be reached via hop- off from this gateway server. This attribute facilitates the automatic routing configuration for the gateway network.
  • HopOn Specifies whether Hop-On from PST Advanced Enabled NETWORK is enabled for a gateway server.
  • Features HopOn for OffNet Specifies the list of users, groups, or Advanced Call List containers authorized to access Hop-On for Features Off-Net calls. License Contains the license data for a gateway Advanced network, including Serial Number and License Features Count.
  • Manual Fallback Specifies code (a combination of multiple Advanced Code telephone keypad keys) for fallback to PST Features NETWORK (null value if manual fallback is disabled). Maximum Specifies the maximum number of outstanding Advanced CallBacks Callback on Busy requests for each user of a Features per gateway server (zero if callbacks are not User allowed, no value if no limit on the number of callback requests).
  • Office Fax Identifies the user's office fax number.
  • Advanced Features Office Phone Identifies the user's office telephone Advanced number. It is used for providing Caller ID, Features including CTN On-Net Number and PST NETWORK Number.
  • Pager Identifies the user's pager number.
  • Advanced Features Passcode Specifies user passcode for the gateway finder Advanced activation/deactivation user authentication Features from a telephone.
  • PBX Specifies the PBX configuration information Advanced Information which is used by the gateway server, including Features PBX Type, Station to CO Trunk Access Code, Station to Gateway Server Trunk Access Code, Gateway Server to Local Trunk Access Code, Gateway Server to Toll Trunk Access Code, and DISA Access Code.
  • PBX Station Specifies the Station Line interface between Advanced Interface the gateway server and the PBX, including Features Card ID, Card Name, Port Number, For Attendant Yes/No, and Fallback Yes/No.
  • PBX Trunk Specifies the Trunk Line interface between Advanced Interface the gateway server and the PBX, including Features Trunk Card ID, Trunk Type, Trunk Protocol, and Trunk Card Name..
  • PST Specifies the PST NETWORK codes for a Advanced NETWORK gateway server, including E164 Country Code, Features Codes E164 Area Code, International Access Code, and Long Distance Access Code.
  • Desktop CTI Specifies the number of licenses installed Advanced License for users who are authorized to access this Features Count class of service, i.e. provided with access to CTI capabilities from the desktop browser. (This value may be for reference only.)
  • Desktop CTI Specifies the list of users, groups or Advanced License List containers who are authorized this class of Features service, i.e. provided with access to CTI capabilities from the desktop browser.
  • Finder Specifies the acceptance code for answering a Advanced Acceptance redirected call using this class of service.
  • Features Code Finder License Specifies the number of licenses installed Advanced Count for users who are authorized to access this Features class of service, i.e. who may have calls forwarded to alternate telephone numbers. (This value may be for reference only.)
  • Finder Specifies the list of users, groups or Advanced License List containers who are authorized this class of Features service, i.e. who are authorized to have calls forwarded to alternate telephone numbers.
  • Mobile Specifies the number of licenses installed Advanced License for users who are authorized this class of Features Count service, i.e. who may operate a portable computer as a virtual desktop from a remote telephone.
  • Mobile Specifies the list of users, groups, or Advanced License List containers who are authorized this class of Features service, i.e. authorized operate a portable computer as a virtual desktop from a remote telephone.
  • UEP Domain Specifies the gateway network Uniform Advanced Extension Plan domain.
  • UEP Domain Contains a list of all the UEP domains in Advanced List the Corporate Telephony Network.
  • Features User Specifies the user preferences for the gateway Advanced Preferences network, including Screen Pops On/Off, Screen Features Pops Audible On/Off, Screen Pops Size Large/Small, and Number of Call Log Entries.
  • VoIP Specifies the address parameters associated Advanced Address with the VoIP subsystem in the gateway server, Features Parameters including VoIP Internet Address, VoIP Intranet Address, and VoIP Port Number.
  • VoIP Encoding Specifies the VoIP encoding parameters, IP including TxCoder (voice CODEC for Telephony transmitting), RxCoder (voice CODEC for receiving), volume (AGC for VoIP transmission), frame size (in milliseconds), and frames per packet (number of VoIP frames per UDP packet).
  • VoIP Hardware Specifies the hardware that is installed in IP the gateway server, including Card Type, Telephony Card ID, and Card Name.
  • VoIP QOS Specifies the QoS parameters for VoIP, IP Parameters including VoIP QoS Detection (interval for Telephony checking VoIP QoS) and VoIP QoS Threshold (threshold based on which the gateway server triggers fallback to PST NETWORK, including Lost Packets, Packets Out Of Order, and Round Trip Delay).
  • H.323 Zone Identifies a human readable H.323 Zone name IP with which a GatekKeeper is associated. Telephony
  • Table 2 lists object classes which are included in the NDS enterprise directory schema extensions in a preferred embodiment of the invention.
  • Table 2 includes the name of each object class added to the schema, a brief definition of each object class, a list of the attributes listed in Table 1 which, in a preferred embodiment of the invention, may be associated with the respective object classes, and an indication as to whether the object class is added to support the use of the enterprise directory to support IP telephony or to support the advanced features.
  • TABLE 2 New Object Classes Included in theEnterprise Directory Schema Extension Object Schema Extension Class Definition Attributes Supports GateKeeper The GateKeeper class License IP Telephony represents an H.323 WhitePages Subtree and GateKeeper entity.
  • Zone Advanced may be multiple GateKeeper Exchange Features GateKeepers in a gateway Gateway List network.
  • Gateway The Gateway class License IP Telephony represents an H.323 CTN Location ID and Gateway entity.
  • a Gateway CTN Numbers Table Advanced is associated with only one CTN Access Code Features GateKeeper.
  • the Gateway Auto Attendant Prefix object also contains the CTN Trunk Translation routing information for this UEP Domain Gateway.
  • the MCU class represents License IP Telephony an H.323 MCU entity.
  • An GateKeeper MCU is associated with only one GateKeeper.
  • GateKeeper The GateKeeper Exchange License IP Telephony Exchange object contains a list of all Desktop CTI License and GateKeepers in the NDS Count Advanced Tree.
  • the Mobile License Count Distinguished Name of this Mobile License List object is administrator UEP Domain List defined when the very first GateKeeper is installed in the NDS Tree. Subsequently, the Distinguished Name of this object has to be specified when the GateKeepers are installed. UEP Specifies the list of GateKeeper Exchange Advanced Domain Gateways belonging to this Features domain. User The User object represents GateKeeper IP Telephony users of network services Gateway and including the gateway Passcode Advanced network service. Office Phone Features Cellular Phone Pager Home Phone
  • the gatekeeper catalog is an important part of the gateway database 51 . It supports many of the features which are unique in the integrated voice gateway system of the invention, e.g. follow me and white pages.
  • the contents of the gatekeeper catalog tables are described in the following tables.
  • certain of the catalog tables e.g. the Gateway Table (shown in Table 6 below), may be divided into a plurality of smaller tables to facilitate access to the information contained in the tables.
  • Custom Date table contains a list of custom dates for a specific follow Me rule.
  • Table 3 describes the contents of the Custom Date table. TABLE 3 Custom Date Table Attribute Description CustomDateID Unique ID used to identify this record followMeID Link to followMe entry CustomDate A custom date value
  • the follow Me table contains a row for each follow Me rule.
  • a follow Me rule is constructed by joining the Follow Me table with the Follow Me Filter table and the Custom Date table.
  • Table 4 describes the contents of the follow Me table.
  • TABLE 4 Follow Me Table Attribute Description
  • FollowMeID Unique ID used to identify this record DN User this FollowMe rule corresponds to FollowMeType DayOfWeek or Override StartDate Start date for this FollowMe rule EndDate End date for this FollowMe rule StartTime Start time for this FollowMe rule EndTime End time for this FollowMe rule Monday Yes/No field. True (Yes) indicates that this FollowMe rule applies to this day of the week Tuesday Yes/No field.
  • the follow Me Filter table specifies a source filter for a specific Follow Me record.
  • Table 5 describes the contents of the Follow Me Filter table.
  • TABLE 5 Follow Me Filter Table Attribute Description Filter ID Unique ID used to identify this record
  • FollowMeID Connects to the followMe table
  • IncludeItem Indicates whether this item should be included in the source filter or not
  • TaddressType Type of Telephony Address number string Taddress The calling Telephony Address Name User defined string
  • the Gateway table contains a record for each gateway server defined in the gateway network.
  • the directory dredger searches the directory and populates this table.
  • Table 6 describes the contents of the Gateway table.
  • TABLE 6 Gateway Table Attribute Description License License data for a gateway network CTN Location ID Location ID for the gateway network in the Corporate Telephony Network numbering plan
  • CTN Trunk Translation table for converting from Translation the PBX numbering format to CTN canonical format UEP Domain Gateway network Uniform Extension Plan domain.
  • the Frequent Contacts table contains the frequent contacts for each of the users in the User table.
  • Table 7 describes the contents of the Frequent Contacts table.
  • Frequent Contacts Table Attribute Description FrequentContactsID Unique ID used to identify this record DestinationDN The DN that this Frequent Contact refers to FeDN Owner of this Frequent Contact record Description User defined text describing this Frequent Contact entry
  • the Routing table contains supported numbers by gateway server. This table along with the Gateway table is used to build a routing table. Table 8 describes the contents of the Routing table. TABLE 8 Routing Table Attribute Description ID Unique ID used to identify this record DN Associated Gateway distinguished name CTNLocationID CTN number identifying the Gateway RangeType CTN or HopOff FromRange Beginning range of the local segment of the E164 Phone Number or the extension number ToRange Ending range of the local segment of the E164 Phone Number or the extension number From PST Beginning range of the NETWORKRange Corresponding PST NETWORK address for the extension ToPST Ending range of the Corresponding NETWORKRange PST NETWORK address for the extension HopOffAreaCode When range type is ‘HopOff’, the area code of the E164 number HopOffCountryCode When range type is ‘HopOff’, the country code of the E164 number Comment User comment
  • the White Pages contains a record for each user in a specified Zone. It is also possible for this table to contain all users in the gateway network. This table can be used as an enterprise wide white pages. Table 9 describes the contents of the White Pages. TABLE 9 White Pages Attribute Description ID Unique ID used to identify this record DN User distinguished name CN User common name EmployeeNumber User's employee number DepartmentName User's department FirstName First name of user MiddleName Middle initial LastName User last name OfficeExtension User office telephone extension Number number Office PST User office PST NETWORK NETWORK telephone number Number Office Fax User office fax number Number CellularPhoneNumber User cellular telephone number HomePhoneNumber User home telephone number Pager User pager number Title User title EmailAddress User email address PostalAddress User postal address City User city StateOrProvince User state or province PostalCode User zip/post code Country User country Location User location DepartmentID User department GatewayName Gateway corresponding for this user DefaultGatekeeper Default Gatekeeper for this user Passcode Preferences User passcode Preferences User
  • the Private Contacts table contains records of contacts users want to track, but who are not listed in the White Pages.
  • the formats in the fields of the Private Contacts table are identical to those of the fields in the White Pages.
  • a temporary table which contains only the user's frequent contact information. This table is constructed from the White Pages and Private Contacts table. The formats of the fields of the Temporary Contacts table are identical to those of the fields in the White Pages.
  • the numbering plan is the equivalent of addressing for telephone numbers.
  • a company's voice network there are various mechanisms for addressing a call to another party, e.g. a PST NETWORK number and an extension number.
  • Current large PBXs are flexible in their numbering plans, and can support numerous types of dialing methods.
  • Uniform Numbering Plans (UNP) telephones at any of a number of sites may be dialed simply by dialing an extension number.
  • UPN Uniform Numbering Plans
  • Such uniform numbering plans may allow for extensions of different lengths (i.e., number of digits).
  • ETN Enterprise Telephone Number
  • telephones at other sites in the company may be dialed using an access code, commonly an “8”, followed by a location code (typically 3 digits), followed by the extension.
  • PST NETWORK Numbering plan telephones at other sites may be dialed by dialing the public telephone number (per the ITU E.164 specification).
  • a trunk group access numbering plan telephones at a particular remote site may be dialed by dialing an access code for a group of trunks, followed by the extension number.
  • the gateway server facilitates a transparent installation with respect to the enterprise's existing numbering plan.
  • the gateway network permits users to continue dialing according to the same numbering plan they use with the PBX alone.
  • the ARS/Numbering Plan routing and digit manipulation tables are reconfigured to deliver calls to remote locations to the gateway server. Thus, the gateway server does not require that the numbering plan be changed.
  • the gateway servers can support UNP and ETN methods, and can support these methods in multi-vendor environments which include PBXs and/or hybrid/key systems over an IP network.
  • the gateway network classifies telephone numbers as PST NETWORK (E.164), ETN (Location+Extension) and UNP (Extension).
  • the three plans are merged into a single numbering scheme for the enterprise by adding configurable prefixes to the PST NETWORK and ETN numbers.
  • the PST NETWORK prefix typically “9”
  • ETN prefix typically “8”
  • the telephone numbers may undergo pre- and post-processing as they traverse the gateway network depending on the capabilities of the PBXs and the preferences of system administrators. For example, if a caller PBX has the capability, and the system administrator chooses to configure the PBX such that all calls are delivered to the gateway server with the telephone number in the gateway network format, the call can be compared directly against the routing tables for routing to the destination. If a PBX does not have the capability, or if the system administrator chooses not to configure the tables in the PBX, then the caller gateway server can perform incoming digit translation.
  • the preprocessing can be set up to apply the same rules to all trunks, or can apply, e.g. PST NETWORK translation to calls on trunks 1 - 8 , and ETN translation to calls on trunks 9 - 16 .
  • the preprocessed numbers can then be compared against the routing tables for routing to the destination.
  • the gateway server delivers the calls without the need for postprocessing the telephone numbers. If the PBX does not have the capability to receive call with the telephone number in the gateway network format, or if the system administrator chooses not to so configure the PBX, then the called gateway server can perform outgoing digit translation.
  • the called telephone number associated with each call received may be formatted to deliver an extension, and ETN number or a PST NETWORK number, with appropriate prefixes, for the particular PBX.
  • Hybrid/key systems with analog trunks typically have an automated attendant unit which answers calls and prompts the caller to enter an extension to reach a called telephone.
  • This is known as a two stage dialing scheme, and is commonly used in smaller office environments.
  • the gateway server permits the caller to directly dial a called telephone without having to deal with an automated attendant.
  • the caller may start the call either by dialing an ETN number (8+LOCATION+Extension), a UNP number (extension) or place the call from the white pages directory via the browser interface.
  • the called gateway may be configured to deliver the call directly to the called telephone.
  • the gateway server alerts the analog trunk.
  • the gateway server plays the configured prefix string followed by the extension number.
  • the call will then alert directly at the called telephone.
  • the caller will hear normal ringing throughout the process until the called telephone is answered.
  • the net effect is that the invention reduces two-stage dialing into a one-stage addressing method.
  • FIGS. 447 and 50- 58 illustrate the configuration of the gateway networks and the components which support the functions described.
  • the telephone network software and hardware (FIG. 3) will be represented by the respective software drivers (e.g., analog driver 67 representing the trunk 66 , analog driver 67 and analog trunk hardware 68 ).
  • a telephone which is coupled to a PBX in a company's gateway network will be referred to as a gateway telephone
  • a telephone which is outside the company and is coupled to the PST NETWORK will be referred to as a PST NETWORK telephone
  • the gateway network and its components at the calling party's end will generally be referred to as the “caller” components, e.g. “caller gateway server”.
  • the gateway network and its components at the called party's end will generally be referred to as the “called” components, e.g. “called gateway server”.
  • FIGS. 4 - 47 and 50 - 58 in general components comprising the gateway network at the caller end of a telephone call are identified by their respective reference numerals shown in FIGS. 2 - 3 (e.g. caller gateway server 26 ) and components comprising the gateway network at the called end of a telephone call will have as their reference numerals 100 plus the respective reference numeral of the corresponding component of gateway network at the caller end (e.g. called gateway server 126 ).
  • Additional components outside both the caller gateway network and the called gateway network will have as their reference numerals 200 , 300 , 400 , etc., plus the respective reference numeral of the corresponding component of gateway network at the caller end (e.g. PST NETWORK telephone 238 ).
  • the interface between the PBX and the gateway server may be illustrated as an analog trunk interface and the telephone drivers in the gateway servers may be illustrated as analog drivers.
  • the interface between the PBX and the gateway server may include analog trunk, DS-1 (T1/E1, PRI, QSIG) and/or analog station lines, with each interface supported by a corresponding telephone driver. Therefore, the illustration of the interface between the PBX and the gateway server as an analog trunk and the telephone drivers in the gateway as analog drivers is by way of illustration, and in no way limits the respective described operations to the particular interface illustrated in the examples.
  • FIGS. depicting methods or scenarios in which a call hops-on to or hops-off from a gateway network
  • a third telephone company central office will be identified as CO 3 13 .
  • the integrated computer telephone system of the invention provides the capability to place a telephone call from a caller gateway telephone to a called gateway telephone via the PST NETWORK.
  • a caller (not illustrated) initiates a call by picking up the handset on the caller telephone 38 and dialing an ARS code, e.g. 9, plus a PST NETWORK telephone number or other digit string.
  • the caller PBX 34 reviews the dialed number against the information in the ARS tables to select a trunk group. It may then modify the digit string, deleting and inserting digits for proper addressing.
  • the caller PBX 34 delivers the call to CO 1 12 .
  • CO 1 12 routes the telephone call through the PST NETWORK 16 to CO 2 14 .
  • CO 2 14 delivers the call to the called PBX 134 via an available trunk and may transmit a subset of the called telephone number.
  • the called telephone 138 rings and is answered by the called party (not illustrated).
  • the gateway network provides the capability to place a telephone call from a caller gateway telephone to a called gateway telephone via an IP network. This is referred to herein as a VoIP call. It is also referred to as “Inter-PBX Toll Bypass,” because, as the term indicates, a long distance toll between remote PBXs is avoided by using the IP network.
  • a caller (not illustrated) initiates a call by picking up the handset on the caller telephone 38 and dialing an ARS code, e.g. “9” for an off-net call or “8” for an on-net call, plus a PST NETWORK telephone number or other digit string.
  • the caller PBX 34 reviews the digital number against the information in the ARS tables and selects a trunk group 35 coupled to the caller gateway server 26 .
  • the caller PBX 34 may modify the dialed digit string, deleting and inserting digits for proper addressing on a trunk in that group.
  • the caller gateway analog driver 67 receives the call.
  • the caller gateway server 26 performs internal operations to determine the IP address of the called gateway server 126 .
  • the gateway engine 50 requests the gatekeeper agent 52 to get an address.
  • the gatekeeper agent 52 places an H.323 compliant request to the gateway gatekeeper 53 .
  • the gateway gatekeeper 53 references tables in the gateway database 51 to determine the called gateway server 126 and its address.
  • the caller gateway VoIP driver 62 transmits packets addressed to the IP address of the called gateway server 126 via the IP network 18 .
  • the caller gateway server 26 and called gateway server 126 communicate via the IP network 18 to initiate a duplex H.323 call.
  • the called gateway server 126 selects a telephone trunk 135 to deliver the call to the called PBX 134 .
  • the called gateway server 126 initiates the call, including the called telephone number, to the called PBX 134 .
  • the called PBX 134 interprets the received telephone number to select a called telephone 138 to ring.
  • the called telephone 138 rings and when answered by the called party (not illustrated) the connection is made.
  • the connection event may propagate through the system.
  • the gateway network provides the capability to place a telephone call to an outside-of-the-company PST NETWORK destination via the IP network.
  • a user in the company can call a long distance PST NETWORK destination by dialing the telephone number as usual.
  • the caller gateway network will set up the call to be carried via the IP network to a called gateway server within the company which is closest to the destination telephone, and make a PST NETWORK connection to “hop-off” to the PST NETWORK destination.
  • the system administrator for each gateway network determines which local hop-off destinations the gateway network will support and configures the gateway server accordingly.
  • the system administrator also configures the gateway server to identify those gateway servers from which the local gateway server will accept hop-off calls.
  • the gateway servers can be configured to support hop-off to local PST NETWORK calls and hop-off to long distance PST NETWORK calls.
  • the ARS table of the PBX in the originating gateway network is configured accordingly for the hop-off calls to be routed to the gateway server.
  • hop-off to PST NETWORK there are several different methods in which hop-off to PST NETWORK may be implemented.
  • the different methods take into consideration variations in the configurations of gateway networks at different installations, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity.
  • Table 10 identifies differences in the configuration for three hop-off to PST NETWORK methods in preferred embodiments of the invention. TABLE 10 Hop-off to PST NETWORK Methods Analog T1 trunk station channels per ports per hop-off hop-off CTI call (at call (at PBX Method Transparent support destination) destination) support A Transparent No 0 1 None B Transparent No 1 1 (only Trunk to during trunk setup) transfer C Transparent No 1 0 Trunk to trunk call
  • FIGS. 6 - 14 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective hop-off to PST NETWORK methods. Connections between the components are not shown in order to simplify the FIGS.
  • the set up of the hop-off and the resulting PST NETWORK call are depicted by a heavy solid line.
  • An arrow head on a solid line indicates the direction of data flow or call flow, as appropriate.
  • a solid line without an arrow head indicates the data or call flows in both directions.
  • One analog station port is used at the destination end of the call during hop-off to PST NETWORK and for the remainder of the call. No T1 trunk channels are required for the hop-off.
  • Method “A” does not use CTI support.
  • Hop-off to PST method “A” will be described with reference to FIGS. 6 - 7 . All steps described below are at the called gateway network 104 .
  • the analog station driver 174 in the called gateway server 126 places a call from an analog station 175 ( 75 in FIG. 3) to the hop-off destination called PST NETWORK telephone 238 .
  • the called gateway server 126 then connects the TDM bus 84 (FIG. 3) time slot of the new PST NETWORK call with that of the incoming VoIP call, completing the hop-off to PST NETWORK call.
  • One analog station port is used at the destination end of the call only during setup of the hop-off to PST NETWORK.
  • One T1 trunk channel is used during setup of the hop-off and for the remainder of the call.
  • the PBX includes trunk-to-trunk transfer capability. Method “B” does not use CTI support.
  • Hop-off to PST NETWORK method “B” will be described with reference to FIGS. 8 - 12 .
  • the called gateway server 126 upon receiving a call from the caller gateway server 26 , the called gateway server 126 makes a call from an analog station 174 in the called gateway server 126 to a T1 trunk 137 in the called gateway network 104 by dialing a specified “hop-off to gateway trunk” telephone number.
  • the called gateway server 126 answers the call at the gateway trunk 137 and recognizes the call as a hop-off to PST NETWORK call.
  • the called gateway server 126 makes a hook-flash transfer to the hop-off destination telephone 238 number.
  • the called gateway server 126 hangs up the analog station 133 .
  • the called gateway server 126 connects the TDM bus 84 (FIG. 3) time slot of the new hop-off call with the time slot of the incoming VoIP call.
  • One T1 trunk channel is used during setup of the hop-off and for the remainder of the call. No analog ports are used.
  • the PBX includes trunk to trunk call, i.e. tie trunk to CO trunk, capability. Method “C” does not use CTI support.
  • Hop-off to PST NETWORK method “C” will be described with reference to FIG. 13- 14 .
  • the called gateway server 126 upon receiving a call from the caller gateway server 26 , the called gateway server 126 makes a call from a T1-tie-trunk channel to the called, i.e. hop-off, PST NETWORK number.
  • the called gateway server 126 connects the TDM bus 84 time slot of the new hop-off call with the time slot of the incoming VoIP call.
  • the gateway network provides the capability to place a telephone call from a PST NETWORK telephone to a telephone on a distant gateway network via a VoIP call.
  • This capability can be combined with the hop-off to PST NETWORK capability, described above, to enable a user to place a long distance call from a caller PST NETWORK telephone to a called PST NETWORK telephone by placing a local call to a local gateway network.
  • the telephone call is then carried via a VoIP call between two gateway networks.
  • the destination gateway network for the VoIP call may be a remote gateway network or the local gateway which receives the call from the PST NETWORK telephone.
  • the invention provides an access mechanism to the company's telephone system whereby a user must be identified and pass through a passcode security scheme. Calls placed by the user are identified by that user's caller ID (for all calls, local and remote). This feature allows companies to choose to employ hop-on whereby a toll free access number may be given to employees so that they may call into the company, and hop-off, and the billing for the call will be linked to the company's PBX rather than the user's calling card.
  • Table 11 identifies scenarios of hop-on to VoIP calls in preferred embodiments of the invention. TABLE 11 Hop-on to VoIP Scenarios Called Called Scenario Telephone Gateway A Gateway Remote B PST NETWORK Remote (hop-off) C Gateway Local D PST NETWORK Local (hop-off)
  • FIGS. 15 - 18 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective scenarios of hop-on to VoIP. Connections between the components are not shown in order to simplify the FIGS. All four hop-on to VoIP scenarios are initiated with a common set of steps. The steps common to all four hop-on to VoIP scenarios will be described with respect to FIG. 15.
  • a caller (not illustrated) at a PST NETWORK telephone 238 lifts the handset and dials a “Remote Access” telephone number for the local caller gateway network 4 .
  • the call is received at CO 1 12 which alerts the caller PBX 34 with the call.
  • the caller PBX 34 routes the call to the caller gateway server 26 .
  • the caller gateway server 26 answers the call and interacts with the caller via interactive voice response (IVR). Using dual tone multi-frequency (DTMF) touch tones, the caller responds to voice prompts which may include the caller's ID, password, etc.
  • the caller gateway server 26 then authenticates the caller against information in the gateway database image of the NDS directory information.
  • the caller gateway server 26 If the caller gateway server 26 is able to authenticate the caller, the caller gateway server 26 then provides the caller with a dial tone. The caller then dials the telephone number of the desired called telephone. Based on the dialed telephone number, the caller gateway server selects a destination.
  • the called telephone is a gateway telephone in a remote gateway network.
  • Scenario “A” will be described with reference to FIG. 16. The remaining steps are the same as the corresponding steps for a basic VoIP call described above.
  • the caller gateway server 26 selects the called gateway server 126 .
  • the caller gateway VoIP driver 62 transmits packets addressed to the IP address of the called gateway network 126 via the IP network 18 .
  • the caller gateway server 26 and called gateway server 126 communicate via the IP network 18 to establish a duplex H.323 call.
  • the called gateway server 126 selects a telephone trunk 135 to deliver the call to the called PBX 134 .
  • the called gateway server 126 transmits the called telephone number to the called PBX 134 .
  • the called PBX 134 interprets the received telephone number to select a called telephone 138 to ring.
  • the called telephone 138 rings and is answered by the called party (not illustrated).
  • the called telephone is a PST NETWORK telephone located near a remote gateway network.
  • the caller gateway server 26 searches the caller gateway routing table to select a destination gateway network, and selects the called gateway network 126 .
  • the remainder of the call setup may employ any one of the three hop-off to PST NETWORK scenarios described above.
  • the called telephone is a gateway telephone coupled to the caller gateway network 4 .
  • Scenario “C” will be described with reference to FIG. 17.
  • the caller gateway server 26 (which is also the called gateway server) selects a telephone trunk 135 to deliver the call to the caller PBX 34 and transmits the called telephone number to the caller PBX 34 .
  • the caller gateway server 26 couples the inbound caller's trunk 35 with the trunk 135 for the called telephone 338 .
  • the caller PBX 34 interprets the telephone number to select a telephone to ring.
  • the called telephone 338 rings and is answered by the called user (not illustrated).
  • the called telephone is a PST NETWORK telephone located near the caller gateway network 4 .
  • Scenario “D” will be described with respect to FIG. 18.
  • the caller gateway server 26 (which is also the called gateway server) selects a telephone trunk 135 to deliver the call to the caller PBX 34 and transmits the called telephone number to the caller PBX 34 .
  • the caller gateway server 26 couples the inbound caller's trunk 35 with the trunk 135 for the called telephone 438 .
  • the caller PBX 34 interprets the telephone number and determines that the call is for a local PST NETWORK telephone.
  • the caller PBX 34 selects an external trunk coupled to CO 1 12 and dials the destination telephone number. CO 1 12 routes the call to the called telephone 438 .
  • the called telephone 438 rings and is answered by the called user (not illustrated).
  • the gateway server constantly monitors the quality of service (QoS) during VoIP network calls using the standard realtime transport control protocol (RTCP).
  • QoS quality of service
  • RTCP realtime transport control protocol
  • the QoS may be specified in terms of end-to-end delay, IP packet loss and jitter. If the QoS falls below a predetermined level set by a system administrator, the gateway server sets up an alternate connection over the PST NETWORK and switches the call to the PST NETWORK connection.
  • the caller can also initiate a fallback to PST NETWORK if the caller decides that the quality of the voice transmission has deteriorated to an unacceptable level.
  • the caller can initiate a fallback to PST NETWORK by entering a specified DTMF key sequence on the telephone, e.g. a combination of the “star” (*) and “pound sign” (#) keys.
  • a system administrator can configure a gateway server to allow or disallow caller-initiated fallback to PST NETWORK.
  • the different methods take into consideration variations in the configurations of gateway networks at different installations, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity.
  • some of the methods allow fallback to PST NETWORK to be transparent to the user, while other methods do not provide transparent fallback to PST NETWORK.
  • transparent fallback to PST NETWORK the users will simply perceive that the quality of voice suddenly improves.
  • non-transparent fallback to PST NETWORK the conversation will be interrupted by the gateway server while the fallback to PST NETWORK takes place.
  • Table 12 identifies differences in the configuration for methods of fallback to PST NETWORK in preferred embodiments of the invention.
  • T1 Analog Trunk station channels ports per per fallback fallback call (at call (at each each CTI end of end of Method Transparent support call) call)
  • PBX support A Transparent No 1 1 Hunt group for gateway network analog lines
  • Hunt group for gateway network analog lines C Transparent No 2 0 Trunk to trunk call
  • E Non- Yes 0 1 (only Hunt group Transparent during for gateway setup) network analog lines (in addition to CTI)
  • FIGS. 19 - 43 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective methods of fallback to PST NETWORK. Connections between the components are not shown in order to simplify the FIGS.
  • An ongoing VoIP telephone call is represented by a heavy dashed line.
  • the set up of the fallback and the resulting PST NETWORK call are depicted by a heavy solid line.
  • Arrow heads at one end of a dashed line or solid line indicate the direction of data flow or call flow.
  • a dashed line or solid line without an arrow head indicates the call or data flows in both directions.
  • One T1 channel and one analog station port are used at each end of the call during fallback to PST NETWORK and for the remainder of the call.
  • the PBX includes a hunt group for the gateway network analog stations. Method “A” does not use CTI support.
  • the call initiation, and subsequent signaling is routed from the caller station analog driver 74 through the caller PBX 34 , the PST NETWORK 16 (including the respective CO's 12 , 14 ), and the called PBX 134 to the called station analog driver 174 in the called gateway server 126 .
  • the called gateway server 126 sends a “fallback ready” DTMF tone back to the caller gateway server 26 .
  • the DTMF tone is routed from the called gateway server 126 through the called PBX 134 , the PST NETWORK 16 and the caller PBX 34 to the called gateway server 26 .
  • the caller gateway server 26 when the caller gateway server 26 receives the fallback ready DTMF tone, the caller gateway server 26 sends the original called telephone number to the called gateway server 126 , and then waits for a short period, e.g. 200 milliseconds (msec), to allow the called gateway server 126 to receive the telephone number.
  • a short period e.g. 200 milliseconds (msec)
  • the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 (FIG. 3) time-slots of the new PST NETWORK call with that of the respective T1 channels of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16 .
  • the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • Two T1 channels are used at each end of the call during fallback to PST NETWORK and for the remainder of the call.
  • One analog station port is used at each end only during fallback to PST NETWORK.
  • the PBX includes trunk to trunk transfer capability, including both CO trunk to tie trunk and CO trunk to CO trunk. Method “B” does not use CTI support.
  • the call initiation, and subsequent signaling is routed from the caller station analog driver 74 in the caller gateway server 26 through the caller PBX 34 , the PST NETWORK 16 (including the respective CO's 12 , 14 ), and the called PBX 134 to the called station analog driver 174 in the called gateway server 126 .
  • the called gateway server 126 sends a “fallback confirm” DTMF tone back to the caller gateway server 26 .
  • the DTMF tone is routed from the caller gateway server 126 through the called PBX 134 , the PST NETWORK 16 and the caller PBX 34 to the called gateway server 26 .
  • both the caller gateway server 26 and the called gateway server 126 place a hook-flash transfer to the respective caller gateway network trunk 35 and called gateway network trunk 135 , respectively, by dialing a “fallback to gateway network trunk” number.
  • both the caller gateway server 26 and called gateway server 126 answer the call at the respective gateway network trunks 67 , 167 and recognize the call as a fallback call.
  • both the caller gateway server 26 and called gateway server 126 then hang up the respective analog stations 74 , 174 .
  • the called gateway server 126 sends a “fallback ready” DTMF tone to a new trunk channel for the PST NETWORK call, and then waits for a short period, e.g. 200 msec, to allow the caller gateway server 26 to receive the DTMF tone.
  • the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 (FIG. 3) time-slot of the new trunk 35 channel with that of the T1 channel of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16 .
  • the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • Fallback to PST NETWORK method “C”, listed in Table 11, implements a transparent fallback to PST NETWORK.
  • Two T1 channels are used at each end of the call during fallback to PST NETWORK and for the remainder of the call. No analog station ports are used.
  • the PBX uses trunk to trunk call capability, i.e. tie trunk to CO trunk on the caller gateway server side, and CO trunk to tie trunk on the called gateway server side.
  • the PBX is configured to enable a trunk to trunk call.
  • Fallback to PST NETWORK method “C” will be described with reference to FIGS. 30 to 33 .
  • an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134 , the caller gateway server 26 and the called gateway server 126 , through the IP network 18 .
  • the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a call from a tie trunk channel to the tie trunk channel of the called gateway server 126 . The call is initiated by dialing a specified telephone number.
  • This step may be a multi-step process, and the implementation may be PBX specific.
  • the caller gateway server 26 waits to receive a “fallback ready” DTMF tone.
  • the called gateway server 126 sends the “fallback ready” DTMF tone to the caller gateway server 26 .
  • the caller gateway server 26 sends the original called telephone number to the called gateway server 126 , and then waits for a short period, e.g. 200 msec.
  • the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 time-slot of the new trunk channel with that of the T1 channel of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16 .
  • the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • Fallback to PST NETWORK method “D”, listed in Table 11, implements a non-transparent fallback to PST NETWORK. No T1 channels are used for the PST NETWORK call after the fallback process. No analog station ports are used.
  • the PBX uses CTI.
  • the gateway servers exchange proprietary messages among themselves using IP sessions which are separate from those used for the voice call.
  • Fallback to PST NETWORK method “D” may be used if the IP connection between the caller gateway server and called gateway server is still good enough to support transmission of data messages. If the IP connection is not adequate for the caller gateway server and called gateway server to exchange data messages, the respective gateway servers may fallback to a PST NETWORK call using method “E” which will be described below.
  • Fallback to PST NETWORK method “D” will be described with reference to FIGS. 34 to 38 .
  • an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134 , the caller gateway server 26 and the called gateway server 126 , through the IP network 18 .
  • the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a “fallback request” message over the IP network 18 .
  • the “fallback request” message contains the caller and called telephone numbers.
  • the caller gateway server waits to receive a “fallback ready” message.
  • the called gateway server 126 after receiving the “fallback request” from the caller gateway server 26 , the called gateway server 126 sends a “fallback ready” message to the caller gateway server 26 over the IP network 18 .
  • the caller gateway server 26 manages the TDM bus 84 time slots to announce the fallback to both the caller and called parties.
  • the caller gateway server 26 uses the CTI link to place the current VoIP call on hold.
  • the caller gateway server 26 uses the CTI link to make a PST NETWORK call from the caller telephone 38 to the called telephone 138 .
  • the called gateway server 126 detects the incoming call and uses the CTI link to place the VoIP call on hold and to pick up the PST NETWORK call.
  • the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • the called gateway server 126 sends a “fallback confirm” DTMF tone to the caller gateway server 26 .
  • the caller gateway server 26 sends the caller and called telephone numbers to the called gateway server 126 .
  • both the caller gateway server 26 and the called gateway server 126 manage the TDM bus 84 time slots to announce the fallback to PST NETWORK to the caller and called parties, respectively.
  • the caller gateway server 26 and called gateway server 126 use CTI to put the current VoIP call on hold (FIG. 42); then to put the new PST NETWORK call on hold (FIG.
  • the caller gateway server 26 and called gateway server 126 then hang up on the respective analog stations, and disconnect the original VoIP call.
  • the gateway server provides the capability to fallback to the PST NETWORK during setup of a call if the call cannot be connected through the called gateway server.
  • Fallback to PST NETWORK during call setup may employ any of the five methods described above for fallback to PST NETWORK during a call. The method employed will depend on the configuration of the particular caller gateway network, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity. However, in each of the five methods described above, fallback to PST NETWORK during call setup does not include the steps which keep the VoIP call connected until the PST NETWORK call is completed, since there is no current VoIP call to maintain.
  • the fallback to PST NETWORK during call setup capability provided by the gateway server of the invention is an improvement over current systems.
  • the caller gateway will “busy out” all of its trunks, or at least a group of trunks allocated to the remote destination.
  • the gateway server avoids this problem by simply setting up the call to be routed back through the PBX.
  • the gateway network of the invention there is no need for the caller gateway to busy itself out merely because the caller gateway found a remote called gateway to be inaccessible.
  • the gateway server supports redirection of an incoming call from a first PBX, and its associated gateway server, to a second PBX, and its associated gateway server, as a result of a call forward (including call transfer, or follow-me). If both the call before (the initial call) and the call after (the final call) a call forward are VoIP calls, the final call can take a direct path between the caller gateway server and called (transfer) gateway server. This “path replacement” feature eliminates unnecessary loops after a call forward.
  • VoIP is sensitive to tandem compression, i.e., when a call is converted to and from a VoIP call twice in series during the call's transmission. Tandem compression results in a substantial drop in voice quality, often to unacceptable quality levels.
  • the gateway server of the invention provides a path replacement feature which substantially improves the quality of voice transmission in a call forwarded call, and improves the utilization of gateway network resources. The quality of voice is substantially improved, because path replacement eliminates the tandem VoIP calls after a call forward. The utilization of gateway network resources is substantially improved because an unnecessary loop is avoided. After a call forward, there are two PBX's and their respective gateway servers involved in the call instead of three PBX's and gateway servers.
  • Path replacement is best described with an example: A call from Boston to Los Angeles is transferred by the Los Angeles party to a New York destination. In current systems, there would be two calls coupled in the Los Angeles PBX, i.e. a call between Boston and Los Angeles and a call between New York and Los Angeles. With IP telephony, this would result in an unacceptable tandem compression arrangement.
  • the gateway server recognizes that a direct and shorter path exists, namely direct communication between Boston and New York gateway networks. The gateway server replaces the routing path to place one call following the direct and shorter path, and with a single compression path. In implementing a path replacement, the gateway servers exchange messages to communicate with each other. The gateway servers use CTI to set up a path replacement.
  • a gateway network user can transfer an incoming call to another gateway network telephone. If an incoming call is a VoIP call, and if the call is transferred to a remote gateway user via VoIP, the gateway server will implement path replacement to eliminate the intermediate PBX loop back. As a result, there will be one direct VoIP link in the transferred call.
  • the original call is placed from the caller telephone at the caller gateway network to the called telephone at the called gateway network, and is then transferred to the transfer telephone at the transfer gateway network.
  • the call transfer may be either unsupervised or supervised, and may be initiated by the called user from a web browser CTI application or from the telephone.
  • the called user clicks an “unsupervised transfer” button displayed on a browser menu.
  • the called gateway server receives the unsupervised call transfer request, and sends a call transfer message to the caller gateway server.
  • the caller gateway server receives the call transfer request message and sets up a VoIP call to the transfer telephone at the transfer gateway network. The caller gateway server then disconnects the original call to the called telephone.
  • the called gateway server receives the supervised call transfer request, uses CTI to place the call on hold, and places a call from the called gateway server to the transfer telephone at the transfer gateway server. After the call to the transfer telephone is connected, the called user clicks a “transfer” menu entry to complete the supervised call transfer.
  • the called gateway server receives the transfer request and sends a call transfer message to the caller gateway server.
  • the caller gateway server sets up a VoIP call to the transfer telephone.
  • the caller gateway server and transfer gateway server manage the TDM bus time slots to connect the caller telephone and transfer telephone via the new direct VoIP call.
  • the caller gateway server and transfer gateway server disconnect the original call from the called gateway server.
  • the called user may initiate a call transfer, with path replacement, using the DTMF buttons on the telephone.
  • the called user initiates the call transfer by entering a transfer code or pressing a transfer button on the telephone, depending on the PBX configuration, and then dials the transfer telephone number.
  • the called PBX places the current call on hold and sends the call to the called gateway server.
  • the called gateway server receives the call from the PBX and initiates the VoIP call to the transfer telephone.
  • the called user enters a supervised or unsupervised transfer DTMF sequence, again PBX dependent.
  • the called gateway server receives a transferred CTI event and sends a call transfer message to the caller gateway server.
  • the caller gateway server receives the transfer message and sets up a VoIP call to the transfer telephone.
  • the caller gateway server manages the TDM bus time slots to connect the caller telephone to the new VoIP call to the transfer telephone.
  • the caller gateway server then disconnects the original call to the called telephone.
  • the gateway network users can set up a call forward, with path replacement, from a web browser CTI application or from the telephone.
  • call forward is a PBX feature, and the operation can be carried out by the PBX alone without the gateway server's involvement.
  • the gateway server will provide call forward with path replacement so that the intermediate PBX loop back is eliminated. As a result, there will be just one direct VoIP link in the forwarded call.
  • the called gateway server Upon receiving an H.323 call setup message, the called gateway server checks to determine if the called user has call forward set up. The called gateway server uses CTI to send an inquiry to the PBX. If the user has call forward set up, and if the call forward destination is at a remote gateway network PBX, the called gateway server sends a “gateway call reroute” message back to the caller gateway server. Upon receiving the call reroute message, the caller gateway server sets up the original call to the transfer gateway server and transfer telephone.
  • the gateway server allows users to redirect incoming telephone calls to any telephone, cellular phone, pager, etc., at other locations, e.g. conference room, home, etc. Users may also set up filters so that only calls from selected caller(s) are redirected.
  • the gateway server can implement the follow me capability with path replacement.
  • the called gateway server Upon receiving an H.323 call setup message, the called gateway server checks the gateway database to determine if the user has follow me set up. If the called user has follow me set up, and if the destination is at a remote gateway server or other H.323 telephone, the called gateway server sends a “gateway call reroute” message back to the caller gateway server. The caller gateway server sets up the original call directly to the remote gateway server or H.323 telephone.
  • the follow me feature of the integrated voice gateway system of the invention is described below.
  • the gateway server supports real-time fax transmission over the IP network (FoIP).
  • the caller gateway server forwards the fax signals from the caller fax machine immediately across the IP network to the called gateway server.
  • the called gateway server sends the signals to the called fax machine.
  • the caller gateway server sends signals from the called fax machine back to the caller gateway server via the IP network.
  • the caller gateway server send the signals to the caller fax machine.
  • Real-time fax transmission over the IP network is provided the same immediacy of delivery that users are used to with fax transmission over the PST NETWORK.
  • the integrated voice gateway system of the invention supports the routing of a fax call from a stand-alone fax machine (or fax server) over the IP network.
  • This feature is basically the same as “Inter-PBX Toll Bypass for Real-Time Voice”, i.e. the basic VoIP call described above with reference to FIG. 5.
  • the gateway engine 50 (FIG. 3) provides automatic fax detection. Fax calls can be routed to a gateway server automatically by the configuration of the PBX ARS table in the same manner as is done for voice calls.
  • a PBX trunk coupled to a gateway server can be dynamically shared between voice and fax calls.
  • This feature can be provided independent of Inter-PBX Toll Bypass for voice calls. If a company decides that the quality of voice over IP is not acceptable for its purposes, the integrated voice gateway system of the invention can still provide for FoIP. In this case, the PBX stations for the fax machines are assigned a special “Class of Service”, and calls originating from these stations are routed by the caller PBX to the caller gateway server.
  • the gateway server can also be configured so that VoIP calls are routed via the company's intranet, and fax calls are routed via the Internet to take advantage of free bandwidth on the Internet.
  • the integrated voice gateway system of the invention supports a fax call from within the company to an outside PST NETWORK fax machine via the IP network and the PST NETWORK.
  • a user in the company can send a fax to an outside fax machine.
  • the fax call is carried via the IP network to the gateway server which is the closest to the called fax machine, and from there a PST NETWORK connection is made from the called gateway server to the called fax machine.
  • hop-off destinations are determined by the system administrator of the 10 destination gateway servers. Both hop-off via local PST NETWORK call and hop-off via long distance PST NETWORK call are supported.
  • the ARS table (or routing table by other names) of the originating PBX needs to be configured accordingly for the hop-off calls to be routed to the gateway server.
  • the integrated voice gateway system of the invention supports the use of laser printers as fax machines.
  • a pseudo fax number can be defined for a printer by the administrator. Once a printer is assigned a pseudo fax number, the printer can receive faxes sent to that pseudo number just like a fax machine.
  • the fax gateway 54 (FIG. 3) in the called gateway server 126 converts the received fax into a printable form before sending the received fax to the print queue. This feature allows the simultaneous transmission and receipt of faxes between company sites without busy signals. It also supports the use of plain paper for printing faxes.
  • the integrated voice gateway system of the invention supports the multi-cast of a fax to a group of recipients.
  • a pseudo fax number representing a group of recipients i.e. fax distribution list
  • a fax sent to a “pseudo fax number” which represents a group is multi-casted to all recipients in the group.
  • Fax multi-cast saves users'time, and reduces the traffic load in the company's network.
  • the caller gateway server sends only one copy of the fax to the called gateway server.
  • the called gateway server then fans out the fax to each of the recipients.
  • the invention provides the user with desktop CTI capabilities.
  • the user may dial, answer, hang-up, transfer, conference, forward, place a call on hold, unhold, and drop a call from the desktop workstation.
  • the user can dial touch tone digits, e.g. in response to IVR commands.
  • the user can also set the DND indicator for all calls or selected calls, and manage multiple call appearances, e.g. select one call to answer and select another call to go to voicemail.
  • the white pages and the individual frequent contact lists from the enterprise directory are available for the user to select destinations for dialing, transfers and conferencing.
  • the call log is also available at the desktop workstation.
  • the PC call control interface is delivered as a Java applet through the web browser.
  • FIG. 47 illustrates a current system in which a CTI server 502 and a workstation 503 are coupled via a LAN 501 .
  • the CTI_APP 504 and CTI.dII 505 are both installed in the workstation 503 .
  • the integrated voice gateway system of the invention as illustrated in FIG. 48, there is no need to install applications, dIIs, and the like in all the users'workstations.
  • the CTI server 97 , gateway server 26 , web server 92 and workstation 24 are all coupled via the company's LAN 22 .
  • the user client 95 is a commercially available web browser-based GUI application. There is no need to install special applications, dIIs, or the like, as all PC call control capabilities are provided via the web browser user client 95 .
  • Screen pops are windows and dialog boxes which, for example, identify the calling and called parties, and provide other information to the user as is described below.
  • the integrated voice gateway system of the invention provides a virtual desktop which allows a computer browser and a telephone at a location other than a user's regular office, e.g. an “alternate office” or a “virtual office”, to be logically associated with the user.
  • an alternate office may be another office within the company, and a virtual office may be at a location off the company's premises.
  • An alternate office within the company is any location that has access to both a gateway telephone, and a desktop workstation having a browser, the workstation coupled to the company's data network.
  • the integrated voice gateway system of the invention supports a user working in an alternate office by providing the user the capability to: redirect desired inbound calls to the telephone in the alternate office, and receive caller ID screen pops on the desktop workstation identifying that the call is for that user; place calls from the telephone in the alternate office and have the user's own caller ID sent to the call's destination; and, have access to the full set of browser based desktop call control (e.g., white pages, transfer) that are available at the user's regular desk.
  • the user first logs in at the remote workstation 524 via the user client 595 browser interface in the alternate office.
  • the login information includes the telephone number of the remote telephone 538 .
  • the gateway engine 550 in the remote gateway server 526 causes the information to be stored in the gateway database 551 in the remote gateway server 526 and to be sent to the user's primary gateway server 26 to be stored in the gateway database 51 in the primary gateway server 26 .
  • the information stored in the gateway database 51 in the primary gateway server may include a filter set up by the user to limit the users whose calls are forwarded to the alternate office. Operation of the follow me feature of the integrated voice gateway system of the invention is described below.
  • the class of service is a set of user attributes which indicate the capabilities that are available to a user.
  • the attributes include both licensing levels and feature activation.
  • the class of service attributes are referenced at different points during operation of the gateway server, and include, for example, when a user logs in—to determine which client to deliver via the web browse; at an originating gateway server—to determine which features are available to a user; and to be transported with a call to a called gateway server—so that feature access may also be addressed at the destination.
  • the class of service available to a user follows the user when the user logs in at an alternate office.
  • the integrated voice gateway system of the invention couples the PBX's in an enterprise in one single Virtual PBX (VPBX).
  • VPBX Virtual PBX
  • This set of VPBX features is an important set of features which set has not previously been available in IP telephony systems.
  • the gateway server relies on the CTI connection to the PBX to provide most of the VPBX features.
  • the integration of the gateway server with the enterprise directory services systems enables the gateway server to provide the full range of VPBX features described herein.
  • the gateway server can also obtain much of the information needed to provide VPBX features via PRI and QSIG interfaces.
  • Table 13 shows the VPBX features which can be supported depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having a QSIG interface with no CTI link, all the features can be provided except for dynamic caller ID for calls which originate from the PST NETWORK or if the caller and called telephones are both coupled to the same PBX.
  • the remaining configurations not having a CTI link between the PBX and the gateway server do not support path replacement, callback on busy or call alert, and only a configuration having a PRI CO trunk or T1/E1 in-band signaling, without a CTI link, can support dynamic caller ID for calls placed from a caller telephone to a called telephone with both telephones “on net”.
  • VPBX Feature Support No CTI and PRI CTI and CO Trunk T1/E1 or T1/E1 No CTI Tie-Trunk with and T1/E1 or In-Band Tie Trunk Analog CO No CTI ANI or Analog Trunk and QSIG Signaling CO Trunk Toll Bypass X X X X X Hop-Off to PST X X X X NETWORK Hop-On from X X X X PST NETWORK Fallback to PST X X X X NETWORK Fail-Safe X X X Operation Path X — — Replacement Dynamic Caller X X X — ID (on net calls) Dynamic Caller X ID (off-net calls, i.e. PST NETWORK and intra-PBX calls) Callback on X X — — Busy Call Alert on X X — — Busy
  • Table 14 shows the features for forwarding calls to alternate telephone numbers which can be supported from a user client depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having a QSIG interface with no CTI link, all the features can be provided except for follow-me for calls which originate off-net. The remaining configurations, not having a CTI link between the PBX and the gateway server also do not support filtered follow-me for on-net or off-net calls.
  • Table 15 shows advanced features which can be supported from a user client depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having no CTI link available, only the enterprisee and personal directories are supported, and the call log for on-net calls.
  • a screen-pop to a user's desktop workstation is a useful interface for most of the VPBX features. Screen-pops may be accompanied by audible sounds and alerts to provide additional emphasis or information to the user. If the user does not have a desktop workstation, or if the user does not log into the gateway server, then the gateway server may provide IVR as the user interface for the VPBX features.
  • VPBX features provided by the integrated voice gateway system of the invention may include: Dynamic Caller ID, Call Log, Callback on Busy, Call Alert, Call Alert via Must Answer Station, follow Me, and Virtual Desktop, each of which will be described below.
  • the invention also supports conventional PBX features, e.g. Ring Through, etc.
  • the integrated voice gateway system of the invention provides the capability to display the caller ID to the called party by a screen-pop on the desktop workstation at the same time the telephone rings.
  • caller ID For many large corporate desktop users, current systems provide caller ID only when a fellow employee calls from within the same PBX system. Calls from employees at other corporate locations only provide the trunk number of the remote location, not the calling telephone number or name. Providing caller ID (including name, telephone number, and other relevant information about the caller) allows the desktop worker to interrupt work, or, for users with multiple telephone lines, to interrupt a current conversation, to answer important calls without answering every call.
  • caller ID On PBX networks where caller ID is provided on the telephone display via proprietary channel signaling, a current limitation is that in a time sharing office environment, the caller ID cannot be dynamically changed. In a typical office environment, a telephone is assigned to an employee.
  • the caller name is the name of the employee to whom the caller telephone is assigned.
  • different employees use the office and the telephone at different times.
  • Additional limitations in current systems are that the PBXs must be from the same vendor, and the PBXs must be connected by leased lines, and the PBX data base of caller names must be entered at each site.
  • the gateway server provides dynamic caller ID, i.e. the telephone number with the correct caller name, based on who is logged on from the office desktop workstation at the time the call is made. If there is no user logged on at the time a call is made, the default information for that telephone is used. If the desktop worker's telephone is being forwarded to another extension, and a CTI event is generated with the forwarding, then the caller ID screen pop will appear with the ringing call at the forwarded extension. In addition, the original called party ID will also be displayed on the screen pop of the forwarded call.
  • dynamic caller ID i.e. the telephone number with the correct caller name
  • the caller ID feature can support calls between gateway telephones, i.e. between two telephones coupled to the same PBX in a gateway network, or between telephones coupled to two PBXs in different gateway networks.
  • gateway telephones i.e. between two telephones coupled to the same PBX in a gateway network, or between telephones coupled to two PBXs in different gateway networks.
  • the caller ID feature can provide the caller ID to the gateway server by the PBX, through CTI (if caller ID is transmitted by the PST NETWORK and by the PBX to the CTI link), or by a VoIP connection.
  • the caller ID feature relies on CTI or inband ANI, PRI or QSIG trunk types at the caller gateway server to provide the caller's telephone number.
  • the caller ID feature also relies on the desktop workstation display at the called party's desktop.
  • the enterprise directory provides the caller name and associated information (e.g. title, department, etc.) with the calling number.
  • FIG. 50 illustrates how the caller ID is obtained at the caller gateway server.
  • the caller (not illustrated) picks up the handset on the caller telephone and dials the desired telephone number.
  • the caller PBX accesses a trunk 35 to the caller gateway server 26 , and dials the call.
  • the caller gateway server receives the telephone number from the caller PBX on a PRI trunk or over the CTI link.
  • the caller gateway PBX 34 delivers the call to the caller gateway server 26 , and, as the call is delivered, the caller PBX 34 also passes the caller ID (i.e. the caller's telephone number) to the caller gateway server 26 via an inband ANI, PRI, QSIG or CTI link. In the case of an ISDN PRI link, the caller PBX 34 may use a call setup message to initiate the call. The caller ID can be transmitted as part of the call setup message.
  • the caller gateway server 26 receives the caller ID as part of the setup message, and the caller PBX 34 and caller gateway server 26 continue to set up the call.
  • the PBX uses a call setup message to initiate a call on the QSIG link.
  • the caller ID information is transmitted as part of the call setup message.
  • the caller gateway server 26 receives the caller ID as part of the setup message, and the caller PBX 34 and caller gateway server 26 continues to establish the call.
  • the CTI link 98 is a separate link from the trunks. To pass the caller ID via the CTI link, the PBX places a call to the caller gateway server 26 using a trunk. While the trunk call is being initiated, the CTI link 98 transmits an event message indicating the call.
  • the event message includes the trunk ID, the called telephone number, and the caller's caller ID.
  • the caller gateway server 26 associates the call being received on the trunk with the CTI link 98 message, and associates the caller ID with the trunk. Using the CTI link 98 to pass the caller ID supports instances in which analog or Ti trunks are used which do not provide caller ID information from the caller PBX 34 .
  • the caller gateway server 26 uses the caller's telephone number to access additional caller ID information in the gateway database, i.e. the local image of the enterprise directory data.
  • the caller gateway server 26 initiates an H.323 VoIP call with the called gateway server 126 over the IP network 18 .
  • the caller gateway server 26 sends the caller ID information to the called gateway server 126 using an H.323 extension, e.g. User Information Extension (UIE).
  • UEE User Information Extension
  • the called gateway server 126 sets up the call with the called PBX 134 , and may include the caller ID for the called PBX to pass to the called telephone 138 .
  • the called PBX rings the called telephone 138 , and, if the called telephone 138 has a caller ID display, the called PBX 134 may include the caller ID for display at the called telephone.
  • the called gateway server 126 checks its gateway database 151 to determine if the called party has a browser logged on to the called gateway server 126 , and if that browser is logically associated with the called telephone 138 .
  • the called gateway server 126 determines that the called party has a browser logged on, and is associated with the called telephone 138 , then the called gateway server 126 delivers the caller ID information to the called desktop workstation via a browser applet.
  • the browser applet results in a screen pop in the browser window at the called desktop workstation.
  • Both the caller gateway server 26 and called gateway server 126 log the calls, and include the caller ID information in the call logs. A description of the Call Log feature follows below.
  • the call log provides a log of outgoing calls and incoming calls including answered calls, abandoned calls and ring through calls for a desktop user.
  • the call log includes the time of call, name and telephone number of the caller, and the result of the call, e.g. forwarded to voice mail, hang-up, inbound/outbound, etc.
  • the call log may be sorted by time.
  • the desktop user can access the call log via a gateway server client or a browser. As is the case with all screen pops, the call log is available to users only when they are logged in to the gateway network. Users can make a return call by clicking any inbound call entry in the call log.
  • the entries in the call log can be imported into a user's personal phone book.
  • the call log is maintained on the gateway server and will continue to log calls even if the user does not log on to the gateway network. Entries in the call log can be deleted, individually and as a group. A user may click a “details” button to access the detailed NDS information for users who are parties to incoming and outgoing calls.
  • the caller gateway server 26 opens a call log record for the caller.
  • Caller ID information is obtained from the enterprise directory 90 for both the caller and called parties and is inserted into the call log record.
  • a call log record is opened for the called party.
  • Caller ID information for both the caller and called parties is inserted in the call log record in the called gateway server 126 .
  • additional information e.g. result, duration, etc. is inserted in the call log records at both the caller gateway server 26 and called gateway server 126 .
  • the integrated voice gateway system of the invention provides several options for a caller at a gateway telephone attempting to call a party at another gateway telephone which is currently busy.
  • the caller may elect to cancel the call or may select one of the options which include: Callback on Busy, Call Alert and Ring Through. These options will be described below. Common to each option is first the determination that a called gateway telephone is busy.
  • a normal call is propagated within the integrated voice gateway system, either within a single gateway network, or as a VoIP call between two gateway networks.
  • FIG. 52 illustrates such a call as a VoIP call between two gateway networks.
  • the caller gateway server 126 uses the called CTI link 198 to the called PBX 134 to maintain the idle/busy status of telephones on the called PBX 134 .
  • the called gateway server 126 receives the call from the caller gateway server 26
  • the called gateway server 126 checks the status of the called telephone 138 .
  • the called gateway server 126 on determining that the called telephone 138 is busy, notifies the caller gateway server 26 of the busy status.
  • the called gateway server 26 receives the busy notice and checks its user logon data to determine if the caller at the caller telephone 38 is currently logged in from a browser. If the caller is logged in, the caller gateway server 126 sends information to the caller's browser 95 to inform the caller that the called telephone 138 is busy. The caller's browser 95 provides a screen pop to the caller indicating that the called telephone 126 is busy. The screen pop also provides the caller with several options from which to choose. The options may include: cancel the call, request a callback, request a call alert or request a ring through. If the caller is not logged in from a browser, the caller may be provided similar options via an IVR interface.
  • the integrated voice gateway system of the invention provides the capability for a caller, if the called telephone is busy, to request that a callback be automatically set up when the called telephone is no longer busy. This feature is not available to most desktop users of current systems since telephone calls are typically immediately forwarded to voice mail systems when a called telephone is busy.
  • Some PBXs offer delayed call forward on busy to allow callers to set callback before the call is forwarded to voice-mail, and some voice mail systems offer callers an option to select callback before taking a message. However, these options require that the PBXs be upgraded, and a requested callback may be canceled if the caller telephone is used before the callback is completed.
  • callback on busy is provided across a network by PBX vendors, the callback option will only work if both the caller and called telephone systems are from the same vendor.
  • the integrated computer telephone system of the invention provides a callback on busy capability which works across networks of mixed telephone systems.
  • the callback option may be provided to the caller via IVR or via a screen pop. If the caller requests a callback be set up, then the gateway servers 4 , 104 will automatically set up the call when the called party hangs up the current call.
  • both the caller and called parties will be provided with the other party's caller ID.
  • the caller ID screen pop it is also noted that the call is a callback call.
  • the gateway servers set up the callback call
  • the original caller telephone is busy
  • the original caller will receive a screen-pop to the effect that the callback is taking place.
  • the caller will have the option to hang up or place the current call on hold to initiate the callback call, or ignore the callback notification. If the caller ignores the callback notification, i.e. continues the current call for more than a specified time, e.g. 15 seconds, the callback will be canceled.
  • the callbacks may be serviced on a first-in-first-out (FIFO) basis, or on a priority basis, e.g. based on class of service of the caller, urgency, etc.
  • FIFO first-in-first-out
  • the integrated voice gateway system of the invention provides the capability for a caller to request a call alert if the called telephone is busy. For current desktop users, there is no capability to send a call waiting signal to a busy party since telephone calls are typically immediately forwarded to voice mail systems when a called telephone is busy.
  • the ability of the integrated computer telephone system of the invention to provide caller ID on all intra-company calls regardless of location is an important part of the call alert feature.
  • the unique ability of the integrated voice gateway system of the invention to allow remote users to send messages to describe their urgent need to talk to a busy party is a significant advance in desktop to desktop communication.
  • the call alert option may be provided to the caller via IVR or via a screen pop. If the caller chooses to request the alert via a screen pop, the caller may include an optional message, e.g. to inform the called party of the purpose of the call.
  • the optional message may be selected from a set of pre-established messages, or may be a message created by the caller.
  • the call alert is delivered to the called party in a screen-pop on the called party's desktop workstation.
  • the caller ID and optional message from the caller will be displayed.
  • the called party can then take the call by hanging up or placing the current call on hold, acknowledge the call alert, or ignore the call alert by continuing the current call for more than a specified time, e.g. 15 seconds. If the called party ignores the call alert, the caller may be given the option to either ring through or set up a callback. The option to ring through or call back may be provided via IVR or screen pop. If the called party has multiple lines, then a call alert will be activated only if all lines are busy.
  • the call alert feature requires that both the caller and called telephones are gateway telephones, and the called party is logged on to the gateway server via the browser interface.
  • the call alert feature uses CTI on both the caller gateway server and called gateway server for on/off hook status and to determine if the called party hangs up or places the current call on hold.
  • the call alert feature also relies on the directory to provide caller ID for a call alert screen pop presented to the called party.
  • the privilege to use call alert may be configurable by the system administrator on a user by user basis.
  • DND Do not Disturb
  • FIGS. 54 and 55 illustrate a call alert scenario using the browser client and screen pops.
  • the caller types a message and clicks a call alert button in the caller user client 95 .
  • the call alert message is passed to the caller gateway server 26 , and then over the IP network 18 to the called gateway server 126 .
  • the called gateway server 126 passes the call alert message to the called user client 195 .
  • the call alert message appears via a screen pop in the called user client 195 .
  • the called user may elect to accept or reject the call alert by clicking an appropriate button in the call alert screen pop.
  • a message is passed to the called gateway server 126 .
  • the called CTI driver 180 passes a message to the called PBX 134 to place the current call on hold.
  • the called analog driver 167 delivers the new call to the called PBX 134 .
  • the called PBX 134 rings the called telephone 138 .
  • the rejection message is passed to the called gateway server 126 and the called user client 195 closes the screen pop. If the called user takes no action, and the call alert times out, the called gateway server 126 passes a message to the called user client 195 to close the call alert screen pop.
  • the called gateway server 126 sends a call alert rejected message to the caller gateway server 26 via the IP network 18 .
  • the caller gateway server 26 passes the call alert rejection message to the caller user client 95 .
  • the rejection message includes applicable options for the caller to select.
  • the integrated voice gateway system of the invention provides the capability for a caller to request a ring through if the called telephone is busy.
  • the ring through option follows normal PBX call coverage options which may typically forward calls to a user's voice mail or a Must Answer Station. The ring through option will be described with reference to FIG. 56.
  • the integrated voice gateway system of the invention provides the capability for a caller to request a call alert if the called telephone is busy and the caller is not using a gateway telephone.
  • a caller typically forwards a call to a designated (e.g. “must answer”) station, e.g. by pressing “0” after being forwarded to voice mail.
  • a designated (e.g. “must answer”) station e.g. by pressing “0” after being forwarded to voice mail.
  • the attendant at a must-answer station is typically located remotely from the called party and hence cannot walk over to the called party and slip a notice that the caller needs to urgently talk to the called party.
  • a PST NETWORK telephone places a call to a gateway telephone, and the called gateway telephone is busy, the caller may elect to transfer to a must-answer station.
  • An attendant at the must-answer station can assist the caller by providing a call alert, for the outside caller, on the co-located workstation of the busy gateway telephone.
  • the integrated computer telephone system of the invention provides the capability for users to redirect incoming telephone calls arriving at their regular PBX station to any telephone or internet phone.
  • the system of the invention also provides users with the capability to set up filters so that only calls from selected callers are redirected. Calls not forwarded can be sent to the normal PBX call coverage options, e.g. voice-mail.
  • the telephone to which the calls are redirected may be another gateway telephone (coupled to the same or a different PBX as the user's telephone), or a PST NETWORK telephone (e.g. remote telephone 338 ), etc.
  • the redirection can be set up as a one-time event or a recurring (e.g., daily) event. However, at any point in time, only one redirection may be in effect.
  • the follow me feature may be setup via the browser or and IVR interface. If a browser is available, the user accesses follow me setup screens via the browser, reviews current options, and may make changes to the configuration. The browser and gateway server exchange data during the interaction.
  • a browser is not available, for example, if the user is setting up the follow me feature from a PST NETWORK telephone, the user may set up follow me by calling a specified telephone number and interacting through an IVR interface. If the user calls from a remote telephone, the system may first authenticate the user's identity. For real time call processing, the user's follow me data is stored in the gateway server's local database. The user's follow me settings are stored in the enterprise directory as part of that user's data.
  • the follow me setup may include several options. For example, the user may schedule follow me periods as one time or periodic recurring events with a different destination telephone number selected for each event (e.g., car phone during the commute home, and home telephone in the evening). The user may set up numerous scheduled events. The user may also use an override option to use an unscheduled alternate destination. The users may configure the system to filter calls based on caller ID, and forward only calls from a list of callers selected by the user. The user may assemble a list of callers from the enterprise white pages and a frequent contact list. The user may create a different filter for each scheduled follow me period.
  • a different destination telephone number selected for each event e.g., car phone during the commute home, and home telephone in the evening.
  • the user may set up numerous scheduled events.
  • the user may also use an override option to use an unscheduled alternate destination.
  • the users may configure the system to filter calls based on caller ID, and forward only calls from a list of callers selected by the
  • an incoming call to a called telephone 138 coupled to a called PBX 134 may come via a VoIP call from a caller telephone 38 coupled to a caller PBX 34 ; via a PST NETWORK call from a caller telephone 438 coupled to the PST NETWORK 16 ; or from a caller telephone 538 coupled to the called PBX 134 .
  • the called PBX 134 sends a CTI event to the called gateway server 126 .
  • the called gateway server 126 checks whether follow me is active for the called party, and, if a filter is active, if the caller matches the filter.
  • the caller does not match an active filter, the call not forwarded, and is simply delivered to the called telephone 138 . If a match is found, the called gateway server 126 initiates a call to the follow me destination telephone. If the original call was an internal PBX call or a call from a PST NETWORK telephone, the gateway server uses the CTI link to redirect the call to the called gateway server 126 . If the original call is a VoIP call, the call is normally directed to the called gateway server 126 , and the called gateway server 126 can redirect the call.
  • the called gateway server 126 plays a message for the caller indicating that the call is being forwarded.
  • the gateway server offers a greeting to the answering party.
  • the answering party replies with an accept code, e.g. DTMF tones, thereby authenticating the answering party.
  • the caller and called party are then connected. If the call forwarded to the destination is not answered, or if the correct accept code is not provided, the caller is provided a message and the call is re-routed to the original called telephone to go through normal PBX coverage options, e.g. voice-mail.

Abstract

An integrated voice gateway system for use within a company which can route a voice telephone call between parties at two different locations over an IP network or over the PST NETWORK. The system can route a voice telephone call from a first location within the system to a second location within the system via the IP network, and then from the second location to a third location via the PST NETWORK. The integrated voice gateway system includes a gateway server which serves as an intranet/Internet telephony gateway. The gateway server routes intra-company voice or facsimile (fax) calls, over the company's intranet or the public Internet. The gateway server provides an alternate voice network to the PST NETWORK for a company. This alternate network is provided at a much lower cost. The gateway server is a combination of hardware and software components which reside on a PC server platform. The gateway server is coupled to a customer premise telephone system, i.e. a PBX via a T1 or E1 trunk for larger systems, or an analog trunk for smaller systems. The gateway server is coupled to the company's intranet via industry standard connections. The gateway servers in a multi-site company are coupled together via the company's intranet or wide area network (WAN) into a gateway network. The gateway server uses PBX call status links to provide many unique and useful features which are otherwise unavailable. The gateway server uses T1 inband ANI, PRI, QSIG or industry standard CTI applications programming interfaces (API) and works with any PBX which supports any of these call status links. The gateway server is equipped with a database of user and gateway objects and attributes, and provides many unique features including caller's name based on caller phone number, address translation, gateway network routing information, user authentication, etc. This database can be integrated with industry standard enterprise directory services systems including any directory which supports the Lightweight Directory Access Protocol (X.500) (LDAP) interface.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a divisional of application Ser. No. 09/061802 filed on Apr. 16, 1998.[0001]
  • FIELD OF THE INVENTION
  • This invention relates to an integrated voice gateway system. [0002]
  • BACKGROUND OF THE INVENTION
  • The widespread popularity of the Internet has provided new means of rapid and comprehensive communication between users located in distant and diverse locations around the world. Methods of sending, finding and retrieving information, previously confined to the domain of government, academia and industry, are now available in business, in the community, and in the home. Formerly arcane technical terms such as telnet, electronic mail (e-mail), file transfer protocol (FTP), hypertext transfer protocol (HTTP) and world wide web (WWW or web) are now widely used. [0003]
  • Very soon after the popularity of the Internet became widespread, new applications of the underlying technology began to emerge. With the concomitant growth of multimedia, a predominately text-based medium quickly expanded to include graphics, imagery, motion pictures and sound. A natural extension of the capability to transmit recorded, digitized sound between personal computers (PC), was the advent of PC based telephony. Although the initial users of PC to PC telephone calls over the Internet were primarily computer hobbyists and the like, there was an early recognition of the fact that the Internet provided the potential for the average user to make a telephone call anywhere in the world for the cost of a local telephone call to an Internet service provider (ISP). [0004]
  • PC to PC telephone technology is limited by the need to be logged on to a PC and the Internet to place or receive a call. Software incorporating proprietary algorithms limit the ability to call to others having the same or similar software. The sound quality is often degraded because of packet loss and delays in forwarding packets from the sender to the receiver over the Internet, operation in a half-duplex mode, and the use of low quality PC speakers and microphones. [0005]
  • With the expectation of improved performance and reduced cost of telephone calls in the business environment, voice gateways have facilitated the interconnection of the private branch exchange (PBX) and the computer network. As used herein, PBX includes hybrid, key systems, and other such systems. Thus, through a PBX coupled to an Internet protocol (IP) network (e.g., intranet, wide area network (WAN), Internet), telephone calls between different sites within a company, or other institution, organization or enterprise (hereinafter referred to as “company”), or between companies, the company or companies having installations at two or more locations which locations may be geographically distant from each other, may be routed over the IP network rather than via the public switched telephone network (PST Network). As used herein, the PST NETWORK includes both public and private networks. This can result in significant cost savings and can also help to improve communication within and between companies by providing a variety of related services which are not available via the PST NETWORK. [0006]
  • The level of integration achieved in current voice gateway systems is quite low, and such systems are limited in the services they can provide. In particular, current voice gateway systems are capable of only routing a nominal telephone call from a calling party at point A to a called party at point B. However, if, for example, the called party is not present, or if the called party's telephone is currently busy, current voice gateway systems do not provide important additional services to facilitate making a connection between the calling party and the called party at a later time or at another location or by an alternative method. [0007]
  • One of the reasons for the limitations is that current voice gateway systems are limited in their ability to obtain, store, update and retrieve necessary information about both the calling party and the called party in order to do anything other than simply attempt to make a straight forward connection between the two points. If the telephone system had sufficient information about both parties, then the system could facilitate making the connection at a later time, at another location or by an alternative method. However, in current voice gateway systems, there is no way to obtain the necessary call status and call control information, nor is there an accessible central data base in which to store and from which to retrieve this information. Current voice gateway systems have no real-time call control/call status information link with the PBX, nor do they have any storage of telephone user information. For example, current voice gateway networks have no information regarding the calling party's name, telephone number, or status of the called party, e.g., busy or idle. It is this information about the calling and called parties which is not readily available, but which is necessary to provide important additional services. [0008]
  • There is a need for a highly integrated voice gateway system for use within a company and between companies having installations at two or more locations which locations may be geographically distant from each other. The integrated voice gateway system should have the ability to route telephone calls between parties at two different locations over the IP network as well as the PST NETWORK, and to automatically select which of the IP network and PST NETWORK overwhich to route telephone calls. The integrated voice gateway system should have the means to obtain, store, update and retrieve information about calling and called parties. For example, in instances in which a calling party is unsuccessful in making a connection to a called party, the integrated voice gateway system should have the means to use information about the calling and called parties to provide services which facilitate making an alternate or subsequent connection between the calling party and the called party. [0009]
  • The following standards are incorporated herein by reference: [0010]
  • ITU-T Recommendation H.323—Packet-based multimedia communications systems; [0011]
  • ITU-T Recommendation X.500—Open systems interconnection—The directory: Overview of concepts, models and services; and [0012]
  • IPNS Forum QSIG Handbook. [0013]
  • SUMMARY OF THE INVENTION
  • We have now invented a highly integrated voice gateway system for use in a company or between companies having installations at two or more locations which locations may be geographically distant from each other. [0014]
  • As used herein, a voice telephone call from a caller telephone to a called telephone, the call carried via an IP network, is referred to as a VoIP call. As used herein, a fax call from a caller fax machine to a called fax machine, the call carried via an IP network, is referred to as an FoIP call. [0015]
  • Accordingly, it is an object of the invention to provide an integrated voice gateway system for use within a company which can route a voice telephone call between parties at two different locations over an IP network as well as the PST NETWORK and to automatically select which of the IP network and PST NETWORK over which to route the calls. It is a further object of the invention to provide a system which can route a voice telephone call between a calling party using a telephone at a first location within the system to a second location within the system via an IP network, and then from the second location to a called party at a third location via the PST NETWORK. [0016]
  • It is an object of the invention to provide an integrated voice gateway system which can place a telephone call over an IP network, and then if, during the telephone call, the quality of the telephone call falls below a predetermined quality level, to be able to reroute the telephone call over the PST NETWORK, and to do so in a manner which is transparent to both the calling and called parties. [0017]
  • It is an object of the invention to provide an integrated voice gateway system which can track any move, add or change to any telephone user in the enterprise in the integrated voice gateway system. It is a further object of the invention to provide an integrated voice gateway system which can integrate with an enterprise directory to allow single point of entry of moves, adds and changes to telephone users and to provide replication of these changes across all enterprise sites. [0018]
  • It is an object of the invention to provide an integrated voice gateway system in which the identification of the calling party (e.g. name, title, department, telephone number) is displayed on a computer screen (rather than on a telephone display) co-located with the called party's telephone, and that such information be displayed regardless of the vendor(s) supplying the telephone equipment used by the calling and called parties. It is a further object of the invention that such information be provided regardless of the desktop workstation or PC (workstation and PC are referred to interchangeably herein), or operating system used via a WWW browser interface. [0019]
  • It is an object of the invention to provide an integrated voice gateway system which can create a log of incoming telephone calls over an IP network which telephone calls are not answered by a called party, and identify the name of each calling party. It is a further object of the invention to provide a log of all incoming and outgoing calls whether the calls are on net (i.e., IP network) or off net (i.e, PST NETWORK or internal PBX). [0020]
  • It is an object of the invention to provide an integrated voice gateway system in which, when a called party's telephone is busy, the system can automatically set up a call between the calling party and the called party as soon as the called party hangs up. It is a further object of the invention to provide such a capability even when a called party has voice mail. [0021]
  • It is an object of the invention to provide an integrated voice gateway system in which, when a called party is busy, the calling party may send a computer message which will be immediately displayed on a computer screen co-located with the called party's telephone, for example to explain why the calling party needs to speak with the called party. [0022]
  • It is an object of the invention to provide an integrated voice gateway system in which, when a called party does not answer an incoming telephone call, the calling party may forward the call, for example from voice mail, to a receptionist or other designated party. It is a further object of the invention to provide the capability for a party at an answering station to send a computer message which will be immediately displayed on a computer screen co-located with the called party's telephone. [0023]
  • It is an object of the invention to provide an integrated voice gateway system in which a user of the system may set up the system to forward that user's telephone calls to a different telephone. It is a further object of the invention to forward calls to PST NETWORK telephones or PC-based IP telephones. It is a further object of the invention to provide the capability for a user to set up the system to forward that user's telephone calls to different telephones according to a time schedule predetermined by the user. It is a still further object of the invention to provide the capability for a user to set up the system to forward telephone calls originating only from one or more calling parties so designated by the user. It is a further object of the invention to provide the capability to setup call forwarding via a browser interface or interactive voice response (IVR). [0024]
  • It is an object of the invention to provide an integrated voice gateway system in which users can initiate telephone functions from the workstation, such functions including, without limitation, dialing a call, transferring a call, add-on conference, and forward a call to/from any white pages entry or personal telephone book entry. [0025]
  • It is an object of the invention to provide an integrated voice gateway system which provides secure access to the system from telephones, including PC-based IP telephones, which are outside the system. [0026]
  • It is an object of the invention to provide an integrated voice gateway system which, when a call from a source to a first destination is transferred from the first destination to a second destination, can direct the path of the call directly from the source to the new destination and thereby maintain the quality of the call. It is an object of the invention to provide an integrated voice gateway system with an operating system independent browser based client which therefor requires no client software installation. It is a further object of the invention to provide the desktop telephone users with a telephone white pages display of any entry in the enterprise directory services database. [0027]
  • In a first aspect, the invention provides a communication system comprising a public switched telephone (PST) network; an IP network; a PBX coupled to the PST network for routing a telephone call over the PST network; a telephone coupled to the PBX; a voice gateway coupled to the PBX through a call status-call control link and a trunk, and coupled to the IP network for routing a telephone call over the IP network; selection means for selecting which of the PST network or the IP network to route a telephone call; and call status means for the gateway server to monitor events associated with incoming calls to the telephone and outgoing calls from the telephone. [0028]
  • In a second aspect, the invention provides a communication system comprising a PST network; an IP network; a PBX coupled to the PST network for routing a telephone call over the PST network; a telephone coupled to the PBX; a voice gateway coupled to the PBX through a call status-call control link and a trunk, and coupled to the IP network for routing a telephone call over the IP network; a desktop workstation coupled to the voice gateway; selection means for selecting which of the PST network or the IP network to route a telephone call; and PC call control means for controlling the telephone from the desktop workstation. [0029]
  • In a third aspect, the invention provides, in a communication system comprising a PST network, an IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones,a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, fallback to PST NETWORK means for rerouting a telephone call connected over the IP network to the PST network. [0030]
  • In a fourth aspect, the invention provides, in a communication system comprising a PST network, an IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones,a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, a method of automatically rerouting an in process telephone call from the IP network to the PST network when the quality of the telephone call over the IP network falls below a predetermined quality level, the method comprising the steps of (a) establishing a connection for the telephone call over the PST network while the telephone call is still connected over the IP network; (b) switching the parties to telephone call over the PST network; and (c) breaking the connection for the telephone call over the IP network while maintaining the telephone call over the PST network. [0031]
  • In a fifth aspect, the invention provides, in a communication system comprising a PST network, an IP network, a plurality of private branch exchanges (PBX) at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX and to the IP network for routing telephone calls over the IP network, and selection means for selecting which of the PST network or the IP network to route telephone calls, fallback during call setup means to automatically route a telephone call over the PST network if, during call setup, the telephone call cannot be setup over the IP network. [0032]
  • In a sixth aspect, the invention provides a method of configuring an enterprise directory for IP telephony, the method comprising the steps of (a) providing an X.500 compatible directory; and (b) including in the schema of the directory at least one of GateKeeper, Gateway, Multipoint Control Unit (MCU), GateKeeper Exchange, and a desktop user object and attribute. [0033]
  • In a seventh aspect, the invention provides a computer telephony integration (CTI) system comprising a PBX, a telephone coupled to the PBX, a local area network (LAN), a voice gateway coupled to the LAN, a CTI server coupled to the PBX and coupled to the LAN, a web server coupled to the LAN, a desktop workstation coupled to the LAN, the desktop workstation comprising a web browser. In an eighth aspect, the invention provides a communication system comprising a PST network, an IP network, a PBX coupled to the PST network for routing a telephone call over the PST network, a voice gateway coupled to the PBX and the IP network for routing a telephone call over the IP network, and selection means for selecting which of the PST network or the IP network to route a telephone call, and for a telephone call placed from a first telephone at a first location, over the IP network to a second telephone at a second location, path replacement means for transferring the telephone call from the second telephone at the second location to a third telephone at a third location, the path replacement means routing the telephone call from the first telephone at the first location over the IP network to the third telephone. [0034]
  • In a ninth aspect, the invention provides a communication system comprising a PST network, IP network, a plurality of PBXs at a plurality of locations, the PBXs coupled to the PST network for routing telephone calls over the PST network, coupled to each PBX a respective plurality of telephones, a plurality of voice gateways, each voice gateway coupled to a respective PBX through a call status and call control link and a trunk, and coupled to the IP network for routing telephone calls over the IP network, coupled to a plurality of voice gateways, selection means for selecting which of the PST network or the IP network to route telephone calls, and feature networking means for providing PBX features among the plurality of locations over the IP network. [0035]
  • The integrated voice gateway system includes a gateway server which serves as an Intranet/internet telephony gateway. The gateway server routes intra-company voice or facsimile (fax) calls, made from user's desktop phones or fax machines/servers, over the company's intranet or the public Internet. The gateway server provides an alternate voice network to the PST NETWORK for a company. This alternate network carries voice and fax calls at a much lower cost. This is because an intranet is built to support bursty data traffic and the bandwidth is underutilized most of the time. The gateway server takes advantage of the underutilized bandwidth when such bandwidth is available to transmit voice. [0036]
  • The gateway server is a combination of hardware and software components which reside on a workstation server platform. The gateway server is coupled to a customer premise telephone system, i.e. a PBX via a T1 or E1 trunk for larger systems, or an analog trunk for smaller systems. The gateway server is coupled to the company's intranet via industry standard connections (e.g., ethernet, frame relay or asynchronous transfer mode (ATM)). Thus, the gateway server is a gateway between the PBX/PST NETWORK and the company's intranet. The gateway servers in a multi-site company are therefore coupled together via the company's intranet or wide area network (WAN) into a gateway network. [0037]
  • The gateway server uses call status and call control integration with the PBX to provide many unique and useful features which are otherwise unavailable. The gateway server supports a variety of call status/call control PBX links including T1 inband ANI, PRI, QSIG (global DSS1 based signaling system for corporate networks, not an acronym, known at the international level as Private Signaling System No. 1 (PSS1)) and CTI. Industry standard CTI applications programming interfaces (API) are supported, including the AT&T/Novell Telephony Services Application Programming Interface (TSAPI), the Microsoft Telephony Application Programming Interface (TAPI), and the European Computer Manufacturers Association (ECMA) Computer Supported Telephony Applications (CSTA) protocol. Hence the gateway server can provide enhanced features via a variety of call status/call control links with the level of enhanced features available depending on the type of link used. [0038]
  • The gateway server is also equipped with a database of user and gateway objects and attributes. This database provides many unique features including providing caller's name based on caller phone number, address translation, gateway network routing information, user authentication, etc. This database is stored in the server but can be integrated with industry standard enterprise directory services systems including Novell Directory Services (NDS), Microsoft Active Directory Services (ADS), Domain NT and any directory which supports the Lightweight Directory Access Protocol (X.500) (LDAP) interface. The integration provides the enterprise with a single point of entry for user adds, moves and changes, and provides replication throughout all corporate sites. [0039]
  • A gateway network in a company essentially connects a company's PBXs, which are often geographically dispersed, into a single intelligent virtual PBX (VPBX). A company-wide VPBX provides advanced end-user features across the company. These features would otherwise be available only within the scope of a single PBX, or would require expensive PBX features interworking products which require expensive PBX resident software and expensive data connections, e.g. dedicated voice tie lines between sites. By providing PBX features interworking via IP, call status-call control and a database of user and gateway objects and attributes, the gateway server offers PBX features interworking, at a lower cost, over a network of mixed PBXs from different vendors and over a single converged network (data tie line or data VPN). [0040]
  • The gateway server works with existing telephone systems, and with the mixed networks of telephone systems commonly found in large companies. The gateway server provides feature interworking using the combination of the desktop telephone and desktop workstation. Current PBX systems provide such internetworking capabilities only between desktop telephones. With the gateway server, however, a worker using a desktop telephone can be notified of an important call via the desktop workstation. The unique ability of the gateway server to control both the desktop telephone and the desktop workstation for calls between remote workers provides many new VPBX features not available with current PBX to PBX solutions, and provides an alternative method for current PBX networking features that is not limited to only sites with the same vendor PBX models. These consistent features across the network substantially improve communications and enhance productivity by making employees at multiple sites feel like they are part of a single community. In addition to end-user visible features, the gateway server also offers benefits such as intelligent routing (using automatic configuration) and increases network performance. [0041]
  • The gateway server supports routing of telephone and fax calls made from desktop telephones or stand alone fax machines, or workstation integrated fax servers over a company's intranet or the public Internet. By configuring a selection table in the server, the gateway server can route real-time fax calls over either the intranet or Internet to minimize the cost of the fax call. The gateway server supports computer-based fax as well as stand-alone fax machines. [0042]
  • By integrating CTI and enterprise directory service with IP telephony, the gateway server provides many more features in a user-friendly way than current Internet/intranet telephony to IP voice gateways. Current voice gateways connect only to a telephone system's voice lines, e.g., analog, ISDN BRI, ISDN PRI, or T1. This provides only for carrying voice or fax calls over IP. The gateway server is unique in that the server also provides a call control and call status link to the telephone system. Moreover, current voice gateways do not store user telephone information such as telephone number and associated user name. The gateway server is unique in that it stores extensive user telephone information and also integrates with industry standard enterprise directory services. The use of extensions to the enterprise directory services to implement IP telephony services is a new concept introduced by the gateway server of the invention. [0043]
  • The gateway server can route long distance calls among multiple company locations and do so in a manner which is transparent to the users, except perhaps for possible differences in the quality of voice transmission. However, the users dial the same way that they currently dial to make calls whether over public or private networks. The routing table of the PBX automatically routes designated calls to the voice gateway and the gateway then decides whether to route the call over the company's intranet or the Internet. [0044]
  • In addition to integrating CTI and enterprise directory service with IP telephony, the gateway server also provides many unique IP telephony features in addition to the VPBX features. [0045]
  • By constantly monitoring the quality of a voice call over the IP network, the gateway network of the invention can continue to maintain a call over the IP network as long as the quality of the call is above a predetermined quality level. If the quality of a voice call over the intranet or Internet falls below a predetermined quality level, e.g. due to network congestion, the gateway server can automatically “fall back” to the PST NETWORK. The gateway server can automatically set up a call over the PST NETWORK between the caller and called party's desktop telephones and switch the parties to the PST NETWORK call. The gateway server can then drop the IP portion of the call such that the caller and called party are then talking over the PST NETWORK. Current voice gateway systems cannot switch a call to the PST NETWORK once the call has been connected. Since data network congestion can change significantly at any time, e.g. a large graphics file is suddenly downloaded in the middle of an IP telephone call, the ability to switch to the PST NETWORK during an IP telephone call is a significant advantage to the calling parties. Current systems require the calling parties to hang up if the voice quality deteriorates during a call, and place a new call, which may encounter the same network congestion problem, unless the entire gateway is shut down. [0046]
  • Moreover, in current voice gateway systems, if one remote gateway is not accessible, the entire gateway must be shut down or callers to the non-accessible remote gateway would be forced to continually hang up and call again and again until the remote gateway is accessible, or dedicated ports would be required for each gateway segment. The integrated voice gateway system of the invention provides the capability to fallback to PST NETWORK during call setup in which only calls directed to a non-accessible gateway are routed over the PST NETWORK, while still allowing other calls to be routed via the gateway and IP network. If a remote gateway is not accessible, a voice call would not necessarily be rerouted over the PST NETWORK as would be done by current voice gateways.[0047]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of an overview of the top-level architecture of an embodiment of an integrated voice gateway system according to a first aspect of the invention. [0048]
  • FIG. 2 is a block diagram of the top-level architecture of a gateway network according to a first aspect of the invention. [0049]
  • FIG. 3 is a block diagram illustrating major software and hardware components of an embodiment of a gateway network according to a first aspect of the invention. [0050]
  • FIG. 3A illustrates the distributed architecture of the enterprise directory. [0051]
  • FIG. 4 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in setting up a basic PST NETWORK call. [0052]
  • FIG. 5 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in setting up a basic VoIP call. [0053]
  • FIGS. [0054] 6-7 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a first method for setting up a hop-off to PST NETWORK call.
  • FIGS. [0055] 8-12 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a second method for setting up a hop-off to PST NETWORK call.
  • FIGS. [0056] 13-14 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a third method for setting up a hop-off to PST NETWORK call.
  • FIG. 15 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a common method for setting up a hop-on to VoIP call. [0057]
  • FIG. 16 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a first scenario for setting up a hop-on to VoIP call. [0058]
  • FIG. 17 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a third scenario for setting up a hop-on to VoIP call. [0059]
  • FIG. 18 illustrates the operation of an embodiment of an integrated voice gateway system of the invention in a fourth scenario for setting up a hop-on to VoIP call. [0060]
  • FIGS. [0061] 19-22 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a first method for setting up a fallback to PST NETWORK call.
  • FIGS. [0062] 23-29 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a second method for setting up a fallback to PST NETWORK call.
  • FIGS. [0063] 30-33 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a third method for setting up a fallback to PST NETWORK call.
  • FIGS. [0064] 34-38 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a fourth method for setting up a fallback to PST NETWORK call.
  • FIGS. [0065] 39-46 illustrate the operation of an embodiment of an integrated voice gateway system of the invention in a fifth method for setting up a fallback to PST NETWORK call.
  • FIG. 47 is a block diagram illustrating a prior art approach to providing a CTI-workstation interface. [0066]
  • FIG. 48 is a block diagram illustrating the computer architecture supporting a PC Call Control feature in an embodiment of an integrated voice gateway system of the invention. [0067]
  • FIG. 49 illustrates the operation of a virtual desktop feature in an embodiment of an integrated voice gateway system of the invention. [0068]
  • FIG. 50 illustrates the operation of a caller name display feature in an embodiment of an integrated voice gateway system of the invention. [0069]
  • FIG. 51 illustrates the operation of a call log feature in an embodiment of an integrated voice gateway system of the invention. [0070]
  • FIG. 52 illustrates the operation of an embodiment of an integrated voice gateway system of the invention when a called telephone is busy. [0071]
  • FIG. 53 illustrates the operation of a callback on busy feature in an embodiment of an integrated voice gateway system of the invention. [0072]
  • FIGS. [0073] 54-55 illustrate the operation of a call alert feature in an embodiment of an integrated voice gateway system of the invention.
  • FIG. 56 illustrates the operation of a ring through feature in an embodiment of an integrated voice gateway system of the invention. [0074]
  • FIGS. [0075] 57-58 illustrate the setup and operation of a follow me feature in an embodiment of an integrated voice gateway system of the invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • FIG. 1 is a block diagram of an overview of the top-level architecture of an embodiment of an integrated [0076] voice gateway system 2 according to a first aspect of the invention. The block diagram depicts three gateway networks 4, 6, 8 of a multi-site company. In embodiments of the invention, such gateway networks may be located, e.g. in different buildings of a large plant, such as in an industrial park or campus setting, in different locations within the same city, or may be located at geographically distant locations, including world-wide. The gateway networks may also be located in different companies. In the particular example depicted in FIG. 1, first and second gateway networks 4, 6 may be within a large industrial park or at different locations within a city as they are both coupled to a first telephone company central office (CO) CO1 12. The third gateway network 8 is geographically distant from both the first and second gateway networks 4, 6 and is coupled to a second CO, CO2 14. CO1 12 and CO2 14 are part of a PST NETWORK 16. The PST NETWORK 16 may include many COs. Each of the gateway networks 4, 6, 8 is coupled to the company's IP network 18. The IP network 18 may include an intranet, the Internet, and the like.
  • In the description of FIG. 2 and subsequent FIGS., a generic embodiment of a gateway network according to the invention will be described with reference to the [0077] first gateway network 4 depicted in FIG. 1.
  • FIG. 2 is a block diagram of the top-level architecture of an embodiment of a gateway network [0078] 4 (represented by the dashed box) according to a first aspect of the invention.
  • The [0079] gateway network 4 includes a local area network (LAN) 22. Coupled to the LAN 22 are one or more workstations 24, a gateway server 26, a directory server 28, and a router 32. The gateway server 26 is also coupled to the PBX 34 via a call status-call control link. The call status-call control link can comprise a CTI link 98, a PRI interface 36, a QSIG interface 36 or an analog driver 33. These interfaces are individually illustrated and described below in reference to FIG. 3.
  • The [0080] PBX 34 is coupled to CO1 12. One or more telephones 38 are coupled to the PBX 34. The telephones 38 may be any telephone device connecting to a PBX, e.g. analog (POTS), proprietary digital, or standards-based digital (ISDN BRI). Each telephone 38 may be logically associated with and may be co-located with a respective workstation 24. The gateway server 26 is also coupled to the PBX 34 via an industry standard telephone station interface 33.
  • The [0081] CTI interface 98 between the gateway server 26 and the PBX 34 uses an industry standard CTI API, e.g., TSAPI, TAPI and CT Connect. Both TSAPI and TAPI focus on call control. The CTI interfaces enable computer control of dialing, answering, transferring and conferencing, and provide status. In PBX environments, the CTI interfaces also support control of advanced features of digital telephones (TAPI) and the switches to which those station sets connect (TSAPI).
  • The [0082] directory server 28 may reside in separate hardware or may be co-located with the gateway server 26 in the same hardware.
  • FIG. 3 is a block diagram illustrating major software and hardware components of an embodiment of a [0083] gateway server 26 according to a first aspect of the invention. The gateway server 26 includes software modules which communicate among themselves and have interconnections to other components through either software drivers supporting interfacing hardware elements, or communication links to other components.
  • The [0084] gateway engine 50 is the central logic coordinating element of the gateway server 26. The gateway engine 50 directs and oversees the activities of the other components of the gateway server 26 and gateway network 4 (FIG. 2). As call processing occurs, the gateway engine 50 accesses routing information from a gateway gatekeeper 53 and directs a communication subsystem 58. The gateway engine 50 also contains the feature logic for VPBX capabilities. The gateway engine 50 also creates logging and statistical data.
  • The [0085] enterprise directory 90 is a company-wide general purpose directory or global database of named objects including users, network devices (e.g. routers, gateways), and network services (e.g. print servers), etc. The enterprise directory 90 is a distributed system with replication and synchronization among its nodes, and has an extensible object schema. The implementation of the enterprise directory 90 in the integrated voice gateway system of the invention includes the extension of the directory schema to support IP telephony.
  • In a preferred embodiment, the [0086] enterprise directory 90 is implemented using a general purpose directory such as NDS. The invention introduces schema extensions in NDS. The schema extensions enhance the NDS base schema so that it supports the Directory Services requirements for an H.323 Recommendation based IP telephony network. In addition to H.323 support, the schema extension enables the H.323 gatekeepers in an H.323 IP telephony network to automatically find each other. This capability is not currently specified and supported by the ITU H.323 Recommendation v.1. The schema extensions also enable the invention to provide many of its unique features, e.g. caller ID, follow me with call filtering, etc.
  • FIG. 3A illustrates the distributed architecture of the [0087] enterprise directory 90. In FIG. 3A, the logical organization of the enterprise directory 90 is illustrated by the large ellipse with NDS at its center and surrounded by a series of pie-shaped logical partitions P1, P2, P3, P4, P5, P6. The number of partitions illustrated in FIG. 3A is arbitrary, as the actual number of partitions in a particular gateway network will depend on the needs of the particular enterprise.
  • Also illustrated in FIG. 3A are a series of gateway servers [0088] 26-1, 26-2, 26-3, 26-4, 26-5, 26-6, each gateway server coupled to a respective physical partition P1′, P2′, P3′, P4′, P5′, P6′ of the enterprise directory 90. The dashed curved lines indicate the correspondence of the physical partitions P1′, P2′, P3′, P4′, P5′, P6′ with the logical partitions P1, P2, P3, P4, P5, P6 of the enterprise directory 90. Each physical partition P1′, P2′, P3′, P4′, P5′, P6′ comprises the portion of the respective enterprise directory 90 applicable to the respective location served by a gateway server 26-1, 26-2, 26-3, 26-4, 26-5, 26-6 in the enterprise's gateway network.
  • In addition, the [0089] enterprise directory 90 at an individual location may include a replica of a partition from another location in the network. This can be done, for example, to facilitate set up of calls between locations which have a high volume of telephone calls. The arrows in FIG. 3A indicate the locations of replicas of partitions which are included in the enterprise directories at other locations. In the configuration illustrated in FIG. 3A, a replica of the partition P1′ at the first location is included in the enterprise directory 90-2 at the second location. Also, both the third and sixth locations have replicas R3′, R6′ of each other's partitions. As indicated above, the replicas of the partitions are automatically synchronized, whereby changes to entries in a partition at one location, are sent to other locations having a replica of the respective partition.
  • Referring again to FIG. 3, the [0090] gateway database 51 is an open database connectivity (ODBC) compatible database. The gateway database 51 contains enterprise white pages, frequent contact information, gateway routing tables, individual user follow me records, and a call log. The gateway database 51 records are fully indexed to provide necessary real-time performance. The enterprise directory 90 is the source of the white pages, and frequent contact and raw routing tables. This information is separately maintained in the gateway database because commercially available implementations of an enterprise directory, e.g. NDS, are not indexed, and are therefore not easily searchable. The gateway database 51 is indexed to facilitate the availability of the data. The data is obtained from the enterprise directory 90 and passed to the gateway database 51 by the dredger 107. The gateway database 51 also includes an operational routing table, user follow me and call log data which are created within the gateway server 26.
  • The [0091] gateway database 51 runs on an ODBC compliant database application. Suitable database applications include, for example, Jet, which is included with Windows NT 4.0, and Oracle 8.
  • The preferred embodiment of the invention includes the X.500 compatible enterprise directory. However, in installations which do not have an X.500 compatible enterprise directory, the alternative embodiments of the gateway network of the invention may include other database configurations. For example, one alternate embodiment may be used in systems which have an SQL Server database. The schema extensions may be added to the existing data structures in the SQL database, or a new, comprehensive schema may be established. In a second alternative embodiment, the enterprise directory includes a database designated the master database at a first location, and duplicate databases, designated slave databases at the remaining locations in the gateway network. In this master-slave configuration, all database administration is performed on the master database. Updates to the master database are exported to a file which is sent to the other locations and imported into the slave databases. The dredging and synchronization process would be the same as for an X.500 compatible enterprise directory. The [0092] database cache 108 is a repository of information contained in RAM in the gateway server 26. The database cache includes data duplicated from the gateway database 51 which data is required to be in RAM to support the performance of the gateway server, and also transient/dynamically changing data, e.g. idle/busy status of users' telephones. Much of the data in the database cache 108 is indexed for rapid retrieval.
  • The [0093] gatekeeper agent 52 is the equivalent of an H.323 gatekeeper client. The gatekeeper agent 52 interacts with the gateway gatekeeper 53 for address translation, e.g. PST NETWORK telephone number to IP address of a remote destination gateway server or H.323 telephone.
  • The [0094] gateway gatekeeper 53 is an embedded equivalent of an H.323 gatekeeper. The gateway gatekeeper 53 services the request for address translation received from the gatekeeper agent 52. This module uses data within the gateway database 51 for performing address translations.
  • The [0095] fax gateway 54 sends and receives faxes to and from an external fax server (not illustrated). The fax gateway 54 also translates faxes into printable files and transfers the files to a print server (not illustrated) for printing. The gateway web server application 55 supports the components of the web client server applications in the gateway network 4. A suitable web server application 55 is the Microsoft NT IIS server application which uses ActiveX server components and Active Server Pages technologies.
  • The user web server application [0096] 56 is a server application component which supports user clients by responding to HTTP user requests by the user clients. The administrator web server application 57 is a server application component which supports system administrator clients by responding to HTTP user requests by administrator clients.
  • In a preferred embodiment, the [0097] web server 92 is a Microsoft NT IIS Server. The web server 92 provides the client/server communication mechanism between browser-based clients, e.g. a user client 95 and an administrative client 96, and the gateway web server application 55, the user web application 56 and the administrator web application 57. The web server 92 may be co-located on the same server hardware as the gateway server 26 or may be on separate server hardware.
  • The user client [0098] 95 (also referred to herein as “browser”) is a browser-based graphical user interface (GUI) application which resides in a desktop workstation 24. Java and HTML are used to provide the user interface. This application interface is used to deliver integrated gateway user features. The administrator client 96 is also a browser-based GUI application, which resides in a desktop workstation 24.
  • The [0099] communications subsystem 58 presents to the gateway engine 50 an abstract appearance of telephony capabilities and activities in the system. The communications system 58 merges information from separate modules (e.g., the telephone network 65 and CTI 76 modules) to present a single logical PBX representation. The communications subsystem 58 also allows calls to be managed in a similar manner by the higher systems, whether telephone network or IP telephony in nature during initiation, while active and at completion.
  • The [0100] IP telephony module 59 is an object oriented abstraction of IP telephony. This module permits hardware from different vendors to be used, thereby isolating their differences from the higher level components of the system. The VoIP submodule 60 is an object oriented abstraction of an H.323 implementation including H.323 call control and H.323 voice transmission over an IP network. The FoIP submodule 61 is an object oriented abstraction of T.IFAX2 implementation including the fax interaction and transmission protocol over an IP network. The VoIP/FoIP driver 62 is the software layer supplied with IP telephony hardware to support the gateway server 26 application. A network interface card (NIC) 63 connection (e.g., ethernet 10baseT) provides the IP connection to the data network (not illustrated) used to transmit and receive IP telephony communications. A digital signal processor (DSP) 64 includes a microprocessor which is specialized to manage real-time digitally encoded signals. For IP telephony, the DSP 64 may include coder/decoder (codec) algorithms to compress and decompress voice signals.
  • The [0101] telephone network module 65 is an object oriented abstraction of switched circuit telephone network connections. These connection types are the foundations of today's telephone network. Elements controlled in the telephone network module 65 include station interfaces 73, trunk interfaces 66, and resources to interact with the media stream (e.g. record and playback voices, detect and generate touch tones, etc.). The telephone network module 65 represents all the call processing information and call status.
  • The [0102] trunk interface submodule 66 is an object oriented abstraction of telephone network trunk connections. Several telephone trunk types may be 5 supported including, e.g., analog trunks (Loop Start and Ground Start), T1/E1 E&M trunks, ISDN PRI trunks (T1/E1), and ISDN QSIG (T1/E1). The trunk interface submodule 66 can interface with a variety of hardware specific software drivers, e.g. analog driver 67, T1/E1E&M driver 69, PRI driver 70, and QSIG driver 71.
  • The [0103] analog trunk hardware 68 supports connecting analog trunk lines 35. The analog trunk hardware 68 provides the physical connection of this trunk type to the gateway server 26 and, in some cases, provides a connection to an internal time division multiplexing (TDM) bus 84. Suitable analog trunk hardware 68 includes the QuickNet Technologies LineJack card.
  • The DS-1 hardware (T1/E1) [0104] 72 supports connecting DS-1 trunk lines (T1/E1 E&M) 37, (PRI) 39, (QSIG) 41. The DS-1 hardware 72 provides the physical connection of this trunk type to the server and, in some cases, provides a connection to the internal TDM bus 84. The DS-1 hardware 72 card may be a T1 card which supports 24 channels (domestic US) or an E1 card which supports 30 channels (European). A suitable DS-1 hardware 72 card is the Dialogic D240.SC card.
  • The [0105] analog station hardware 75 supports connecting analog station lines 33. The analog station hardware 75 provides the physical connection to the gateway server 26 and, in some cases, provides a connection to the internal TDM bus 84. A suitable analog station hardware 75 is the Dialogic DIALOG/4 card.
  • The TDM bus [0106] 84 is an internal bus which provides a switching matrix for circuit switched telephone connections. The TDM bus 84 is used to transport voice signals or other call content from one hardware device (e.g., analog trunk 68, DS-1 H/W (T1/E1) 72, and analog station H/W 75) to another within the system. The TDM bus 84 may exist both internal to a single card as well as providing a physical connection where multiple cards may be interconnected. Suitable implementations of a TDM bus 84 include the Dialogic SC-Bus and the Natural Microsystems MVIP bus.
  • The [0107] station interface submodule 73 is an object oriented abstraction of telephone network station connections. The interactions embodied in the station interface submodule 73 represent the operation of a telephone device connected to a telephone system PBX or public network. In the embodiment illustrated in FIG. 3, the station interface submodule 73 is implemented using analog station connections (POTS telephone), however the station interface submodule 73 may also be implemented using digital telephone connections, e.g. ISDN BRI emulation. The station interface submodule 73 interfaces with a variety of station hardware specific software drivers, illustrated in FIG. 3 as an analog station driver 74.
  • The [0108] CTI module 76 provides an object oriented abstraction of a CTI link connection to a PBX. The CTI module 76 supports the delivery of events received and the receipt of call control commands in an abstract sense for processing and subsequent handoff for delivery to the PBX 34 over the CTI link 98. The CTI module 76 can support the requirements of industry standard CTI links, e.g. TSAPI, TAPI and CT Connect. The TSAPI submodule 77 supports all communications with the TSAPI driver 80. The TSAPI submodule 77 normalizes any TSAPI differences which exist among various PBX implementations into a common TSAPI abstraction, and presents this abstraction to the CTI module 76. The TAPI submodule 78 supports all communications with the TAPI driver 81. The TAPI submodule 78 normalizes any TAPI differences which exist among the various PBX implementations into a common TAPI abstraction and presents this abstraction to the CTI module 76. The CT Connect submodule 79 supports all communications with the CT Connect driver 82. The CT Connect submodule 79 normalizes any CT Connect differences which exist among the various PBX implementations into a common CT Connect abstraction and presents this abstraction to the CTI module 76.
  • The [0109] CTI server 97 is a client/server application which controls the flow of information between the gateway server 26 and the PBX 34 over the PBX CTI link 98. The core CTI server module 102 provides the central logic for the application. The CTI client driver 99 manages logical link connectivity to client applications. The CTI client driver 99 also manages a communications link 106 to the CT Connect driver 82, and brokers the information flow to and from the CT Connect driver 82. The PBX-specific driver 101 interfaces with the CTI server core module 102, translates the CTI server's 97 standard messaging to/from the particular protocol used by the specific PBX 34, and delivers the information to/from the physical connection to the PBX 34. The physical connection to the PBX 34 may be an ethernet NIC, or a dedicated physical link with a protocol, e.g. X.25 or ISDN BRI. Suitable client/server CTI implementations include Novell TSAPI, Microsoft TAPI2.1 and Dialogic CT Connect. The CTI server 97 may be a stand alone application on separate server hardware or may reside in the same server hardware as the gateway server 26.
  • The [0110] gateway server 26 integrates with telecommunications customer premises equipment (CPE), in particular PBXs for large sites and hybrid/key systems at smaller locations. The term PBX is used herein interchangeably to refer to all such systems.
  • The automatic route selection (ARS) [0111] 103 is a functional capability that the PBX 34 employs to select the preferred trunk for placing a call. PBXs may have a variety of trunks attached, including local lines, direct lines to a long distance provider, private leased lines interconnecting with other company PBXs, and virtual private networks. The ARS 103, sometimes also called least cost routing (LCR), reviews the number dialed, and identifies a preferred trunk. If the preferred trunk is busy, the ARS 103 will proceed to a subsequent choice. The ARS 103 then adds or deletes digits to condition the number dialed and transmit the call over the selected line. This feature is also available on some hybrid/key systems. In a preferred embodiment of the invention, the ARS 103 is configured to route calls destined across the gateway network to the gateway server as the preferred first choice. The PBX 34 uses trunks to connect to the PST NETWORK CO and to interconnect to other PBXs. Various types of trunks may be used, including analog, T1, E1, ISDN PRI, and QSIG. In a preferred embodiment, the gateway server 26 can support all the trunk types listed.
  • A PBX station line is a connection for a telephone device. PBXs may support several types of telephone devices, including analog (POTS), proprietary digital stations, and ISDN terminals. The [0112] gateway server 26 may use analog station lines 33 to interface with the PBX.
  • Enterprise Directory Schema Extensions
  • The integrated computer telephone system introduces schema extensions in industry standard enterprise directory services systems to support IP telephony. While the description of the schema extensions will be presented in terms of NDS, it is understood that the schema extensions are applicable to other industry standard directory systems. [0113]
  • The schema extensions enhance the NDS base schema so that the schema supports the Directory Services requirement for an ITU H.323 Recommendation based IP telephony network. In addition to H.323 support, the schema extensions enable the H.323 gatekeepers in an H.323 IP telephony network to automatically find each other. This capability is not currently specified and supported by ITU H.323 Recommendation v.1. The schema extensions also enable the gateway server to provide additional features, e.g. caller ID and call filtering. The schema extension includes additional NDS objects and additional NDS attributes. The schema enhancement defines the relationships among the additional NDS objects and attributes. The additional NDS objects for H.323 include H.323 Gateway, H.323 Gatekeeper, and H.323 Multipoint Control Unit (MCU). The additional NDS attributes are applicable to the additional H.323 objects and existing NDS objects. [0114]
  • Table 1 lists the attributes which are included in the NDS enterprise directory schema extensions in a preferred embodiment of the invention. Table 1 includes the name of each attribute added to the schema, a brief definition of each attribute, and an indication as to whether the attribute is added to support the use of the enterprise directory to support IP telephony or to support the advanced features [0115]
    TABLE 1
    New Attributes Included in the Enterprise Directory Schema Extension
    Attribute Definition Supports
    Attendant Specifies the telephone number for a gateway Advanced
    Number server for Finder activation/deactivation, Features
    HopOn from PST NETWORK, etc.
    Auto Attendant Specifies the dialing string for the auto Advanced
    Prefix attendant preceding the extension number Features
    (null value if no autoattendant and Direct
    Inward Dialing is available for the PBX).
    CallAlert Specifies the time-out period, in seconds, Advanced
    Timeout for Call Alert inaction for a gateway server. Features
    Call Log Specifies the duration, in days, of the call Advanced
    Configuration log parameters for a gateway server, Features
    including Call Log Duration, Call Log Type
    1, Call Log Type 2, . . . (where Call Log
    Type i specifies the event logging level for
    a gateway server. There can be multiple
    event logging levels.).
    WhitePages Specifies the scope of the whirte pages in Advanced
    Subtree the context of the enterprise directory. The Features
    gateway server catalog contains WhitePages
    and other information derived from the
    enterprise directory. This attribute
    establishes the directory contents that the
    WhitePages contain.
    Cellular Specifies the user's cellular phone number. Advanced
    Phone Features
    CTI Specifies the CTI link between the gateway Advanced
    server and the PBX, including CTI Type, Link Features
    Name, and Server Name.
    CTN Access Specifies the special trunk access code to Advanced
    Code the Corporate Telephony Network, e.g. “8” Features
    (null value if the PBX does not support CTN
    dialing).
    CTNLocation Specifies the location ID(s) for the gateway Advanced
    ID network in the Corporate Telephony Network Features
    numbering plan.
    CTN Numbers Specifies the Corporate Telephony Network Advanced
    Table numbers (or number patterns) represented by Features
    the gateway network for its PBX and its
    satellite PBXs (i.e. PBXs connected to
    the gateway server indirectly through another
    PBX, and which use the gateway server to get
    on to the IP network), including Location
    ID, Extension Range, PST NETWORK pattern,
    and, Comments (for the system administrator).
    CTN Trunk Specifies the translation table for Advanced
    Translation converting from the PBX numbering format to Features
    CTN canonical format, including Trunk Group
    ID, Trunk ID Range, Number of Digits to
    Delete, Digit to Prepend, and Trunk Card ID,
    and Comments.
    FallBack Specifies the fallback number for a gateway Advanced
    Number server. This is the PST NETWORK number Features
    that the gateway servers use to call each
    other for fallback to PST NETWORK.
    GateKeeper Specifies the default GateKeeper with which IP
    an entity such as Gateway and H.323 Terminal Telephony
    should register. Entities are allowed to
    register with GateKeeper for the H.323 Zone
    to which the entity belongs.
    GatekKeeper Identifies the GateKeeper Exchange with IP
    Exchange which a GateKeeper is associated. Telephony
    Gateway Specifies the gateway associated with a IP
    gateway network entity, e.g. a user. Telephony
    Gateway List Specifies the gateway servers associated with IP
    a GateKeeper. Telephony
    Home Phone Specifies the user's home phone number. Advanced
    Features
    HopOff Specifies whether Hop-Off to PST NETWORK Advanced
    Enabled is enabled for a gateway server. Features
    HopOff PST Specifies the PST NETWORK number patterns Advanced
    NETWORK for hop-off to PST NETWORK for the gateway Features
    Patterns server. Only PST NETWORK numbers which
    match these patterns can be reached via hop-
    off from this gateway server. This attribute
    facilitates the automatic routing
    configuration for the gateway network.
    HopOn Specifies whether Hop-On from PST Advanced
    Enabled NETWORK is enabled for a gateway server. Features
    HopOn for OffNet Specifies the list of users, groups, or Advanced
    Call List containers authorized to access Hop-On for Features
    Off-Net calls.
    License Contains the license data for a gateway Advanced
    network, including Serial Number and License Features
    Count.
    Manual Fallback Specifies code (a combination of multiple Advanced
    Code telephone keypad keys) for fallback to PST Features
    NETWORK (null value if manual fallback is
    disabled).
    Maximum Specifies the maximum number of outstanding Advanced
    CallBacks Callback on Busy requests for each user of a Features
    per gateway server (zero if callbacks are not
    User allowed, no value if no limit on the number
    of callback requests).
    Office Fax Identifies the user's office fax number. Advanced
    Features
    Office Phone Identifies the user's office telephone Advanced
    number. It is used for providing Caller ID, Features
    including CTN On-Net Number and PST NETWORK
    Number.
    Pager Identifies the user's pager number. Advanced
    Features
    Passcode Specifies user passcode for the gateway finder Advanced
    activation/deactivation user authentication Features
    from a telephone.
    PBX Specifies the PBX configuration information Advanced
    Information which is used by the gateway server, including Features
    PBX Type, Station to CO Trunk Access Code,
    Station to Gateway Server Trunk Access Code,
    Gateway Server to Local Trunk Access Code,
    Gateway Server to Toll Trunk Access Code,
    and DISA Access Code.
    PBX Station Specifies the Station Line interface between Advanced
    Interface the gateway server and the PBX, including Features
    Card ID, Card Name, Port Number, For
    Attendant Yes/No, and Fallback Yes/No.
    PBX Trunk Specifies the Trunk Line interface between Advanced
    Interface the gateway server and the PBX, including Features
    Trunk Card ID, Trunk Type, Trunk Protocol,
    and Trunk Card Name..
    PST Specifies the PST NETWORK codes for a Advanced
    NETWORK gateway server, including E164 Country Code, Features
    Codes E164 Area Code, International Access Code,
    and Long Distance Access Code.
    Desktop CTI Specifies the number of licenses installed Advanced
    License for users who are authorized to access this Features
    Count class of service, i.e. provided with access
    to CTI capabilities from the desktop
    browser. (This value may be for reference
    only.)
    Desktop CTI Specifies the list of users, groups or Advanced
    License List containers who are authorized this class of Features
    service, i.e. provided with access to CTI
    capabilities from the desktop browser.
    Finder Specifies the acceptance code for answering a Advanced
    Acceptance redirected call using this class of service. Features
    Code
    Finder License Specifies the number of licenses installed Advanced
    Count for users who are authorized to access this Features
    class of service, i.e. who may have calls
    forwarded to alternate telephone numbers.
    (This value may be for reference only.)
    Finder Specifies the list of users, groups or Advanced
    License List containers who are authorized this class of Features
    service, i.e. who are authorized to have
    calls forwarded to alternate telephone
    numbers.
    Mobile Specifies the number of licenses installed Advanced
    License for users who are authorized this class of Features
    Count service, i.e. who may operate a portable
    computer as a virtual desktop from a remote
    telephone. (This value may be for reference
    only.)
    Mobile Specifies the list of users, groups, or Advanced
    License List containers who are authorized this class of Features
    service, i.e. authorized operate a portable
    computer as a virtual desktop from a remote
    telephone.
    UEP Domain Specifies the gateway network Uniform Advanced
    Extension Plan domain. Features
    UEP Domain Contains a list of all the UEP domains in Advanced
    List the Corporate Telephony Network. Features
    User Specifies the user preferences for the gateway Advanced
    Preferences network, including Screen Pops On/Off, Screen Features
    Pops Audible On/Off, Screen Pops Size
    Large/Small, and Number of Call Log Entries.
    VoIP Specifies the address parameters associated Advanced
    Address with the VoIP subsystem in the gateway server, Features
    Parameters including VoIP Internet Address, VoIP
    Intranet Address, and VoIP Port Number.
    VoIP Encoding Specifies the VoIP encoding parameters, IP
    including TxCoder (voice CODEC for Telephony
    transmitting), RxCoder (voice CODEC for
    receiving), volume (AGC for VoIP
    transmission), frame size (in milliseconds),
    and frames per packet (number of VoIP frames
    per UDP packet).
    VoIP Hardware Specifies the hardware that is installed in IP
    the gateway server, including Card Type, Telephony
    Card ID, and Card Name.
    VoIP QOS Specifies the QoS parameters for VoIP, IP
    Parameters including VoIP QoS Detection (interval for Telephony
    checking VoIP QoS) and VoIP QoS Threshold
    (threshold based on which the gateway server
    triggers fallback to PST NETWORK, including
    Lost Packets, Packets Out Of Order, and
    Round Trip Delay).
    H.323 Zone Identifies a human readable H.323 Zone name IP
    with which a GatekKeeper is associated. Telephony
  • Table 2 lists object classes which are included in the NDS enterprise directory schema extensions in a preferred embodiment of the invention. Table 2 includes the name of each object class added to the schema, a brief definition of each object class, a list of the attributes listed in Table 1 which, in a preferred embodiment of the invention, may be associated with the respective object classes, and an indication as to whether the object class is added to support the use of the enterprise directory to support IP telephony or to support the advanced features. [0116]
    TABLE 2
    New Object Classes Included in theEnterprise Directory Schema Extension
    Object Schema Extension
    Class Definition Attributes Supports
    GateKeeper The GateKeeper class License IP Telephony
    represents an H.323 WhitePages Subtree and
    GateKeeper entity. There H.323 Zone Advanced
    may be multiple GateKeeper Exchange Features
    GateKeepers in a gateway Gateway List
    network.
    Gateway The Gateway class License IP Telephony
    represents an H.323 CTN Location ID and
    Gateway entity. A Gateway CTN Numbers Table Advanced
    is associated with only one CTN Access Code Features
    GateKeeper. The Gateway Auto Attendant Prefix
    object also contains the CTN Trunk Translation
    routing information for this UEP Domain
    Gateway. HopOff PST NETWORK
    Pattern
    VoIP Address Parameter
    VoIP Encoding
    VoIP QoS Parameters
    VoIP Hardware
    GateKeeper
    PST NETWORK Codes
    Fall Back Number
    Attendant Number
    Call Log Configuration
    Call Alert Timeout
    Maximum CallBacks Per
    User
    Manual Fallback Code
    Finder Acceptance Code
    Hop On Enabled
    Hop Off Enabled
    PBX Trunk Interface
    PBX Station Interface
    CTI
    PBX Information
    HopON for OffNet Call List
    MCU The MCU class represents License IP Telephony
    an H.323 MCU entity. An GateKeeper
    MCU is associated with
    only one GateKeeper.
    GateKeeper The GateKeeper Exchange License IP Telephony
    Exchange object contains a list of all Desktop CTI License and
    GateKeepers in the NDS Count Advanced
    Tree. There can be only a Desktop CTI License List Features
    single GateKeeper Finder License Count
    Exchange object in the Finder License List
    entire NDS Tree. The Mobile License Count
    Distinguished Name of this Mobile License List
    object is administrator UEP Domain List
    defined when the very first
    GateKeeper is installed in
    the NDS Tree.
    Subsequently, the
    Distinguished Name of this
    object has to be specified
    when the GateKeepers are
    installed.
    UEP Specifies the list of GateKeeper Exchange Advanced
    Domain Gateways belonging to this Features
    domain.
    User The User object represents GateKeeper IP Telephony
    users of network services Gateway and
    including the gateway Passcode Advanced
    network service. Office Phone Features
    Cellular Phone
    Pager
    Home Phone
  • Gatekeeper Catalog Description
  • The gatekeeper catalog is an important part of the [0117] gateway database 51. It supports many of the features which are unique in the integrated voice gateway system of the invention, e.g. follow me and white pages. The contents of the gatekeeper catalog tables are described in the following tables. In preferred embodiments, certain of the catalog tables, e.g. the Gateway Table (shown in Table 6 below), may be divided into a plurality of smaller tables to facilitate access to the information contained in the tables.
  • Custom Date Table
  • The Custom Date table contains a list of custom dates for a specific Follow Me rule. Table 3 describes the contents of the Custom Date table. [0118]
    TABLE 3
    Custom Date Table
    Attribute Description
    CustomDateID Unique ID used to identify this record
    FollowMeID Link to FollowMe entry
    CustomDate A custom date value
  • Follow Me Table
  • The Follow Me table contains a row for each Follow Me rule. A Follow Me rule is constructed by joining the Follow Me table with the Follow Me Filter table and the Custom Date table. Table 4 describes the contents of the Follow Me table. [0119]
    TABLE 4
    Follow Me Table
    Attribute Description
    FollowMeID Unique ID used to identify this record
    DN User this FollowMe rule corresponds to
    FollowMeType DayOfWeek or Override
    StartDate Start date for this FollowMe rule
    EndDate End date for this FollowMe rule
    StartTime Start time for this FollowMe rule
    EndTime End time for this FollowMe rule
    Monday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Tuesday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Wednesday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Thursday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Friday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Saturday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    Sunday Yes/No field. True (Yes) indicates that
    this FollowMe rule applies to this day of
    the week
    DestinationType Specifies the type of destination
    telephone number
    DestinationTAddress Specifies the destination telephony
    address to forward call to
    DestinationDescription User defined text
    DestinationName User defined text
    FilterEnabled Yes/No field. True (Yes) indicates that the
    source filter (if defined) should be used
  • Follow Me Filter Table
  • The Follow Me Filter table specifies a source filter for a specific Follow Me record. Table 5 describes the contents of the Follow Me Filter table. [0120]
    TABLE 5
    Follow Me Filter Table
    Attribute Description
    Filter ID Unique ID used to identify this record
    FollowMeID Connects to the FollowMe table
    IncludeItem Indicates whether this item should be
    included in the source filter or not
    TaddressType Type of Telephony Address number string
    Taddress The calling Telephony Address
    Name User defined string
  • Gateway Table
  • The Gateway table contains a record for each gateway server defined in the gateway network. The directory dredger searches the directory and populates this table. Table 6 describes the contents of the Gateway table. [0121]
    TABLE 6
    Gateway Table
    Attribute Description
    License License data for a gateway network
    CTN Location ID Location ID for the gateway network
    in the Corporate Telephony Network
    numbering plan
    CTN Numbers Corporate Telephony Network
    Table numbers (or number patterns)
    represented by the gateway network
    for its PBX and its satellite PBXs
    CTN Access Trunk access code to the Corporate
    Code Telephony Network
    Auto Attendant Dialing string for the auto attendant
    Prefix preceding the extension number
    CTN Trunk Translation table for converting from
    Translation the PBX numbering format to CTN
    canonical format
    UEP Domain Gateway network Uniform Extension
    Plan domain.
    HopOff PST PST NETWORK number patterns for
    NETWORK hop-off to PST NETWORK for the
    Patterns gateway server
    VoIP Address Address parameter associated with
    Parameter the VoIP subsystem
    VoIP Encoding VoIP encoding parameters
    VoIP QoS QoS parameters for VoIP
    Parameters
    VoIP Hardware VoIP hardware installed in the
    gateway server
    GateKeeper Default GateKeeper with which the
    gateway should register
    PST NETWORK PST NETWORK codes for the
    Codes gateway server
    Fall Back Fallback number for the gateway
    Number server
    Attendant Telephone number for a gateway
    Number server for Finder
    activation/deactivation, Hop On from
    PST NETWORK, etc.
    Call Log Duration, in days, of the call log
    Configuration parameters
    Call Alert Time-out period for Call Alert inaction
    Timeout
    Maximum Maximum number of outstanding
    CallBacks Per Callback on busy requests for each
    User user
    Manual Fallback Code for fallback to PST NETWORK
    Code
    Finder Acceptance code for answering a
    Acceptance redirected call
    Code
    Hop On Enabled Whether Hop-On is enabled for the
    gateway server
    Hop Off Enabled Whether Hop-Off to PST NETWORK
    is enabled
    PBX Trunk Trunk line interface between the
    Interface gateway server and the PBX
    PBX Station Station line interface between the
    Interface gateway server and the PBX
    CTI CTI link between the gateway server
    and the PBX
    PBX Information PBX configuration information
    HopON for List of users, groups or containers
    OffNet Call List authorized to access Hop-On for Off-
    Net calls
  • Frequent Contacts Table
  • The Frequent Contacts table contains the frequent contacts for each of the users in the User table. Table 7 describes the contents of the Frequent Contacts table. [0122]
    TABLE 7
    Frequent Contacts Table
    Attribute Description
    FrequentContactsID Unique ID used to identify this record
    DestinationDN The DN that this Frequent Contact
    refers to
    FeDN Owner of this Frequent Contact
    record
    Description User defined text describing this
    Frequent Contact entry
  • Routing Table
  • The Routing table contains supported numbers by gateway server. This table along with the Gateway table is used to build a routing table. Table 8 describes the contents of the Routing table. [0123]
    TABLE 8
    Routing Table
    Attribute Description
    ID Unique ID used to identify this record
    DN Associated Gateway distinguished
    name
    CTNLocationID CTN number identifying the Gateway
    RangeType CTN or HopOff
    FromRange Beginning range of the local segment
    of the E164 Phone Number or the
    extension number
    ToRange Ending range of the local segment of
    the E164 Phone Number or the
    extension number
    From PST Beginning range of the
    NETWORKRange Corresponding PST NETWORK
    address for the extension
    ToPST Ending range of the Corresponding
    NETWORKRange PST NETWORK address for the
    extension
    HopOffAreaCode When range type is ‘HopOff’, the area
    code of the E164 number
    HopOffCountryCode When range type is ‘HopOff’, the
    country code of the E164 number
    Comment User comment
  • White Pages
  • The White Pages contains a record for each user in a specified Zone. It is also possible for this table to contain all users in the gateway network. This table can be used as an enterprise wide white pages. Table 9 describes the contents of the White Pages. [0124]
    TABLE 9
    White Pages
    Attribute Description
    ID Unique ID used to identify this record
    DN User distinguished name
    CN User common name
    EmployeeNumber User's employee number
    DepartmentName User's department
    FirstName First name of user
    MiddleName Middle initial
    LastName User last name
    OfficeExtension User office telephone extension
    Number number
    Office PST User office PST NETWORK
    NETWORK telephone number
    Number
    Office Fax User office fax number
    Number
    CellularPhoneNumber User cellular telephone number
    HomePhoneNumber User home telephone number
    Pager User pager number
    Title User title
    EmailAddress User email address
    PostalAddress User postal address
    City User city
    StateOrProvince User state or province
    PostalCode User zip/post code
    Country User country
    Location User location
    DepartmentID User department
    GatewayName Gateway corresponding for this user
    DefaultGatekeeper Default Gatekeeper for this user
    Passcode User passcode
    Preferences User preferences
    FollowMeEnabled Yes/No field. True (Yes) implies that
    follow me is enabled for this user
  • Private Contacts
  • The Private Contacts table contains records of contacts users want to track, but who are not listed in the White Pages. The formats in the fields of the Private Contacts table are identical to those of the fields in the White Pages. [0125]
  • Temporary Contacts
  • When a user wishes to view the user's frequent contacts, a temporary table is built which contains only the user's frequent contact information. This table is constructed from the White Pages and Private Contacts table. The formats of the fields of the Temporary Contacts table are identical to those of the fields in the White Pages. [0126]
  • Numbering Plan
  • The numbering plan is the equivalent of addressing for telephone numbers. In a company's voice network, there are various mechanisms for addressing a call to another party, e.g. a PST NETWORK number and an extension number. There are also various access mechanisms for the respective addressing schemes. Current large PBXs are flexible in their numbering plans, and can support numerous types of dialing methods. In Uniform Numbering Plans (UNP), telephones at any of a number of sites may be dialed simply by dialing an extension number. Such uniform numbering plans may allow for extensions of different lengths (i.e., number of digits). In an Enterprise Telephone Number (ETN) plan, telephones at other sites in the company may be dialed using an access code, commonly an “8”, followed by a location code (typically 3 digits), followed by the extension. In a PST NETWORK Numbering plan, telephones at other sites may be dialed by dialing the public telephone number (per the ITU E.164 specification). In a trunk group access numbering plan, telephones at a particular remote site may be dialed by dialing an access code for a group of trunks, followed by the extension number. [0127]
  • The UNP and ETN methods are commonly limited to single vendor PBX solutions. Key systems are far more limited in their numbering plan capabilities. Key systems typically support PST NETWORK dialing and perhaps Tie Trunks, but do not support UNP or ETN methods. [0128]
  • The gateway server facilitates a transparent installation with respect to the enterprise's existing numbering plan. The gateway network permits users to continue dialing according to the same numbering plan they use with the PBX alone. the ARS/Numbering Plan routing and digit manipulation tables are reconfigured to deliver calls to remote locations to the gateway server. Thus, the gateway server does not require that the numbering plan be changed. [0129]
  • In a voice gateway system, as illustrated in FIG. 1, the gateway servers can support UNP and ETN methods, and can support these methods in multi-vendor environments which include PBXs and/or hybrid/key systems over an IP network. The gateway network classifies telephone numbers as PST NETWORK (E.164), ETN (Location+Extension) and UNP (Extension). The three plans are merged into a single numbering scheme for the enterprise by adding configurable prefixes to the PST NETWORK and ETN numbers. For a PST NETWORK number, the PST NETWORK prefix (typically “9”) is appended to the PST NETWORK number. For ETN numbers, the ETN prefix (typically “8”) is appended to the telephone number. [0130]
  • The telephone numbers may undergo pre- and post-processing as they traverse the gateway network depending on the capabilities of the PBXs and the preferences of system administrators. For example, if a caller PBX has the capability, and the system administrator chooses to configure the PBX such that all calls are delivered to the gateway server with the telephone number in the gateway network format, the call can be compared directly against the routing tables for routing to the destination. If a PBX does not have the capability, or if the system administrator chooses not to configure the tables in the PBX, then the caller gateway server can perform incoming digit translation. The preprocessing can be set up to apply the same rules to all trunks, or can apply, e.g. PST NETWORK translation to calls on trunks [0131] 1-8, and ETN translation to calls on trunks 9-16. The preprocessed numbers can then be compared against the routing tables for routing to the destination.
  • At the destination, if the called PBX has the capability, and the system administrator chooses to configure the PBX to receive call with the telephone number in the gateway network format, then the gateway server delivers the calls without the need for postprocessing the telephone numbers. If the PBX does not have the capability to receive call with the telephone number in the gateway network format, or if the system administrator chooses not to so configure the PBX, then the called gateway server can perform outgoing digit translation. The called telephone number associated with each call received may be formatted to deliver an extension, and ETN number or a PST NETWORK number, with appropriate prefixes, for the particular PBX. [0132]
  • Hybrid/key systems with analog trunks typically have an automated attendant unit which answers calls and prompts the caller to enter an extension to reach a called telephone. This is known as a two stage dialing scheme, and is commonly used in smaller office environments. The gateway server permits the caller to directly dial a called telephone without having to deal with an automated attendant. The caller may start the call either by dialing an ETN number (8+LOCATION+Extension), a UNP number (extension) or place the call from the white pages directory via the browser interface. The called gateway may be configured to deliver the call directly to the called telephone. When the call arrives at the gateway server, the gateway server alerts the analog trunk. When the call is answered by the PBX, the gateway server plays the configured prefix string followed by the extension number. The call will then alert directly at the called telephone. The caller will hear normal ringing throughout the process until the called telephone is answered. The net effect is that the invention reduces two-stage dialing into a one-stage addressing method. [0133]
  • In the following descriptions of several functions of the integrated voice gateway system of the invention, reference will be had to FIGS. 447 and 50-[0134] 58 which illustrate the configuration of the gateway networks and the components which support the functions described. In the interest of simplifying the FIGS., only those components which are necessary to describe the respective functions are depicted in the corresponding FIGS. For example, the telephone network software and hardware (FIG. 3) will be represented by the respective software drivers (e.g., analog driver 67 representing the trunk 66, analog driver 67 and analog trunk hardware 68).
  • In certain instances in which signals are depicted, although connections between components are not explicitly depicted, reference numerals coupled to the signals are understood to, be referring to the described interface (e.g., station analog port, trunk, etc.). In the descriptions of the functions, a telephone which is coupled to a PBX in a company's gateway network will be referred to as a gateway telephone, and a telephone which is outside the company and is coupled to the PST NETWORK will be referred to as a PST NETWORK telephone. The gateway network and its components at the calling party's end will generally be referred to as the “caller” components, e.g. “caller gateway server”. The gateway network and its components at the called party's end will generally be referred to as the “called” components, e.g. “called gateway server”. [0135]
  • In the description of the operation of an integrated voice gateway system of the invention in FIGS. [0136] 4-47 and 50-58, in general components comprising the gateway network at the caller end of a telephone call are identified by their respective reference numerals shown in FIGS. 2-3 (e.g. caller gateway server 26) and components comprising the gateway network at the called end of a telephone call will have as their reference numerals 100 plus the respective reference numeral of the corresponding component of gateway network at the caller end (e.g. called gateway server 126). Additional components outside both the caller gateway network and the called gateway network will have as their reference numerals 200, 300, 400, etc., plus the respective reference numeral of the corresponding component of gateway network at the caller end (e.g. PST NETWORK telephone 238).
  • In FIGS. [0137] 4-47 and 50-58, unless otherwise specified in a particular method or scenario, the interface between the PBX and the gateway server may be illustrated as an analog trunk interface and the telephone drivers in the gateway servers may be illustrated as analog drivers. However, as illustrated in FIG. 3 and described in reference to FIG. 3 and elsewhere herein, the interface between the PBX and the gateway server may include analog trunk, DS-1 (T1/E1, PRI, QSIG) and/or analog station lines, with each interface supported by a corresponding telephone driver. Therefore, the illustration of the interface between the PBX and the gateway server as an analog trunk and the telephone drivers in the gateway as analog drivers is by way of illustration, and in no way limits the respective described operations to the particular interface illustrated in the examples.
  • In FIGS. depicting methods or scenarios in which a call hops-on to or hops-off from a gateway network, a third telephone company central office will be identified as [0138] CO3 13.
  • In the description of the operation of an embodiment of an integrated voice gateway system of the invention with respect to FIGS. [0139] 4-58, telephone calls are generally described as being initiated by a caller lifting a handset and dialing a telephone number. Likewise, the connection is generally described as being made when a called party lifts the handset and answers the call. The integrated computer telephone system of the invention provides the user with an integrated, comprehensive, and easy to use PC Call Control capability via a web browser interface. The PC Call Control capability is described below. It is understood that all of the methods and scenarios of operation illustrated by the FIGS., and described herein, may be controlled by the user from the telephone via DTMF buttons or from the desktop workstation via the web browser interface. The PC Call Control features of the integrated voice gateway system of the invention are described below.
  • Basic PST NETWORK Call
  • In a preferred embodiment, the integrated computer telephone system of the invention provides the capability to place a telephone call from a caller gateway telephone to a called gateway telephone via the PST NETWORK. Referring to FIG. 4, a caller (not illustrated) initiates a call by picking up the handset on the [0140] caller telephone 38 and dialing an ARS code, e.g. 9, plus a PST NETWORK telephone number or other digit string. The caller PBX 34 reviews the dialed number against the information in the ARS tables to select a trunk group. It may then modify the digit string, deleting and inserting digits for proper addressing. The caller PBX 34 delivers the call to CO1 12. CO1 12 routes the telephone call through the PST NETWORK 16 to CO2 14. CO2 14 delivers the call to the called PBX 134 via an available trunk and may transmit a subset of the called telephone number. The called telephone 138 rings and is answered by the called party (not illustrated).
  • Basic VoIP Call
  • In a preferred embodiment, the gateway network provides the capability to place a telephone call from a caller gateway telephone to a called gateway telephone via an IP network. This is referred to herein as a VoIP call. It is also referred to as “Inter-PBX Toll Bypass,” because, as the term indicates, a long distance toll between remote PBXs is avoided by using the IP network. [0141]
  • Referring to FIG. 5, a caller (not illustrated) initiates a call by picking up the handset on the [0142] caller telephone 38 and dialing an ARS code, e.g. “9” for an off-net call or “8” for an on-net call, plus a PST NETWORK telephone number or other digit string. The caller PBX 34 reviews the digital number against the information in the ARS tables and selects a trunk group 35 coupled to the caller gateway server 26. The caller PBX 34 may modify the dialed digit string, deleting and inserting digits for proper addressing on a trunk in that group. The caller gateway analog driver 67 receives the call. The caller gateway server 26 performs internal operations to determine the IP address of the called gateway server 126. Referring again to FIG. 3, within the caller gateway server 26, the gateway engine 50 requests the gatekeeper agent 52 to get an address. The gatekeeper agent 52 places an H.323 compliant request to the gateway gatekeeper 53. The gateway gatekeeper 53 references tables in the gateway database 51 to determine the called gateway server 126 and its address. The caller gateway VoIP driver 62 transmits packets addressed to the IP address of the called gateway server 126 via the IP network 18. The caller gateway server 26 and called gateway server 126 communicate via the IP network 18 to initiate a duplex H.323 call. The called gateway server 126 then selects a telephone trunk 135 to deliver the call to the called PBX 134. The called gateway server 126 initiates the call, including the called telephone number, to the called PBX 134. The called PBX 134 interprets the received telephone number to select a called telephone 138 to ring. The called telephone 138 rings and when answered by the called party (not illustrated) the connection is made. The connection event may propagate through the system.
  • Hop-off to PST NETWORK Call
  • In a preferred embodiment, the gateway network provides the capability to place a telephone call to an outside-of-the-company PST NETWORK destination via the IP network. A user in the company can call a long distance PST NETWORK destination by dialing the telephone number as usual. The caller gateway network will set up the call to be carried via the IP network to a called gateway server within the company which is closest to the destination telephone, and make a PST NETWORK connection to “hop-off” to the PST NETWORK destination. [0143]
  • The system administrator for each gateway network determines which local hop-off destinations the gateway network will support and configures the gateway server accordingly. The system administrator also configures the gateway server to identify those gateway servers from which the local gateway server will accept hop-off calls. The gateway servers can be configured to support hop-off to local PST NETWORK calls and hop-off to long distance PST NETWORK calls. The ARS table of the PBX in the originating gateway network is configured accordingly for the hop-off calls to be routed to the gateway server. [0144]
  • In preferred embodiments of the invention, there are several different methods in which hop-off to PST NETWORK may be implemented. The different methods take into consideration variations in the configurations of gateway networks at different installations, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity. [0145]
  • Table 10 identifies differences in the configuration for three hop-off to PST NETWORK methods in preferred embodiments of the invention. [0146]
    TABLE 10
    Hop-off to PST NETWORK Methods
    Analog
    T1 trunk station
    channels per ports per
    hop-off hop-off
    CTI call (at call (at PBX
    Method Transparent support destination) destination) support
    A Transparent No 0 1 None
    B Transparent No 1 1 (only Trunk to
    during trunk
    setup) transfer
    C Transparent No 1 0 Trunk to
    trunk
    call
  • Hop-off to PST NETWORK will be described with respect to FIGS. [0147] 6-14. FIGS. 6-14 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective hop-off to PST NETWORK methods. Connections between the components are not shown in order to simplify the FIGS. The set up of the hop-off and the resulting PST NETWORK call are depicted by a heavy solid line. An arrow head on a solid line indicates the direction of data flow or call flow, as appropriate. A solid line without an arrow head indicates the data or call flows in both directions.
  • Hop-off to PST NETWORK method “A”, listed in Table 10, implements a transparent hop-off to PST NETWORK. One analog station port is used at the destination end of the call during hop-off to PST NETWORK and for the remainder of the call. No T1 trunk channels are required for the hop-off. Method “A” does not use CTI support. [0148]
  • Hop-off to PST method “A” will be described with reference to FIGS. [0149] 6-7. All steps described below are at the called gateway network 104. Referring to FIG. 6, upon receiving a VoIP call from the caller gateway server 26, the analog station driver 174 in the called gateway server 126 places a call from an analog station 175 (75 in FIG. 3) to the hop-off destination called PST NETWORK telephone 238. Referring to FIG. 7, the called gateway server 126 then connects the TDM bus 84 (FIG. 3) time slot of the new PST NETWORK call with that of the incoming VoIP call, completing the hop-off to PST NETWORK call.
  • Hop-off to PST NETWORK method “B”, listed in Table 10, implements a transparent hop-off to PST NETWORK. One analog station port is used at the destination end of the call only during setup of the hop-off to PST NETWORK. One T1 trunk channel is used during setup of the hop-off and for the remainder of the call. The PBX includes trunk-to-trunk transfer capability. Method “B” does not use CTI support. [0150]
  • Hop-off to PST NETWORK method “B” will be described with reference to FIGS. [0151] 8-12. Referring to FIG. 8, upon receiving a call from the caller gateway server 26, the called gateway server 126 makes a call from an analog station 174 in the called gateway server 126 to a T1 trunk 137 in the called gateway network 104 by dialing a specified “hop-off to gateway trunk” telephone number. Referring to FIG. 9, the called gateway server 126 answers the call at the gateway trunk 137 and recognizes the call as a hop-off to PST NETWORK call. Referring to FIG. 10, the called gateway server 126 makes a hook-flash transfer to the hop-off destination telephone 238 number. Referring to FIG. 11, the called gateway server 126 hangs up the analog station 133. Referring to FIG. 12, the called gateway server 126 connects the TDM bus 84 (FIG. 3) time slot of the new hop-off call with the time slot of the incoming VoIP call.
  • Hop-off to PST NETWORK method “C”, listed in Table 10, implements a transparent hop-off to PST NETWORK. One T1 trunk channel is used during setup of the hop-off and for the remainder of the call. No analog ports are used. The PBX includes trunk to trunk call, i.e. tie trunk to CO trunk, capability. Method “C” does not use CTI support. [0152]
  • Hop-off to PST NETWORK method “C” will be described with reference to FIG. 13-[0153] 14. Referring to FIG. 13, upon receiving a call from the caller gateway server 26, the called gateway server 126 makes a call from a T1-tie-trunk channel to the called, i.e. hop-off, PST NETWORK number. Referring to FIG. 14, the called gateway server 126 connects the TDM bus 84 time slot of the new hop-off call with the time slot of the incoming VoIP call.
  • Hop-on to VoIP Call
  • In a preferred embodiment, the gateway network provides the capability to place a telephone call from a PST NETWORK telephone to a telephone on a distant gateway network via a VoIP call. This capability can be combined with the hop-off to PST NETWORK capability, described above, to enable a user to place a long distance call from a caller PST NETWORK telephone to a called PST NETWORK telephone by placing a local call to a local gateway network. The telephone call is then carried via a VoIP call between two gateway networks. Moreover, the destination gateway network for the VoIP call may be a remote gateway network or the local gateway which receives the call from the PST NETWORK telephone. [0154]
  • It will be seen below that in scenarios in which the called gateway is local to the caller telephone (scenarios C and D, below), the connection to the called telephone will not actually be a VoIP call. However, in such scenarios, the invention provides an access mechanism to the company's telephone system whereby a user must be identified and pass through a passcode security scheme. Calls placed by the user are identified by that user's caller ID (for all calls, local and remote). This feature allows companies to choose to employ hop-on whereby a toll free access number may be given to employees so that they may call into the company, and hop-off, and the billing for the call will be linked to the company's PBX rather than the user's calling card. [0155]
  • Table 11 identifies scenarios of hop-on to VoIP calls in preferred embodiments of the invention. [0156]
    TABLE 11
    Hop-on to VoIP Scenarios
    Called Called
    Scenario Telephone Gateway
    A Gateway Remote
    B PST NETWORK Remote
    (hop-off)
    C Gateway Local
    D PST NETWORK Local
    (hop-off)
  • FIGS. [0157] 15-18 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective scenarios of hop-on to VoIP. Connections between the components are not shown in order to simplify the FIGS. All four hop-on to VoIP scenarios are initiated with a common set of steps. The steps common to all four hop-on to VoIP scenarios will be described with respect to FIG. 15.
  • Referring to FIG. 15, a caller (not illustrated) at a [0158] PST NETWORK telephone 238 lifts the handset and dials a “Remote Access” telephone number for the local caller gateway network 4. The call is received at CO1 12 which alerts the caller PBX 34 with the call. The caller PBX 34 routes the call to the caller gateway server 26. The caller gateway server 26 answers the call and interacts with the caller via interactive voice response (IVR). Using dual tone multi-frequency (DTMF) touch tones, the caller responds to voice prompts which may include the caller's ID, password, etc. The caller gateway server 26 then authenticates the caller against information in the gateway database image of the NDS directory information. If the caller gateway server 26 is able to authenticate the caller, the caller gateway server 26 then provides the caller with a dial tone. The caller then dials the telephone number of the desired called telephone. Based on the dialed telephone number, the caller gateway server selects a destination.
  • In hop-on to VoIP scenario “A”, the called telephone is a gateway telephone in a remote gateway network. Scenario “A” will be described with reference to FIG. 16. The remaining steps are the same as the corresponding steps for a basic VoIP call described above. The [0159] caller gateway server 26 selects the called gateway server 126. The caller gateway VoIP driver 62 transmits packets addressed to the IP address of the called gateway network 126 via the IP network 18. The caller gateway server 26 and called gateway server 126 communicate via the IP network 18 to establish a duplex H.323 call. The called gateway server 126 then selects a telephone trunk 135 to deliver the call to the called PBX 134. The called gateway server 126 transmits the called telephone number to the called PBX 134. The called PBX 134 interprets the received telephone number to select a called telephone 138 to ring. The called telephone 138 rings and is answered by the called party (not illustrated).
  • In hop-on to VoIP scenario “B”, the called telephone is a PST NETWORK telephone located near a remote gateway network. As indicated above for the steps common to all three hop-on to VoIP scenarios, the [0160] caller gateway server 26 searches the caller gateway routing table to select a destination gateway network, and selects the called gateway network 126. The remainder of the call setup may employ any one of the three hop-off to PST NETWORK scenarios described above.
  • In hop-on to VoIP scenario “C”, the called telephone is a gateway telephone coupled to the [0161] caller gateway network 4. Scenario “C” will be described with reference to FIG. 17. The caller gateway server 26 (which is also the called gateway server) selects a telephone trunk 135 to deliver the call to the caller PBX 34 and transmits the called telephone number to the caller PBX 34. The caller gateway server 26 couples the inbound caller's trunk 35 with the trunk 135 for the called telephone 338. The caller PBX 34 interprets the telephone number to select a telephone to ring. The called telephone 338 rings and is answered by the called user (not illustrated).
  • In hop-on to VoIP scenario “D”, the called telephone is a PST NETWORK telephone located near the [0162] caller gateway network 4. Scenario “D” will be described with respect to FIG. 18. The caller gateway server 26 (which is also the called gateway server) selects a telephone trunk 135 to deliver the call to the caller PBX 34 and transmits the called telephone number to the caller PBX 34. The caller gateway server 26 couples the inbound caller's trunk 35 with the trunk 135 for the called telephone 438. The caller PBX 34 interprets the telephone number and determines that the call is for a local PST NETWORK telephone. The caller PBX 34 selects an external trunk coupled to CO1 12 and dials the destination telephone number. CO1 12 routes the call to the called telephone 438. The called telephone 438 rings and is answered by the called user (not illustrated).
  • Fallback to PST NETWORK
  • In a preferred embodiment, the gateway server constantly monitors the quality of service (QoS) during VoIP network calls using the standard realtime transport control protocol (RTCP). The QoS may be specified in terms of end-to-end delay, IP packet loss and jitter. If the QoS falls below a predetermined level set by a system administrator, the gateway server sets up an alternate connection over the PST NETWORK and switches the call to the PST NETWORK connection. [0163]
  • The caller can also initiate a fallback to PST NETWORK if the caller decides that the quality of the voice transmission has deteriorated to an unacceptable level. The caller can initiate a fallback to PST NETWORK by entering a specified DTMF key sequence on the telephone, e.g. a combination of the “star” (*) and “pound sign” (#) keys. A system administrator can configure a gateway server to allow or disallow caller-initiated fallback to PST NETWORK. [0164]
  • In preferred embodiments of the invention, there are several different methods in which fallback to PST NETWORK may be implemented. The different methods take into consideration variations in the configurations of gateway networks at different installations, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity. In addition, some of the methods allow fallback to PST NETWORK to be transparent to the user, while other methods do not provide transparent fallback to PST NETWORK. In the case of transparent fallback to PST NETWORK, the users will simply perceive that the quality of voice suddenly improves. In the case of non-transparent fallback to PST NETWORK, the conversation will be interrupted by the gateway server while the fallback to PST NETWORK takes place. Table 12 identifies differences in the configuration for methods of fallback to PST NETWORK in preferred embodiments of the invention. [0165]
    TABLE 12
    Fallback to PST NETWORK Methods
    T1 Analog
    Trunk station
    channels ports
    per per
    fallback fallback
    call (at call (at
    each each
    CTI end of end of
    Method Transparent support call) call) PBX support
    A Transparent No 1 1 Hunt group
    for gateway
    network
    analog lines
    B Transparent No 2 1 (only PST
    during NETWORK
    setup) trunk to tie
    trunk
    transfer;
    Hunt group
    for gateway
    network
    analog lines
    C Transparent No 2 0 Trunk to
    trunk call
    D Non- Yes 0 0 None (except
    Transparent CTI support)
    E Non- Yes 0 1 (only Hunt group
    Transparent during for gateway
    setup) network
    analog lines
    (in addition to
    CTI)
  • Fallback to PST NETWORK will be described with respect to FIGS. [0166] 19-43. FIGS. 19-43 depict certain components of a caller gateway network 4 and a called gateway network 104 which support the respective methods of fallback to PST NETWORK. Connections between the components are not shown in order to simplify the FIGS. An ongoing VoIP telephone call is represented by a heavy dashed line. The set up of the fallback and the resulting PST NETWORK call are depicted by a heavy solid line. Arrow heads at one end of a dashed line or solid line indicate the direction of data flow or call flow. A dashed line or solid line without an arrow head indicates the call or data flows in both directions.
  • Fallback to PST NETWORK method “A”, listed in Table 12, implements a transparent fallback to PST NETWORK. One T1 channel and one analog station port are used at each end of the call during fallback to PST NETWORK and for the remainder of the call. The PBX includes a hunt group for the gateway network analog stations. Method “A” does not use CTI support. [0167]
  • Fallback to PST NETWORK method “A” will be described with reference to FIGS. [0168] 19 to 22. Referring to FIG. 19, an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134, the caller gateway server 26 and the called gateway server 126, through the IP network 18. In fallback to PST NETWORK method “A”, when the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a call from an analog station in the caller gateway server 26 to the hunt group of analog stations in the called gateway server 126. The call initiation, and subsequent signaling, is routed from the caller station analog driver 74 through the caller PBX 34, the PST NETWORK 16 (including the respective CO's 12, 14), and the called PBX 134 to the called station analog driver 174 in the called gateway server 126. Referring to FIG. 20, the called gateway server 126 sends a “fallback ready” DTMF tone back to the caller gateway server 26. The DTMF tone is routed from the called gateway server 126 through the called PBX 134, the PST NETWORK 16 and the caller PBX 34 to the called gateway server 26. Referring again to FIG. 19, when the caller gateway server 26 receives the fallback ready DTMF tone, the caller gateway server 26 sends the original called telephone number to the called gateway server 126, and then waits for a short period, e.g. 200 milliseconds (msec), to allow the called gateway server 126 to receive the telephone number. Referring to FIG. 21, the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 (FIG. 3) time-slots of the new PST NETWORK call with that of the respective T1 channels of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16. Referring to FIG. 22, the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call. Fallback to PST NETWORK method “B”, listed in Table 12, implements a transparent fallback to PST NETWORK. Two T1 channels are used at each end of the call during fallback to PST NETWORK and for the remainder of the call. One analog station port is used at each end only during fallback to PST NETWORK. The PBX includes trunk to trunk transfer capability, including both CO trunk to tie trunk and CO trunk to CO trunk. Method “B” does not use CTI support.
  • Fallback to PST NETWORK method “B” will be described with reference to FIGS. [0169] 23 to 29. Referring to FIG. 23, an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134, the caller gateway server 26 and the called gateway server 126, through the IP network 18. In fallback to PST NETWORK method “B”, when the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a call from an analog station 73 in the caller gateway server 26 to the hunt group of analog stations in the called gateway server 126. The call initiation, and subsequent signaling, is routed from the caller station analog driver 74 in the caller gateway server 26 through the caller PBX 34, the PST NETWORK 16 (including the respective CO's 12,14), and the called PBX 134 to the called station analog driver 174 in the called gateway server 126. Referring to FIG. 24, the called gateway server 126 sends a “fallback confirm” DTMF tone back to the caller gateway server 26. The DTMF tone is routed from the caller gateway server 126 through the called PBX 134, the PST NETWORK 16 and the caller PBX 34 to the called gateway server 26. Referring again to FIG. 23, when the caller gateway server 26 receives the fallback confirm DTMF tone, the caller gateway server 26 sends the original caller and called telephone numbers to the called gateway server 126. Referring to FIG. 25, both the caller gateway server 26 and the called gateway server 126 place a hook-flash transfer to the respective caller gateway network trunk 35 and called gateway network trunk 135, respectively, by dialing a “fallback to gateway network trunk” number. Continuing to refer to FIG. 25, both the caller gateway server 26 and called gateway server 126 answer the call at the respective gateway network trunks 67, 167 and recognize the call as a fallback call. Referring to FIG. 26, both the caller gateway server 26 and called gateway server 126 then hang up the respective analog stations 74,174. Referring to FIG. 27, the called gateway server 126 sends a “fallback ready” DTMF tone to a new trunk channel for the PST NETWORK call, and then waits for a short period, e.g. 200 msec, to allow the caller gateway server 26 to receive the DTMF tone. Referring to FIG. 28, the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 (FIG. 3) time-slot of the new trunk 35 channel with that of the T1 channel of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16. Referring to FIG. 29, the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • Fallback to PST NETWORK method “C”, listed in Table 11, implements a transparent fallback to PST NETWORK. Two T1 channels are used at each end of the call during fallback to PST NETWORK and for the remainder of the call. No analog station ports are used. The PBX uses trunk to trunk call capability, i.e. tie trunk to CO trunk on the caller gateway server side, and CO trunk to tie trunk on the called gateway server side. The PBX is configured to enable a trunk to trunk call. [0170]
  • Fallback to PST NETWORK method “C” will be described with reference to FIGS. [0171] 30 to 33. Referring to FIG. 30, an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134, the caller gateway server 26 and the called gateway server 126, through the IP network 18. In fallback to PST NETWORK method “C”, when the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a call from a tie trunk channel to the tie trunk channel of the called gateway server 126. The call is initiated by dialing a specified telephone number. This step may be a multi-step process, and the implementation may be PBX specific. After initiating the call, the caller gateway server 26 waits to receive a “fallback ready” DTMF tone. Referring to FIG. 31, after the called gateway server receives the tie-trunk call, the called gateway server 126 sends the “fallback ready” DTMF tone to the caller gateway server 26. Referring again to FIG. 30, the caller gateway server 26 sends the original called telephone number to the called gateway server 126, and then waits for a short period, e.g. 200 msec. Referring to FIG. 32, the caller gateway server 26 and the called gateway server 126 then connect the respective TDM bus 84 time-slot of the new trunk channel with that of the T1 channel of the original VoIP call, thereby establishing the telephone call via the PST NETWORK 16. Referring to FIG. 33, the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • Fallback to PST NETWORK method “D”, listed in Table 11, implements a non-transparent fallback to PST NETWORK. No T1 channels are used for the PST NETWORK call after the fallback process. No analog station ports are used. The PBX uses CTI. The gateway servers exchange proprietary messages among themselves using IP sessions which are separate from those used for the voice call. [0172]
  • Fallback to PST NETWORK method “D” may be used if the IP connection between the caller gateway server and called gateway server is still good enough to support transmission of data messages. If the IP connection is not adequate for the caller gateway server and called gateway server to exchange data messages, the respective gateway servers may fallback to a PST NETWORK call using method “E” which will be described below. [0173]
  • Fallback to PST NETWORK method “D” will be described with reference to FIGS. [0174] 34 to 38. Referring to FIG. 34, an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134, the caller gateway server 26 and the called gateway server 126, through the IP network 18. In fallback to PST NETWORK method “D”, when the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a “fallback request” message over the IP network 18. The “fallback request” message contains the caller and called telephone numbers. The caller gateway server waits to receive a “fallback ready” message. Referring to FIG.35, after receiving the “fallback request” from the caller gateway server 26, the called gateway server 126 sends a “fallback ready” message to the caller gateway server 26 over the IP network 18. Referring to FIG. 36, the caller gateway server 26 manages the TDM bus 84 time slots to announce the fallback to both the caller and called parties. Referring to FIG. 37, the caller gateway server 26 uses the CTI link to place the current VoIP call on hold. The caller gateway server 26 then uses the CTI link to make a PST NETWORK call from the caller telephone 38 to the called telephone 138. The called gateway server 126 detects the incoming call and uses the CTI link to place the VoIP call on hold and to pick up the PST NETWORK call. Referring to FIG. 38, the caller gateway server 26 and called gateway server 126 then disconnect the original VoIP call.
  • In fallback to PST NETWORK method “E”, listed in Table 11, no T1 channels are used for the PST NETWORK call after the fallback process. One analog station port is used during the fallback to PST NETWORK process. The PBX includes CTI and has a hunt group for the gateway network analog stations. [0175]
  • Fallback to PST NETWORK method “E” will be described with reference to FIGS. [0176] 39 to 46. Referring to FIG. 39, an ongoing VoIP call is routed between a caller telephone 38 and a called telephone 138 through the caller PBX 34 and called PBX 134, the caller gateway server 26 and the called gateway server 126, through the IP network 18. In fallback to PST NETWORK method “E”, when the caller gateway server 26 determines that the QoS has fallen below the level specified by the system administrator, the caller gateway server 26 initiates a telephone call from an analog station in the caller gateway server 26 to the hunt group of analog stations in the called gateway server 126. Referring to FIG. 40, the called gateway server 126 sends a “fallback confirm” DTMF tone to the caller gateway server 26. Referring again to FIG. 39, the caller gateway server 26 sends the caller and called telephone numbers to the called gateway server 126. Referring to FIG. 41, both the caller gateway server 26 and the called gateway server 126 manage the TDM bus 84 time slots to announce the fallback to PST NETWORK to the caller and called parties, respectively. Referring to FIGS. 42-45, the caller gateway server 26 and called gateway server 126 use CTI to put the current VoIP call on hold (FIG. 42); then to put the new PST NETWORK call on hold (FIG. 43); and then to make a call from the analog station in the respective gateway networks to the caller (FIG. 44), and answer the call for the caller (FIG. 45). Referring to FIG. 46, the caller gateway server 26 and called gateway server 126 then hang up on the respective analog stations, and disconnect the original VoIP call.
  • Fallback to PST NETWORK During Call Setup
  • In addition to providing the capability to fallback to PST NETWORK during a VoIP call, the gateway server provides the capability to fallback to the PST NETWORK during setup of a call if the call cannot be connected through the called gateway server. Fallback to PST NETWORK during call setup may employ any of the five methods described above for fallback to PST NETWORK during a call. The method employed will depend on the configuration of the particular caller gateway network, e.g. PBX configuration and capability, CTI capabilities, additional hardware availability and voice channel capacity. However, in each of the five methods described above, fallback to PST NETWORK during call setup does not include the steps which keep the VoIP call connected until the PST NETWORK call is completed, since there is no current VoIP call to maintain. [0177]
  • The fallback to PST NETWORK during call setup capability provided by the gateway server of the invention is an improvement over current systems. In many current systems, if a caller gateway placing a call to a remote gateway cannot access the remote gateway, the caller gateway will “busy out” all of its trunks, or at least a group of trunks allocated to the remote destination. Then, as succeeding gateways find either the remote gateway or the initial caller gateway inaccessible, they will “busy out” their own respective trunks. This “domino” effect can lead to the entire network being brought down because an individual segment of the network is down. However, the gateway server avoids this problem by simply setting up the call to be routed back through the PBX. In the gateway network of the invention, there is no need for the caller gateway to busy itself out merely because the caller gateway found a remote called gateway to be inaccessible. [0178]
  • Path Replacement
  • The gateway server supports redirection of an incoming call from a first PBX, and its associated gateway server, to a second PBX, and its associated gateway server, as a result of a call forward (including call transfer, or follow-me). If both the call before (the initial call) and the call after (the final call) a call forward are VoIP calls, the final call can take a direct path between the caller gateway server and called (transfer) gateway server. This “path replacement” feature eliminates unnecessary loops after a call forward. [0179]
  • VoIP is sensitive to tandem compression, i.e., when a call is converted to and from a VoIP call twice in series during the call's transmission. Tandem compression results in a substantial drop in voice quality, often to unacceptable quality levels. In a preferred embodiment, the gateway server of the invention provides a path replacement feature which substantially improves the quality of voice transmission in a call forwarded call, and improves the utilization of gateway network resources. The quality of voice is substantially improved, because path replacement eliminates the tandem VoIP calls after a call forward. The utilization of gateway network resources is substantially improved because an unnecessary loop is avoided. After a call forward, there are two PBX's and their respective gateway servers involved in the call instead of three PBX's and gateway servers. [0180]
  • Path replacement is best described with an example: A call from Boston to Los Angeles is transferred by the Los Angeles party to a New York destination. In current systems, there would be two calls coupled in the Los Angeles PBX, i.e. a call between Boston and Los Angeles and a call between New York and Los Angeles. With IP telephony, this would result in an unacceptable tandem compression arrangement. However the gateway server recognizes that a direct and shorter path exists, namely direct communication between Boston and New York gateway networks. The gateway server replaces the routing path to place one call following the direct and shorter path, and with a single compression path. In implementing a path replacement, the gateway servers exchange messages to communicate with each other. The gateway servers use CTI to set up a path replacement. [0181]
  • Path Replacement for Call Transfer
  • A gateway network user can transfer an incoming call to another gateway network telephone. If an incoming call is a VoIP call, and if the call is transferred to a remote gateway user via VoIP, the gateway server will implement path replacement to eliminate the intermediate PBX loop back. As a result, there will be one direct VoIP link in the transferred call. [0182]
  • In the path replacement for call transfer methods describes below, the original call is placed from the caller telephone at the caller gateway network to the called telephone at the called gateway network, and is then transferred to the transfer telephone at the transfer gateway network. The call transfer may be either unsupervised or supervised, and may be initiated by the called user from a web browser CTI application or from the telephone. [0183]
  • Unsupervised Call Transfer from the Browser
  • To initiate an unsupervised call transfer, the called user clicks an “unsupervised transfer” button displayed on a browser menu. The called gateway server receives the unsupervised call transfer request, and sends a call transfer message to the caller gateway server. The caller gateway server receives the call transfer request message and sets up a VoIP call to the transfer telephone at the transfer gateway network. The caller gateway server then disconnects the original call to the called telephone. [0184]
  • Supervised Call Transfer from the Browser
  • To initiate a supervised call transfer, the called user clicks a “supervised transfer” button displayed on a browser menu. The called gateway server receives the supervised call transfer request, uses CTI to place the call on hold, and places a call from the called gateway server to the transfer telephone at the transfer gateway server. After the call to the transfer telephone is connected, the called user clicks a “transfer” menu entry to complete the supervised call transfer. The called gateway server receives the transfer request and sends a call transfer message to the caller gateway server. The caller gateway server sets up a VoIP call to the transfer telephone. The caller gateway server and transfer gateway server manage the TDM bus time slots to connect the caller telephone and transfer telephone via the new direct VoIP call. The caller gateway server and transfer gateway server disconnect the original call from the called gateway server. [0185]
  • Call Transfer from the Telephone
  • The called user may initiate a call transfer, with path replacement, using the DTMF buttons on the telephone. The called user initiates the call transfer by entering a transfer code or pressing a transfer button on the telephone, depending on the PBX configuration, and then dials the transfer telephone number. The called PBX places the current call on hold and sends the call to the called gateway server. The called gateway server receives the call from the PBX and initiates the VoIP call to the transfer telephone. The called user enters a supervised or unsupervised transfer DTMF sequence, again PBX dependent. The called gateway server receives a transferred CTI event and sends a call transfer message to the caller gateway server. The caller gateway server receives the transfer message and sets up a VoIP call to the transfer telephone. The caller gateway server manages the TDM bus time slots to connect the caller telephone to the new VoIP call to the transfer telephone. The caller gateway server then disconnects the original call to the called telephone. [0186]
  • Path Replacement for Call Forward
  • The gateway network users can set up a call forward, with path replacement, from a web browser CTI application or from the telephone. In either case, call forward is a PBX feature, and the operation can be carried out by the PBX alone without the gateway server's involvement. However, if the incoming call is via VoIP and is forwarded to a remote site also via VoIP, the gateway server will provide call forward with path replacement so that the intermediate PBX loop back is eliminated. As a result, there will be just one direct VoIP link in the forwarded call. [0187]
  • Upon receiving an H.323 call setup message, the called gateway server checks to determine if the called user has call forward set up. The called gateway server uses CTI to send an inquiry to the PBX. If the user has call forward set up, and if the call forward destination is at a remote gateway network PBX, the called gateway server sends a “gateway call reroute” message back to the caller gateway server. Upon receiving the call reroute message, the caller gateway server sets up the original call to the transfer gateway server and transfer telephone. [0188]
  • Path Replacement for Follow-me
  • The gateway server allows users to redirect incoming telephone calls to any telephone, cellular phone, pager, etc., at other locations, e.g. conference room, home, etc. Users may also set up filters so that only calls from selected caller(s) are redirected. The gateway server can implement the follow me capability with path replacement. [0189]
  • Upon receiving an H.323 call setup message, the called gateway server checks the gateway database to determine if the user has follow me set up. If the called user has follow me set up, and if the destination is at a remote gateway server or other H.323 telephone, the called gateway server sends a “gateway call reroute” message back to the caller gateway server. The caller gateway server sets up the original call directly to the remote gateway server or H.323 telephone. The follow me feature of the integrated voice gateway system of the invention is described below. [0190]
  • Real-time Fax over the IP Network
  • The gateway server supports real-time fax transmission over the IP network (FoIP). The caller gateway server forwards the fax signals from the caller fax machine immediately across the IP network to the called gateway server. The called gateway server, in turn sends the signals to the called fax machine. The caller gateway server sends signals from the called fax machine back to the caller gateway server via the IP network. The caller gateway server send the signals to the caller fax machine. Real-time fax transmission over the IP network is provided the same immediacy of delivery that users are used to with fax transmission over the PST NETWORK. [0191]
  • Inter-PBX Toil Bypass for Real-Time Fax
  • In a preferred embodiment, the integrated voice gateway system of the invention supports the routing of a fax call from a stand-alone fax machine (or fax server) over the IP network. This feature is basically the same as “Inter-PBX Toll Bypass for Real-Time Voice”, i.e. the basic VoIP call described above with reference to FIG. 5. The gateway engine [0192] 50 (FIG. 3) provides automatic fax detection. Fax calls can be routed to a gateway server automatically by the configuration of the PBX ARS table in the same manner as is done for voice calls. A PBX trunk coupled to a gateway server can be dynamically shared between voice and fax calls.
  • This feature can be provided independent of Inter-PBX Toll Bypass for voice calls. If a company decides that the quality of voice over IP is not acceptable for its purposes, the integrated voice gateway system of the invention can still provide for FoIP. In this case, the PBX stations for the fax machines are assigned a special “Class of Service”, and calls originating from these stations are routed by the caller PBX to the caller gateway server. [0193]
  • When FoIP is supported in conjunction with VoIP, the gateway server can also be configured so that VoIP calls are routed via the company's intranet, and fax calls are routed via the Internet to take advantage of free bandwidth on the Internet. [0194]
  • Hop-off to PST NETWORK for Real-time Fax
  • In a preferred embodiment, the integrated voice gateway system of the invention supports a fax call from within the company to an outside PST NETWORK fax machine via the IP network and the PST NETWORK. A user in the company, can send a fax to an outside fax machine. The fax call is carried via the IP network to the gateway server which is the closest to the called fax machine, and from there a PST NETWORK connection is made from the called gateway server to the called fax machine. [0195]
  • Supported hop-off destinations are determined by the system administrator of the [0196] 10 destination gateway servers. Both hop-off via local PST NETWORK call and hop-off via long distance PST NETWORK call are supported. The ARS table (or routing table by other names) of the originating PBX needs to be configured accordingly for the hop-off calls to be routed to the gateway server.
  • Hop-off to PST NETWORK methods are listed in Table 10. and described above with reference to FIGS. [0197] 6-14.
  • Redirection of Incoming Fax to Printer
  • In a preferred embodiment, the integrated voice gateway system of the invention supports the use of laser printers as fax machines. A pseudo fax number can be defined for a printer by the administrator. Once a printer is assigned a pseudo fax number, the printer can receive faxes sent to that pseudo number just like a fax machine. The fax gateway [0198] 54 (FIG. 3) in the called gateway server 126 converts the received fax into a printable form before sending the received fax to the print queue. This feature allows the simultaneous transmission and receipt of faxes between company sites without busy signals. It also supports the use of plain paper for printing faxes.
  • Fax Multi-Cast
  • In a preferred embodiment, the integrated voice gateway system of the invention supports the multi-cast of a fax to a group of recipients. A pseudo fax number representing a group of recipients (i.e. fax distribution list) can be defined by the administrator or a user. A fax sent to a “pseudo fax number” which represents a group is multi-casted to all recipients in the group. [0199]
  • Fax multi-cast saves users'time, and reduces the traffic load in the company's network. When more than one recipient of a multi-cast group is on the same called gateway server, the caller gateway server sends only one copy of the fax to the called gateway server. The called gateway server then fans out the fax to each of the recipients. [0200]
  • PC Call Control
  • The invention provides the user with desktop CTI capabilities. The user may dial, answer, hang-up, transfer, conference, forward, place a call on hold, unhold, and drop a call from the desktop workstation. The user can dial touch tone digits, e.g. in response to IVR commands. The user can also set the DND indicator for all calls or selected calls, and manage multiple call appearances, e.g. select one call to answer and select another call to go to voicemail. The white pages and the individual frequent contact lists from the enterprise directory are available for the user to select destinations for dialing, transfers and conferencing. The call log is also available at the desktop workstation. The PC call control interface is delivered as a Java applet through the web browser. [0201]
  • Current CTI applications only provide the user a personal telephone book or an application specific directory. Current CTI applications do not provide the user with access to the enterprise directory. In the integrated voice gateway system of the invention, the PC call control capability is integrated with the IP telephone voice gateway, and provides the user with a white pages directory, based upon the enterprise directory, to serve as a phone book directory, and integrated with a CTI application. [0202]
  • Since the PC call control feature is browser based, there is no desktop application to install, and the PC call control capability is compatible with multiple computers and operating systems. This is illustrated in FIGS. 47 and 48. FIG. 47 illustrates a current system in which a [0203] CTI server 502 and a workstation 503 are coupled via a LAN 501. The CTI application CTI_APP 504 and CTI dynamic link library (dII) CTI.dII 505. The CTI_APP 504 and CTI.dII 505 are both installed in the workstation 503. This can be very expensive, and present a complex logistical problem in a large organization to install, maintain and update the CTI_APP 504 and CTI.dII 505 as required for new features, bug fixes, operating system upgrades and the like. In the integrated voice gateway system of the invention, as illustrated in FIG. 48, there is no need to install applications, dIIs, and the like in all the users'workstations. The CTI server 97, gateway server 26, web server 92 and workstation 24 are all coupled via the company's LAN 22. The user client 95 is a commercially available web browser-based GUI application. There is no need to install special applications, dIIs, or the like, as all PC call control capabilities are provided via the web browser user client 95. Installation, maintenance and upgrade of the call control application is accomplished as necessary only on the respective servers. The user begins by logging in via a browser screen. Once the user is logged in, the user can receive “screen pops” from the gateway server 26. Screen pops are windows and dialog boxes which, for example, identify the calling and called parties, and provide other information to the user as is described below.
  • Virtual Desktop
  • The integrated voice gateway system of the invention provides a virtual desktop which allows a computer browser and a telephone at a location other than a user's regular office, e.g. an “alternate office” or a “virtual office”, to be logically associated with the user. As used herein, an alternate office may be another office within the company, and a virtual office may be at a location off the company's premises. An alternate office within the company is any location that has access to both a gateway telephone, and a desktop workstation having a browser, the workstation coupled to the company's data network. Reference FIG. 49, the integrated voice gateway system of the invention supports a user working in an alternate office by providing the user the capability to: redirect desired inbound calls to the telephone in the alternate office, and receive caller ID screen pops on the desktop workstation identifying that the call is for that user; place calls from the telephone in the alternate office and have the user's own caller ID sent to the call's destination; and, have access to the full set of browser based desktop call control (e.g., white pages, transfer) that are available at the user's regular desk. As illustrated in FIG. 49, the user first logs in at the [0204] remote workstation 524 via the user client 595 browser interface in the alternate office. The login information includes the telephone number of the remote telephone 538. The gateway engine 550 in the remote gateway server 526 causes the information to be stored in the gateway database 551 in the remote gateway server 526 and to be sent to the user's primary gateway server 26 to be stored in the gateway database 51 in the primary gateway server 26. The information stored in the gateway database 51 in the primary gateway server may include a filter set up by the user to limit the users whose calls are forwarded to the alternate office. Operation of the follow me feature of the integrated voice gateway system of the invention is described below.
  • Traveling Class of Service
  • The class of service is a set of user attributes which indicate the capabilities that are available to a user. The attributes include both licensing levels and feature activation. The class of service attributes are referenced at different points during operation of the gateway server, and include, for example, when a user logs in—to determine which client to deliver via the web browse; at an originating gateway server—to determine which features are available to a user; and to be transported with a call to a called gateway server—so that feature access may also be addressed at the destination. [0205]
  • As indicated above in the description of the Virtual Desktop feature, the class of service available to a user follows the user when the user logs in at an alternate office. [0206]
  • Virtual PBX Features
  • The integrated voice gateway system of the invention couples the PBX's in an enterprise in one single Virtual PBX (VPBX). This enables the system of the invention to provide several useful end-user features which are collectively referred to herein as VPBX features. This set of VPBX features is an important set of features which set has not previously been available in IP telephony systems. The gateway server relies on the CTI connection to the PBX to provide most of the VPBX features. The integration of the gateway server with the enterprise directory services systems enables the gateway server to provide the full range of VPBX features described herein. As an alternative to CTI, the gateway server can also obtain much of the information needed to provide VPBX features via PRI and QSIG interfaces. Table 13 shows the VPBX features which can be supported depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having a QSIG interface with no CTI link, all the features can be provided except for dynamic caller ID for calls which originate from the PST NETWORK or if the caller and called telephones are both coupled to the same PBX. The remaining configurations, not having a CTI link between the PBX and the gateway server do not support path replacement, callback on busy or call alert, and only a configuration having a PRI CO trunk or T1/E1 in-band signaling, without a CTI link, can support dynamic caller ID for calls placed from a caller telephone to a called telephone with both telephones “on net”. [0207]
    TABLE 13
    VPBX Feature Support
    No CTI
    and PRI
    CTI and CO Trunk
    T1/E1 or T1/E1 No CTI
    Tie-Trunk with and T1/E1
    or In-Band Tie Trunk
    Analog CO No CTI ANI or Analog
    Trunk and QSIG Signaling CO Trunk
    Toll Bypass X X X X
    Hop-Off to PST X X X X
    NETWORK
    Hop-On from X X X X
    PST
    NETWORK
    Fallback to PST X X X X
    NETWORK
    Fail-Safe X X X X
    Operation
    Path X X
    Replacement
    Dynamic Caller X X X
    ID (on net calls)
    Dynamic Caller X
    ID
    (off-net calls,
    i.e. PST
    NETWORK and
    intra-PBX calls)
    Callback on X X
    Busy
    Call Alert on X X
    Busy
  • Table 14 shows the features for forwarding calls to alternate telephone numbers which can be supported from a user client depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having a QSIG interface with no CTI link, all the features can be provided except for follow-me for calls which originate off-net. The remaining configurations, not having a CTI link between the PBX and the gateway server also do not support filtered follow-me for on-net or off-net calls. [0208]
    TABLE 14
    Follow-me Feature Support
    CTI and No CTI
    T1/E1 No CTI and T1/E1
    Tie-Trunk and QSI Tie Trunk
    or Analog G or PRI or Analog
    CO Trunk CO Trunk CO Trunk
    Intelligent Follow-me
    Follow-me (on-net calls) X X X
    Follow-me (off-net calls) X
    Scheduling via Browser X X X
    Turn on/off via any phone X X X
    Voice Mail Coverage X X X
    Filtered Follow-me (on-net calls) X X
    Filtered Follow-me (off-net calls) X
    Alternate Office:
    Alternate Office: Identify User X X X
    Calls
    Remote H.323 User
    NetMeeting Integration X X X
  • Table 15 shows advanced features which can be supported from a user client depending on the interfaces which are available. It can be seen that all of the features can be supported in a system having a CTI link between the PBX and the gateway server, and either a T1/E1 tie trunk or an analog CO trunk. In a configuration having no CTI link available, only the enterprisee and personal directories are supported, and the call log for on-net calls. [0209]
    TABLE 15
    Advanced Feature Support
    No CTI
    and QSIG
    or PRI CO
    CTI and Trunk or
    T1/E1 T1/E1 Tie
    Tie-Trunk Trunk or
    or Analog Analog CO
    CO Trunk Trunk
    Directory
    Enterprise Directory X X
    Personal Directory X X
    Call Log
    Call Log for On-net calls X X
    Call Log for Off-net calls X
    Desktop Call Control X
    Make Call X
    Answer Call X
    Hang Up Call X
    Hold Call X
    Transfer Call X
    Forward Call X
    Display of Active Calls X
    Do Not Disturb X
  • The provision of a screen-pop to a user's desktop workstation is a useful interface for most of the VPBX features. Screen-pops may be accompanied by audible sounds and alerts to provide additional emphasis or information to the user. If the user does not have a desktop workstation, or if the user does not log into the gateway server, then the gateway server may provide IVR as the user interface for the VPBX features. [0210]
  • VPBX features provided by the integrated voice gateway system of the invention may include: Dynamic Caller ID, Call Log, Callback on Busy, Call Alert, Call Alert via Must Answer Station, Follow Me, and Virtual Desktop, each of which will be described below. The invention also supports conventional PBX features, e.g. Ring Through, etc. [0211]
  • Dynamic Caller ID
  • The integrated voice gateway system of the invention provides the capability to display the caller ID to the called party by a screen-pop on the desktop workstation at the same time the telephone rings. [0212]
  • For many large corporate desktop users, current systems provide caller ID only when a fellow employee calls from within the same PBX system. Calls from employees at other corporate locations only provide the trunk number of the remote location, not the calling telephone number or name. Providing caller ID (including name, telephone number, and other relevant information about the caller) allows the desktop worker to interrupt work, or, for users with multiple telephone lines, to interrupt a current conversation, to answer important calls without answering every call. On PBX networks where caller ID is provided on the telephone display via proprietary channel signaling, a current limitation is that in a time sharing office environment, the caller ID cannot be dynamically changed. In a typical office environment, a telephone is assigned to an employee. In this case, the caller name is the name of the employee to whom the caller telephone is assigned. In a time sharing office situation, different employees use the office and the telephone at different times. Additional limitations in current systems are that the PBXs must be from the same vendor, and the PBXs must be connected by leased lines, and the PBX data base of caller names must be entered at each site. [0213]
  • Reference FIG. 50, the gateway server provides dynamic caller ID, i.e. the telephone number with the correct caller name, based on who is logged on from the office desktop workstation at the time the call is made. If there is no user logged on at the time a call is made, the default information for that telephone is used. If the desktop worker's telephone is being forwarded to another extension, and a CTI event is generated with the forwarding, then the caller ID screen pop will appear with the ringing call at the forwarded extension. In addition, the original called party ID will also be displayed on the screen pop of the forwarded call. [0214]
  • The caller ID feature can support calls between gateway telephones, i.e. between two telephones coupled to the same PBX in a gateway network, or between telephones coupled to two PBXs in different gateway networks. For calls originating from telephones outside a gateway network (e.g. PST NETWORK telephone, internet telephone), the caller ID feature can provide the caller ID to the gateway server by the PBX, through CTI (if caller ID is transmitted by the PST NETWORK and by the PBX to the CTI link), or by a VoIP connection. [0215]
  • The caller ID feature relies on CTI or inband ANI, PRI or QSIG trunk types at the caller gateway server to provide the caller's telephone number. The caller ID feature also relies on the desktop workstation display at the called party's desktop. The enterprise directory provides the caller name and associated information (e.g. title, department, etc.) with the calling number. [0216]
  • FIG. 50 illustrates how the caller ID is obtained at the caller gateway server. The caller (not illustrated) picks up the handset on the caller telephone and dials the desired telephone number. The caller PBX accesses a [0217] trunk 35 to the caller gateway server 26, and dials the call. The caller gateway server receives the telephone number from the caller PBX on a PRI trunk or over the CTI link.
  • The [0218] caller gateway PBX 34 delivers the call to the caller gateway server 26, and, as the call is delivered, the caller PBX 34 also passes the caller ID (i.e. the caller's telephone number) to the caller gateway server 26 via an inband ANI, PRI, QSIG or CTI link. In the case of an ISDN PRI link, the caller PBX 34 may use a call setup message to initiate the call. The caller ID can be transmitted as part of the call setup message. The caller gateway server 26 receives the caller ID as part of the setup message, and the caller PBX 34 and caller gateway server 26 continue to set up the call. In the case of a QSIG link, the PBX uses a call setup message to initiate a call on the QSIG link. The caller ID information is transmitted as part of the call setup message. The caller gateway server 26 receives the caller ID as part of the setup message, and the caller PBX 34 and caller gateway server 26 continues to establish the call. The CTI link 98 is a separate link from the trunks. To pass the caller ID via the CTI link, the PBX places a call to the caller gateway server 26 using a trunk. While the trunk call is being initiated, the CTI link 98 transmits an event message indicating the call. The event message includes the trunk ID, the called telephone number, and the caller's caller ID. The caller gateway server 26 associates the call being received on the trunk with the CTI link 98 message, and associates the caller ID with the trunk. Using the CTI link 98 to pass the caller ID supports instances in which analog or Ti trunks are used which do not provide caller ID information from the caller PBX 34.
  • The [0219] caller gateway server 26 uses the caller's telephone number to access additional caller ID information in the gateway database, i.e. the local image of the enterprise directory data. The caller gateway server 26 initiates an H.323 VoIP call with the called gateway server 126 over the IP network 18. As the call is placed, the caller gateway server 26 sends the caller ID information to the called gateway server 126 using an H.323 extension, e.g. User Information Extension (UIE).
  • The called [0220] gateway server 126 sets up the call with the called PBX 134, and may include the caller ID for the called PBX to pass to the called telephone 138. The called PBX rings the called telephone 138, and, if the called telephone 138 has a caller ID display, the called PBX 134 may include the caller ID for display at the called telephone. The called gateway server 126 checks its gateway database 151 to determine if the called party has a browser logged on to the called gateway server 126, and if that browser is logically associated with the called telephone 138. If the called gateway server 126 determines that the called party has a browser logged on, and is associated with the called telephone 138, then the called gateway server 126 delivers the caller ID information to the called desktop workstation via a browser applet. The browser applet results in a screen pop in the browser window at the called desktop workstation. Both the caller gateway server 26 and called gateway server 126 log the calls, and include the caller ID information in the call logs. A description of the Call Log feature follows below.
  • Call Log
  • The call log provides a log of outgoing calls and incoming calls including answered calls, abandoned calls and ring through calls for a desktop user. The call log includes the time of call, name and telephone number of the caller, and the result of the call, e.g. forwarded to voice mail, hang-up, inbound/outbound, etc. The call log may be sorted by time. The desktop user can access the call log via a gateway server client or a browser. As is the case with all screen pops, the call log is available to users only when they are logged in to the gateway network. Users can make a return call by clicking any inbound call entry in the call log. The entries in the call log can be imported into a user's personal phone book. The call log is maintained on the gateway server and will continue to log calls even if the user does not log on to the gateway network. Entries in the call log can be deleted, individually and as a group. A user may click a “details” button to access the detailed NDS information for users who are parties to incoming and outgoing calls. [0221]
  • Reference FIG. 51, When the caller makes a call from the [0222] caller telephone 38, the caller gateway server 26 opens a call log record for the caller. Caller ID information is obtained from the enterprise directory 90 for both the caller and called parties and is inserted into the call log record. When the call arrives at the called gateway server 126, a call log record is opened for the called party. Caller ID information for both the caller and called parties is inserted in the call log record in the called gateway server 126. When the call is over, or if for some reason the call is not completed, e.g. caller is busy, additional information (e.g. result, duration, etc.) is inserted in the call log records at both the caller gateway server 26 and called gateway server 126.
  • Destination Busy
  • The integrated voice gateway system of the invention provides several options for a caller at a gateway telephone attempting to call a party at another gateway telephone which is currently busy. The caller may elect to cancel the call or may select one of the options which include: Callback on Busy, Call Alert and Ring Through. These options will be described below. Common to each option is first the determination that a called gateway telephone is busy. [0223]
  • Referring to FIG. 52, a normal call is propagated within the integrated voice gateway system, either within a single gateway network, or as a VoIP call between two gateway networks. FIG. 52 illustrates such a call as a VoIP call between two gateway networks. As part of its normal processing function, the [0224] caller gateway server 126 uses the called CTI link 198 to the called PBX 134 to maintain the idle/busy status of telephones on the called PBX 134. When the called gateway server 126 receives the call from the caller gateway server 26, the called gateway server 126 checks the status of the called telephone 138. The called gateway server 126, on determining that the called telephone 138 is busy, notifies the caller gateway server 26 of the busy status. The called gateway server 26 receives the busy notice and checks its user logon data to determine if the caller at the caller telephone 38 is currently logged in from a browser. If the caller is logged in, the caller gateway server 126 sends information to the caller's browser 95 to inform the caller that the called telephone 138 is busy. The caller's browser 95 provides a screen pop to the caller indicating that the called telephone 126 is busy. The screen pop also provides the caller with several options from which to choose. The options may include: cancel the call, request a callback, request a call alert or request a ring through. If the caller is not logged in from a browser, the caller may be provided similar options via an IVR interface.
  • Callback on Busy
  • The integrated voice gateway system of the invention provides the capability for a caller, if the called telephone is busy, to request that a callback be automatically set up when the called telephone is no longer busy. This feature is not available to most desktop users of current systems since telephone calls are typically immediately forwarded to voice mail systems when a called telephone is busy. Some PBXs offer delayed call forward on busy to allow callers to set callback before the call is forwarded to voice-mail, and some voice mail systems offer callers an option to select callback before taking a message. However, these options require that the PBXs be upgraded, and a requested callback may be canceled if the caller telephone is used before the callback is completed. If callback on busy is provided across a network by PBX vendors, the callback option will only work if both the caller and called telephone systems are from the same vendor. The integrated computer telephone system of the invention provides a callback on busy capability which works across networks of mixed telephone systems. [0225]
  • Reference FIG. 53, the callback option may be provided to the caller via IVR or via a screen pop. If the caller requests a callback be set up, then the [0226] gateway servers 4, 104 will automatically set up the call when the called party hangs up the current call.
  • When the callback call takes place, both the caller and called parties will be provided with the other party's caller ID. In the caller ID screen pop, it is also noted that the call is a callback call. [0227]
  • If, when the gateway servers set up the callback call, the original caller telephone is busy, the original caller will receive a screen-pop to the effect that the callback is taking place. The caller will have the option to hang up or place the current call on hold to initiate the callback call, or ignore the callback notification. If the caller ignores the callback notification, i.e. continues the current call for more than a specified time, e.g. 15 seconds, the callback will be canceled. [0228]
  • If a called party has multiple callback requests pending, then the callbacks may be serviced on a first-in-first-out (FIFO) basis, or on a priority basis, e.g. based on class of service of the caller, urgency, etc. [0229]
  • Call Alert
  • The integrated voice gateway system of the invention provides the capability for a caller to request a call alert if the called telephone is busy. For current desktop users, there is no capability to send a call waiting signal to a busy party since telephone calls are typically immediately forwarded to voice mail systems when a called telephone is busy. The ability of the integrated computer telephone system of the invention to provide caller ID on all intra-company calls regardless of location is an important part of the call alert feature. In addition, the unique ability of the integrated voice gateway system of the invention to allow remote users to send messages to describe their urgent need to talk to a busy party is a significant advance in desktop to desktop communication. [0230]
  • The call alert option may be provided to the caller via IVR or via a screen pop. If the caller chooses to request the alert via a screen pop, the caller may include an optional message, e.g. to inform the called party of the purpose of the call. The optional message may be selected from a set of pre-established messages, or may be a message created by the caller. [0231]
  • The call alert is delivered to the called party in a screen-pop on the called party's desktop workstation. The caller ID and optional message from the caller will be displayed. The called party can then take the call by hanging up or placing the current call on hold, acknowledge the call alert, or ignore the call alert by continuing the current call for more than a specified time, e.g. [0232] 15 seconds. If the called party ignores the call alert, the caller may be given the option to either ring through or set up a callback. The option to ring through or call back may be provided via IVR or screen pop. If the called party has multiple lines, then a call alert will be activated only if all lines are busy.
  • The call alert feature requires that both the caller and called telephones are gateway telephones, and the called party is logged on to the gateway server via the browser interface. The call alert feature uses CTI on both the caller gateway server and called gateway server for on/off hook status and to determine if the called party hangs up or places the current call on hold. The call alert feature also relies on the directory to provide caller ID for a call alert screen pop presented to the called party. [0233]
  • The privilege to use call alert may be configurable by the system administrator on a user by user basis. [0234]
  • If a user prefers not to be disturbed by call alert messages, the user can set a Do not Disturb (DND) indicator on the user's telephone. The DND indicator may be set via a screen pop provided on the user's desktop workstation. [0235]
  • FIGS. 54 and 55 illustrate a call alert scenario using the browser client and screen pops. Referring to FIG. 54, the caller types a message and clicks a call alert button in the [0236] caller user client 95. The call alert message is passed to the caller gateway server 26, and then over the IP network 18 to the called gateway server 126. The called gateway server 126 passes the call alert message to the called user client 195. The call alert message appears via a screen pop in the called user client 195. The called user may elect to accept or reject the call alert by clicking an appropriate button in the call alert screen pop. If the called user accepts the call alert, a message is passed to the called gateway server 126. The called CTI driver 180 passes a message to the called PBX 134 to place the current call on hold. The called analog driver 167 delivers the new call to the called PBX 134. The called PBX 134 rings the called telephone 138.
  • Referring to FIG. 55, if the called user rejects the call alert, the rejection message is passed to the called [0237] gateway server 126 and the called user client 195 closes the screen pop. If the called user takes no action, and the call alert times out, the called gateway server 126 passes a message to the called user client 195 to close the call alert screen pop.
  • If the call alert times out or is rejected, after closing the screen pop, the called [0238] gateway server 126 sends a call alert rejected message to the caller gateway server 26 via the IP network 18. The caller gateway server 26 passes the call alert rejection message to the caller user client 95. The rejection message includes applicable options for the caller to select.
  • Ring Through
  • The integrated voice gateway system of the invention provides the capability for a caller to request a ring through if the called telephone is busy. The ring through option follows normal PBX call coverage options which may typically forward calls to a user's voice mail or a Must Answer Station. The ring through option will be described with reference to FIG. 56. [0239]
  • The description of Destination Busy above concluded with the caller being provided several options, via browser or IVR, including ring through. If the caller is logged on via a browser, the caller would select the ring through option in the browser window at the caller workstation. The browser passes the selection to the caller gateway server. If the caller is not logged on, the caller would select the ring through option by pressing a designated key on the telephone. The [0240] caller gateway server 26 detects the DTMF tone selecting the ring through option. The caller gateway server 26 then notifies the called gateway server 126 that the caller has requested to ring through. The called gateway server 126 places an inbound call to the called PBX 134 for the called telephone 138. Since the called telephone 138 is busy, the called PBX 134 follows the normal process set up for the PBXs in the system, e.g. voice mail, must-answer station, etc.
  • Call Alert Via Must-Answer Station
  • The integrated voice gateway system of the invention provides the capability for a caller to request a call alert if the called telephone is busy and the caller is not using a gateway telephone. In current systems, a caller typically forwards a call to a designated (e.g. “must answer”) station, e.g. by pressing “0” after being forwarded to voice mail. In a large company, the attendant at a must-answer station is typically located remotely from the called party and hence cannot walk over to the called party and slip a notice that the caller needs to urgently talk to the called party. When a caller from outside a gateway network, e.g. a PST NETWORK telephone, places a call to a gateway telephone, and the called gateway telephone is busy, the caller may elect to transfer to a must-answer station. An attendant at the must-answer station can assist the caller by providing a call alert, for the outside caller, on the co-located workstation of the busy gateway telephone. [0241]
  • Follow Me
  • The integrated computer telephone system of the invention provides the capability for users to redirect incoming telephone calls arriving at their regular PBX station to any telephone or internet phone. The system of the invention also provides users with the capability to set up filters so that only calls from selected callers are redirected. Calls not forwarded can be sent to the normal PBX call coverage options, e.g. voice-mail. [0242]
  • In current PBX systems, users can program the PBX to call forward all calls to an inside-the-PBX or outside-the-PBX location. However, this generally needs to be done from the user's desktop telephone. In order to program the PBX from an outside location, expensive equipment for telecommuting must generally be attached to the PBX. These current systems offer only an IVR interface, but no browser interface. In current PBX systems there is no way to link caller ID to call forwarding. Hence, filtered call forwarding is not possible in the current systems. The telephone to which the calls are redirected may be another gateway telephone (coupled to the same or a different PBX as the user's telephone), or a PST NETWORK telephone (e.g. remote telephone [0243] 338), etc. The redirection can be set up as a one-time event or a recurring (e.g., daily) event. However, at any point in time, only one redirection may be in effect.
  • Follow me setup and operation will be described with reference to FIGS. [0244] 57-58. Referring to FIG. 57, the follow me feature may be setup via the browser or and IVR interface. If a browser is available, the user accesses follow me setup screens via the browser, reviews current options, and may make changes to the configuration. The browser and gateway server exchange data during the interaction.
  • If a browser is not available, for example, if the user is setting up the follow me feature from a PST NETWORK telephone, the user may set up follow me by calling a specified telephone number and interacting through an IVR interface. If the user calls from a remote telephone, the system may first authenticate the user's identity. For real time call processing, the user's follow me data is stored in the gateway server's local database. The user's follow me settings are stored in the enterprise directory as part of that user's data. [0245]
  • The follow me setup may include several options. For example, the user may schedule follow me periods as one time or periodic recurring events with a different destination telephone number selected for each event (e.g., car phone during the commute home, and home telephone in the evening). The user may set up numerous scheduled events. The user may also use an override option to use an unscheduled alternate destination. The users may configure the system to filter calls based on caller ID, and forward only calls from a list of callers selected by the user. The user may assemble a list of callers from the enterprise white pages and a frequent contact list. The user may create a different filter for each scheduled follow me period. [0246]
  • Referring to FIG. 58, an incoming call to a called [0247] telephone 138 coupled to a called PBX 134, may come via a VoIP call from a caller telephone 38 coupled to a caller PBX 34; via a PST NETWORK call from a caller telephone 438 coupled to the PST NETWORK 16; or from a caller telephone 538 coupled to the called PBX 134. In the case of a local PBX or PST NETWORK call, the called PBX 134 sends a CTI event to the called gateway server 126. The called gateway server 126 checks whether follow me is active for the called party, and, if a filter is active, if the caller matches the filter. If no filter is active, all calls are forwarded. If the caller does not match an active filter, the call not forwarded, and is simply delivered to the called telephone 138. If a match is found, the called gateway server 126 initiates a call to the follow me destination telephone. If the original call was an internal PBX call or a call from a PST NETWORK telephone, the gateway server uses the CTI link to redirect the call to the called gateway server 126. If the original call is a VoIP call, the call is normally directed to the called gateway server 126, and the called gateway server 126 can redirect the call.
  • The called [0248] gateway server 126 plays a message for the caller indicating that the call is being forwarded. When the forwarded call is answered, the gateway server offers a greeting to the answering party. The answering party replies with an accept code, e.g. DTMF tones, thereby authenticating the answering party. The caller and called party are then connected. If the call forwarded to the destination is not answered, or if the correct accept code is not provided, the caller is provided a message and the call is re-routed to the original called telephone to go through normal PBX coverage options, e.g. voice-mail.
  • While various embodiments and features of the invention have been described, those skilled in the art will recognize that variations and additions to those features and functions can be made within the scope of the invention. The invention is therefore intended to be limited only by the scope of the appended claims. [0249]

Claims (19)

    We claim
  1. 27. A method of configuring an enterprise directory for IP telephony, the method comprising the steps of
    (a) providing an X.500 compatible directory; and
    (b) including in a schema of the directory at least one object for representing a component of an IP telephony system, the component selected from a group consisting of:
    a GateKeeper;
    a Gateway;
    a Multipoint Control Unit (MCU);
    a GateKeeper Exchange; and
    a user with associated telephony service attributes.
  2. 165. A communication system comprising:
    a public switched telephone (PST) network;
    an internet protocol (IP) network;
    a plurality of gateway networks coupled to the PST network and the IP network, each of the plurality of gateway networks configured to route a telephone call over the PST network or the IP network; and
    a directory server coupled to the plurality of gateway networks, the directory server comprising an enterprise directory having an extensible schema configured to provide data to support routing of telephone calls.
  3. 166. A communication system according to claim 165 wherein each of the plurality of gateway networks comprise a gateway database capable of providing information for routing the telephone call over the IP network, and wherein the gateway database is created from information dredged from the directory server.
  4. 167. A communication system according to claim 166 wherein the directory server is coupled to the IP network, and wherein users of the communication system can make changes to objects in the directory server representing components of the communication system through a web browser coupled to the IP network.
  5. 168. A communication system according to claim 166 further comprising computer software capable of automatically updating the gateway databases to reflect changes in the directory server.
  6. 169. A communication system according to claim 166 further comprising computer software capable of updating the gateway databases when a new gateway network is added to the communication system and information for the new gateway network entered in the directory server.
  7. 170. A communication system according to claim 169 wherein the computer software is configured to update a gateway database associated with one of the plurality of gateway networks when the gateway network is placed in operation.
  8. 171. A communication system according to claim 165 wherein the directory server comprises in its schema at least one object selected from a group consisting of:
    an object configured to represent a GateKeeper;
    an object configured to represent a Gateway;
    an object configured to represent a Multipoint Control Unit;
    an object configured to represent a GateKeeper Exchange; and
    an object configured to represent communication system user with associated telephony services attributes.
  9. 172. A communication system according to claim 165 wherein the enterprise directory includes at least one directory selected from the group consisting of:
    a Novell Directory Services (NDS) compatible directory;
    a Microsoft Active Directory Services® (ADS) compatible directory;
    a Microsoft NT® domain compatible directory;
    an X.500 compatible directory;
    a Netscape® Directory Server; and
    a lightweight directory access protocol (LDAP) server.
  10. 173. A communication system according to claim 165 wherein the telephones comprise IP telephones.
  11. 174. A communication system according to claim 173 wherein the IP telephones include H.323 compliant telephones.
  12. 175. A communication system according to claim 165 wherein the telephones comprise non-IP telephones including at least one telephone selected from the group consisting of:
    private branch exchange telephones; and
    plain old telephones (POTS).
  13. 176. A method of operating a communication system having a plurality of gate way networks coupled to an internet protocol (IP) network and to a public switched telephone (PST) network to route a telephone call over the IP network, the method comprising steps of:
    providing a directory server;
    accessing the directory server to create a plurality of gateway databases, each gateway database associated with one of the plurality of gateway networks and each gateway database comprising a list of telephone numbers that each of the plurality of gateway networks will accept;
    connecting a user to one of the plurality of gateway networks via a calling telephone;
    accepting a telephone number entered by the user;
    accessing the gateway database associated with the gateway network to determine which of the plurality of gateway networks will accept the telephone number entered by the user; and
    routing the telephone call from the calling telephone over the IP network.
  14. 177. A method according to claim 176 wherein the step of providing a directory server comprises the steps of:
    coupling an enterprise directory having an extensible schema to the IP network; and
    extending the schema of the enterprise directory with objects representing components of the communication system to create the directory server.
  15. 178. A method according to claim 176 wherein the step of providing a directory server comprises the steps of:
    designating one of the plurality of gateway databases as a master database;
    designating the remaining gateway databases as slave databases; and
    creating within a schema of the master database objects representing components of the communication system to create the directory server.
  16. 179. A method according to claim 176 wherein the step of providing a directory server further comprises the steps of:
    accessing a company database coupled to the IP network; and
    copying the company database to the master database.
  17. 180. A method according to claim 176 comprising the further step of accessing the directory server to provide a company white pages comprising lists of users and telephone numbers.
  18. 181. A method according to claim 180 comprising wherein the step of providing a company white pages comprises the step of providing company white pages in which the telephone numbers depend on a location from which the company white pages is accessed.
  19. 184. A communication system comprising:
    a public switched telephone (PST) network;
    an internet protocol (IP) network;
    a plurality of voice gateways coupled to the PST network and the IP network, each of the plurality of voice gateways configured to route a telephone call over the PST network or the IP network; and
    general purpose directory-services comprising a distributed network of directory servers coupled to the plurality of voice gateways, the directory services configured to provide data to support routing of telephone calls over the IP network and having an extensible schema including at least one IP telephony object selected from a group consisting of:
    an object configured to represent a GateKeeper;
    an object configured to represent a Gateway;
    an object configured to represent a Multipoint Control Unit;
    an object configured to represent a GateKeeper Exchange; and
    an object configured to represent communication system user with associated IP telephony services attributes,
    the directory-services comprising at least one directory-services selected from the group consisting of:
    a Novell Directory Services® (NDS);
    a Microsoft Active Directory Services® (ADS);
    an X.500 based directory-services;
    a Netscape® Directory Server; and
    a lightweight directory access protocol (LDAP) compatible directory-services,
    whereby a single point of entry is provided for making additions, changes and deletions of the IP telephony objects by making additions, changes and deletions in the schema of the directory services.
US10/086,602 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway Abandoned US20030091028A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/086,602 US20030091028A1 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US5376397P 1997-07-25 1997-07-25
US6374297P 1997-10-17 1997-10-17
US7305698P 1998-01-29 1998-01-29
US6180298A 1998-04-16 1998-04-16
US10/086,602 US20030091028A1 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US6180298A Division 1997-07-25 1998-04-16

Publications (1)

Publication Number Publication Date
US20030091028A1 true US20030091028A1 (en) 2003-05-15

Family

ID=27489583

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/086,602 Abandoned US20030091028A1 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway
US10/086,268 Abandoned US20030095542A1 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway
US10/086,262 Expired - Fee Related US7280530B2 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway

Family Applications After (2)

Application Number Title Priority Date Filing Date
US10/086,268 Abandoned US20030095542A1 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway
US10/086,262 Expired - Fee Related US7280530B2 (en) 1997-07-25 2002-03-04 Apparatus and method for integrated voice gateway

Country Status (4)

Country Link
US (3) US20030091028A1 (en)
EP (1) EP1021757A1 (en)
AU (1) AU8576798A (en)
WO (1) WO1999005590A2 (en)

Cited By (103)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020138603A1 (en) * 2001-03-20 2002-09-26 Robohm Kurt W. Systems and methods for updating IP communication service attributes
US20020136222A1 (en) * 2001-03-20 2002-09-26 Kurt W. Robohm Systems and methods for updating IP communication service attributes using an LDAP
US20040092293A1 (en) * 2002-11-06 2004-05-13 Samsung Electronics Co., Ltd. Third-party call control type simultaneous interpretation system and method thereof
US20040120301A1 (en) * 2002-12-24 2004-06-24 Kitchin Duncan M. Method and apparatus to establish communication with wireless communication networks
US20040143620A1 (en) * 2001-05-21 2004-07-22 Abraham Fisher Intervening ip calls during a modem session
US20040236586A1 (en) * 2003-05-22 2004-11-25 Honeywell International, Inc. Method and system for standardizing the quality of materials and services used in structured cabling networks
US20050111435A1 (en) * 2003-11-26 2005-05-26 James Yang [internet-protocol (ip) phone with built-in gateway as well as telephone network structure and multi-point conference system using ip phone]
US20050138128A1 (en) * 2003-12-23 2005-06-23 Baniel Uri S. Method and device for grab transferring an instant messaging and presence (IMP) session
US20050177376A1 (en) * 2004-02-05 2005-08-11 Avaya Technology Corp. Recognition results postprocessor for use in voice recognition systems
US20050180404A1 (en) * 2002-11-14 2005-08-18 Ey-Taeg Kwon Method for collect call service based on VoIP technology and system thereof
US20060077962A1 (en) * 2004-10-07 2006-04-13 Santera Systems, Inc. Methods and systems for measurement-based call admission control in a media gateway
US20060114885A1 (en) * 2004-11-09 2006-06-01 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks
US20060133367A1 (en) * 2004-12-21 2006-06-22 Cisco Technology, Inc. Selecting a routing mode for a call session
US20060135157A1 (en) * 2004-11-02 2006-06-22 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks, and packet switch apparatus therefor
US7082119B1 (en) * 2000-06-28 2006-07-25 Cisco Technology, Inc. Full PBX telephony feature preservation across a voice over packet network
US20060182131A1 (en) * 2005-01-21 2006-08-17 L-3 Communications Corporation Gateway interface control
US20070109963A1 (en) * 2005-11-17 2007-05-17 Edward Walter Internet protocol telephony proxy device
WO2007026029A3 (en) * 2005-09-02 2007-05-24 Data Connection Ltd Telephone call processing method and apparatus
US20070121920A1 (en) * 2003-06-30 2007-05-31 Silver Edward M Caller controlled network-based timed ring suppression
US20070121921A1 (en) * 2003-06-30 2007-05-31 Silver Edward M Network-based timed ring suppression
US20070127455A1 (en) * 2005-12-07 2007-06-07 Ricoh Company, Limited Call control server
US20070161386A1 (en) * 2006-01-10 2007-07-12 Scott Faber Systems and methods to provide availability indication
US20070160076A1 (en) * 2006-01-10 2007-07-12 Scott Faber Systems and methods to arrange call back
US20070206613A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for executing originating services in a terminating network for IMS and non-IMS applications
US20070206573A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing
US20070206572A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network
US20070206571A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling call originations using SMS and hotline capabilities
US20080032728A1 (en) * 2006-08-03 2008-02-07 Bina Patel Systems, methods and devices for communicating among multiple users
US20080043976A1 (en) * 2006-07-20 2008-02-21 Microsoft Corporation Management of telephone call routing using a directory services schema
US7376827B1 (en) * 1999-11-05 2008-05-20 Cisco Technology, Inc. Directory-enabled network elements
US20080147745A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing synchronization of directory data
US20080162720A1 (en) * 2006-12-29 2008-07-03 Aman Gulati Methods and apparatus for implementing a pluggable policy module within a session over internet protocol network
US7415021B1 (en) * 2004-09-22 2008-08-19 Sun Microsystems, Inc. Method and apparatus for preserving null semantics during use of a forwarding method
US20090003318A1 (en) * 2007-06-28 2009-01-01 Embarq Holdings Company, Llc System and method for voice redundancy service
US20090031415A1 (en) * 2007-07-26 2009-01-29 International Business Machines Corporation Dynamic Network Tunnel Endpoint Selection
US20090054032A1 (en) * 2006-02-15 2009-02-26 Huawei Technologies Co., Ltd. Method, system and vpbx for sending short messages
US20090257361A1 (en) * 2006-09-28 2009-10-15 Qualcomm Incorporated Methods and apparatus for determining communication link quality
US20100008264A1 (en) * 2008-07-09 2010-01-14 General Instrument Corporation Method and apparatus for facilitating installation of packet-switched telephony equipment on a subscriber premises
US20100165857A1 (en) * 2006-09-28 2010-07-01 Qualcomm Incorporated Methods and apparatus for determining quality of service in a communication system
US7782897B1 (en) 2004-08-26 2010-08-24 Juniper Networks, Inc. Multimedia over internet protocol border controller for network-based virtual private networks
US7899167B1 (en) * 2003-08-15 2011-03-01 Securus Technologies, Inc. Centralized call processing
US7916845B2 (en) 2006-04-13 2011-03-29 Securus Technologies, Inc. Unauthorized call activity detection and prevention systems and methods for a Voice over Internet Protocol environment
US20110081911A1 (en) * 2006-03-02 2011-04-07 Andrew Silver System and method for enabling vpn-less session setup for connecting mobile data devices to an enterprise data network
US20110090796A1 (en) * 1999-12-30 2011-04-21 Avaya Inc. ADAPTIVELY MAINTAINING QUALITY OF SERVICE (QoS) IN DISTRIBUTED PBX NETWORKS
US7990882B1 (en) * 1999-12-30 2011-08-02 Avaya Inc. Adaptively maintaining quality of service (QoS) in distributed PBX networks
US8000269B1 (en) 2001-07-13 2011-08-16 Securus Technologies, Inc. Call processing with voice over internet protocol transmission
US8045585B2 (en) 2000-08-18 2011-10-25 Juniper Networks, Inc. Method and apparatus providing media aggregation in a packet-switched network
US20120028629A1 (en) * 2008-09-30 2012-02-02 Yajian Liu Method and apparatus for setting a transmit power level
US8135001B1 (en) * 2008-04-16 2012-03-13 Globaltel IP, Inc. Multi ad hoc interoperable communicating networks
US20120144015A1 (en) * 2010-12-02 2012-06-07 A10 Networks, Inc. System and Method for Distributing Application Traffic to Servers Based on Dynamic Service Response Time
US8249057B1 (en) 2000-08-18 2012-08-21 Juniper Networks, Inc. Methods and apparatus providing an overlay network for voice over internet protocol applications
US8340260B1 (en) 2003-08-15 2012-12-25 Securus Technologies, Inc. Inmate management and call processing systems and methods
US20130003723A1 (en) * 2002-12-05 2013-01-03 Resource Consortium Limited Virtual PBX based on Feature Server Modules
US8462637B1 (en) * 2005-01-04 2013-06-11 Sheridan Ross P.C. Dial plan routing for fragmented networks
US20130170361A1 (en) * 2011-12-10 2013-07-04 Web3Tel Inc. System and Method of Interactive call control for calls and connections created in different communication networks
US8619954B2 (en) 2003-09-29 2013-12-31 At&T Intellectual Property I, L.P. Methods, systems, and products for ring suppression
US9025438B1 (en) * 2010-06-29 2015-05-05 Century Link Intellectual Property LLC System and method for communication failover
US20150326732A1 (en) * 2006-06-30 2015-11-12 Centurylink Intellectual Property Llc System and Method for Re-Routing Calls
US9256353B2 (en) 2006-12-19 2016-02-09 Vmware, Inc. Providing application and device management using entitlements
US9264299B1 (en) 2013-03-14 2016-02-16 Centurylink Intellectual Property Llc Transparent PSTN failover
US9300703B2 (en) 2007-06-26 2016-03-29 Yellowpages.Com Llc Systems and methods to provide telephonic connections via concurrent calls
US20160205145A1 (en) * 2011-01-10 2016-07-14 Vtech Telecommunications Limited Peer-to-peer internet protocol telephone system with system-wide configuration data
US9497201B2 (en) 2006-10-17 2016-11-15 A10 Networks, Inc. Applying security policy to an application session
US9521141B2 (en) 2014-02-12 2016-12-13 Bank Of America Corporation Caller validation
US9531846B2 (en) 2013-01-23 2016-12-27 A10 Networks, Inc. Reducing buffer usage for TCP proxy session based on delayed acknowledgement
US9560193B1 (en) 2002-04-29 2017-01-31 Securus Technologies, Inc. Systems and methods for detecting a call anomaly using biometric identification
US9635179B1 (en) * 2011-10-10 2017-04-25 West Corporation Consumer care system
US9705800B2 (en) 2012-09-25 2017-07-11 A10 Networks, Inc. Load distribution in data networks
US9768856B2 (en) 2013-06-07 2017-09-19 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving service in wireless communication system
US9843484B2 (en) 2012-09-25 2017-12-12 A10 Networks, Inc. Graceful scaling in software driven networks
US9900252B2 (en) 2013-03-08 2018-02-20 A10 Networks, Inc. Application delivery controller and global server load balancer
US9906591B2 (en) 2011-10-24 2018-02-27 A10 Networks, Inc. Combining stateless and stateful server load balancing
US9906422B2 (en) 2014-05-16 2018-02-27 A10 Networks, Inc. Distributed system to determine a server's health
US9942152B2 (en) 2014-03-25 2018-04-10 A10 Networks, Inc. Forwarding data packets using a service-based forwarding policy
US9942162B2 (en) 2014-03-31 2018-04-10 A10 Networks, Inc. Active application response delay time
US20180103150A1 (en) * 2016-06-21 2018-04-12 Avaya Inc. Mobility bonding network
US9960967B2 (en) 2009-10-21 2018-05-01 A10 Networks, Inc. Determining an application delivery server based on geo-location information
US9961135B2 (en) 2010-09-30 2018-05-01 A10 Networks, Inc. System and method to balance servers based on server load status
US9979801B2 (en) 2011-12-23 2018-05-22 A10 Networks, Inc. Methods to manage services over a service gateway
US9979828B1 (en) * 2005-04-12 2018-05-22 Tp Lab, Inc. Voice virtual private network
US9986061B2 (en) 2014-06-03 2018-05-29 A10 Networks, Inc. Programming a data network device using user defined scripts
US9992229B2 (en) 2014-06-03 2018-06-05 A10 Networks, Inc. Programming a data network device using user defined scripts with licenses
US9990683B2 (en) 2002-04-29 2018-06-05 Securus Technologies, Inc. Systems and methods for acquiring, accessing, and analyzing investigative information
US9992107B2 (en) 2013-03-15 2018-06-05 A10 Networks, Inc. Processing data packets using a policy based network path
US10002141B2 (en) 2012-09-25 2018-06-19 A10 Networks, Inc. Distributed database in software driven networks
US10021174B2 (en) 2012-09-25 2018-07-10 A10 Networks, Inc. Distributing service sessions
US10038693B2 (en) 2013-05-03 2018-07-31 A10 Networks, Inc. Facilitating secure network traffic by an application delivery controller
US10044582B2 (en) 2012-01-28 2018-08-07 A10 Networks, Inc. Generating secure name records
US10115080B2 (en) 2002-04-29 2018-10-30 Securus Technologies, Inc. System and method for proactively establishing a third-party payment account for services rendered to a resident of a controlled-environment facility
US10129122B2 (en) 2014-06-03 2018-11-13 A10 Networks, Inc. User defined objects for network devices
US10180962B1 (en) * 2007-09-28 2019-01-15 Iqor Us Inc. Apparatuses, methods and systems for a real-time phone configurer
USRE47296E1 (en) 2006-02-21 2019-03-12 A10 Networks, Inc. System and method for an adaptive TCP SYN cookie with time validation
US10230770B2 (en) 2013-12-02 2019-03-12 A10 Networks, Inc. Network proxy layer for policy-based application proxies
US10243791B2 (en) 2015-08-13 2019-03-26 A10 Networks, Inc. Automated adjustment of subscriber policies
US10419491B1 (en) * 2013-12-16 2019-09-17 8X8, Inc. System and method for monitoring computing servers for possible unauthorized access
CN110275718A (en) * 2013-12-31 2019-09-24 宏正自动科技股份有限公司 The installation and starting method of network equipment and system and embedded Control program
US10581976B2 (en) 2015-08-12 2020-03-03 A10 Networks, Inc. Transmission control of protocol state exchange for dynamic stateful service insertion
US10796392B1 (en) 2007-05-22 2020-10-06 Securus Technologies, Llc Systems and methods for facilitating booking, bonding and release
US10880721B2 (en) 2008-07-28 2020-12-29 Voip-Pal.Com, Inc. Mobile gateway
US10932317B2 (en) 2009-09-17 2021-02-23 VolP-Pal.com, Inc. Uninterrupted transmission of internet protocol transmissions during endpoint changes
US11079910B1 (en) * 2019-02-06 2021-08-03 Fuze, Inc. Softphone control integration
US11405846B2 (en) 2006-03-02 2022-08-02 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
TWI801096B (en) * 2022-01-14 2023-05-01 陳立新 Method of extending pbx communication functions and connectivity

Families Citing this family (260)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6717938B1 (en) 1999-04-15 2004-04-06 J2 Global Communications, Inc. System controlling use of a communication channel
US20020118671A1 (en) * 1995-11-15 2002-08-29 Data Race, Inc. Extending office telephony and network data services to a remote client through the internet
US6041109A (en) * 1995-12-29 2000-03-21 Mci Communications Corporation Telecommunications system having separate switch intelligence and switch fabric
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network
US6418461B1 (en) 1997-10-06 2002-07-09 Mci Communications Corporation Intelligent call switching node in an intelligent distributed network architecture
US6389009B1 (en) 2000-12-28 2002-05-14 Vertical Networks, Inc. Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses
US6181694B1 (en) 1998-04-03 2001-01-30 Vertical Networks, Inc. Systems and methods for multiple mode voice and data communciations using intelligently bridged TDM and packet buses
FR2780592B1 (en) * 1998-06-25 2000-08-04 Alsthom Cge Alcatel METHOD FOR TRANSMITTING SIGNALING DATA
US6560216B1 (en) * 1998-09-17 2003-05-06 Openwave Systems Inc. Data network computing device call processing
US6856676B1 (en) * 1998-10-15 2005-02-15 Alcatel System and method of controlling and managing voice and data services in a telecommunications network
JP2000244581A (en) * 1999-02-19 2000-09-08 Fujitsu Ltd Internet telephony void system
FI108768B (en) * 1999-02-23 2002-03-15 Ericsson Telefon Ab L M Call routing in communication networks
JP4703006B2 (en) * 1999-02-24 2011-06-15 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Method and system for call routing and codec negotiation in hybrid voice / data / internet / wireless systems
US6590869B1 (en) * 1999-03-11 2003-07-08 Siemens Information & Communication Networks, Inc. Method and apparatus for selecting whether to place a call over the internet or the PSTN using a two tiered process
CA2365420A1 (en) 1999-04-01 2000-10-12 Callwave Inc. Method and apparatus for providing expanded telecommunications service
GB2352125A (en) * 1999-04-30 2001-01-17 Nokia Corp Wireless intranet office
US6781983B1 (en) * 1999-05-03 2004-08-24 Cisco Technology, Inc. Packet-switched telephony with circuit-switched backup
US7203189B2 (en) * 1999-05-07 2007-04-10 Mitel Networks Corporation Network implemented communication system
WO2000069156A1 (en) * 1999-05-12 2000-11-16 Starvox, Inc. Method and apparatus for integrated voice gateway with interface to mobile telephone, ip telephone and un-pbx systems
AUPQ116399A0 (en) * 1999-06-23 1999-07-15 Telefonaktiebolaget Lm Ericsson (Publ) Multilevel precedence and pre-emption in a call and bearer separated networks
SE9903595L (en) * 1999-06-23 2000-12-24 Ericsson Telefon Ab L M Internet telephony improvements
GB2351869B (en) * 1999-06-26 2003-12-31 Ibm A voice processing system
US7444407B2 (en) * 2000-06-29 2008-10-28 Transnexus, Inc. Intelligent end user devices for clearinghouse services in an internet telephony system
DE19930146B4 (en) * 1999-06-30 2005-03-17 Siemens Ag Method for establishing a telecommunication connection via an intermediate network
US6801523B1 (en) * 1999-07-01 2004-10-05 Nortel Networks Limited Method and apparatus for performing internet protocol address resolutions in a telecommunications network
WO2001006740A2 (en) * 1999-07-14 2001-01-25 Starvox, Inc. Method and apparatus for integrating a voice gateway with an ip/pbx telephone system
US7804815B1 (en) * 1999-09-17 2010-09-28 Intertex Data Ab System and apparatus for telecommunication
AU7565000A (en) * 1999-09-21 2001-04-24 Telefonaktiebolaget Lm Ericsson (Publ) System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion
US6987756B1 (en) 1999-10-07 2006-01-17 Nortel Networks Limited Multi-mode endpoint in a communication network system and methods thereof
KR100644579B1 (en) * 1999-10-26 2006-11-13 삼성전자주식회사 Real-time audio/video communication device in internet and method thereof
FR2800956B1 (en) * 1999-11-10 2002-02-22 Sagem FAX SYSTEM WITH CENTRAL DIRECTORY
US6363065B1 (en) * 1999-11-10 2002-03-26 Quintum Technologies, Inc. okApparatus for a voice over IP (voIP) telephony gateway and methods for use therein
US6735175B1 (en) * 1999-12-16 2004-05-11 Ericsson Inc. Changing quality of service for voice over IP calls
US6853713B1 (en) 1999-12-17 2005-02-08 Nortel Networks Limited Client-server network for managing internet protocol voice packets
WO2001047235A2 (en) 1999-12-22 2001-06-28 Transnexus, Inc. Rate provisioning for internet telephony clearinghouse system
FR2803155B1 (en) * 1999-12-23 2002-03-15 Cit Alcatel APPLICABLE HALF LINK FOR PRIVATE NETWORK EXCHANGER
US6937713B1 (en) 1999-12-30 2005-08-30 At&T Corp. IP call forward profile
US6826173B1 (en) 1999-12-30 2004-11-30 At&T Corp. Enhanced subscriber IP alerting
US6775267B1 (en) 1999-12-30 2004-08-10 At&T Corp Method for billing IP broadband subscribers
US7180889B1 (en) 1999-12-30 2007-02-20 At&T Corp. Personal control of address assignment and greeting options for multiple BRG ports
US7068668B2 (en) 2000-01-07 2006-06-27 Feuer Donald S Method and apparatus for interfacing a public switched telephone network and an internet protocol network for multi-media communication
GB0000464D0 (en) * 2000-01-10 2000-03-01 British Telecomm Telecommunications interface
AU2001230921A1 (en) * 2000-01-11 2001-07-24 Transnexus, Inc. Architectures for clearing and settlement services between internet telephony clearinghouses
DE10005282A1 (en) * 2000-02-07 2001-08-09 Ericsson Telefon Ab L M Private branch exchange or private communication network for integrating internet-assisted multimedia communication technology with conventional telephone technology, sets up calls based on signalling information
FI113827B (en) * 2000-02-17 2004-06-15 Wicom Comm Oy Package Network Telephone
JP2001237897A (en) * 2000-02-22 2001-08-31 Nec Corp Hybrid type telephony system
FR2805955B1 (en) * 2000-03-02 2002-09-06 Sagem METHOD FOR ESTABLISHING A COMMUNICATION WITH A MOBILE TELEPHONE DURING A ROAMING PHASE
FR2806246B1 (en) * 2000-03-08 2005-02-11 Sagem METHOD OF CALLING, FOR COMMUNICATION THROUGH A COMPUTER NETWORK, A TERMINAL OF A FIRST REGIONAL CELLULAR NETWORK MOVING IN THE REGION OF A SECOND REGIONAL CELLULAR NETWORK
US6934279B1 (en) 2000-03-13 2005-08-23 Nortel Networks Limited Controlling voice communications over a data network
WO2002021747A2 (en) * 2000-04-04 2002-03-14 Alcatel, Societe Anonyme Fail-over circuit for voice-enabled switch
CN1199477C (en) * 2000-04-06 2005-04-27 西门子公司 Telecommunications system with a packet-switching communications network and a method for operating the same telecommunication system
DE10018794A1 (en) * 2000-04-15 2001-10-25 Tenovis Gmbh & Co Kg Telecommunication system
FI20001293A (en) * 2000-05-30 2001-12-01 Nokia Networks Oy Transmission of IP speech in a wireless telecommunications network
EP1168735A1 (en) * 2000-06-30 2002-01-02 BRITISH TELECOMMUNICATIONS public limited company Method to assess the quality of a voice communication over packet networks
AU2001279112A1 (en) * 2000-08-01 2002-02-13 Endius Incorporated Method and apparatus for securing vertebrae
US7325029B1 (en) * 2000-08-08 2008-01-29 Chang Ifay F Methods for enabling e-commerce voice communication
US6718030B1 (en) 2000-08-10 2004-04-06 Westell Technologies, Inc. Virtual private network system and method using voice over internet protocol
US20020031115A1 (en) * 2000-09-11 2002-03-14 Petryna Brian J. System and method for automatically establishing a telephone call over a computer network
WO2002023854A2 (en) * 2000-09-11 2002-03-21 Transnexus, Inc. Clearinghouse server for internet telephony and multimedia communications
US7394818B1 (en) * 2000-09-22 2008-07-01 Qwest Communications International Inc. Extended multi-line hunt group communication
DE10048484A1 (en) 2000-09-29 2002-04-18 Siemens Ag Method and gateway device for implementing a feature control signaling during the transition between different communication networks
FI113139B (en) * 2000-10-03 2004-02-27 Sonera Oyj A method, server, and system for establishing a connection for calls
EP1202176B1 (en) * 2000-10-31 2012-04-25 Hewlett-Packard Development Company, L.P. Message-based software system
US7218722B1 (en) 2000-12-18 2007-05-15 Westell Technologies, Inc. System and method for providing call management services in a virtual private network using voice or video over internet protocol
US7525956B2 (en) 2001-01-11 2009-04-28 Transnexus, Inc. Architectures for clearing and settlement services between internet telephony clearinghouses
US6816583B2 (en) 2001-02-12 2004-11-09 Siemens Aktiengesellschaft System and method for call transferring in a communication system
US7012915B1 (en) * 2001-02-14 2006-03-14 3Com Corporation Personalized LCD directory
US20020116464A1 (en) * 2001-02-20 2002-08-22 Mak Joon Mun Electronic communications system and method
US6907031B1 (en) * 2001-02-26 2005-06-14 At&T Corp. Customer premises equipment call re-routing technique
US7411984B1 (en) * 2001-02-27 2008-08-12 Nortel Networks Limited Method of providing tone information to nodes in a packet network
KR100396280B1 (en) * 2001-02-28 2003-09-03 삼성전자주식회사 Call forwarding method
US7355988B1 (en) * 2001-03-08 2008-04-08 Cisco Technology, Inc. Application server having asynchronous event manager configured for terminating messaging operations and rolling back prescribed data structures
US6898624B2 (en) * 2001-03-19 2005-05-24 Hewlett-Packard Development Company, L.P. System and method providing an embedded web server facsimile service
US7339934B2 (en) * 2001-04-06 2008-03-04 Level 3 Communications, Llc Alternate routing of voice communication in a packet-based network
US7215643B2 (en) * 2003-07-29 2007-05-08 Level 3 Communications, Llc System and method for providing alternate routing in a network
US20020181691A1 (en) * 2001-05-22 2002-12-05 Teltone Corporation PBX remote telephone control system
KR100383625B1 (en) 2001-05-26 2003-05-14 삼성전자주식회사 Routing service method in voice over internet protocol system
EP1286527A1 (en) * 2001-08-21 2003-02-26 Hewlett-Packard Company, A Delaware Corporation A telecommunications system and a method of selecting call attributes
KR100421015B1 (en) * 2001-08-29 2004-03-04 삼성전자주식회사 Internet facsimile providing voice mail
US20030043787A1 (en) * 2001-09-04 2003-03-06 Emerson Harry E. Interactive device control system for integrating the internet with the public switched telephone network
DE10143937B4 (en) * 2001-09-07 2007-08-09 Siemens Ag Device and method for data exchange
JP3642515B2 (en) * 2001-09-14 2005-04-27 松下電器産業株式会社 Network connection device, communication system, communication method, communication program, and recording medium
US7630359B1 (en) * 2001-09-28 2009-12-08 At&T Corp. Technique for providing translation between the packet environment and the PSTN environment
KR100876760B1 (en) * 2001-10-13 2009-01-07 삼성전자주식회사 Method for converting call processing in internet protocol telephony exchange system
KR100450964B1 (en) * 2001-10-13 2004-10-02 삼성전자주식회사 Method for servicing of station group in internet protocol telephony exchange system
KR100456123B1 (en) * 2001-11-06 2004-11-15 하경림 communication integration system for establishing fittest communication route depending on information of user's communication terminals and calling method using the same
US7200139B1 (en) * 2001-11-08 2007-04-03 At&T Corp. Method for providing VoIP services for wireless terminals
US7426218B1 (en) * 2001-11-27 2008-09-16 Verizon Business Global Llc Communication systems and QSIG communications methods
US7245716B2 (en) 2001-12-12 2007-07-17 International Business Machines Corporation Controlling hold queue position adjustment
US7167551B2 (en) * 2001-12-12 2007-01-23 International Business Machines Corporation Intermediary device based callee identification
US9088645B2 (en) * 2001-12-12 2015-07-21 International Business Machines Corporation Intermediary device initiated caller identification
US20030108159A1 (en) * 2001-12-12 2003-06-12 International Business Machines Corporation Destination device based callee identification
US8150400B1 (en) 2001-12-13 2012-04-03 At&T Intellectual Property I, L.P. Local point of presence
US7443970B2 (en) * 2001-12-17 2008-10-28 International Business Machines Corporation Logging calls according to call context
KR20030063063A (en) * 2002-01-22 2003-07-28 (주)보익스 Method and Apparatus for Exchanging a Rout of Telephone Call by Using an IP-PBX
US7212622B2 (en) * 2002-02-14 2007-05-01 Itxc Ip Holdings Sarl Call routing system
JP3852365B2 (en) * 2002-04-25 2006-11-29 日本電気株式会社 Internet protocol-compatible private branch exchange, terminal interface redundant configuration method, and program thereof
US7218629B2 (en) 2002-07-01 2007-05-15 Lonverged Data Solutions Llc Methods for initiating telephone communications using a telephone number extracted from user-highlighted content on a computer
US7885896B2 (en) 2002-07-09 2011-02-08 Avaya Inc. Method for authorizing a substitute software license server
US8041642B2 (en) 2002-07-10 2011-10-18 Avaya Inc. Predictive software license balancing
US7376415B2 (en) * 2002-07-12 2008-05-20 Language Line Services, Inc. System and method for offering portable language interpretation services
KR100469269B1 (en) * 2002-07-24 2005-02-02 엘지전자 주식회사 An Internet Telephone and a telecommunication method using the same
US7966520B2 (en) * 2002-08-30 2011-06-21 Avaya Inc. Software licensing for spare processors
US7707116B2 (en) * 2002-08-30 2010-04-27 Avaya Inc. Flexible license file feature controls
US7681245B2 (en) * 2002-08-30 2010-03-16 Avaya Inc. Remote feature activator feature extraction
US7698225B2 (en) 2002-08-30 2010-04-13 Avaya Inc. License modes in call processing
DE10241196A1 (en) * 2002-09-05 2004-03-25 Siemens Ag Communication device with processorless motherboard e.g. for integrated functions, has control device pluggable on to mother board and having a processor connected to a second interface
JP4266625B2 (en) * 2002-12-02 2009-05-20 Necインフロンティア株式会社 External LAN connection IP key telephone system, its terminal and main device, and its external LAN connection method
KR100475188B1 (en) * 2002-12-13 2005-03-10 삼성전자주식회사 Call control Apparatus in Private Branch eXchange and method therof
US7890997B2 (en) 2002-12-26 2011-02-15 Avaya Inc. Remote feature activation authentication file system
US7363381B2 (en) 2003-01-09 2008-04-22 Level 3 Communications, Llc Routing calls through a network
CA2513498C (en) * 2003-01-22 2011-10-11 Nimcat Networks Inc. Call transfer system, method and network devices
JP4205445B2 (en) * 2003-01-24 2009-01-07 株式会社日立コミュニケーションテクノロジー Exchange device
WO2004075582A1 (en) * 2003-02-21 2004-09-02 Nortel Networks Limited Data communication apparatus and method for establishing a codec-bypass connection
US7756042B2 (en) * 2003-02-26 2010-07-13 Alcatel-Lucent Usa Inc. Bandwidth guaranteed provisioning in network-based mobile virtual private network (VPN) services
US7260557B2 (en) * 2003-02-27 2007-08-21 Avaya Technology Corp. Method and apparatus for license distribution
US7099306B2 (en) * 2003-04-16 2006-08-29 Level 3 Communications, Llc System and method for internet protocol telephony advertisement protocol
US6705521B1 (en) * 2003-05-23 2004-03-16 Chunghwa Telecom Co., Ltd. Automatic car toll computing and charging method
SG120098A1 (en) * 2003-05-26 2006-03-28 Chunghwa Telecom Co Ltd Automatic car toll computing and charging method
US8594078B2 (en) 2003-06-02 2013-11-26 At&T Intellectual Property I, L.P. Method and apparatus for stand-alone voice over internet protocol with POTS telephone support
CN100388743C (en) * 2003-06-14 2008-05-14 华为技术有限公司 An adapter and communication method and system implemented by using same
US7606217B2 (en) * 2003-07-02 2009-10-20 I2 Telecom International, Inc. System and method for routing telephone calls over a voice and data network
US20050018652A1 (en) * 2003-07-21 2005-01-27 Siemens Information And Communication Networks, Inc. System and method for proxy gatekeeper in H.323 based IP telephony systems
US7920684B2 (en) * 2003-08-11 2011-04-05 Arbinet-Thexchange, Inc. Method and system for processing call setup messages using call attributes
US7356023B2 (en) * 2003-09-23 2008-04-08 Sbc Knowledge Ventures, L.P. System and method for facilitating packetized calls between managed networks
DE10347393A1 (en) * 2003-10-09 2005-05-12 Deutsche Telekom Ag Telecommunications network connection method for a telephone, whereby the network can be either a switched or packet based network and a standard interface has stored configuration data for determining connection type
US7417981B2 (en) * 2003-10-15 2008-08-26 Vonage Holdings Corp. Method and apparatus for enhanced Internet Telephony
JP4328595B2 (en) * 2003-10-21 2009-09-09 Necインフロンティア株式会社 Network, private branch exchange, and multiprotocol communication terminal control method used therefor
US20050125559A1 (en) * 2003-12-02 2005-06-09 Mutha Kailash K. Employment of one or more identifiers of one or more communication devices to determine one or more internet protocol addresses
US7715412B2 (en) 2003-12-09 2010-05-11 At&T Corp. Decomposed H.323 network border element for use in a voice-over-internet protocol network
JP4155920B2 (en) * 2003-12-25 2008-09-24 株式会社日立コミュニケーションテクノロジー Media gateway and automatic call forwarding service system
US6929507B2 (en) * 2003-12-30 2005-08-16 Huang Liang Precision Enterprise Co., Ltd. Coaxial connector structure
US7480695B2 (en) * 2004-01-22 2009-01-20 International Business Machines Corporation Using phone service to initiate requests for web information
KR100521154B1 (en) * 2004-02-03 2005-10-12 삼성전자주식회사 Apparatus and method processing call in voice/data integration switching system
US7616741B2 (en) 2004-02-06 2009-11-10 At&T Intellectual Property I, L.P. System and method for facilitating a custom ring in connection with a call
US7386111B2 (en) * 2004-02-10 2008-06-10 Vonage Network Inc. Method and apparatus for placing a long distance call based on a virtual phone number
US20050180338A1 (en) * 2004-02-17 2005-08-18 Nokia Corporation Swapping voice and video calls
US7474432B1 (en) * 2004-03-05 2009-01-06 Callwave, Inc. Methods and systems for fax routing
US7480065B1 (en) 2004-03-05 2009-01-20 Callwave, Inc. Facsimile telecommunications system and method
WO2005089147A2 (en) * 2004-03-11 2005-09-29 Transnexus, Inc. Method and system for routing calls over a packet switched computer network
US8027265B2 (en) 2004-03-19 2011-09-27 Genband Us Llc Providing a capability list of a predefined format in a communications network
US7990865B2 (en) 2004-03-19 2011-08-02 Genband Us Llc Communicating processing capabilities along a communications path
GB2413724A (en) * 2004-04-02 2005-11-02 * Siemens Aktiengesellschaft Path replacement in voip
US7480260B1 (en) * 2004-05-13 2009-01-20 3Com Corporation Method and apparatus for implementing a presence-based universal camp-on feature in packet-based telephony systems
US8126017B1 (en) * 2004-05-21 2012-02-28 At&T Intellectual Property Ii, L.P. Method for address translation in telecommunication features
EP1759463A4 (en) * 2004-06-02 2011-12-28 Mobilemax Inc System for optimizing cellular telephone call placement with minimal user overhead
US7924812B1 (en) * 2004-06-02 2011-04-12 Sprint Communications Company L.P. Domain and service based update messaging
US7809381B2 (en) 2004-07-16 2010-10-05 Bridgeport Networks, Inc. Presence detection for cellular and internet protocol telephony
US20060018449A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Telephone call routing
US8184793B2 (en) * 2004-07-20 2012-05-22 Qwest Communications International Inc. Multi-line telephone calling
US20060018448A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Routing telephone calls via a data network
US20060018310A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Data network call routing
US7447194B1 (en) * 2004-09-08 2008-11-04 Sprint Communications Company L.P. Application server update message processing
US7707405B1 (en) 2004-09-21 2010-04-27 Avaya Inc. Secure installation activation
US7697513B1 (en) * 2004-09-30 2010-04-13 Network Equipment Technologies, Inc. Private branch exchange (PBX) networking over IP networks
US8229858B1 (en) * 2004-09-30 2012-07-24 Avaya Inc. Generation of enterprise-wide licenses in a customer environment
US7747851B1 (en) 2004-09-30 2010-06-29 Avaya Inc. Certificate distribution via license files
US20060077943A1 (en) * 2004-10-12 2006-04-13 Mino Holdings, Inc. C/O M&C Corporate Services Limited Method and system for processing international calls using a voice over IP process
US20060165057A1 (en) * 2004-11-04 2006-07-27 Sbc Knowledge Ventures, L.P. Presenting dialup access numbers status information using an automated voice response system
US7822017B2 (en) * 2004-11-18 2010-10-26 Alcatel Lucent Secure voice signaling gateway
US8238329B2 (en) 2005-12-13 2012-08-07 Transnexus, Inc. Method and system for securely authorizing VoIP interconnections between anonymous peers of VoIP networks
US7457283B2 (en) * 2004-12-13 2008-11-25 Transnexus, Inc. Method and system for securely authorized VoIP interconnections between anonymous peers of VoIP networks
DE102005004864A1 (en) * 2005-02-02 2006-08-03 Siemens Ag Communication method for network e.g. local network, decides which node will be used for communication by using distributed data bank
US7823196B1 (en) 2005-02-03 2010-10-26 Sonicwall, Inc. Method and an apparatus to perform dynamic secure re-routing of data flows for public services
US20060210036A1 (en) 2005-03-16 2006-09-21 Jeffrey Citron System for effecting a telephone call over a computer network without alphanumeric keypad operation
US20060210040A1 (en) * 2005-03-16 2006-09-21 Jeffrey Citron Transfer identification software enabling electronic communication system
US8683044B2 (en) * 2005-03-16 2014-03-25 Vonage Network Llc Third party call control application program interface
US8825108B2 (en) 2005-04-06 2014-09-02 Qwest Communications International Inc. Call handling on dual-mode wireless handsets
US8989813B2 (en) * 2005-04-06 2015-03-24 Qwest Communications International Inc. Handset registration in a dual-mode environment
US20060227948A1 (en) * 2005-04-08 2006-10-12 Sbc Knowledge Ventures, L.P. System and method for implementing call controls in a telephony network
US7623633B2 (en) * 2005-04-28 2009-11-24 Cisco Technology, Inc. System and method for providing presence information to voicemail users
US20060268848A1 (en) * 2005-05-25 2006-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Connection type handover of voice over internet protocol call based low-quality detection
US7970400B2 (en) * 2005-05-25 2011-06-28 Telefonaktiebolaget Lm Ericsson (Publ) Connection type handover of voice over internet protocol call based on resource type
US20060268900A1 (en) * 2005-05-25 2006-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Local switching of calls setup by multimedia core network
US7801105B2 (en) * 2005-05-25 2010-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Scheduling radio resources for symmetric service data connections
US8289952B2 (en) * 2005-05-25 2012-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced VoIP media flow quality by adapting speech encoding based on selected modulation and coding scheme (MCS)
US8369311B1 (en) 2005-07-01 2013-02-05 Callwave Communications, Llc Methods and systems for providing telephony services to fixed and mobile telephonic devices
US7957517B2 (en) * 2005-08-26 2011-06-07 At&T Intellectual Property Ii, L.P. Method and apparatus for providing internet protocol call transfer in communication networks
US7814023B1 (en) 2005-09-08 2010-10-12 Avaya Inc. Secure download manager
US7912203B2 (en) * 2005-09-09 2011-03-22 Avaya Inc. Method and apparatus for providing called party information to a coverage point during survivable processor operation
US7792276B2 (en) * 2005-09-13 2010-09-07 Language Line Services, Inc. Language interpretation call transferring in a telecommunications network
US8023626B2 (en) * 2005-09-13 2011-09-20 Language Line Services, Inc. System and method for providing language interpretation
US7894596B2 (en) * 2005-09-13 2011-02-22 Language Line Services, Inc. Systems and methods for providing language interpretation
EP1935154B1 (en) * 2005-10-13 2011-06-01 Vonage Holdings Corp. Method and system for detecting a change in device attachment
US7532581B1 (en) * 2005-10-28 2009-05-12 Mindspeed Technologies, Inc. Voice quality monitoring and reporting
MX2008006172A (en) 2005-11-09 2008-10-09 Vonage Holdings Corp Method and system for customized caller identification.
US8566342B2 (en) * 2005-12-07 2013-10-22 Berm Logic Llc In-memory data optimization system
US7924820B2 (en) * 2005-12-07 2011-04-12 Marron Interconnect Llc Method and system for facilitating communications
US8649485B2 (en) 2005-12-28 2014-02-11 Sap Ag System and method for automated connection triggered by availability status
AU2007211267A1 (en) * 2006-02-01 2007-08-09 Vonage Holdings Corp. Method and apparatus for communicating a status of a device in a packet-based communication network
US20070183397A1 (en) * 2006-02-07 2007-08-09 Bennett James D Computing device supporting selective local call termination and call bridging
US20070183399A1 (en) * 2006-02-07 2007-08-09 Bennett James D Telephone supporting selective local call termination and call bridging
US8917717B2 (en) * 2007-02-13 2014-12-23 Vonage Network Llc Method and system for multi-modal communications
US7844040B2 (en) * 2006-02-23 2010-11-30 Qualcomm Incorporated Device and method for announcing an incoming call
CN101390337B (en) * 2006-02-27 2011-09-28 沃纳格控股公司 Automatic device configuration
US20070201432A1 (en) * 2006-02-28 2007-08-30 Ankur Sood Voice gateway for multiple voice communication network
CN101411175A (en) * 2006-03-30 2009-04-15 英国电讯有限公司 Routing of telecommunications
US20070239625A1 (en) * 2006-04-05 2007-10-11 Language Line Services, Inc. System and method for providing access to language interpretation
US7593523B2 (en) * 2006-04-24 2009-09-22 Language Line Services, Inc. System and method for providing incoming call distribution
US8184798B2 (en) * 2006-06-13 2012-05-22 Tekelec Methods, systems and computer program products for accessing number portability (NP) and E.164 number (ENUM) data using a common NP/ENUM data locator structure
US8509786B2 (en) * 2006-08-04 2013-08-13 At&T Intellectual Property I, L.P. Systems and methods for handling calls in a wireless enabled PBX system using mobile switching protocols
US8503431B2 (en) * 2006-08-25 2013-08-06 Wireless Wonders Ltd. Mobile phone related indirect communication system and method
US9270799B2 (en) 2006-08-25 2016-02-23 Wireless Wonders Ltd. Using indirect communication to provide a solution to use international dialing convention and incorporating phone numbers for non-phone devices
US7773738B2 (en) * 2006-09-22 2010-08-10 Language Line Services, Inc. Systems and methods for providing relayed language interpretation
US20080086700A1 (en) * 2006-10-06 2008-04-10 Rodriguez Robert A Systems and Methods for Isolating On-Screen Textual Data
FR2909249B1 (en) * 2006-11-28 2009-05-01 Alcatel Sa METHOD FOR TRANSFERRING TELEPHONE COMMUNICATION FROM WIRELESS NETWORK TO ANOTHER AND MOBILE BI-MODE TELEPHONE TERMINAL FOR CARRYING OUT SAID METHOD.
US8346239B2 (en) 2006-12-28 2013-01-01 Genband Us Llc Methods, systems, and computer program products for silence insertion descriptor (SID) conversion
US7929544B2 (en) * 2006-12-29 2011-04-19 Alcatel-Lucent Usa Inc. Method and apparatus for linking identification data to a call in a network
US20080192655A1 (en) * 2007-02-09 2008-08-14 Ted Vagelos Systems And Methods For Providing Enhanced Telephone Services
US8213440B2 (en) * 2007-02-21 2012-07-03 Tekelec Global, Inc. Methods, systems, and computer program products for using a location routing number based query and response mechanism to route calls to IP multimedia subsystem (IMS) subscribers
JP5168991B2 (en) * 2007-04-12 2013-03-27 Necカシオモバイルコミュニケーションズ株式会社 Portable terminal device and program
WO2009006195A2 (en) * 2007-07-02 2009-01-08 Motorola, Inc. Method and system for optimizing two-stage dialing
GB0713786D0 (en) * 2007-07-16 2007-08-22 Cellfire Security Technologies Call processing system
US9137377B2 (en) * 2007-08-22 2015-09-15 Citrix Systems, Inc. Systems and methods for at least partially releasing an appliance from a private branch exchange
US8750490B2 (en) * 2007-08-22 2014-06-10 Citrix Systems, Inc. Systems and methods for establishing a communication session among end-points
US8315362B2 (en) * 2007-08-22 2012-11-20 Citrix Systems, Inc. Systems and methods for voicemail avoidance
US8792118B2 (en) * 2007-09-26 2014-07-29 Ringcentral Inc. User interfaces and methods to provision electronic facsimiles
US20090086278A1 (en) * 2007-09-27 2009-04-02 Ringcentral, Inc. Electronic facsimile delivery systems and methods
US8670545B2 (en) 2007-09-28 2014-03-11 Ringcentral, Inc. Inbound call identification and management
US8600391B2 (en) 2008-11-24 2013-12-03 Ringcentral, Inc. Call management for location-aware mobile devices
US8275110B2 (en) 2007-09-28 2012-09-25 Ringcentral, Inc. Active call filtering, screening and dispatching
US20090110172A1 (en) * 2007-10-26 2009-04-30 Musa Raoul Unmehopa Method of queuing and returning calls to an interactive voice response system
US20090109962A1 (en) * 2007-10-27 2009-04-30 Joseph Hosteny Method and apparatus for dynamically allocating and routing telephony endpoints
US20090187848A1 (en) * 2007-12-21 2009-07-23 Richard Leo Murtagh Methods and systems for identifying a process for analyzing data displayed by a window to a user of a computing device
US8713440B2 (en) * 2008-02-13 2014-04-29 Microsoft Corporation Techniques to manage communications resources for a multimedia conference event
JP5012561B2 (en) * 2008-02-25 2012-08-29 沖電気工業株式会社 Callee information notification system, callee information notification method, application server, and communication terminal
US8594679B2 (en) * 2008-03-07 2013-11-26 Tekelec Global, Inc. Methods, systems, and computer readable media for routing a message service message through a communications network
TWI383703B (en) * 2008-04-28 2013-01-21 Quanta Comp Inc Communication system and method thereof
SG157972A1 (en) * 2008-06-16 2010-01-29 Teliwave Pte Ltd Internet based communication system and method
US8612614B2 (en) 2008-07-17 2013-12-17 Citrix Systems, Inc. Method and system for establishing a dedicated session for a member of a common frame buffer group
KR20100039508A (en) * 2008-10-08 2010-04-16 삼성전자주식회사 Apparatus and method for providing fax service in ip multimedia subsystem
US9584959B2 (en) 2008-11-24 2017-02-28 Tekelec Global, Inc. Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network
US8611879B2 (en) * 2008-11-24 2013-12-17 Ringcentral, Inc. Bridge line appearance for location-aware mobile devices
US8780383B2 (en) 2008-11-25 2014-07-15 Ringcentral, Inc. Authenticated facsimile transmission from mobile devices
WO2010062981A2 (en) 2008-11-26 2010-06-03 Ringcentral, Inc. Centralized status server for call management of location-aware mobile devices
US8467306B2 (en) * 2008-12-04 2013-06-18 At&T Intellectual Property I, L. P. Blending telephony services in an internet protocol multimedia subsystem
US8428243B2 (en) * 2008-12-19 2013-04-23 Verizon Patent And Licensing Inc. Method and system for trunk independent gateway transfer of calls
WO2010081490A1 (en) * 2009-01-16 2010-07-22 Telefonaktiebolaget L M Ericsson (Publ) Signalling messages in a communications network node to communicate a called address string
US8582560B2 (en) 2009-01-30 2013-11-12 Level 3 Communications, Llc System and method for routing calls associated with private dialing plans
JP5381194B2 (en) * 2009-03-16 2014-01-08 富士通株式会社 Communication program, relay node, and communication method
EP2443811B1 (en) 2009-06-17 2018-10-17 Bridgeport Networks, Inc. Enhanced presence detection for routing decisions
US8908541B2 (en) 2009-08-04 2014-12-09 Genband Us Llc Methods, systems, and computer readable media for intelligent optimization of digital signal processor (DSP) resource utilization in a media gateway
US8224337B2 (en) * 2009-09-16 2012-07-17 Tekelec, Inc. Methods, systems, and computer readable media for providing foreign routing address information to a telecommunications network gateway
US8621004B2 (en) * 2009-09-24 2013-12-31 Verizon Patent And Licensing Inc. Method and system for transfer of calls from an IP based phone
US8374183B2 (en) * 2010-06-22 2013-02-12 Microsoft Corporation Distributed virtual network gateways
US9621721B2 (en) * 2010-10-22 2017-04-11 Mitel Networks Corporation Incoming call redirection
US20120143912A1 (en) * 2010-12-05 2012-06-07 Unisys Corp. Extending legacy database engines with object-based functionality
GB2487392B (en) * 2011-01-19 2015-03-18 Bank Of America System for improving the efficiency of a cellular gateway
US8605875B2 (en) * 2011-02-24 2013-12-10 International Business Machines Corporation Dynamic call management and display
WO2012135931A1 (en) * 2011-04-04 2012-10-11 Cambrai Solutions Inc. Application server for provisioning a controlled communications system in a cloud-based environment
US8817777B2 (en) * 2011-08-10 2014-08-26 Microsoft Corporation Hybrid unified communications deployment between cloud and on-premise
CN103200205A (en) * 2012-01-05 2013-07-10 华为技术有限公司 Voice examination and approval method, equipment and system
US9087191B2 (en) * 2012-08-24 2015-07-21 Vmware, Inc. Method and system for facilitating isolated workspace for applications
US20150081495A1 (en) * 2013-09-19 2015-03-19 Barclays Bank Plc System and Method for Account Succession
US9397947B2 (en) 2014-03-11 2016-07-19 International Business Machines Corporation Quality of experience for communication sessions
US10122682B1 (en) * 2016-06-23 2018-11-06 8X8, Inc. Region-based bridging of calls using client-specific control and revised caller identifiers
EP3491813B1 (en) * 2016-08-01 2022-02-09 Youmail, Inc System and method for facilitating setup and joining of conference calls
US10193992B2 (en) 2017-03-24 2019-01-29 Accenture Global Solutions Limited Reactive API gateway
JP6403239B1 (en) * 2017-03-31 2018-10-10 Necプラットフォームズ株式会社 Telephone exchange system, telephone exchange apparatus, method, and program
US10033709B1 (en) 2017-11-20 2018-07-24 Microsoft Technology Licensing, Llc Method and apparatus for improving privacy of communications through channels having excess capacity

Citations (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4313036A (en) * 1980-02-19 1982-01-26 Rolm Corporation Distributed CBX system employing packet network
US4317197A (en) * 1978-06-02 1982-02-23 Texas Instruments Incorporated Transparent intelligent network for data and voice
US4334306A (en) * 1978-06-02 1982-06-08 Texas Instruments Incorporated Transparent intelligent network for data and voice
US4442321A (en) * 1981-06-08 1984-04-10 Rockwell International Corporation Transparent dialing between interconnected telecommunication switching systems
US4494230A (en) * 1982-06-25 1985-01-15 At&T Bell Laboratories Fast packet switching system
US4567323A (en) * 1983-07-12 1986-01-28 At&T Bell Laboratories Method and apparatus for providing a plurality of special services
US4587651A (en) * 1983-05-04 1986-05-06 Cxc Corporation Distributed variable bandwidth switch for voice, data, and image communications
US4597073A (en) * 1985-08-27 1986-06-24 Data Race, Inc. Full-duplex split-speed data communication unit for remote DTE
US4747127A (en) * 1985-12-23 1988-05-24 American Telephone And Telegraph Company, At&T Bell Laboratories Customer programmable real-time system
US4803720A (en) * 1986-09-22 1989-02-07 International Business Machines Corporation Dual plane cross point switch architecture for a micro-PBX
US4811334A (en) * 1986-07-01 1989-03-07 U.S. Philips Corp. Method of operation of a nodal telephone and data communication network to provide specific facilities in changeable domains of the network
US4897866A (en) * 1988-10-19 1990-01-30 American Telephone And Telegraph Company, At&T Bell Laboratories Telecommunication system with subscriber controlled feature modification
US4901312A (en) * 1988-05-05 1990-02-13 Hui Man H Remote interconnection of local area networks
US4907260A (en) * 1987-10-05 1990-03-06 Ambassador College Telephone line communications control system
US4924500A (en) * 1989-05-17 1990-05-08 Northern Telecom Limited Carrier independent network services
US4982421A (en) * 1989-10-27 1991-01-01 At&T Bell Laboratories Virtual private line service
US4993018A (en) * 1987-02-06 1991-02-12 Fujitsu Limited Self-routing switching system with multiple link connections between incoming and outgoing lines
US5097528A (en) * 1991-02-25 1992-03-17 International Business Machines Corporation System for integrating telephony data with data processing systems
US5107493A (en) * 1989-08-02 1992-04-21 At&T Bell Laboratories High-speed packet data network using serially connected packet and circuit switches
US5179585A (en) * 1991-01-16 1993-01-12 Octel Communications Corporation Integrated voice messaging/voice response system
US5185742A (en) * 1990-12-31 1993-02-09 At&T Bell Laboratories Transparent signaling for remote terminals
US5185786A (en) * 1990-11-13 1993-02-09 Dialogic Corporation Automatic call center overflow retrieval system
US5193110A (en) * 1990-10-09 1993-03-09 Boston Technology, Incorporated Integrated services platform for telephone communication system
US5212691A (en) * 1990-10-30 1993-05-18 Nec Corporation Private network with means for establishing virtual tie trunks between PBXS through ISDN public network
US5220562A (en) * 1989-05-12 1993-06-15 Hitachi, Ltd. Bridge apparatus and a communication system between networks using the bridge apparatus
US5222125A (en) * 1991-09-03 1993-06-22 At&T Bell Laboratories System for providing personalized telephone calling features
US5303290A (en) * 1991-11-29 1994-04-12 At&T Bell Laboratories System for elminating glare in virtual private line circuits
US5311572A (en) * 1991-10-03 1994-05-10 At&T Bell Laboratories Cooperative databases call processing system
US5311577A (en) * 1992-03-06 1994-05-10 International Business Machines Corporation Data processing system, method and program for constructing host access tables for integration of telephony data with data processing systems
US5313465A (en) * 1992-05-13 1994-05-17 Digital Equipment Corporation Method of merging networks across a common backbone network
US5315646A (en) * 1990-12-18 1994-05-24 Bell Communications Research Systems and processes for providing multiple interfaces for telephone services
US5321743A (en) * 1992-02-24 1994-06-14 At&T Bell Laboratories Shared-tenant services arrangement providing numbering-plan independence and cross-plan access to tenant groups
US5321744A (en) * 1992-09-29 1994-06-14 Excel, Inc. Programmable telecommunication switch for personal computer
US5323452A (en) * 1990-12-18 1994-06-21 Bell Communications Research, Inc. Visual programming of telephone network call processing logic
US5386464A (en) * 1991-12-19 1995-01-31 Telefonaktiebolaget L M Ericsson Feature control system utilizing design oriented state table language
US5390242A (en) * 1991-12-30 1995-02-14 At&T Corp. Rerouting in a distributed telecommunication system
US5404565A (en) * 1991-08-07 1995-04-04 International Business Machines Corporation Message tracking in a parallel network employing a status word at each node which reflects a message's progress
US5404451A (en) * 1990-02-06 1995-04-04 Nemirovsky; Paul System for identifying candidate link, determining underutilized link, evaluating addition of candidate link and removing of underutilized link to reduce network cost
US5404396A (en) * 1993-08-27 1995-04-04 Telefonaktiebolaget Lm Ericsson Feature interaction manager
US5414762A (en) * 1994-01-18 1995-05-09 Q.Sys International, Inc. Telephony controller with functionality command converter
US5418844A (en) * 1992-04-17 1995-05-23 Bell Atlantic Network Services, Inc. Automatic access to information service providers
US5418845A (en) * 1992-05-28 1995-05-23 At&T Corp. Arrangement for obtaining information from a switching system database by an adjunct processor
US5420916A (en) * 1992-02-20 1995-05-30 Nec Corporation Signaling network having common signaling node for protocol conversion
US5422941A (en) * 1992-02-28 1995-06-06 Bell Atlantic Network Services, Inc. Extension of centrex services
US5428679A (en) * 1993-03-23 1995-06-27 C&P Of Maryland Automated service assurance method and system
US5481534A (en) * 1991-09-27 1996-01-02 At&T Corp. Data packet switch apparatus and method with enhanced charge assessment capability
US5481603A (en) * 1993-09-28 1996-01-02 At&T Corp. Intelligent call processing based upon complete identification of calling station
US5483576A (en) * 1993-03-31 1996-01-09 Data Race, Inc. Method and apparatus for communicating data over a radio transceiver with a modem
US5483585A (en) * 1993-12-29 1996-01-09 British Telecommunications, Plc Apparatus for managing an element manager for a telecommunications switch
US5487110A (en) * 1994-02-01 1996-01-23 Dsc Communications Corporation Apparatus and method for virtual private telephone line with automatic ring down
US5490212A (en) * 1993-08-30 1996-02-06 Alcatel Sel Aktiengesellschaft Call-routing method for a virtual private network as well as service computer and exchange therefor
US5491694A (en) * 1994-01-28 1996-02-13 Cabletron Systems, Inc. System and method for allocating a shared resource among competing devices
US5491686A (en) * 1994-03-18 1996-02-13 Fujitsu Limited Composite ring network having an increased redundancy for restoring communication path
US5493564A (en) * 1994-03-25 1996-02-20 Sprint International Communications Corp. Method and apparatus for global routing of electronic messages
US5495479A (en) * 1993-07-30 1996-02-27 International Business Machines Corporation Method and apparatus for an automatic decomposition of a network topology into a backbone and subareas
US5495484A (en) * 1993-10-12 1996-02-27 Dsc Communications Corporation Distributed telecommunications switching system
US5497368A (en) * 1993-08-18 1996-03-05 Koninklijke Ptt Nederland N.V. Routing method for a hierarchical communications network, and a hierarchical communications network having improved routing
US5502816A (en) * 1994-03-25 1996-03-26 At&T Corp. Method of routing a request for a virtual circuit based on information from concurrent requests
US5502757A (en) * 1993-12-22 1996-03-26 At&T Corp. Location dependent service for a wireless telephone
US5509058A (en) * 1992-09-11 1996-04-16 Mitel Corporation Global management of telephone directory
US5509065A (en) * 1993-11-12 1996-04-16 Teltrend Inc. Dual span monitoring system for maintenance shelf control
US5515429A (en) * 1991-03-12 1996-05-07 Fujitsu Limited Backup apparatus against line defect and backup method against line defect
US5517562A (en) * 1994-11-01 1996-05-14 Independent Telecommunications Network, Inc. Method and system for providing a distributed service network for telecommunications service providers
US5517564A (en) * 1994-07-29 1996-05-14 British Telecommunications Public Limited Company Communication apparatus and method
US5519772A (en) * 1994-01-31 1996-05-21 Bell Communications Research, Inc. Network-based telephone system having interactive capabilities
US5519770A (en) * 1990-06-26 1996-05-21 Australian And Overseas Telecommunications Corporation Limited Enhanced telephony apparatus and system
US5521909A (en) * 1994-07-22 1996-05-28 Newbridge Networks Corporation Frame relay management system
US5521970A (en) * 1995-03-29 1996-05-28 At&T Corp. Arrangement for extending call-coverage across a network of nodes
US5600644A (en) * 1995-03-10 1997-02-04 At&T Method and apparatus for interconnecting LANs
US5602909A (en) * 1995-12-21 1997-02-11 Stentor Resource Centre, Inc. Number portability using database query
US5602843A (en) * 1994-07-21 1997-02-11 Mitel Corporation Integrated wired and wireless telecommunications system
US5602851A (en) * 1993-12-22 1997-02-11 International Business Machines Corporation Multi-port bridge
US5604737A (en) * 1993-12-15 1997-02-18 Hitachi, Ltd. Voice communication system and voice communication method
US5606600A (en) * 1995-05-10 1997-02-25 Mci Communications Corporation Generalized statistics engine for telephone network employing a network information concentrator
US5608721A (en) * 1995-04-03 1997-03-04 Motorola, Inc. Communications network and method which implement diversified routing
US5608790A (en) * 1995-06-07 1997-03-04 Lucent Technologies Inc. Trunk utilization in a telecommunications network
US5608871A (en) * 1993-11-17 1997-03-04 Kabushiki Kaisha Toshiba Inter-network connection apparatus having address searching/registering sections, network control sections with a receiving FIFO memory and a sending FIFO memory
US5610977A (en) * 1995-12-21 1997-03-11 Stentor Resource Centre, Inc. Number portability using ISUP message option
US5610910A (en) * 1995-08-17 1997-03-11 Northern Telecom Limited Access to telecommunications networks in multi-service environment
US5621728A (en) * 1994-09-12 1997-04-15 Bell Atlantic Network Services, Inc. Level 1 gateway controlling broadband communications for video dial tone networks
US5623605A (en) * 1994-08-29 1997-04-22 Lucent Technologies Inc. Methods and systems for interprocess communication and inter-network data transfer
US5633924A (en) * 1993-09-30 1997-05-27 Lucent Technologies Inc. Telecommunication network with integrated network-wide automatic call distribution
US5712907A (en) * 1995-09-18 1998-01-27 Open Port Technology, Inc. Pro-active message delivery system and method
US5717748A (en) * 1994-10-28 1998-02-10 Lucent Technologies Inc. Means and method for updating databases supporting local telephone number portability
US5727047A (en) * 1995-01-03 1998-03-10 Lucent Technologies Inc. Arrangement for interfacing a telephone device with a personal computer
US5732078A (en) * 1996-01-16 1998-03-24 Bell Communications Research, Inc. On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network
US5737333A (en) * 1995-06-23 1998-04-07 Lucent Technologies Inc. Method and apparatus for interconnecting ATM-attached hosts with telephone-network attached hosts
US5742596A (en) * 1995-11-12 1998-04-21 Phonet Communication Ltd. Network based distributed PBX system
US5745556A (en) * 1995-09-22 1998-04-28 At&T Corp. Interactive and information data services telephone billing system
US5752082A (en) * 1995-06-29 1998-05-12 Data Race System for multiplexing pins of a PC card socket and PC card bus adapter for providing audio communication between PC card and computer sound system
US5862211A (en) * 1997-01-13 1999-01-19 Lucent Technologies Inc. Automatic simultaneous voice-and-data call setup for remote-site servicing
US5867494A (en) * 1996-11-18 1999-02-02 Mci Communication Corporation System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
US5884262A (en) * 1996-03-28 1999-03-16 Bell Atlantic Network Services, Inc. Computer network audio access and conversion system
US5884032A (en) * 1995-09-25 1999-03-16 The New Brunswick Telephone Company, Limited System for coordinating communications via customer contact channel changing system using call centre for setting up the call between customer and an available help agent
US5907548A (en) * 1995-12-28 1999-05-25 Lucent Technologies Inc. Telephone network local access using data messaging
US6016343A (en) * 1993-10-15 2000-01-18 Link Usa Corporation Call-processing system and method
US6016499A (en) * 1997-07-21 2000-01-18 Novell, Inc. System and method for accessing a directory services respository
US6026087A (en) * 1997-03-14 2000-02-15 Efusion, Inc. Method and apparatus for establishing a voice call to a PSTN extension for a networked client computer

Family Cites Families (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3769462A (en) 1972-09-29 1973-10-30 Stromberg Carlson Corp Private automatic branch exchange service circuit complex
US3925621A (en) 1974-01-17 1975-12-09 Collins Arthur A Inc Digital circuit switched time-space-time switch equipped time division transmission loop system
US4348554A (en) 1980-03-21 1982-09-07 Bell Telephone Laboratories, Incorporated Method of providing virtual private network telephone service
US4488289A (en) 1982-06-25 1984-12-11 At&T Bell Laboratories Interface facility for a packet switching system
US4707827A (en) 1986-03-21 1987-11-17 Zenith Electronics Corporation Bridging techniques for local area networks
US4787082A (en) 1986-07-24 1988-11-22 American Telephone And Telegraph Company, At&T Bell Laboratories Data flow control arrangement for local area network
US4764919A (en) 1986-09-05 1988-08-16 American Telephone And Telegraph Company, At&T Bell Laboratories Virtual PBX call processing method
US4782517A (en) 1986-09-08 1988-11-01 Bell Communications Research, Inc. System and method for defining and providing telephone network services
US4970722A (en) 1987-11-02 1990-11-13 Amp Incorporated Broadband local area network
US4866758A (en) 1988-10-31 1989-09-12 American Telephone And Telegraph Company Phone management server for use with a personal computer LAN
US4942602A (en) 1989-01-06 1990-07-17 International Business Machines Corporation Coordinated transfer of voice and information through a network of digital switches
JP2749098B2 (en) 1989-02-03 1998-05-13 株式会社日立製作所 Communication line switching / combination method
US4959854A (en) 1990-01-26 1990-09-25 Intervoice Inc. Apparatus and method for automatically reconfiguring telephone network resources
FR2661298B1 (en) 1990-04-23 1992-06-12 Cit Alcatel METHOD AND DEVICE FOR RETURNING TO A NORMAL LINK AFTER USE OF A BACKUP LINK IN A DATA TRANSMISSION SYSTEM.
JP2816385B2 (en) 1990-06-29 1998-10-27 富士通株式会社 Route selection method for PBX tenant service
US5333185A (en) 1991-06-03 1994-07-26 At&T Bell Laboratories System for processing calling party information for international communications services
DE4119672A1 (en) 1991-06-14 1992-12-17 Standard Elektrik Lorenz Ag CONNECTING BETWEEN TERMINALS FOR MOBILE PARTICIPANTS IN A NETWORK
US5327489A (en) 1991-12-16 1994-07-05 At&T Bell Laboratories Method and apparatus for monitoring a network for customer signaling during the term of a call
US5365520A (en) 1992-03-27 1994-11-15 Motorola, Inc. Dynamic signal routing
US5377261A (en) 1992-05-04 1994-12-27 At&T Corp. Apparatus and method for accessing both local and network-based features at a telephone terminal
DE4221474C2 (en) 1992-06-30 1994-07-14 Siemens Ag Communication system for multi-service communication terminals in local area networks
US5448631A (en) 1992-10-13 1995-09-05 U S West Advanced Technologies, Inc. Apparatus for handling features in a telephone network
US5440624A (en) 1992-11-10 1995-08-08 Netmedia, Inc. Method and apparatus for providing adaptive administration and control of an electronic conference
JPH084273B2 (en) 1992-11-30 1996-01-17 日本電気株式会社 Complex communication network
US5436957A (en) 1992-12-24 1995-07-25 Bell Atlantic Network Services, Inc. Subscriber control of access restrictions on a plurality of the subscriber's telephone lines
US5450482A (en) 1992-12-29 1995-09-12 At&T Corp. Dynamic network automatic call distribution
US5371735A (en) 1993-03-04 1994-12-06 International Business Machines Corporation Communication network with non-unique device identifiers and method of establishing connection paths in such a network
US5377186A (en) 1993-07-21 1994-12-27 Telefonaktiebolaget L M Ericsson System for providing enhanced subscriber services using ISUP call-setup protocol
CN1075306C (en) 1993-09-22 2001-11-21 At&T有限公司 Method for permitting subscribers to change call features in real time
US5440563A (en) 1993-10-12 1995-08-08 At&T Corp. Service circuit allocation in large networks
US5448632A (en) 1993-10-27 1995-09-05 At&T Corp. Call monitoring system for intelligent call processing
US5463684A (en) 1993-11-03 1995-10-31 Microlog Corporation Telecommunications system for transferring calls without a private branch exchange
US5469500A (en) 1993-11-12 1995-11-21 Voiceplex Corporation Method and apparatus for delivering calling services
US5473679A (en) 1993-12-09 1995-12-05 At&T Corp. Signaling system for broadband communications networks
US5465294A (en) 1994-06-30 1995-11-07 At&T Corp. System and method for recovering from a telecommunications disaster
CA2168484C (en) * 1995-03-13 2000-12-05 Mehmet Reha Civanlar Client-server architecture using internet and public switched networks
US5526413A (en) * 1995-04-17 1996-06-11 Bell Atlantic Network Services, Inc. Advanced intelligent network access by customer premise equipment
FI104869B (en) * 1995-05-24 2000-04-14 Ericsson Telefon Ab L M Method for establishing a voice connection between networks and an intelligent network service
DE69634854T2 (en) * 1995-12-11 2006-06-08 Hewlett-Packard Development Co., L.P., Houston METHOD OF ACCESSING SERVICE SUBJECT FOR APPLICATION IN A REMOTE CONTROL SYSTEM
US7336649B1 (en) * 1995-12-20 2008-02-26 Verizon Business Global Llc Hybrid packet-switched and circuit-switched telephony system
US5946386A (en) * 1996-03-11 1999-08-31 Xantel Corporation Call management system with call control from user workstation computers
US6584094B2 (en) * 1996-09-12 2003-06-24 Avaya Technology Corp. Techniques for providing telephonic communications over the internet
US5987102A (en) * 1997-03-14 1999-11-16 Efusion, Inc. Method and apparatus for bridging a voice call including selective provision of information in non-audio to the caller
US6337858B1 (en) * 1997-10-10 2002-01-08 Nortel Networks Limited Method and apparatus for originating voice calls from a data network
US6208057B1 (en) * 1998-12-28 2001-03-27 Visteon Global Technologies, Inc. Electrical machine with reduced audible noise

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4317197A (en) * 1978-06-02 1982-02-23 Texas Instruments Incorporated Transparent intelligent network for data and voice
US4334306A (en) * 1978-06-02 1982-06-08 Texas Instruments Incorporated Transparent intelligent network for data and voice
US4313036A (en) * 1980-02-19 1982-01-26 Rolm Corporation Distributed CBX system employing packet network
US4442321A (en) * 1981-06-08 1984-04-10 Rockwell International Corporation Transparent dialing between interconnected telecommunication switching systems
US4494230A (en) * 1982-06-25 1985-01-15 At&T Bell Laboratories Fast packet switching system
US4587651A (en) * 1983-05-04 1986-05-06 Cxc Corporation Distributed variable bandwidth switch for voice, data, and image communications
US4567323A (en) * 1983-07-12 1986-01-28 At&T Bell Laboratories Method and apparatus for providing a plurality of special services
US4597073A (en) * 1985-08-27 1986-06-24 Data Race, Inc. Full-duplex split-speed data communication unit for remote DTE
US4747127A (en) * 1985-12-23 1988-05-24 American Telephone And Telegraph Company, At&T Bell Laboratories Customer programmable real-time system
US4811334A (en) * 1986-07-01 1989-03-07 U.S. Philips Corp. Method of operation of a nodal telephone and data communication network to provide specific facilities in changeable domains of the network
US4803720A (en) * 1986-09-22 1989-02-07 International Business Machines Corporation Dual plane cross point switch architecture for a micro-PBX
US4993018A (en) * 1987-02-06 1991-02-12 Fujitsu Limited Self-routing switching system with multiple link connections between incoming and outgoing lines
US4907260A (en) * 1987-10-05 1990-03-06 Ambassador College Telephone line communications control system
US4901312A (en) * 1988-05-05 1990-02-13 Hui Man H Remote interconnection of local area networks
US4897866A (en) * 1988-10-19 1990-01-30 American Telephone And Telegraph Company, At&T Bell Laboratories Telecommunication system with subscriber controlled feature modification
US5220562A (en) * 1989-05-12 1993-06-15 Hitachi, Ltd. Bridge apparatus and a communication system between networks using the bridge apparatus
US4924500A (en) * 1989-05-17 1990-05-08 Northern Telecom Limited Carrier independent network services
US5107493A (en) * 1989-08-02 1992-04-21 At&T Bell Laboratories High-speed packet data network using serially connected packet and circuit switches
US4982421A (en) * 1989-10-27 1991-01-01 At&T Bell Laboratories Virtual private line service
US5404451A (en) * 1990-02-06 1995-04-04 Nemirovsky; Paul System for identifying candidate link, determining underutilized link, evaluating addition of candidate link and removing of underutilized link to reduce network cost
US5519770A (en) * 1990-06-26 1996-05-21 Australian And Overseas Telecommunications Corporation Limited Enhanced telephony apparatus and system
US5193110A (en) * 1990-10-09 1993-03-09 Boston Technology, Incorporated Integrated services platform for telephone communication system
US5212691A (en) * 1990-10-30 1993-05-18 Nec Corporation Private network with means for establishing virtual tie trunks between PBXS through ISDN public network
US5185786A (en) * 1990-11-13 1993-02-09 Dialogic Corporation Automatic call center overflow retrieval system
US5315646A (en) * 1990-12-18 1994-05-24 Bell Communications Research Systems and processes for providing multiple interfaces for telephone services
US5323452A (en) * 1990-12-18 1994-06-21 Bell Communications Research, Inc. Visual programming of telephone network call processing logic
US5185742A (en) * 1990-12-31 1993-02-09 At&T Bell Laboratories Transparent signaling for remote terminals
US5416830A (en) * 1991-01-16 1995-05-16 Octel Communications Corporation Integrated voice meassaging/voice response system
US5179585A (en) * 1991-01-16 1993-01-12 Octel Communications Corporation Integrated voice messaging/voice response system
US5097528A (en) * 1991-02-25 1992-03-17 International Business Machines Corporation System for integrating telephony data with data processing systems
US5515429A (en) * 1991-03-12 1996-05-07 Fujitsu Limited Backup apparatus against line defect and backup method against line defect
US5404565A (en) * 1991-08-07 1995-04-04 International Business Machines Corporation Message tracking in a parallel network employing a status word at each node which reflects a message's progress
US5222125A (en) * 1991-09-03 1993-06-22 At&T Bell Laboratories System for providing personalized telephone calling features
US5481534A (en) * 1991-09-27 1996-01-02 At&T Corp. Data packet switch apparatus and method with enhanced charge assessment capability
US5311572A (en) * 1991-10-03 1994-05-10 At&T Bell Laboratories Cooperative databases call processing system
US5303290A (en) * 1991-11-29 1994-04-12 At&T Bell Laboratories System for elminating glare in virtual private line circuits
US5386464A (en) * 1991-12-19 1995-01-31 Telefonaktiebolaget L M Ericsson Feature control system utilizing design oriented state table language
US5390242A (en) * 1991-12-30 1995-02-14 At&T Corp. Rerouting in a distributed telecommunication system
US5420916A (en) * 1992-02-20 1995-05-30 Nec Corporation Signaling network having common signaling node for protocol conversion
US5321743A (en) * 1992-02-24 1994-06-14 At&T Bell Laboratories Shared-tenant services arrangement providing numbering-plan independence and cross-plan access to tenant groups
US5422941A (en) * 1992-02-28 1995-06-06 Bell Atlantic Network Services, Inc. Extension of centrex services
US5311577A (en) * 1992-03-06 1994-05-10 International Business Machines Corporation Data processing system, method and program for constructing host access tables for integration of telephony data with data processing systems
US5418844A (en) * 1992-04-17 1995-05-23 Bell Atlantic Network Services, Inc. Automatic access to information service providers
US5313465A (en) * 1992-05-13 1994-05-17 Digital Equipment Corporation Method of merging networks across a common backbone network
US5418845A (en) * 1992-05-28 1995-05-23 At&T Corp. Arrangement for obtaining information from a switching system database by an adjunct processor
US5509058A (en) * 1992-09-11 1996-04-16 Mitel Corporation Global management of telephone directory
US5321744A (en) * 1992-09-29 1994-06-14 Excel, Inc. Programmable telecommunication switch for personal computer
US5428679A (en) * 1993-03-23 1995-06-27 C&P Of Maryland Automated service assurance method and system
US5483576A (en) * 1993-03-31 1996-01-09 Data Race, Inc. Method and apparatus for communicating data over a radio transceiver with a modem
US5495479A (en) * 1993-07-30 1996-02-27 International Business Machines Corporation Method and apparatus for an automatic decomposition of a network topology into a backbone and subareas
US5497368A (en) * 1993-08-18 1996-03-05 Koninklijke Ptt Nederland N.V. Routing method for a hierarchical communications network, and a hierarchical communications network having improved routing
US5404396A (en) * 1993-08-27 1995-04-04 Telefonaktiebolaget Lm Ericsson Feature interaction manager
US5490212A (en) * 1993-08-30 1996-02-06 Alcatel Sel Aktiengesellschaft Call-routing method for a virtual private network as well as service computer and exchange therefor
US5481603A (en) * 1993-09-28 1996-01-02 At&T Corp. Intelligent call processing based upon complete identification of calling station
US5633924A (en) * 1993-09-30 1997-05-27 Lucent Technologies Inc. Telecommunication network with integrated network-wide automatic call distribution
US5495484A (en) * 1993-10-12 1996-02-27 Dsc Communications Corporation Distributed telecommunications switching system
US6016343A (en) * 1993-10-15 2000-01-18 Link Usa Corporation Call-processing system and method
US5509065A (en) * 1993-11-12 1996-04-16 Teltrend Inc. Dual span monitoring system for maintenance shelf control
US5608871A (en) * 1993-11-17 1997-03-04 Kabushiki Kaisha Toshiba Inter-network connection apparatus having address searching/registering sections, network control sections with a receiving FIFO memory and a sending FIFO memory
US5604737A (en) * 1993-12-15 1997-02-18 Hitachi, Ltd. Voice communication system and voice communication method
US5602851A (en) * 1993-12-22 1997-02-11 International Business Machines Corporation Multi-port bridge
US5502757A (en) * 1993-12-22 1996-03-26 At&T Corp. Location dependent service for a wireless telephone
US5483585A (en) * 1993-12-29 1996-01-09 British Telecommunications, Plc Apparatus for managing an element manager for a telecommunications switch
US5414762A (en) * 1994-01-18 1995-05-09 Q.Sys International, Inc. Telephony controller with functionality command converter
US5491694A (en) * 1994-01-28 1996-02-13 Cabletron Systems, Inc. System and method for allocating a shared resource among competing devices
US5519772A (en) * 1994-01-31 1996-05-21 Bell Communications Research, Inc. Network-based telephone system having interactive capabilities
US5487110A (en) * 1994-02-01 1996-01-23 Dsc Communications Corporation Apparatus and method for virtual private telephone line with automatic ring down
US5491686A (en) * 1994-03-18 1996-02-13 Fujitsu Limited Composite ring network having an increased redundancy for restoring communication path
US5502816A (en) * 1994-03-25 1996-03-26 At&T Corp. Method of routing a request for a virtual circuit based on information from concurrent requests
US5493564A (en) * 1994-03-25 1996-02-20 Sprint International Communications Corp. Method and apparatus for global routing of electronic messages
US5602843A (en) * 1994-07-21 1997-02-11 Mitel Corporation Integrated wired and wireless telecommunications system
US5521909A (en) * 1994-07-22 1996-05-28 Newbridge Networks Corporation Frame relay management system
US5517564A (en) * 1994-07-29 1996-05-14 British Telecommunications Public Limited Company Communication apparatus and method
US5623605A (en) * 1994-08-29 1997-04-22 Lucent Technologies Inc. Methods and systems for interprocess communication and inter-network data transfer
US5621728A (en) * 1994-09-12 1997-04-15 Bell Atlantic Network Services, Inc. Level 1 gateway controlling broadband communications for video dial tone networks
US5717748A (en) * 1994-10-28 1998-02-10 Lucent Technologies Inc. Means and method for updating databases supporting local telephone number portability
US5517562A (en) * 1994-11-01 1996-05-14 Independent Telecommunications Network, Inc. Method and system for providing a distributed service network for telecommunications service providers
US5727047A (en) * 1995-01-03 1998-03-10 Lucent Technologies Inc. Arrangement for interfacing a telephone device with a personal computer
US5600644A (en) * 1995-03-10 1997-02-04 At&T Method and apparatus for interconnecting LANs
US5521970A (en) * 1995-03-29 1996-05-28 At&T Corp. Arrangement for extending call-coverage across a network of nodes
US5608721A (en) * 1995-04-03 1997-03-04 Motorola, Inc. Communications network and method which implement diversified routing
US5606600A (en) * 1995-05-10 1997-02-25 Mci Communications Corporation Generalized statistics engine for telephone network employing a network information concentrator
US5608790A (en) * 1995-06-07 1997-03-04 Lucent Technologies Inc. Trunk utilization in a telecommunications network
US5737333A (en) * 1995-06-23 1998-04-07 Lucent Technologies Inc. Method and apparatus for interconnecting ATM-attached hosts with telephone-network attached hosts
US5752082A (en) * 1995-06-29 1998-05-12 Data Race System for multiplexing pins of a PC card socket and PC card bus adapter for providing audio communication between PC card and computer sound system
US5610910A (en) * 1995-08-17 1997-03-11 Northern Telecom Limited Access to telecommunications networks in multi-service environment
US5712907A (en) * 1995-09-18 1998-01-27 Open Port Technology, Inc. Pro-active message delivery system and method
US5745556A (en) * 1995-09-22 1998-04-28 At&T Corp. Interactive and information data services telephone billing system
US5884032A (en) * 1995-09-25 1999-03-16 The New Brunswick Telephone Company, Limited System for coordinating communications via customer contact channel changing system using call centre for setting up the call between customer and an available help agent
US5742596A (en) * 1995-11-12 1998-04-21 Phonet Communication Ltd. Network based distributed PBX system
US5610977A (en) * 1995-12-21 1997-03-11 Stentor Resource Centre, Inc. Number portability using ISUP message option
US5602909A (en) * 1995-12-21 1997-02-11 Stentor Resource Centre, Inc. Number portability using database query
US5907548A (en) * 1995-12-28 1999-05-25 Lucent Technologies Inc. Telephone network local access using data messaging
US5732078A (en) * 1996-01-16 1998-03-24 Bell Communications Research, Inc. On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network
US5884262A (en) * 1996-03-28 1999-03-16 Bell Atlantic Network Services, Inc. Computer network audio access and conversion system
US5867494A (en) * 1996-11-18 1999-02-02 Mci Communication Corporation System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
US5862211A (en) * 1997-01-13 1999-01-19 Lucent Technologies Inc. Automatic simultaneous voice-and-data call setup for remote-site servicing
US6026087A (en) * 1997-03-14 2000-02-15 Efusion, Inc. Method and apparatus for establishing a voice call to a PSTN extension for a networked client computer
US6016499A (en) * 1997-07-21 2000-01-18 Novell, Inc. System and method for accessing a directory services respository

Cited By (205)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7376827B1 (en) * 1999-11-05 2008-05-20 Cisco Technology, Inc. Directory-enabled network elements
US7990882B1 (en) * 1999-12-30 2011-08-02 Avaya Inc. Adaptively maintaining quality of service (QoS) in distributed PBX networks
US8477602B2 (en) 1999-12-30 2013-07-02 Avaya Inc. Adaptively maintaining quality of service (QoS) in distributed PBX networks
US20110090796A1 (en) * 1999-12-30 2011-04-21 Avaya Inc. ADAPTIVELY MAINTAINING QUALITY OF SERVICE (QoS) IN DISTRIBUTED PBX NETWORKS
US7830865B2 (en) 2000-06-28 2010-11-09 Cisco Technology, Inc. Full PBX telephony feature preservation across a voice over packet network
US7082119B1 (en) * 2000-06-28 2006-07-25 Cisco Technology, Inc. Full PBX telephony feature preservation across a voice over packet network
US8249057B1 (en) 2000-08-18 2012-08-21 Juniper Networks, Inc. Methods and apparatus providing an overlay network for voice over internet protocol applications
US8045585B2 (en) 2000-08-18 2011-10-25 Juniper Networks, Inc. Method and apparatus providing media aggregation in a packet-switched network
US20020138603A1 (en) * 2001-03-20 2002-09-26 Robohm Kurt W. Systems and methods for updating IP communication service attributes
US8660017B2 (en) * 2001-03-20 2014-02-25 Verizon Business Global Llc Systems and methods for updating IP communication service attributes using an LDAP
US20020136222A1 (en) * 2001-03-20 2002-09-26 Kurt W. Robohm Systems and methods for updating IP communication service attributes using an LDAP
US20040143620A1 (en) * 2001-05-21 2004-07-22 Abraham Fisher Intervening ip calls during a modem session
US8000269B1 (en) 2001-07-13 2011-08-16 Securus Technologies, Inc. Call processing with voice over internet protocol transmission
US10115080B2 (en) 2002-04-29 2018-10-30 Securus Technologies, Inc. System and method for proactively establishing a third-party payment account for services rendered to a resident of a controlled-environment facility
US9990683B2 (en) 2002-04-29 2018-06-05 Securus Technologies, Inc. Systems and methods for acquiring, accessing, and analyzing investigative information
US9560193B1 (en) 2002-04-29 2017-01-31 Securus Technologies, Inc. Systems and methods for detecting a call anomaly using biometric identification
US10178224B2 (en) 2002-04-29 2019-01-08 Securus Technologies, Inc. Systems and methods for detecting a call anomaly using biometric identification
US20040092293A1 (en) * 2002-11-06 2004-05-13 Samsung Electronics Co., Ltd. Third-party call control type simultaneous interpretation system and method thereof
US7876744B2 (en) * 2002-11-14 2011-01-25 Ey-Taeg Kwon Method for collect call service based on VoIP technology and system thereof
US20050180404A1 (en) * 2002-11-14 2005-08-18 Ey-Taeg Kwon Method for collect call service based on VoIP technology and system thereof
US20110080906A1 (en) * 2002-11-14 2011-04-07 Ey-Taeg Kwon Method for collect call service based on voip technology and system thereof
US8477766B2 (en) * 2002-11-14 2013-07-02 Ey-Taeg Kwon Method for collect call service based on VoIP technology and system thereof
US9832321B2 (en) 2002-11-14 2017-11-28 Ey-Taeg Kwon Method for collect call service based on voip technology and system thereof
US20110184746A1 (en) * 2002-11-14 2011-07-28 Howlink Global Llc System and method for providing counseling service
US20130003723A1 (en) * 2002-12-05 2013-01-03 Resource Consortium Limited Virtual PBX based on Feature Server Modules
US7613160B2 (en) * 2002-12-24 2009-11-03 Intel Corporation Method and apparatus to establish communication with wireless communication networks
US20040120301A1 (en) * 2002-12-24 2004-06-24 Kitchin Duncan M. Method and apparatus to establish communication with wireless communication networks
US20040236586A1 (en) * 2003-05-22 2004-11-25 Honeywell International, Inc. Method and system for standardizing the quality of materials and services used in structured cabling networks
US20070121921A1 (en) * 2003-06-30 2007-05-31 Silver Edward M Network-based timed ring suppression
US9426280B2 (en) 2003-06-30 2016-08-23 At&T Intellectual Property I, L.P. Network-based timed ring suppression
US8548158B2 (en) * 2003-06-30 2013-10-01 At&T Intellectual Property I, L. P. Network based timed ring suppression
US20070121920A1 (en) * 2003-06-30 2007-05-31 Silver Edward M Caller controlled network-based timed ring suppression
US7899167B1 (en) * 2003-08-15 2011-03-01 Securus Technologies, Inc. Centralized call processing
US8577003B2 (en) * 2003-08-15 2013-11-05 Securus Technologies, Inc. Centralized call processing
US20110110276A1 (en) * 2003-08-15 2011-05-12 Securus Technologies, Inc. Centralized call processing
US8340260B1 (en) 2003-08-15 2012-12-25 Securus Technologies, Inc. Inmate management and call processing systems and methods
US9936069B2 (en) 2003-09-29 2018-04-03 At&T Intellectual Property I, L.P. Methods, systems, and products for suppression of alerts
US9525774B2 (en) 2003-09-29 2016-12-20 At&T Intellectual Property I, L.P. Methods, systems, and products for suppression of alerts
US9137382B2 (en) 2003-09-29 2015-09-15 At&T Intellectual Property I, L.P. Methods, systems, and products for suppression of alerts
US8619954B2 (en) 2003-09-29 2013-12-31 At&T Intellectual Property I, L.P. Methods, systems, and products for ring suppression
US10740861B1 (en) 2003-11-24 2020-08-11 Securus Technologies, Inc. Systems and methods for acquiring, accessing, and analyzing investigative information
US20050111435A1 (en) * 2003-11-26 2005-05-26 James Yang [internet-protocol (ip) phone with built-in gateway as well as telephone network structure and multi-point conference system using ip phone]
US20050138128A1 (en) * 2003-12-23 2005-06-23 Baniel Uri S. Method and device for grab transferring an instant messaging and presence (IMP) session
US7899671B2 (en) * 2004-02-05 2011-03-01 Avaya, Inc. Recognition results postprocessor for use in voice recognition systems
US20050177376A1 (en) * 2004-02-05 2005-08-11 Avaya Technology Corp. Recognition results postprocessor for use in voice recognition systems
US7782897B1 (en) 2004-08-26 2010-08-24 Juniper Networks, Inc. Multimedia over internet protocol border controller for network-based virtual private networks
US7415021B1 (en) * 2004-09-22 2008-08-19 Sun Microsystems, Inc. Method and apparatus for preserving null semantics during use of a forwarding method
US20060077962A1 (en) * 2004-10-07 2006-04-13 Santera Systems, Inc. Methods and systems for measurement-based call admission control in a media gateway
US7764605B2 (en) * 2004-10-07 2010-07-27 Genband Inc. Methods and systems for measurement-based call admission control in a media gateway
US20060135157A1 (en) * 2004-11-02 2006-06-22 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks, and packet switch apparatus therefor
US20060114885A1 (en) * 2004-11-09 2006-06-01 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks
WO2006068836A3 (en) * 2004-12-21 2007-02-01 Cisco Tech Inc Selecting a routing mode for a call session
US7558246B2 (en) 2004-12-21 2009-07-07 Cisco Technology, Inc. Selecting a routing mode for a call session
US20060133367A1 (en) * 2004-12-21 2006-06-22 Cisco Technology, Inc. Selecting a routing mode for a call session
US8462637B1 (en) * 2005-01-04 2013-06-11 Sheridan Ross P.C. Dial plan routing for fragmented networks
US20060182131A1 (en) * 2005-01-21 2006-08-17 L-3 Communications Corporation Gateway interface control
US9979828B1 (en) * 2005-04-12 2018-05-22 Tp Lab, Inc. Voice virtual private network
WO2007026029A3 (en) * 2005-09-02 2007-05-24 Data Connection Ltd Telephone call processing method and apparatus
US20080240400A1 (en) * 2005-09-02 2008-10-02 Data Connection Limited Telephone call processing method and apparatus
US8611522B2 (en) 2005-09-02 2013-12-17 Metaswitch Networks Ltd Telephone call processing method and apparatus
US20070109963A1 (en) * 2005-11-17 2007-05-17 Edward Walter Internet protocol telephony proxy device
US20070127455A1 (en) * 2005-12-07 2007-06-07 Ricoh Company, Limited Call control server
US9473622B2 (en) * 2005-12-07 2016-10-18 Ricoh Company, Limited Call control server
US11194627B2 (en) 2005-12-19 2021-12-07 Vmware, Inc. Managing a virtualized application workspace on a managed computing device
US8245129B2 (en) * 2005-12-19 2012-08-14 Vmware, Inc. Method and system for providing synchronization of directory data
US10198162B2 (en) 2005-12-19 2019-02-05 Vmware, Inc. Method for installing or upgrading an application
US9317333B2 (en) 2005-12-19 2016-04-19 Vmware, Inc. Method and system for providing load balancing for virtualized application workspaces
US10338969B2 (en) 2005-12-19 2019-07-02 Vmware, Inc. Managing a virtualized application workspace on a managed computing device
US20080147745A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing synchronization of directory data
US20080147787A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing load balancing for virtualized application workspaces
US20070160076A1 (en) * 2006-01-10 2007-07-12 Scott Faber Systems and methods to arrange call back
US8125931B2 (en) 2006-01-10 2012-02-28 Utbk, Inc. Systems and methods to provide availability indication
US20070161386A1 (en) * 2006-01-10 2007-07-12 Scott Faber Systems and methods to provide availability indication
US20070291783A1 (en) * 2006-01-10 2007-12-20 Utbk, Inc. Systems and Methods to Provide Real Time Communication Connections
US7720091B2 (en) * 2006-01-10 2010-05-18 Utbk, Inc. Systems and methods to arrange call back
US9106473B2 (en) 2006-01-10 2015-08-11 Yellowpages.Com Llc Systems and methods to connect buyers and sellers
US20090054032A1 (en) * 2006-02-15 2009-02-26 Huawei Technologies Co., Ltd. Method, system and vpbx for sending short messages
USRE47296E1 (en) 2006-02-21 2019-03-12 A10 Networks, Inc. System and method for an adaptive TCP SYN cookie with time validation
US8861491B2 (en) * 2006-03-02 2014-10-14 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US7903635B2 (en) 2006-03-02 2011-03-08 Tango Networks, Inc. System and method for enabling DTMF detection in a VoIP network
US20110312300A1 (en) * 2006-03-02 2011-12-22 Andrew Silver Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US20070206735A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling DTMF detection in a VoIP network
US8175053B2 (en) 2006-03-02 2012-05-08 Tango Networks, Inc. System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network
US20070206580A1 (en) * 2006-03-02 2007-09-06 Andrew Silver Call flow system and method use in VoIP telecommunication system
US8023479B2 (en) * 2006-03-02 2011-09-20 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US20070206563A1 (en) * 2006-03-02 2007-09-06 Andrew Silver Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US20070206571A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling call originations using SMS and hotline capabilities
US8271049B2 (en) 2006-03-02 2012-09-18 Tango Networks, Inc. System and method for enabling DTMF detection in a VoIP network
US7974618B2 (en) 2006-03-02 2011-07-05 Tango Networks, Inc. System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing
US20110116498A1 (en) * 2006-03-02 2011-05-19 Andrew Silver System and method for enabling dtmf detection in a voip network
US8428578B2 (en) 2006-03-02 2013-04-23 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US20110090823A1 (en) * 2006-03-02 2011-04-21 Andrew Silver System and method for enabling call originations using sms and hotline capabilities
US10567930B2 (en) 2006-03-02 2020-02-18 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US20110081911A1 (en) * 2006-03-02 2011-04-07 Andrew Silver System and method for enabling vpn-less session setup for connecting mobile data devices to an enterprise data network
US11871216B2 (en) 2006-03-02 2024-01-09 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US8488598B2 (en) 2006-03-02 2013-07-16 Tango Networks, Inc. Call flow system and method for use in a VoIP telecommunication system
US20110075609A1 (en) * 2006-03-02 2011-03-31 Andrew Silver Call flow system and method for use in a voip telecommunication system
US10616818B2 (en) 2006-03-02 2020-04-07 Tango Networks, Inc. System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing
US11811554B2 (en) * 2006-03-02 2023-11-07 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US11638126B2 (en) 2006-03-02 2023-04-25 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US7890096B2 (en) 2006-03-02 2011-02-15 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US7873001B2 (en) 2006-03-02 2011-01-18 Tango Networks, Inc. System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network
US20070206569A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling multi-line mobile telephone service capabilities on a single-line mobile telephone
US7873032B2 (en) 2006-03-02 2011-01-18 Tango Networks, Inc. Call flow system and method use in VoIP telecommunication system
US8958346B2 (en) 2006-03-02 2015-02-17 Tango Networks, Inc. Calling line/name identification of enterprise subscribers in mobile calls
US20200145894A1 (en) * 2006-03-02 2020-05-07 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US10674419B2 (en) 2006-03-02 2020-06-02 Tango Networks, Inc. System and method for executing originating services in a terminating network for IMS and non-IMS applications
US20070206573A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing
US10904816B2 (en) * 2006-03-02 2021-01-26 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US11622311B2 (en) 2006-03-02 2023-04-04 Tango Networks, Inc. Calling line/name identification of enterprise subscribers in mobile calls
US20070206572A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network
US9215319B2 (en) 2006-03-02 2015-12-15 Tango Networks, Inc. System and method for executing originating services in a terminating network for IMS and non-IMS applications
US10939255B2 (en) 2006-03-02 2021-03-02 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US11849380B2 (en) 2006-03-02 2023-12-19 Tango Networks, Inc. Call flow system and method for use in a VoIP telecommunication system
US10945187B2 (en) 2006-03-02 2021-03-09 Tango Networks, Inc. Call flow system and method for use in a VoIP telecommunication system
US20070206613A1 (en) * 2006-03-02 2007-09-06 Andrew Silver System and method for executing originating services in a terminating network for IMS and non-IMS applications
US11405846B2 (en) 2006-03-02 2022-08-02 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US11412435B2 (en) 2006-03-02 2022-08-09 Tango Networks, Inc. System and method for executing originating services in a terminating network for IMS and non-IMS applications
US7916845B2 (en) 2006-04-13 2011-03-29 Securus Technologies, Inc. Unauthorized call activity detection and prevention systems and methods for a Voice over Internet Protocol environment
US20150326732A1 (en) * 2006-06-30 2015-11-12 Centurylink Intellectual Property Llc System and Method for Re-Routing Calls
US9549004B2 (en) * 2006-06-30 2017-01-17 Centurylink Intellectual Property Llc System and method for re-routing calls
US20080043976A1 (en) * 2006-07-20 2008-02-21 Microsoft Corporation Management of telephone call routing using a directory services schema
US7831034B2 (en) * 2006-07-20 2010-11-09 Microsoft Corporation Management of telephone call routing using a directory services schema
US20080032728A1 (en) * 2006-08-03 2008-02-07 Bina Patel Systems, methods and devices for communicating among multiple users
US20090257361A1 (en) * 2006-09-28 2009-10-15 Qualcomm Incorporated Methods and apparatus for determining communication link quality
US8553526B2 (en) 2006-09-28 2013-10-08 Qualcomm Incorporated Methods and apparatus for determining quality of service in a communication system
US9191226B2 (en) * 2006-09-28 2015-11-17 Qualcomm Incorporated Methods and apparatus for determining communication link quality
US20100165857A1 (en) * 2006-09-28 2010-07-01 Qualcomm Incorporated Methods and apparatus for determining quality of service in a communication system
US9497201B2 (en) 2006-10-17 2016-11-15 A10 Networks, Inc. Applying security policy to an application session
US9841882B2 (en) 2006-12-19 2017-12-12 Vmware, Inc. Providing application and device management using entitlements
US9256353B2 (en) 2006-12-19 2016-02-09 Vmware, Inc. Providing application and device management using entitlements
US20080162720A1 (en) * 2006-12-29 2008-07-03 Aman Gulati Methods and apparatus for implementing a pluggable policy module within a session over internet protocol network
US7774481B2 (en) 2006-12-29 2010-08-10 Genband Us Llc Methods and apparatus for implementing a pluggable policy module within a session over internet protocol network
US10796392B1 (en) 2007-05-22 2020-10-06 Securus Technologies, Llc Systems and methods for facilitating booking, bonding and release
US9300703B2 (en) 2007-06-26 2016-03-29 Yellowpages.Com Llc Systems and methods to provide telephonic connections via concurrent calls
US8976785B2 (en) 2007-06-28 2015-03-10 Centurylink Intellectual Property Llc System and method for voice redundancy service
US20090003318A1 (en) * 2007-06-28 2009-01-01 Embarq Holdings Company, Llc System and method for voice redundancy service
US20110083174A1 (en) * 2007-07-26 2011-04-07 International Business Machines Corporation Dynamic Network Tunnel Endpoint Selection
US20090031415A1 (en) * 2007-07-26 2009-01-29 International Business Machines Corporation Dynamic Network Tunnel Endpoint Selection
US7992201B2 (en) 2007-07-26 2011-08-02 International Business Machines Corporation Dynamic network tunnel endpoint selection
US8261339B2 (en) 2007-07-26 2012-09-04 International Business Machines Corporation Dynamic network tunnel endpoint selection
US10180962B1 (en) * 2007-09-28 2019-01-15 Iqor Us Inc. Apparatuses, methods and systems for a real-time phone configurer
US8135001B1 (en) * 2008-04-16 2012-03-13 Globaltel IP, Inc. Multi ad hoc interoperable communicating networks
US20100008264A1 (en) * 2008-07-09 2010-01-14 General Instrument Corporation Method and apparatus for facilitating installation of packet-switched telephony equipment on a subscriber premises
US10880721B2 (en) 2008-07-28 2020-12-29 Voip-Pal.Com, Inc. Mobile gateway
US8666422B2 (en) * 2008-09-30 2014-03-04 Ip.Access Limited Method and apparatus for setting a transmit power level
US20120028629A1 (en) * 2008-09-30 2012-02-02 Yajian Liu Method and apparatus for setting a transmit power level
US10932317B2 (en) 2009-09-17 2021-02-23 VolP-Pal.com, Inc. Uninterrupted transmission of internet protocol transmissions during endpoint changes
US9960967B2 (en) 2009-10-21 2018-05-01 A10 Networks, Inc. Determining an application delivery server based on geo-location information
US10735267B2 (en) 2009-10-21 2020-08-04 A10 Networks, Inc. Determining an application delivery server based on geo-location information
US9025438B1 (en) * 2010-06-29 2015-05-05 Century Link Intellectual Property LLC System and method for communication failover
US9961135B2 (en) 2010-09-30 2018-05-01 A10 Networks, Inc. System and method to balance servers based on server load status
US10447775B2 (en) 2010-09-30 2019-10-15 A10 Networks, Inc. System and method to balance servers based on server load status
US9961136B2 (en) * 2010-12-02 2018-05-01 A10 Networks, Inc. Distributing application traffic to servers based on dynamic service response time
US9609052B2 (en) * 2010-12-02 2017-03-28 A10 Networks, Inc. Distributing application traffic to servers based on dynamic service response time
US10516730B2 (en) 2010-12-02 2019-12-24 A10 Networks, Inc. Distributing application traffic to servers based on dynamic service response time
US20170187793A1 (en) * 2010-12-02 2017-06-29 A10 Networks, Inc. Distributing Application Traffic to Servers Based on Dynamic Service Response Time
US10178165B2 (en) * 2010-12-02 2019-01-08 A10 Networks, Inc. Distributing application traffic to servers based on dynamic service response time
US20120144015A1 (en) * 2010-12-02 2012-06-07 A10 Networks, Inc. System and Method for Distributing Application Traffic to Servers Based on Dynamic Service Response Time
US9756085B2 (en) * 2011-01-10 2017-09-05 Vtech Telecommunications Limited Peer-to-peer internet protocol telephone system with system-wide configuration data
US20160205145A1 (en) * 2011-01-10 2016-07-14 Vtech Telecommunications Limited Peer-to-peer internet protocol telephone system with system-wide configuration data
US9635179B1 (en) * 2011-10-10 2017-04-25 West Corporation Consumer care system
US10484465B2 (en) 2011-10-24 2019-11-19 A10 Networks, Inc. Combining stateless and stateful server load balancing
US9906591B2 (en) 2011-10-24 2018-02-27 A10 Networks, Inc. Combining stateless and stateful server load balancing
US20130170361A1 (en) * 2011-12-10 2013-07-04 Web3Tel Inc. System and Method of Interactive call control for calls and connections created in different communication networks
US9979801B2 (en) 2011-12-23 2018-05-22 A10 Networks, Inc. Methods to manage services over a service gateway
US10044582B2 (en) 2012-01-28 2018-08-07 A10 Networks, Inc. Generating secure name records
US10491523B2 (en) 2012-09-25 2019-11-26 A10 Networks, Inc. Load distribution in data networks
US9705800B2 (en) 2012-09-25 2017-07-11 A10 Networks, Inc. Load distribution in data networks
US10862955B2 (en) 2012-09-25 2020-12-08 A10 Networks, Inc. Distributing service sessions
US9843484B2 (en) 2012-09-25 2017-12-12 A10 Networks, Inc. Graceful scaling in software driven networks
US10021174B2 (en) 2012-09-25 2018-07-10 A10 Networks, Inc. Distributing service sessions
US10516577B2 (en) 2012-09-25 2019-12-24 A10 Networks, Inc. Graceful scaling in software driven networks
US10002141B2 (en) 2012-09-25 2018-06-19 A10 Networks, Inc. Distributed database in software driven networks
US9531846B2 (en) 2013-01-23 2016-12-27 A10 Networks, Inc. Reducing buffer usage for TCP proxy session based on delayed acknowledgement
US11005762B2 (en) 2013-03-08 2021-05-11 A10 Networks, Inc. Application delivery controller and global server load balancer
US9900252B2 (en) 2013-03-08 2018-02-20 A10 Networks, Inc. Application delivery controller and global server load balancer
US9264299B1 (en) 2013-03-14 2016-02-16 Centurylink Intellectual Property Llc Transparent PSTN failover
US9866429B2 (en) 2013-03-14 2018-01-09 Centurylink Intellectual Property Llc Transparent PSTN failover
US10659354B2 (en) 2013-03-15 2020-05-19 A10 Networks, Inc. Processing data packets using a policy based network path
US9992107B2 (en) 2013-03-15 2018-06-05 A10 Networks, Inc. Processing data packets using a policy based network path
US10038693B2 (en) 2013-05-03 2018-07-31 A10 Networks, Inc. Facilitating secure network traffic by an application delivery controller
US10305904B2 (en) 2013-05-03 2019-05-28 A10 Networks, Inc. Facilitating secure network traffic by an application delivery controller
US9768856B2 (en) 2013-06-07 2017-09-19 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving service in wireless communication system
US10230770B2 (en) 2013-12-02 2019-03-12 A10 Networks, Inc. Network proxy layer for policy-based application proxies
US10419491B1 (en) * 2013-12-16 2019-09-17 8X8, Inc. System and method for monitoring computing servers for possible unauthorized access
CN110275718A (en) * 2013-12-31 2019-09-24 宏正自动科技股份有限公司 The installation and starting method of network equipment and system and embedded Control program
US9521141B2 (en) 2014-02-12 2016-12-13 Bank Of America Corporation Caller validation
US9942152B2 (en) 2014-03-25 2018-04-10 A10 Networks, Inc. Forwarding data packets using a service-based forwarding policy
US10257101B2 (en) 2014-03-31 2019-04-09 A10 Networks, Inc. Active application response delay time
US9942162B2 (en) 2014-03-31 2018-04-10 A10 Networks, Inc. Active application response delay time
US10686683B2 (en) 2014-05-16 2020-06-16 A10 Networks, Inc. Distributed system to determine a server's health
US9906422B2 (en) 2014-05-16 2018-02-27 A10 Networks, Inc. Distributed system to determine a server's health
US10749904B2 (en) 2014-06-03 2020-08-18 A10 Networks, Inc. Programming a data network device using user defined scripts with licenses
US10880400B2 (en) 2014-06-03 2020-12-29 A10 Networks, Inc. Programming a data network device using user defined scripts
US9986061B2 (en) 2014-06-03 2018-05-29 A10 Networks, Inc. Programming a data network device using user defined scripts
US9992229B2 (en) 2014-06-03 2018-06-05 A10 Networks, Inc. Programming a data network device using user defined scripts with licenses
US10129122B2 (en) 2014-06-03 2018-11-13 A10 Networks, Inc. User defined objects for network devices
US10581976B2 (en) 2015-08-12 2020-03-03 A10 Networks, Inc. Transmission control of protocol state exchange for dynamic stateful service insertion
US10243791B2 (en) 2015-08-13 2019-03-26 A10 Networks, Inc. Automated adjustment of subscriber policies
US9961205B1 (en) * 2016-06-21 2018-05-01 Avaya Inc. Mobility bonding network
US10440127B2 (en) 2016-06-21 2019-10-08 Avaya Inc. Mobility bonding network
US20180103150A1 (en) * 2016-06-21 2018-04-12 Avaya Inc. Mobility bonding network
US11079910B1 (en) * 2019-02-06 2021-08-03 Fuze, Inc. Softphone control integration
TWI801096B (en) * 2022-01-14 2023-05-01 陳立新 Method of extending pbx communication functions and connectivity

Also Published As

Publication number Publication date
AU8576798A (en) 1999-02-16
US20030095541A1 (en) 2003-05-22
US7280530B2 (en) 2007-10-09
EP1021757A1 (en) 2000-07-26
US20030095542A1 (en) 2003-05-22
WO1999005590A3 (en) 1999-04-22
WO1999005590A2 (en) 1999-02-04

Similar Documents

Publication Publication Date Title
US7280530B2 (en) Apparatus and method for integrated voice gateway
US6807272B2 (en) System and method for providing telephony services to remote subscribers
US9706029B1 (en) Methods and systems for call processing
US9942410B2 (en) Controller for the intelligent interconnection of two communication networks, and method of use for same
US6804224B1 (en) System and method for providing telephone service having private branch exchange features in a voice-over-data network telephony system
US6298062B1 (en) System providing integrated services over a computer network
US5881142A (en) Integrated communications control device for a small office configured for coupling within a scalable network
US6721398B1 (en) Unified messaging system
US6430176B1 (en) Multimedia channel management through PSTN signaling
EP1279299B1 (en) Telephone call control system and method for the public switched telephone network
US6529596B1 (en) Web-based control of telephone
US20050074109A1 (en) Integrated personal call management system
US20020061100A1 (en) Virtual telephony
WO2001006740A2 (en) Method and apparatus for integrating a voice gateway with an ip/pbx telephone system
US7369648B1 (en) Apparatus and method for PBX-integrated unified messaging services on a switched backbone
CA2483128A1 (en) Call management service
US6532288B1 (en) Tandem access control processor connected to the public switched telephone network for controlling features
US20040052350A1 (en) System and method for delivering enhanced voice and data services in parallel with an incumbent phone company
Cisco Cisco Voice Telephony
Cisco Chap 2: Overview of the Cisco VoIP Infrastructure Solution for SIP
EP1445909A1 (en) Application for initiating telecommunications connections system, method and apparatus
US20020075848A1 (en) Local switch attached telephony access node
EP1290818A1 (en) System providing integrated services over a computer network

Legal Events

Date Code Title Description
AS Assignment

Owner name: STARVOX COMMUNICATIONS INC., CALIFORNIA

Free format text: DOCUMENT PREVIOUSLY RECORDED AT REEL 018419 FRAME 0045 CONTAINED ERRORS IN APPLICATION NUMBER 10/086628. DOCUMENT RERECORDED TO CORRECT ERRORS ON STATED REEL.;ASSIGNOR:STARVOX, INC.;REEL/FRAME:018581/0730

Effective date: 20060911

Owner name: STARVOX COMMUNICATIONS, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STARVOX, INC.;REEL/FRAME:018419/0045

Effective date: 20060911

AS Assignment

Owner name: TRINAD CAPITAL MASTER FUND LTD. (35%), CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.;REEL/FRAME:021141/0530

Effective date: 20080623

Owner name: DKR SOUNDSHORE OASIS HOLDING FUND LTD. WITH COPIES

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.;REEL/FRAME:021141/0530

Effective date: 20080623

Owner name: DKR SOUNDSHORE OASIS HOLDING FUND LTD. (65%), CAYM

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.;REEL/FRAME:021141/0530

Effective date: 20080623

AS Assignment

Owner name: DKR SOUNDSHORE OASIS HOLDING FUND LTD. (65%), CAYM

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.;REEL/FRAME:021167/0766

Effective date: 20080506

Owner name: TRINAD CAPITAL MASTER FUND LTD. (35%), CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DKR SOUNDSHORE OASIS HOLDING FUND LTD. ON BEHALF OF STARVOX COMMUNICATIONS, INC.;REEL/FRAME:021167/0766

Effective date: 20080506

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION