Telephony controller with functionality command converter

• US 5,414,762 A
• Filed: 01/18/1994
• Issued: 05/09/1995
• Est. Priority Date: 01/18/1994
• Status: Expired due to Fees

• Current Assignee: Q.SyS International, Inc.
• Original Assignee: Q.SyS International, Inc.
• Inventors: Johnson, Mark, Flisik, Robert C.
• Primary Examiner(s): Dwyer, James L.
• Assistant Examiner(s): HONG, HARRY S
• Application Number:
  US08/183,992
• Time in Patent Office: 476 Days
• Field of Search: 379/157, 379/198, 379/201, 379/202, 379/203, 379/204, 379/205, 379/206, 379/207, 379/225, 379/227, 379/231, 379/232, 379/234, 379/268, 379/269, 379/94, 370/62, 370/94.1
• US Class Current: 379/198
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing
• CPC Class Codes: H04Q 3/625 Arrangements in the private branch exchange

Abstract

A telephony controller for controlling a private automatic branch exchange (PABX) is disclosed that utilizes a single functionality command protocol to reduce the data traffic on a computer network or the like used to control a PABX. The telephony controller includes a functionality command converter, a communication layer for communicating with computer terminals on the computer network, and a PABX interface for communicating with the PABX. The single functionality command protocol uses a generic command format for a number of function commands that are converted by the functionality command converter into the PABX commands corresponding to the vendor specific PABX. The functionality converter generates the PABX commands to implement a function command and monitors the PABX to determine whether the command has been implemented. The functionality command converter generates data messages corresponding to the outcome of the functionality command execution which are transmitted to the command originating terminal. Additionally, the telephony controller is capable of controlling different vendor PABXs without requiring any change in the communication format between the controller and the computer terminals.

Claims

1. A telephony controller for controlling a private automatic branch exchange (PABX) comprising:

a communication layer for receiving functionality commands from a plurality of command originating computer terminals, said functionality commands conforming to a single functionality command protocol;

a functionality command converter for converting said functionality commands received by said communication layer to PABX commands; and

a PABX interface for transmitting said PABX commands to a PABX and for receiving PABX status information from said PABX, whereby said command originating computer terminals may control and monitor said PABX.

2. The controller of claim 1 further comprising:

a shared memory for communicating between said communication layer and said functionality command converter.

3. The controller of claim 2, said shared memory further comprising:

a communication FIFO for receiving said functionality commands from said communication layer.

4. The controller of claim 3 wherein said communication layer receives command status messages from said functionality command converter for transmission to one of said command originating computer terminals in said plurality.

5. The controller of claim 4, said communication layer further comprising:

a socket process for each of said command originating terminals.

6. The controller of claim 5, said shared memory further comprising:

a socket process FIFO for communicating said command status messages from said functionality command converter to said socket process corresponding to one of said command originating terminals.

7. The controller of claim 6, said functionality command converter further including:

a converter control module for converting said functionality commands and transmitting said PABX commands to said PABX interface; and

a monitor module for receiving and verifying said functionality commands from said socket processes, said monitor module provides said verified functionality commands to said converter control module.

8. The controller of claim 7, said verified functionality commands are provided to said converter control module through said shared memory.

9. The controller of claim 7, wherein said converter control module receives PABX status information from said PABX interface, generates command status messages in response to said PABX status information, and writes said command status messages to one of said socket process FIFOs in said shared memory, said one socket process FIFO corresponding to said socket process for one of said command originating computer terminals.

10. The controller of claim 1, said functionality command converter further comprising:

a first library of function command routines for converting functionality commands to PABX commands for a vendor specific PABX.

11. The controller of claim 10, further comprising:

a second PABX interface for a second PABX; and

a second library of function command routines for converting functionality commands to PABX commands for said second PABX.

12. The controller of claim 1, wherein said single functionality command protocol includes:

a command mnemonic;

a command originating terminal identifier; and

command parameter data for converting said function commands to said PABX commands.

13. The controller of claim 12 wherein said command mnemonic, said command originating terminal identifier, and said command parameter data are provided in an ASCII string and said command mnemonic, said originating terminal identifier, and said command parameter data are delimited by a field delimiter.

14. A method for interfacing a computer terminal to a private automatic branch exchange (PABX) comprising the steps of:

receiving functionality commands from one of a plurality of command originating computer terminals, said functionality commands being in a predetermined single functionality command protocol;

converting said functionality commands to PABX commands corresponding to a vendor specific PABX; and

transmitting said PABX commands to a PABX interface for controlling said PABX.

15. The method of claim 14, said receiving step further comprising:

verifying said receipt of said functionality commands; and

transmitting a transmission status message to said command originating terminal.

16. The method of claim 14, said converting step further comprising:

parsing a function command mnemonic;

verifying command data parameters within said functionality command; and

generating vendor specific PABX commands corresponding to said function command mnemonic and said verified function command data.

17. The method of claim 14, said converting step further comprising:

receiving PABX status information from said PABX;

updating a functionality command execution status in response to said PABX status information;

generating PABX commands in response to a function command execution status indicating incomplete execution; and

transmitting a function command status message to one of said command originating terminals in response to a function command status indicting completion of function command execution.