Control interface for computer supported telephony applications (CSTA) protocols

• US 20030002648A1
• Filed: 05/23/2001
• Published: 01/02/2003
• Est. Priority Date: 05/23/2001
• Status: Active Grant

• Current Assignee: Unify Inc. (Atos SE)
• Original Assignee: Siemens Information And Communication Networks, Inc.
• Inventors: Hettish, Mark Bernard
• Granted Patent: US 6,985,575 B2
• Time in Patent Office: Days
• US Class Current: 379/229
• 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/1322 PBX
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking
• CPC Class Codes: H04Q 3/62 for connecting to private branch exchanges

Abstract

A control interface for CSTA protocols utilizes ActiveX properties, methods, events, and pages to access all of the events and services provided by the CSTA protocols. Common paradigms such as Invoke_ID and timers are built in to the interface. The interface further provides statistics and diagnostics via property pages.

Claims

1. A control interface for controlling CSTA protocols in a PBX switch, said control interface comprising:

(a) a computing platform coupled to the PBX switch; and

(b) component based interface objects running on the computing platform and defining properties, methods, and events, said properties, methods and events being mapped to control substantially every event and service of said PBX switch.

2. A control interface according to claim 1, wherein said component based interface objects is ActiveX.

3. A control interface according to claim 2, wherein ActiveX properties are mapped to session configuration.

4. A control interface according to claim 2, wherein ActiveX includes property pages and said property pages are mapped to session configuration.

5. A control interface according to claim 2, wherein ActiveX methods and events are mapped to startup and teardown a connection to the PBX switch.

6. A control interface according to claim 2, wherein substantially all CSTA and private data fields are supported.

7. A control interface according to claim 2, wherein invoke ID generation is automatic and configurable.

8. A control interface according to claim 2, wherein invoke ID timing is automatic and configurable.

9. A control interface according to claim 2, wherein heartbeat messages and replies are automatically generated.

10. A control interface according to claim 9, wherein said heartbeat messages and replies are configurable.

11. A control interface according to claim 2, wherein statuses and errors are automatically logged.

12. A control interface according to claim 11, wherein said statuses and errors are viewable via ActiveX property pages.

14. A method according to claim 13, wherein said component based interface objects is ActiveX.

15. A method according to claim 14, wherein ActiveX properties are mapped to session configuration.

16. A method according to claim 14, wherein ActiveX includes property pages and said property pages are mapped to session configuration.

17. A method according to claim 14, wherein ActiveX methods and events are mapped to startup and teardown a connection to the PBX switch.

18. A method according to claim 14, wherein substantially all CSTA and private data fields are supported.

19. A method according to claim 14, wherein invoke ID generation is automatic and configurable.

20. A method according to claim 14, wherein invoke ID timing is automatic and configurable.

21. A method according to claim 14, wherein heartbeat messages and replies are automatically generated.

22. A method according to claim 21, wherein said heartbeat messages and replies are configurable.

23. A method according to claim 14, wherein statuses and errors are automatically logged.

24. A method according to claim 23, wherein said statuses and errors are viewable via ActiveX property pages.

13. A method for controlling CSTA protocols in a PBX switch, said method comprising the steps of:

(a) coupling a computing platform to the PBX switch; and

(b) running component based interface objects on the computing platform, wherein the component based interface objects defines properties, methods, and events which are mapped to control substantially every event and service of the PBX switch.