System and method for reporting the addition and deletion of TAPI line and phone devices in absence of such notifiction from a PBX

• US 6,975,715 B1
• Filed: 02/09/2000
• Issued: 12/13/2005
• Est. Priority Date: 02/09/2000
• Status: Expired due to Fees

• Current Assignee: Unify Inc. (Atos SE)
• Original Assignee: Siemens Communications Incorporated (Siemens AG)
• Inventors: Hettish, Mark Bernard
• Primary Examiner(s): Deane, Jr., William J.
• Application Number:
  US09/501,134
• Time in Patent Office: 2,134 Days
• Field of Search: 379/201.01, 379/201.03, 379/211.02, 379/319, 379/229, 379/230, 379/201.02, 379/198, 379/32.01
• US Class Current: 379/201.01
• CPC Class Codes: H04M 3/42323 PBX's with CTI arrangements
• CPC Class Codes: H04Q 2213/13003 Constructional details of switching devices
• CPC Class Codes: H04Q 2213/13034 A/D conversion, code compression/expansion
• CPC Class Codes: H04Q 2213/1305 Software aspects
• CPC Class Codes: H04Q 2213/13093 Personal computer, PC
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13109 Initializing, personal profile
• CPC Class Codes: H04Q 2213/1322 PBX
• CPC Class Codes: H04Q 3/54516 Initialization, software or data downloading G06F9/445 takes precedence
• CPC Class Codes: H04Q 3/54533 Configuration data, translation, passwords, databases
• CPC Class Codes: H04Q 3/62 for connecting to private branch exchanges

Abstract

A TAPI service provider may request configuration information from hardware such as a PBX. Configuration information received from the hardware is stored in a list and compared to the existing configuration list. Two new lists are then generated: an added list and a deleted list. All devices in the deleted list are deleted from the internal database and deleted messages are sent to the TAPI service provider. All new devices are temporarily added to the internal database and addition messages are sent to the TAPI service provider. The new device configuration list is then saved, and the added devices are marked as permanent.

Claims

1. A method for updating configuration information in a TAPI system, comprising:

a TAPI service provider storing configuration information in a first configuration table object;

a TAPI service provider requesting update static configuration information from a telephony device;

a TAPI service provider receiving said update static configuration information; and

a TAPI service provider storing said static update configuration information for system use as a second configuration table object.

2. A method in accordance with claim 1, further comprising generating a deleted devices configuration table object and an added devices configuration table object.

3. A method in accordance with claim 2, comprising notifying said TAPI system that each device in said deleted devices configuration table object has been dynamically deleted.

4. A method in accordance with claim 2, comprising notifying said TAPI system that each device in said added devices configuration table object has been dynamically deleted.

5. A TAPI system, comprising:

means associated with a TAPI service provider for storing configuration information in a first configuration table object;

means associated with a TAPI service provider for requesting update static configuration information from a telephony device;

means associated with a TAPI service provider for receiving said update static configuration information; and

means associated with a TAPI service provider for storing said static update configuration information for system use as a second configuration table object.

6. A system in accordance with claim 5, said storing means further comprising means for generating a deleted devices configuration table object and an added devices configuration table object.

7. A system in accordance with claim 6, further comprising means for notifying said TAPI system that each device in said deleted devices configuration table object has been dynamically deleted.

8. A system in accordance with claim 6, further comprising means for notifying said TAPI system that each device in said added devices configuration table object has been dynamically deleted.

9. A system in accordance with claim 6, said TAPI service provider further adapted to notify a TAPI application that each device in said deleted devices configuration table object has been dynamically deleted.

10. A system in accordance with claim 6, said TAPI service provider further adapted to notify a TAPI application that each device in said added devices configuration table object has been dynamically deleted.

11. A TAPI system, comprising:

a TAPI service provider adapted to store configuration information received from a telephony device in a first configuration table object; and

a telephony device adapted to transmit update static configuration information to said TAPI service provider;

wherein said TAPI service provider is adapted to store said static update configuration information for system use as a second configuration table object.

12. A system in accordance with claim 11, said TAPI service provider further adapted to generate a deleted devices configuration table object and an added devices configuration table object.