Multiplex communications – Pathfinding or routing – Combined circuit switching and packet switching
Reexamination Certificate
2000-05-04
2004-11-16
Nguyen, Steven (Department: 2665)
Multiplex communications
Pathfinding or routing
Combined circuit switching and packet switching
C370S389000, C370S397000, C370S401000, C379S231000, C379S234000
Reexamination Certificate
active
06819665
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates in general to network-based voice communications, and more particularly to a voice-LAN PBX (Private Branch Exchange) implemented using H.323 Gatekeepers.
BACKGROUND OF THE INVENTION
H.323 is an emerging standard for multi-media communication. This standard governs communications between terminals and other entities over a packet switched network. A person of ordinary skill in the art and who is familiar with the H.323 standard will understand the elements of establishing third party call control via a Gatekeeper. Briefly, upon powering up, a H.323 endpoint (desktop) implements a discovery process for determining which Gatekeeper to register with. This can be effected in a number of ways, such as by multicasting a message which identifies the endpoint (i.e. the GRQ message) to a predetermined multicast address. The assigned Gatekeeper then responds (i.e. the GCF/GRJ message) with its RAS channel address (i.e. IP address). Before attempting to place a call, the endpoint must register with the Gatekeeper (i.e. the RRQ message) by advising it of its transport address and any aliases (discussed below). Registration is then confirmed by the Gatekeeper (i.e. via the RCF/RRJ message). Actual call signaling takes place over and established channel between two H.323 endpoints using Q.931 messages. For third party (i.e. Gatekeeper) call control, the originating endpoint sends a H.225 Admission Request (ARQ) to the Gatekeeper over the previously established RAS channel. The Gatekeeper responds with an ACF message which specifies the call signaling transport address to use for the call setup. The originating endpoint then transmits a Setup message to the Gatekeeper which, in turn, sends a Setup message to the destination endpoint. The destination endpoint then sends an admission request (ARQ) to the Gatekeeper and receives an acknowledgment (ACF) therefrom. Finally, a Connect message is sent from the destination endpoint to the Gatekeeper which contains the address of the originating endpoint for H.425 control messages to the originating endpoint.
The inventors have recognized the desirability of adapting the H.323 standard to voice communications such as traditionally implemented via a PBX. In the context of this contemplated telephony application, a call setup under the H.323 protocol requires two H.323 compliant endpoints to completely set up the call.
There are some features of PBXs, such as callback, recall, and make call (TAPI), among others, which require the system to make a half call to a device, and only after there has been some user response at the device then initiate a full call between the two endpoints. For example, in order to ‘ring’ a device in a PBX, the system itself initiates ringing of the device (without any requirement to have actual communication between endpoints). Then, when the device is ‘answered’ (i.e. the user goes off hook), the PBX establishes a call between the two endpoints. The H.323 standard does not allow for such behavior since the protocol requires two H.323 endpoints in order to initiate and complete a call.
Also, there are group features, such as key line appearances, pickup groups, etc., that are necessary in a PBX, and which are not supported by the H.323 endpoint communication protocol. Group features are normally handled in the PBX call control, and many different device types can be members of groups. Since H.323 requires communication between distinct H.323 entities, it is not possible to establish features wherein multiple H.323 endpoints are arranged in a group. Similarly, it is not possible to select from a group of trunks or a particular trunk to make a call.
SUMMARY OF THE INVENTION
According to the present invention, a system is provided for implementing full PBX functionality in a networked environment, using the H.323 standard. Specifically, an H.323 Gatekeeper is provided into which PBX call control functions are incorporated to enable feature interaction while controlling resource allocation. Also, software elements are provided for accommodating half call, group and trunk selection features within the H.323 environment.
REFERENCES:
patent: 6278478 (2001-08-01), Ferriere
patent: 6314284 (2001-11-01), Patel et al.
patent: 6374302 (2002-04-01), Lalasso et al.
patent: 6430176 (2002-08-01), Christie, IV
patent: 6430699 (2002-08-01), Carter et al.
patent: 6449260 (2002-09-01), Sassin et al.
patent: 6490275 (2002-12-01), Sengodan
patent: 6507647 (2003-01-01), Mandalia
patent: 6553116 (2003-04-01), Vander Meiden
patent: 6731609 (2004-05-01), Hirni et al.
patent: 9817048 (1998-04-01), None
patent: 9857485 (1998-12-01), None
Fullarton Sonya
Peres Eliana
Pinard Debbie
Sit Harold
Jones Day
Mitel Knowledge Corporation
Nguyen Steven
Stevens Roberta
LandOfFree
Private branch exchange implemented using H.323 gatekeeper does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Private branch exchange implemented using H.323 gatekeeper, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Private branch exchange implemented using H.323 gatekeeper will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3291713