CSTA is a protocol interface to external CTI (Computer Telephony Integration) applications to control the SIP endpoints. The interface is used by the Lotus Sametime Unified Telephony applications and Telephony Application Server. These applications support the ECMA (European Computer Manufacturers Association) standard. CSTA applies with the Lotus Sametime Unified Telephony Common Application Platform (CAP) to control and monitor telecommunication activities on SIP endpoints. The CSTA service is a call processing component that subscribes for call processing events in the UCE (Universal Call Engine) and sends CSTA information messages to the CSTA Signaling Manager (CSTASM). It receives CSTA information messages from the CSTA Service and handles conversions to GNF (Global Number Format) as needed.
CSTA-Service distinguishes the public number ONDs from the private number ONDs. The public numbers are to be resolved to a GNF format whereas the private numbers are not be converted into GNF. Instead of the GNF number, the private numbers with no barrier code, if one is included, should be reported in the responses and the events sent to CSTA-SM and also being stored in SSAL.
CSTA (Computer Supported Telecommunications Applications) Support Features
Lotus Sametime Unified Telephony provides a standard European Computer Manufacturers' Association (ECMA) Computer Supported Telecommunications Applications (CSTA) protocol interface to external CTI applications, which permits applications such as Telephony Application Server, and Lotus Sametime to control the Lotus Sametime Unified Telephony SIP endpoints. It also describes other Lotus Sametime Unified Telephony capabilities relevant to applications that utilize the CSTA interface.
CSTA Services Support
Lotus Sametime Unified Telephony supports a list of standard CSTA services.
How to Configure CSTA Settings
With the CSTA settings the maximum number of CSTA sessions (up to 256), the CSTA IP addresses (and ports) and the maximum number of monitored endpoints will be defined.
How to Provision a Subscriber for CSTA
This procedure describes how to configure CSTA at the feature profile or subscriber level. Feature profiles, in turn, can be created and configured at the switch level or the BG (Business Group) level. At the subscriber level, the previously assigned feature profile can be overwritten to selectively enable, disable or modify the feature configuration for the particular subscriber. Those subscriber-level modifications effectively disconnect the individual service configuration from the underlying feature profile: a subsequent Reset Subscriber Lines
on the feature profile will not influence a disconnected service configuration.
Application Populated Caller ID
APCID (Application Populated Caller ID) provides SIP or CSTA enabled outbound call center applications with the capability to present to the called party a valid callback number for the specific marketing customer's outbound campaign.