Jump to: navigation, search

Hardware and software prerequisites


Before you install Feature Server, ensure that your system is equipped with the hardware, software and other related requirements detailed in this section.

Hardware

The following table lists the hardware requirements:

Category Prerequisite
Host Install Feature Server on its own dedicated host, unless you are deploying to a small or lab environment. Do not co-locate any other applications on this host.
Operating system

To view supported operating systems, see the Genesys Supported Operating Environment Reference Guide.

  • All Feature Servers in your environment must run on either Linux or Windows. You cannot mix Linux and Windows machines.
  • If you are running RHEL 7, you must:
    • Install all RHEL 7 compatibility packages
    • Install libcurl.so.3 (64-bit only) (RHEL7 has libcurl 4.3.0 but Feature Server requires libcurl 3.0.0 to start).
    • Create a symbolic link for libcurl.so.3 (64-bit only):
      cd /usr/lib64
      ln -s /usr/lib64/libcurl.so.4.3.0 ./libcurl.so.3
  • If you are running RHEL 6, you must:
    • Install all RHEL 6 compatibility packages
    • Create a symbolic link for libcurl.so.3 (64-bit only):
      cd /usr/lib64
      ln -s /usr/lib64/libcurl.so.4.1.1 ./libcurl.so.3
  • If you are running RHEL 5, you must install the C++ compatibility library (compat-libstdc++-33-3.2.3-61.i386.rpm)
RAM 4GB of RAM or above available to the Java process.

Software

The following table lists the software requirements:

Category Prerequisite
Java Runtime Environment (JRE) Java Runtime Environment v1.7 64-bit or higher.


Java heap size By default, the Java heap size is set to 1GB in launcher.xml. To avoid java heap memory error, increase the Java heap size to 1/4th of the system's RAM size as this is the maximum permissible Java heap size.
To increase the Java heap size, update the default value of the jvm_option2 option in launcher.xml.
Below is an example launcher.xml file for a Feature Server machine that has 16GB RAM with a 4GB java heap size.

<parameter name="jvm_option2" displayName="jvm_option2"  mandatory="true" hidden="true" readOnly="true">
    <description><![CDATA[Cassandra related]]></description>
    <valid-description><![CDATA[]]></valid-description>
    <effective-description/>
    <format type="string" default="-Xmx4g" />
    <validation></validation>  
  </parameter>

Note: If you are using the launcher_64 executable, you will need to update launcher_64.xml instead of launcher.xml.

Genesys requirements Install and configure:
  • Genesys Management Framework: See the Genesys Administrator Management Framework Deployment Guide for details.
  • Genesys Media Server 8.5.x (recommended) or 8.1.5 (minimum) components: Resource Manager and Media Control Platform. See Genesys Media Server 8.5 Deployment Guide.
  • Genesys Administrator Extension: 8.1.400.59 or higher. See the Genesys Administrator Extension Deployment Guide for details.
  • Genesys SIP Server
    • A SIP Server 8.1.1 (or later) instance for managing agents: ACD functionality requires SIP Server 8.1.101.56 or later.
      Note: If you want to use an existing premise SIP Server to also process voicemail, you must use SIP Server version 8.1 or higher.
    • To provision phones with Feature Server version 8.1.201.52 or later requires SIP Server version 8.1.101.75 or later. See the Genesys SIP Server Deployment guide for details.

See the Genesys SIP Server Deployment Guide for details.
  • All application templates: Use the supplied templates for SIP Feature Server.

Device management

You can manage SIP desk phones from Polycom, AudioCodes, Genesys, and Yealink using the SIP Device Management area of Genesys Administrator Extension (GAX). If you require this feature, then install and configure the following:

  • Syslog server (mandatory)
  • LDAP server (optional)
  • NTP server (optional)

For details on the implementation, see Implement device management.

Sizing

Feature Server provides three tools to help you size your environment:

  • To calculate the database (embedded Cassandra) disk space requirements for voicemail and device management, enter your information in column B of the SIP Feature Server 8.1.2 Sizing Guide. The guide also calculates network disk space needed for device management functionality.
  • To calculate sizing requirements that match your performance needs, use this Feature Server Sizing Tool.
  • In the case of a co-located/external Cassandra, Feature Server requires a minimum of one Cassandra node per Feature Server pair. However, it is also based on the number of replicas that are required in a data center.
  • For help with other sizing requirements, view Voicemail Performance Test Results.

External Cassandra

If Genesys SIP Feature Server is configured with an external Cassandra cluster, then the Cassandra nodes require the following hardware and software.

Category Requirements
Operating System All Cassandra nodes in your environment must run on either Linux or Windows. You cannot mix Linux and Windows machines.

The clocks on all the Cassandra nodes and Feature Server must be synchronized.

RAM 8 GB of RAM or above.
Runtime environment For Cassandra 2.2.x, Java Runtime Environment (JRE) v1.7 64-bit or higher

For Cassandra 3.x, Java Runtime Environment (JRE) v1.8 64-bit or higher

User resource limits For Linux environment, ensure that the following user resource limits are present and use the ulimit -a command to view the current limits:
  • memlock - unlimited
  • nofile - 100000
  • nproc - 32768
  • as - unlimited

Ports

Important
Do not use the following ports for any other applications that share the host on which you install Feature Server/Cassandra.

Feature Server Nodes

Feature Server uses the following default ports.

Port Used for
8080 http
8443 https
8800 Dial plan

Cassandra Nodes

Cassandra nodes use the following default ports.

Port Used for
7000 Cassandra Storage_port
7001 Cassandra SSL_Storage_port
9160 Cassandra rpc_port
7199 (External Cassandra) or 9192 (Embedded Cassandra) JMX remote port
9042 CQL port (Cassandra v2.2)

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on November 14, 2017, at 05:16.