Connectors are key elements to Promptar integration capabilities.

Sitting between the server and the outside world, they ensure a seamless and common experience across a wide range of integration requirements both on the phone system side as well as towards applications.

Grouped into functional categories, focusing on particular integration technologies, they seek to keep their abilities as broadly scoped as possible. This results in connectors that tend to be configurable enough to cover many different integration requirements.


Application Connectors
Match caller IDs with application records and return application fields to the server. They also handle external directory lookups.
Phone System Connectors
Produce call events for the configured extensions and handle call control commands on behalf of users.
Session Connectors
Handle in context call information, whether towards the desktop client or producing output to other systems.

Available Connectors


The REST connector integrates with existing applications via HTTP.
Focused in RESTful access to information, the connector is configurable to accomodate other HTTP-based interfaces like XML-RPC, SOAP and others, while supporting multiple authentication mechanisms. Matching resources and finding related ones is easy, based on a model that relates them to one another, where each HTTP request and subsequent processing is adjustable to the finest detail.

Normally used along with an application kit to kick-start integration needs.


URC stands for Universal Relational Connector – it integrates with external applications by querying associated SQL databases.
Supporting Oracle, Microsoft SQL Server, PostgreSQL, MySQL and SQLite, among others, via ODBC, the connector can be configured and modeled after any existing schema to allow Promptar to match any records and obtain related information.

Normally used along with an application kit to kick-start integration needs.


The AMI connector integrates with Asterisk based phone systems via the Asterisk Management Interface.
Highlights include support for SIP, IAX2 and DAHDI/Zap channels and seamless integration with existing dialplans, requiring no changes.
Does not support client based call answering nor hold/resume.


The CSTA connector integrates with phone systems supporting the ECMA/ISO/IEC CSTA standard over TCP.
Highlights include support for Phase I, II and III in third-party call control mode.
Remote call control capabilities vary with phone system manufacturer and handset models.


The HTTPBX connector integrates with phone systems or with individual phone devices via the HTTP protocol.
Supports combinations of centralized/distributed call signalling/control topologies and HTTPS for increased privacy and security.
Signalling and remote call control capabilities vary with the phone system and phone devices.


The TAPI connector integrates with phone systems supporting Microsoft TAPI.
Highlights include support for any combination of centralized, distributed, single- or multi-line TSPs.
Remote call control capabilities vary with the phone system manufacturer, handset models and TSP.


XLATE is a phone system filter connector.
It is used to process phone numbers in order to facilitate matching and performance, improve readability, tolerate bad user input and more.


The BCDRs connector feeds call detail records into an external SQL database of your choice.
Use Oracle, Microsoft SQL Server, PostgreSQL, MySQL and others, via ODBC, and build your analytics from there.

Include as many details per call as you like: track time, date, duration, caller IDs, ring/talk/hold times, internal transfers and more. Optionally set the server processing rules to associate and store in-context application data to each call record.


The Desktop Client Connector, DCC for short, mediates sessions between clients and the server.
Among other capabilities, it tracks calls on behalf of users when the client isn't running, supporting deferred notification of missed calls.