Configuring the GVP Reporting Server Database. Genesys 8.5

Configuring GVP Configuring the GVP Reporting Server Database

4. On the User tab, in the Runtime Parameters field, change the language setting.

This configuration affects all JVM default locales.

Configuring the GVP Reporting Server Database

The GVP 8.5 Reporting Server requires one of two supported relational database systems is installed Microsoft SQL Server or Oracle. The database and the Reporting Server can share a host or you can install the database on a separate host. This section describes how to create the GVP Reporting database schema and partitioning the database in the following topics:

•

Before You Begin

•

Setting Up the Database

•

Partitioning CDR and Event Log Tables

•

Recovery Model for Microsoft SQL Server

Before You Begin

• Genesys recommends that the VP Reporting Server is installed before you or your database administrator create a database in your Database Management System

(DBMS).

• Ensure that a fully functional instance of the Microsoft SQL Server or Oracle exists in your deployment.

• Create the Reporting Server database.

Important

This section describes the creation of the database schema only. The setup of the

Microsoft SQL Server or Oracle 10g instances is outside the scope of this document. For information about setting up these instances, see the vendor documentation.

• For installations using an Oracle database, the database administrator should grant the following system privileges to the user(s) who will own the Reporting Server schema:

◦ CREATE TRIGGER

◦ CREATE SEQUENCE

◦ CREATE TABLE

GVP Deployment Guide 387

Configuring GVP Configuring the GVP Reporting Server Database

◦ CREATE PROCEDURE

◦ FORCE TRANSACTION

◦ CREATE VIEW

◦ CREATE SESSION

◦ UNLIMITED TABLESPACE

Setting Up the Database

This section includes a description of a generic procedure to create the database schemas.

Important

Genesys recommends that the user setting up an Oracle database be a different user than the one used to create the Configuration Server database.

The table below contains the paths to the scripts that are used to create the database schema. Select the path to the script that matches the edition (standard or enterprise) of the database that you selected during installation of the Reporting Server component.

A minor change is required when Reporting

Server is deployed with an Oracle RAC database. When the hibernate.remote.database configuration option is used, the Reporting Server internally appends some parameters to the value of the hibernate.remote.url option, including the value of the hibernate.remote.database

option. Therefore, ensure the hibernate.remote.url option is properly configured for use with Oracle RAC by configuring the hibernate.remote.database option with the value blank.

GVP Deployment Guide 388

Configuring GVP Configuring the GVP Reporting Server Database

Script file

Table 30: Database Script Files

Default path

mssql_schema.sql

For Windows:

<Installation_Directory>\Program Files\

GCTI\gvp\VP Reporting Server 8.5\

RS_App_Name\scripts\standard

<Installation_Directory>\Program Files\

GCTI\gvp\VP Reporting Server 8.5\

RS_App_Name\scripts\enterprise oracle_schema.sql

For Windows:

<Install_Dir>\Program Files\GCTI\gvp\VP

Reporting Server 8.5\RS_App_Name\scripts\ standard <Install_Dir>\Program Files\GCTI\ gvp\VP Reporting Server 8.5\RS_App_Name\ scripts\enterprise

For Linux:

<Install_root>/opt/genesys/gvp/

VP_Reporting_Server_8.5/scripts\standard

<Install_root>/opt/genesys/gvp/

VP_Reporting_Server_8.5/scripts\enterprise

Important

The Reporting Server supports the partitioning option for Oracle 10g or 11g enterprise version, and SQL Server 2008 enterprise versions. For all other databases, including SQL Server 2005

(enterprise or standard), use the \scripts\ standard\ path to find the appropriate scripts.

GVP Deployment Guide 389

Configuring GVP Configuring the GVP Reporting Server Database

Reporting Server in Partition Mode on Oracle

When the Reporting Server is installed in partitioned mode (Enterprise) on Oracle by and the default GATHER_STATS_JOB option is used to automatically gather statistics, server performance can be severely affected. In partitioned mode, the

Reporting Server database uses rotating staging tables that are flushed throughout the day. These volatile tables are not suited for automatic statistics gathering.

Genesys recommends the following:

◦ Disable the GATHER_STATS_JOB option before you install the Reporting

Server database to ensure that inaccurate statistics are not associated with the staging tables.

◦ Use the provided lock-stats script to lock the staging tables, for example:

<RS_INSTALLATION_DIRECTORY>/scripts/enterprise/

ReportingService/sql/oracle-lock-stats.sql

This script uses the following Oracle SQL procedure:

DBMS_STATS.LOCK_TABLE_STATS ( ownname VARCHAR2, tabname VARCHAR2);

…where the ownname option must be the name of the schema that is associated with the Reporting Server tables. The script assumes the schema name is REPORTING. You must replace all instances of REPORTING with the proper schema name.

Procedure: Setting Up a Database for the Reporting Server

There are many available query tools that SQL Server and Oracle 10 g can use to execute Structured Query Language (SQL) scripts. For example, SQL Server

Management Studio is included in Microsoft SQL Enterprise edition, and Oracle SQL

Developer is available on the Oracle website.

Oracle is the only supported database when the Reporting Server DBMS is installed on Linux operating systems.

Microsoft cumulative update packages for SQL Server contain the most recent hot fixes and security fixes. Ensure that the hot fix that is listed as a prerequisite for this procedure is included in the Service Pack that you have installed.

GVP Deployment Guide 390

Configuring GVP Configuring the GVP Reporting Server Database

1. Verify that:

▪ Microsoft SQL hot-fix build 3175 must be installed.

▪ The Microsoft SQL Server Management Studio development tool is installed on the SQL Server.

▪ Sun Java Runtime Environment, is installed.

2. On the SQL server, select the Reporting Server database (MSSQL or Oracle) and run the appropriate script. See

{{Documentation:GVP:GDG:CGRSD:DRAFT#TBL30DSF|Table: Database

Script Files]] for a list of DBMSs and the corresponding name and location of the initialization script files.

3. Open the folder that matches your database type.

4. Load and execute the initialization script that corresponds to your DBMS. For information about how to upgrade the database schemas, see Migrating to

GVP 8.5.

Partitioning CDR and Event Log Tables

GVP 8.1.2 and later releases support partitioned CDR and Event Log tables in the

Reporting Database. The Resource Manager, Media Control Platform, Call Control

Platform, VAR CDR tables, and Event Logs table tend to grow rapidly in large-scale environments. To improve the read/write performance, these database tables can be split into multiple partitions, each of which represents a specific period of time.

Partitioning is supported only in the Enterprise editions of Oracle and Microsoft SQL databases.

The Reporting Database can be configured for partitioning in the following ways:

◦ During the installation of Reporting Server 8.1.2, if the user selects the

Enterprise edition of either product, the rs.partitioning.enabled

configuration option in the persistence section is automatically set to true.

◦ The rs.partitioning.partitions-per-day option in the persistence section is used to change the number of partitions per day. The default value is 6, however, the value can be increased in environments that experience high call volumes.

Tip

When database partitioning is enabled,

Genesys recommends that you not change the partitioning mode of operation or the number of partitions (even after the

GVP Deployment Guide 391

Configuring GVP Configuring the GVP Reporting Server Database

Reporting Server is started), because of issues that might arise if the database schema or stored data is changed.

◦ The Reporting Database 8.1.2 schemas are different for enterprise and standard editions and are located in different directories. To create the schema that is compatible with your database selection, see Procedure:

Setting Up a Database for the Reporting Server, on page 287. For more a complete list of configuration options for database partitioning, see the GVP

8.5 User's Guide.

Recovery Model for Microsoft SQL Server

If you are installing your database on Microsoft SQL Server, Genesys recommends that you use the SQL Server Simple Recovery Model, which is a simple backup that can be used to replace your entire database in the event of a failure or to restore your database to another server. This mode enables you to do a complete backup (all of the data) or a differential backup

(data that has changed since the last complete backup only).

This model is a basic recovery model. Every transaction is written to the transaction log, however, the space is reused by new transactions when previous transactions are complete and written to the data file. Since this space is reused, you cannot do a point-in-time recovery. The most recent restore point becomes either the complete backup or the latest differential backup. However, because the transaction log space is reused, the log does get continuously larger, as it does in the Full Recovery Model.

For more information about the types of data this recovery mode is used for and a complete list of backups you can use, see the MSSQL Tips web site.

Tip

If you choose not to use this recovery mode, Genesys recommends that you backup your transaction logs regularly.

Use one of these two methods to configure the Simple Recovery Model...

GVP Deployment Guide 392

Configuring GVP Configuring the GVP Reporting Server Database

METHOD 1

Use T-SQL to enter the following command line:

ALTER DATABASE <dbName> SET RECOVERY recoveryOption GO where <dbName> is the name of the database.

METHOD 2

Use SQL Server Management Studio:

1. Right-click on database name and select Properties.

2. Select the Options page.

3. Click the Recovery model: drop-down menu and select Simple.

4. Click OK to save the configuration.

Procedure: Specify a Non-schema-owner Oracle User on

Reporting Server (Running Oracle Partition Mode)

Enable Reporting Server to run in Oracle partition mode, using an application user other than the schema owner. (Please edit and change "password", usernames and table space names if needed.)

Oracle documentation offers a reason for this procedure: System privileges can be very powerful, and should be granted only when necessary to roles and trusted users of the database. It is better to define application users and grant those users the necessary privileges on the schema owners objects.

1. Install your Oracle database.

2. Create Users, role and current schema trigger.

Note that the schema user's system privileges must be granted directly; not through a role.

3. Run the following statements in a connection as SYSDBA:

-- USER SQL

CREATE USER RS_SCHEMA_OWNER IDENTIFIED BY password

DEFAULT TABLESPACE "USERS"

TEMPORARY TABLESPACE "TEMP";

-- ROLES

-- SYSTEM PRIVILEGES

GVP Deployment Guide 393

Configuring GVP Configuring the GVP Reporting Server Database

GRANT FORCE TRANSACTION TO RS_SCHEMA_OWNER ;

GRANT CREATE TRIGGER TO RS_SCHEMA_OWNER ;

GRANT CREATE SEQUENCE TO RS_SCHEMA_OWNER ;

GRANT CREATE TABLE TO RS_SCHEMA_OWNER ;

GRANT CREATE VIEW TO RS_SCHEMA_OWNER ;

GRANT CREATE SESSION TO RS_SCHEMA_OWNER ;

GRANT UNLIMITED TABLESPACE TO RS_SCHEMA_OWNER ;

GRANT CREATE PROCEDURE TO RS_SCHEMA_OWNER ;

/

-- USER SQL

CREATE USER GEN_REPORTING_APP_RS IDENTIFIED BY password

DEFAULT TABLESPACE "USERS"

TEMPORARY TABLESPACE "TEMP";

-- ROLES

-- SYSTEM PRIVILEGES

GRANT CREATE SESSION TO GEN_REPORTING_APP_RS ;

GRANT UNLIMITED TABLESPACE TO

GEN_REPORTING_APP_RS ;

/

CREATE ROLE GEN_REPORTING_RW_ROLE

/

GRANT GEN_REPORTING_RW_ROLE TO GEN_REPORTING_APP_RS

/

CREATE OR REPLACE TRIGGER

GEN_REPORTING_APP_RS.AFTER_LOGON_TRIGGER

AFTER LOGON ON GEN_REPORTING_APP_RS.SCHEMA

BEGIN

EXECUTE IMMEDIATE 'ALTER SESSION SET current_schema=RS_SCHEMA_OWNER';

END;

/

4. Run the Reporting Server script in

RS_INSTALL_ROOT/scripts/enterprise/ oracle-schema.sql

using the schema owner's connection.

5. Run the following statements, using the schema owner's connection:

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CUSTOM_VARS_FUTURE TO GEN_REPORTING_RW_ROLE ;

GVP Deployment Guide 394

Configuring GVP Configuring the GVP Reporting Server Database

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CUSTOM_VARS_STAGE_1 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CUSTOM_VARS_STAGE_2 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CUSTOM_VARS_STAGE_3 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

DATECOMPONENTS TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

EVENT_LOGS_FUTURE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

EVENT_LOGS_STAGE_1 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

EVENT_LOGS_STAGE_2 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

EVENT_LOGS_STAGE_3 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LAST_ARRIVAL_COUNTED_TABLE TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LAST_PARTITIONED TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LAST_PARTITIONED_ERROR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LAST_PROCESSED_JMS_MESSAGE TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LATENCIES TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LATENCY_CONFIGURATIONS TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LASTCUTOFFRECORD TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

LASTSUMMARIZED TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_TREAT_NV_COUNTS_FUTURE TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_TREAT_NV_COUNTS_STAGE_1 TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_TREAT_NV_COUNTS_STAGE_2 TO

GVP Deployment Guide 395

Configuring GVP Configuring the GVP Reporting Server Database

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_TREAT_NV_COUNTS_STAGE_3 TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_COUNTS_FUTURE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_COUNTS_STAGE_1 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_COUNTS_STAGE_2 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_COUNTS_STAGE_3 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_COUNTED_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_30MIN TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_5MIN TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_DAY TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_HOUR TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_MONTH TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_IVR_ACTION_STATS_WEEK TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_RESULT_STATS_30MIN TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_RESULT_STATS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_RESULT_STATS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_RESULT_STATS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

GVP Deployment Guide 396

Configuring GVP Configuring the GVP Reporting Server Database

PERIOD_RESULT_STATS_MONTH TO

GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PERIOD_RESULT_STATS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

TIMECOMPONENTS TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_CDR_STAGE_1_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RM_CDR_STAGE_1_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RM_CDR_STAGE_2_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RM_CDR_STAGE_3_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RM_CDR_FUTURE_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RM_CDR_HIST_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_ARRIVALS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

PSTNC_PEAKS_WEEK TO GEN_REPORTING_RW_ROLE ;

GVP Deployment Guide 397

Configuring GVP Configuring the GVP Reporting Server Database

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RMDN_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RMDN_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

RMDN_ARRIVALS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_STAGE_1_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_STAGE_2_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_STAGE_3_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_FUTURE_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_HIST_TABLE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_ARRIVALS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_DURATIONS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_30MIN TO GEN_REPORTING_RW_ROLE ;

GVP Deployment Guide 398

Configuring GVP Configuring the GVP Reporting Server Database

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

ASR_PEAKS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_ARRIVALS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CTIC_PEAKS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CUSTOM_VARS_HIST TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

EVENT_LOGS_HIST TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_ARRIVALS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_EXT_FUTURE TO GEN_REPORTING_RW_ROLE ;

GVP Deployment Guide 399

Configuring GVP Configuring the GVP Reporting Server Database

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_EXT_HIST TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_EXT_STAGE_1 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_EXT_STAGE_2 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_CDR_EXT_STAGE_3 TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_DAY TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_HOUR TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_MONTH TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_PEAKS_WEEK TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_TREAT_NV_COUNTS_HIST TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_ARRIVALS_30MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

MCP_VXML_ARRIVALS_5MIN TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_CDR_EXT_FUTURE TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_CDR_EXT_HIST TO GEN_REPORTING_RW_ROLE ;

GRANT ALTER,SELECT,INSERT,UPDATE,DELETE ON

CCP_CDR_EXT_STAG

GVP Deployment Guide 400

Maintaining GVP Configuring the GVP Reporting Server Database

Maintaining GVP

Learn how to stop, start, and uninstall Genesys Voice Platform components.

•

Starting and Stopping the Components

•

Uninstalling the Components

•

Managing the Cache

Starting and Stopping the Components

Use Genesys Administrator to safely and easily start, stop, and gracefully stop each of the components in a GVP Solution object. A graceful stop causes the Application or Solution object to stop accepting new requests and to wait for all media requests to complete. Media requests, such as call recording or conferences, might take a long time to complete using a graceful stop. However, using a stop abruptly terminates any call recording or conference with no chance of recovery, so using a graceful stop is recommended whenever possible.

Prioritizing the startup of the GVP components is important to ensure it is successful. After the initial installation or any time that the systems are shut down for maintenance, use the startup priority that is outlined in the section

Startup Sequence for the VPS

.

You can also use Genesys Administrator to configure the components to start automatically.

This section contains the following procedures:

•

Starting and Stopping GVP Solution Objects

•

Starting and Stopping GVP Application Objects

•

Configuring Application Objects to Start Automatically

Procedure: Starting and Stopping GVP Solution Objects

Use this procedure only if you have created Solution Objects (optional).

1. Verify that:

◦ The GVP components are installed. See

Installing Manually on Windows

or

Installing Manually on Linux

.

◦ A Solution object is created (done automatically since version 8.1.2).

2. Log in to Genesys Administrator.

3. On the Provisioning tab, select Environment > Solutions.

4. Select the Solution object that you want to start.

GVP Deployment Guide 401

Maintaining GVP Configuring the GVP Reporting Server Database

5. In the Tasks panel, click the Runtime section down arrow. The section opens to display the options Start, Stop, and Graceful Stop.

6. Select one of these options.

Procedure: Starting and Stopping GVP Application Objects

1. Verify that the GVP components are installed. See

Manually Installing GVP on

Windows

or

Manually Installing GVP on Linux

.

2. Log in to Genesys Administrator.

3. On the Provisioning tab, select Environment > Applications.

4. Select the Application object that you want to start or stop.

5. In the Tasks panel, click the Runtime section down arrow.

6. Select one of the options that the section opens to display: Start, Stop, or Graceful

Stop.

Graceful Shutdown of the Reporting Server

To minimize the risk of data loss, always shut down components with active client connections to the Reporting Server before shutting down the Reporting Server itself.

Components such as MCP, RM, CCP and MRCP Proxy should be shut down gracefully first; only then can the Reporting Server be shut down safely.

If the Reporting Server goes down unexpectedly or unintentionally, restart it and give it some time to process queued-up local data before shutting down client components.

Procedure: Configuring Application Objects to Start

Automatically

This procedure presents two different ways to configure the components.

1. Log in to Genesys Administrator.

2. On the Provisioning tab, select Environment > Applications. The

Configuration tab appears.

3. Configure the Application in one of two ways:

METHOD ONE

a. Double-click the Application object that you want to configure to start automatically.

In the Server Info section: b. Scroll down to the Auto Restart field.

GVP Deployment Guide 402

Maintaining GVP Configuring the GVP Reporting Server Database c. Click the True check box to enable it.

METHOD TWO

On the Options tab, from the View drop-down menu: a. Select Advanced View (Annex).

b. In the sml section, click New.

The New Option dialog box appears.

c. In the Name field, enter autostart.

d. In the Value field, enter true.

4. Save the changes.

Uninstalling the Components

Before you begin to uninstall the components, ensure that they are stopped by using the

Stop applications gracefully option in Genesys Administrator. Uninstall the GVP components one at a time.

The procedures to uninstall the GVP components manually are included in this section, but uninstalling the components by using Genesys Administrator is recommended.

Procedure: Uninstalling GVP Components by Using Genesys

Administrator

1. Before uninstalling a component on Linux, ensure that write permissions are configured on the LCA folder by issuing the following command as root on the server: chmod a+w /opt/genesys/lca

2. Log in to Genesys Administrator.

3. On the Provisioning tab, select Environment > Applications.

4. Double-click the Application object that you want to uninstall.

The Configuration tab appears.

5. In the tool bar, select Uninstall.

A Confirm dialog box appears.

6. Click Yes.

A dialog box appears that indicates that the uninstallation process is complete.

Procedure: Uninstalling GVP Components Manually (Windows)

Uninstall GVP manually, one component at a time, on a Windows host.

GVP Deployment Guide 403

Maintaining GVP Configuring the GVP Reporting Server Database

1. Log on to the host where the component is installed, to uninstall it manually.

2. Stop the Application objects to be uninstalled by using the Stop GVP Applications

Gracefully option in Genesys Administrator. See

Procedure: Starting and Stopping

GVP Application Objects

.

3. From the Start menu, select Control Panel > Add/Remove Programs.

4. Select the appropriate GVP component from the list of currently installed programs.

5. Click Remove.

6. When the uninstall is complete for each of the GVP components, restart the machine.

Procedure: Uninstalling GVP Components Manually (Linux)

1. Log on to the Linux host where the component is installed.

2. Stop the components by using the Stop GVP Applications Gracefully option in

Genesys Administrator. See

Procedure: Starting and Stopping GVP Application

Objects

.

3. Delete the installation directory.

Managing the Cache

This section describes ways in which you can manage the Squid and Page Collector cache manually on Windows and Linux hosts, see:

Squid Cache Management

The table below summarizes the commands that you can use to force the cache to be refreshed, purged, or cleared. Issue these commands in the cmd console window on the

Media Control Platform or Call Control Platform host whose cache you want to manage.

Objective

Table: Manual Cache Management Commands

Command

Windows OS

C:\squid\bin\squidclient -s -r <uri>

Refresh an object.

Where <uri> is the full URI of the object that you want to refresh.

Purge an object.

C:\squid\bin\squidclient -s -m PURGE <uri>

GVP Deployment Guide 404

Maintaining GVP Configuring the GVP Reporting Server Database

Where <uri> is the full URI of the object that you want to purge.

C:\squid\bin\sbin\squid -k shutdown -n SquidNT

Clear the entire cache.

Refresh an object.

Purge an object.

echo

> C:\squid\var\cache\swap.state

net start SquidNT

Linux OS

/usr/local/squid/bin/client -s -r <uri>

Where <uri> is the full URI of the object that you want to refresh.

/usr/local/squid/bin/client -s -m <PURGE> <uri>

Where <uri> is the full URI of the object that you want to refresh.

/usr/local/squid/bin/squid -k shutdown

Clear the entire cache.

echo "" > /usr/local/squid/cache/swap.state

/usr/local/squid/bin/squid

For more information about how GVP handles caching, see

Caching

.

Rotating the Caching Logs (Windows)

Schedule a daily task in Windows Scheduler to rotate the logs for the Squid caching service.

GVP does not rotate the logs automatically because Squid caching is a third-party application.

Tip

GVP Deployment Guide 405

Maintaining GVP Configuring the GVP Reporting Server Database

In GVP version 8.1.2 and above, the Squid Caching

Proxy automatically rotates the caching logs, therefore, this procedure is only required for GVP

8.1.1 and earlier 8.x releases.

Procedure: Scheduling the Caching Logs Rotation (Windows)

Schedule a daily task to rotate the Squid caching service logs on Windows.

1. Verify that the Squid caching proxy is installed and service is running. See

Manually

Installing GVP on Windows

.

2. From the Windows Start menu, select All Programs > Accessories >

Notepad.

3. Enter the following script:

@echo

C:\squid\sbin\squid.exe -k rotate -n SquidNT

@pause

@echo

4. Save the file with the extension .bat for example, SquidTask.bat.

5. From the Windows Start menu, select All Programs > > System Tools >

Scheduled Tasks.

6. Double-click Add Scheduled Task.

The Scheduled Task Wizard appears.

7. Click Next to browse to the .bat file you created in an earlier step.

8. Double-click the file.

The Scheduled Task Wizard automatically populates the Task Name field.

9. In the Perform this task: section, select Daily.

10. Click Next and enter 2:00 AM in the Start Time field.

11. Select the Every Day radio button.

12. In the Start Date field, enter the date that you want the task to start for example, 5/

12/2008.

13. Click Next to enter the username of the person who is scheduling the task

14. In the Password and Confirm Password fields, enter the password.

15. Click Next to finish and quit the wizard.

Tip

GVP Deployment Guide 406

Maintaining GVP Configuring the GVP Reporting Server Database

To uninstall the log rotation schedule, delete the scheduled task.

Scheduling the Caching Logs Rotation (Linux)

You can configure a rotation schedule for the Squid caching logs on Linux using the /etc/ logrotate.d/squid file. The default configuration is to rotate the logs weekly, retain the last five files, and compress each archived file, however the file can be modified to suit your needs.

[+] This script is a typical configuration in the Squid log rotation file:

/var/log/squid/access.log { weekly rotate 5 copytruncate compress notifempty missingok

}

/var/log/squid/cache.log { weekly rotate 5 copytruncate compress notifempty missingok

}

/var/log/squid/store.log { weekly rotate 5 copytruncate compress notifempty missingok

# This script asks squid to rotate its logs on its own.

# Restarting squid is a long process and it is not worth

# doing it just to rotate logs postrotate

/usr/sbin/squid -k rotate endscript

}

GVP Deployment Guide 407

Maintaining GVP Configuring the GVP Reporting Server Database

For more information about the logrotate capabilities of Linux, check the vendor documentation or visit the website.

Page Collector Cache Management

Purge the Page Collector cache manually by configuring the Media Control Platform

Application object in Genesys Administrator.

Procedure: Purging the Page Collector Cache Manually

Configure the Media Control Platform to purge the Page Collector cache the next time that the server is restarted.

1. Log in to Genesys Administrator.

2. On the Provisioning tab, select Environment > Applications.

3. Double-click the Media Control Platform Application object that you want to configure.

The Configuration tab appears.

4. On the Options tab, from the View drop-down list: a. Select Advanced View (Options).

b. In the PageCollector section, set value of the PurgeCache parameter to 1; for example, PurgeCache = 1.

c. Save the changes.

GVP Deployment Guide 408

Resource Manager High Availability Configuring the GVP Reporting Server Database

Resource Manager High Availability

This topic describes how to configure the Genesys Voice Platform (GVP) Resource Manager and the Configuration Database for High Availability (HA) on Windows and Linux operating systems.

•

Overview

•

Monitoring the NICs

•

Integrating GVP with SIP Server for an Active-Active Resource Manager

Configuration

•

Resource Manager HA (Windows)

•

Resource Manager HA (Linux)

Overview

High availability for Resource Manager is achieved by combining two Resource Manager instances in an HA-pair, which enables the resource-management function to be distributed over two servers to provide redundancy. The active Resource Manager node (running on server 1) simultaneously handles the incoming IP traffic and updates the other Resource

Manager node (in the HA-pair) with information about the active sessions, thereby achieving high availability and scalability.

HA prevents single point-of-failure and provides immediate failure recovery. In addition, administrators can manage the HA-pair as a single system either locally or remotely.

HA Modes

To configure the Resource Manager Application in HA mode, use the cluster.ha-mode parameter to set the value to active standby, active active, or None. A value of None, which is the default, means the Resource Manager is in stand-alone mode. Two HA modes exist for Resource Manager:

• Active Standby: Where only the active instance processes SIP requests and the backup instance processes SIP requests when the active instance fails. Two

Resource Manager instances share the same virtual IP address but only one instance is actively receiving network traffic.

To configure the Resource Manager in active standby mode, see

Task Summary:

Configuring the RM in HA Active Standby Mode (Windows)

and

Configuring the RM in High Availability Active-Standby Mode (Linux)

GVP Deployment Guide 409

Resource Manager High Availability Configuring the GVP Reporting Server Database

• Active Active: Where either one of the active nodes can process SIP requests. This mode is similar to the virtual IP solution; however, an external load balancer maintains the virtual IP address that forwards information to the active nodes in the cluster. The load balancer can apply proprietary load-balancing rules when it forwards the requests.

The virtual IP address for the active active HA-pair is configured by using the cluster.virtual-ip parameter in the Resource Manager Application. The Resource

Manager advertises the virtual IP address in the Record-Route and Via headers so that SIP Server or the Media Control Platform can send mid-call requests and responses to the load balancer.

To configure the Resource Manager in active active mode, see

Task Summary:

Configuring the RM in HA Active-Active Mode (Windows)

and

Configuring the RM in

High Availability Active-Active Mode (Linux)

Tip

When configured as an HA-pair, both Resource

Manager instances must manage the same set of resources.

In addition, the load balancer must have the routing capability to route the same SIP transactions to the same Resource Manager instance.

(The load balancer must be SIP-aware and support the Call-ID stickiness feature to ensure this requirement is met.) The same Resource Manager node must process the SIP transaction in its entirety.

Before You Begin

Before you begin the procedures in this section, pay attention to the following information:

Ensure that the Resource Manager hosts...

...are configured and fully functional in stand-alone mode.

...reside on the same subnet.

...have at least two network interface cards (NICs) that are configured with unique IP addresses (within the same subnet).

GVP Deployment Guide 410

Resource Manager High Availability Configuring the GVP Reporting Server Database

...have one virtual IP address allocated for the cluster (to be shared by the Resource

Manager hosts in the HA-pair)

Tip

If you are configuring HA on Linux by using the

Simple Virtual IP failover option, only one NIC is required. However, to avoid a single point-of-failure if the NIC or network switch fails, you must use the

Bonding Driver failover option with two NICs. The bonding driver is configured to share one IP address among two NICs operating one NIC as active and the other as standby. See

Resource Manager HA

(Linux)

. If you configure active active HA on either

Windows or Linux, only one NIC per server is required.

• If you are deploying the Supplementary

Services Gateway (SSG) on the same host as the Resource Manager, be aware of a possible port conflict. The default HTTPS

Port for the Supplementary Services

Gateway is 9801 (controlled by the HTTPS

Port parameter in the HTTP section), which is also the default port value for the

Resource Manager member.1 and member.2 cluster parameters when they are configured for HA. Use Genesys

Administrator to change the values, if required.

• When you configure the Resource Manager for active standby HA, five IP addresses are required. (If you are using the Simple Virtual

IP failover option, only three IP addresses are required.) The first network adapter handles the network traffic that is addressed to the server as part of the HA-pair, while the second network adapter is used for intrahost communication. Figure 32 depicts an example of how IP addresses are assigned to the servers.

GVP Deployment Guide 411

Resource Manager High Availability Configuring the GVP Reporting Server Database

• Simple Network Management Protocol

(SNMP) Management Information Bases

(MIB) function properly when there is only one instance of a GVP component on a host.

It is not recommended that you install the

SNMP MIBs on a server that is hosting more than one instance of the Resource Manager.

SNMP traps are sent by the active Resource

Manager only.

Figure: IP Address Assignation for active standby HA

Monitoring the NICs

When the Resource Manager is configured as an active standby HA-pair, it monitors the

NICs to determine network error instances for example, when a cable is unplugged. If any of the NICs encounters errors, the network is considered to be down.

The Resource Manager must monitor the NICs that are used in the HA-pair to ensure that the Network Load Balancing (NLB) is working properly:

GVP Deployment Guide 412

Resource Manager High Availability Configuring the GVP Reporting Server Database

• For Windows: One with NLB configured, and one with the IP address of the host computer.

• For Linux: If only one NIC is used in the HA-pair, it must be monitored.

When there are more than two NICs present in the system and the other NICs are not part of the NLB HA-pair, it is recommended that you specify the Media Access Control (MAC) addresses of the NICs that you want to monitor.

To specify the NICs that you want to monitor, use the steps in

Procedure: Specifying the

NICs to Monitor (Windows)

, and

Procedure: Specifying the NICs for Monitoring (Linux)

.

Tip

When Windows NLB is used, the standby Resource

Manager can take up to seven (7) seconds to become active when failover occurs. However, there is no data loss, even for those calls that are in progress.

Integrating GVP with SIP Server for an Active-Active

Resource Manager Configuration

For all GVP deployments with SIP Server that will support Resource Manager High

Availability Active-Active in IP modes, configure a VoIP service DN.

[+] GVP as a Self-service IVR

In self-service mode, GVP works as an IVR for handling inbound calls that are forwarded by

SIP Server. Calls can be self-service (where the call terminates at GVP), or assisted service

(where GVP transfers the call to an agent as needed).

Configure GVP as a Trunk DN in SIP Server:

contact

Table: Trunk DN Configuration (Inbound)

Parameter Value

"::msml" prefix sip-busy-type

Initial digits that match the DNIS number

2

GVP Deployment Guide 413

Resource Manager High Availability Configuring the GVP Reporting Server Database

Geo-location (optional) <location1, location2>

For HPE, configure GVP as a Trunk Group DN in SIP Server:

Parameter

contact

Table: Trunk Group DN Configuration (Outbound)

Value

"::msml" subscriptionid

<DN_Name> make-callrfc3725-flow 1 referenabled false ring-toneon-makecall false request-uri sip:msml@<RMHost>:<RMport>;gvp-tenant-id=[<Tenant-Name>]

[+] GVP as an Inbound Media Server

In this mode, SIP Server is an application server and GVP is a media server performing requests such treatment, greeting, music, conference, and recording.

Configure GVP as a VoIP Service DN in SIP Server:

Table: VoIP Service DN Configuration Parameters

Name Value Type

contact-list (for IP mode) Resource Manager's contacts Mandatory service-type msml Mandatory

<time in seconds> oos-check

(Active OOS functionality)

Mandatory oos-force geo-location

<time in seconds> Mandatory

<location1, location2> Optional

GVP Deployment Guide 414

Resource Manager High Availability Configuring the GVP Reporting Server Database subscription-id

<tenant_name>

Optional

Parameter Notes

Contact-list

Use contact-list when SIP-Server Resource Manager High Availability Active-Active

(SIP-S RM HA A-A) is deployed in IP mode.

Contact-list contains comma-separated URIs,and is used when SIP-S RM HA A-A is deployed in IP mode.

A new DN level parameter contact-list is introduced for supporting Multiple IP address configuration. This parameter will have comma-separated list of any valid SIP URI.

Configure each URI using following format:

[sip/sips:][number@]hostport[;transport=(tcp/udp/tls)]

Where:

• sip/sips: is an optional prefix.

• number is the DN number (currently ignored.)

• hostport is a host:port pair, where host is a dotted IP address for the endpoint.

Tip

Media Server mode uses the same VOIP service

DN that is used to configure Resource Manager contacts. This mode requires Media Server status notification functionality, so the subscription-ID parameter must be added in the VOIP service DN.

[+] GVP as an Outbound Media Server

In this mode, GVP is a media server providing outbound services such as Call Progress

Analysis, music treatment, media bridging (ASM mode) and playing the VXML application.

Configure GVP as a Trunk Group with these parameters:

GVP Deployment Guide 415

Resource Manager High Availability Configuring the GVP Reporting Server Database

Parameter name

contact subscriptionid

"::msml"

<DN_Name>

Parameter value

make-callrfc3725-flow 1 referenabled false ring-toneon-makecall false request-uri sip:msml@<RMHost>:<RMport>media-service=cpd;gvp-tenant-id=[<Tenant-Name>]

In deployments of CTI through an IVR Server (used for playing VoiceXML applications after the outbound call is established), configure GVP as a set of Voice treatment port DNs, with this parameter:

Parameter name Parameter value

contact "::msml"

For Voicemail Integration, you must configure a VoIP service DN along with the msml VoIP service DN. Configure the voicemail VoIP service DN with these parameters:

Parameter Value

contact

"::msml" service-type voicemail

[+] Limitations of the Active-Active RM Configuration

Integration of GVP with SIP Server for RM HA (Active-Active) is not supported with DNS

SRV as RM Virtual-IP or SIP-S contact.

SIP Server supports Resource Manager configuration in these ways:

• Multiple IP addresses (IP mode) In IP mode, SIP Server does not support configuring priority and weightage for each IP address. All entries are considered of equal priority and weight. Set cluster.ha-mode to active-active.

GVP Deployment Guide 416

Resource Manager High Availability Configuring the GVP Reporting Server Database

SIP Server supports only the round-robin load-balancing method to support Resource

Manager HA Active-Active.

See also in the SIP Server Deployment Guide:

• Configuring an MSML Service in Chapter 4: SIP Devices Support.

• Genesys Voice Platform Integration in Chapter 5: SIP Server Feature Support.

When SIP Server is configured for Resource Manager High Availability Active-Active, all the calls going to the RM will be in either TCP or UDP format, based on what transport is specified in the VoIP service DN.

Notes on Resource Manager Configuration for Active-Active

(Load Balancing)

Set these options on each Resource Manager:

• Set cluster.ha-mode to active-active.

• Set cluster.virtual-ip to the RM IP address.

• Set Cluster.member.1|2 to the corresponding RM IP:Port.

• On each MCP, set transport.staticroutelist to RM Node1 contact, RM

Node2 contact.

• In the sip section: routeset=<sip:ipaddress:port;lr> must be one of the

Resource Managers.

Configure half of the MCP's route-set to point to one RM, and the other half of the MCP's route-set to point to the other RM.

• In the vrmrecorder section: routeset=<sip:ipaddress:port;lr> must be one of the Resource Managers.

Configure half of the MCP's route-set to point to one RM, and the other half of the MCP's route-set to point to the other RM.

Tip

The configuration parameter transport.staticroutelist

is also applicable for other SIP components such as

CTIC and CCP.

GVP Deployment Guide 417