2. Requirements

Before starting an installation, in-advance planning is recommended. Refer to the Promptar Server Setup Guide for that. Regarding this connector, ensure you are using one (or a combination) of the following supported phone systems:

Each of these systems is supported independently, regardless of each other and regardless of the type of device, PBX or service it interoperates with; in other words, as long as the integration scenario includes one of the above listed phone systems, it is supported by this connector.

See the Connector Specific section, ahead, for the detailed requirements per phone system.

2.1. General

Promptar HTTPBX Connector runs on both Linux and Windows operating systems. The technical requirements are outlined in the following table:

Linux Windows

Operating System

RHEL 5 or later

32/64 bit

Windows Server 2003 SP2 or later

32/64 bit

Available RAM

64 MB

64 MB

Disk Space

50 MB

50 MB

Notes:

  • Promptar is 32 bit software. If you’re targeting 64 bit Linux, 32 bit software dependencies must be installed; these are described below in 64 Bit Linux Requirements.
  • Promptar Server and connectors are packaged in RPM format for Linux installation and are tested and supported on RHEL or equivalent distributions, like CentOS. However, if you so require, we know Promptar to successfully run on top of distributions, such as Debian or Ubuntu. In those cases, a special support agreement may be delivered.
  • Both RAM requirements and disk space requirements may grow depending on the complexity of the installation and on the implemented logging policies. However, the specified requirements are adequate for typical installations.

64 Bit Linux Requirements

To ensure Promptar Server and connectors run on 64 bit Linux installations, a few 32 bit packages need to be installed. Before any 32 bit package installation, ensure your system is fully up to date by running:

# yum update

For 64 bit CentOS 5, install 32 bit zlib and its dependencies by running:

# yum install zlib.i386

For 64 bit CentOS 6 or 7, install 32 bit zlib and its dependencies by running:

# yum install zlib.i686

2.2. Connector Specific

In addition to the requirements listed above, the following table details per-phone system requirements.

Phone System Requirement

Broadworks

Integrating with Broadworks phone systems requires:

  • Broadworks system support for XSI release 19.0 or later.
  • Take note of the URL of the XSI interface.
  • The XSI URL must be reachable from the connector.
  • Take note of the user and password for each extension to be used.

Switchvox

Integrating with Switchvox phone systems requires:

  • Privileged access to configure Switchvox Event Triggers.
  • The connector host must be reachable by Switchvox HTTP requests.
  • Take note of the user, password and account id for each extension to be used.

Polycom Phones

Integrating with Polycom phones requires:

  • SoundPoint IP models, running UC 4.0 or later and/or VVX models, running UC 5.5 or later.
  • Privileged access to configure each phone’s Telephony Event Notifications and Push Request Parameters.
  • Take note of the MAC address, SIP URI, line number, push username and push password for each phone/extension to be used.

Snom Phones

Integrating with Snom phones requires:

  • 3xx, 7xx and/or 8xx models, running firmware v8 or later.
  • Privileged access to configure each phone’s Action URLs.
  • Take note of the SIP URI, phone username and password for each phone/extension to be used.

Yealink Phones

Integrating with Yealink phones requires:

  • SIP-T2x and/or SIP-T4x models, running firmware version x.81 or later.
  • Privileged access to configure each phone’s Action URLs and Action URI.
  • Take note of the SIP URI, phone username and password for each phone/extension to be used.

About Phone device Support

 

Given the growing number of devices and software/firmware releases in the market, it is possible other models and/or earlier software/firmware releases work. They are currently untested, nonetheless.

2.3. Limitations

Current limitations are, on a phone system basis:

  • Broadworks

    • Each configured extension uses an independent XSI event channel long running HTTP connection.
    • Attended call transfer signalling may be incomplete on some occasions.
  • Switchvox

    • Call transfer signalling is not supported.
    • Call hold/resume is not supported.
  • Polycom, Snom and Yealink Phones

    • It is not possible to issue call control commands over HTTPS while requiring phone certificate validation if the default phone certificates are used. Workarounds are either not requiring certificate validation or deploying custom certificates on the phones.
    • Call control may not work correctly when the phone is participating in more than one call.
    • Attended call transfer signalling is not supported on most scenarios.