GVP85DG Table of Contents Page

---

Provision DIDs to DID Group mapping

Now Tenant Administrators can provision DIDs to DID Group mapping. The implementation provides a UI interface so GAX user can use a GUI interface to create/edit/delete DID and DID Group mapping. This new functionality includes overlap checking across multiple tenants, to ensure that there are no duplicate DIDs.

To use the DID Groups feature, Tenant Administrators need the privilege PRIVILEGE_DID_GROUP_SERVICE. They can perform the following functions if they have also have these privileges:

• To access Configuration Manager: ACCESS_CONFIGMANAGER
• Accessing Voice Platform Profiles…

  To read Voice Platform Profiles: READ_VOICEPLATFORMPROFILES

  To modify General options and the state of Voice Platform profiles: MODIFY_VOICEPLATFORMPROFILES

  To modify items in the Options and Annex sections of Voice Platform Profiles: MODIFY_OPTIONS_VOICEPLATFORMPROFILES

  To create or hold Full Control of Voice Platform Profiles: CREATE_VOICEPLATFORMPROFILES

  To delete Voice Platform profiles: DELETE_VOICEPLATFORMPROFILES

GAX application options>

Configure this feature with the options below.
Note: All of these options require Read/Create/Update permission to the tenant object.

 [gvp-rpt]
did-source-type = "switch"
did-source = [
{name: <name of switch object>}
,
{name: <name of switch object>}
]

Notes:

• If did-source-type = switch and did-source are not set, then the plug-in will retrieve the DNs of type TrunkGroup from all the switches available to the user in the current tenant.
• If customers use DNs of type Trunk, they should also use did-source-type="tenant" and manually provision the DIDs accordingly.

or

[gvp-rpt]
did-source-type = "tenant"

Provision DIDs in the <tenant object> options:

[gvp-dids]
111
112
... ''(and so on)''

Note: If did-source-type is not set, it will default to tenant.

---

Welcome

• What's in this Document

Planning

GDGintro

• 1 Introduction

GDGarch

• 2 GVP Architecture

GDGHGW 3 How GVP Works

• 3 How GVP Works

GDGHGWRMW How the Resource Manager Works

• 3.1 How the Resource Manager Works

GDGHGWPSW How the Policy Server Works

• 3.2 How the Policy Server Works

GDGHGWCTICW How the CTI Connector Works

• 3.3 How the CTI Connector Works

GDGHGWPCW How the PSTN Connector Works

• 3.4 How the PSTN Connector Works

HGWMCPW How the Media Control Platform Works

GDGHGWCCPW How the Call Control Platform Works

GDGHGWFMW How the Fetching Module Works

GDGHGWMPW How the MRCP Proxy Works

GDGHGWSSGW How the Supplementary Services Gateway Works

GDGHGWLAR Logging and Reporting

GDGPAP 4 Prerequisites and Planning

Installation

GDGPOS 5 Preparing the Operating System for GVP

GDGinstall 6 Installing GVP

GDGPICG 7 Post-Installation Configuration of GVP

MGVP 8 Maintaining the Genesys Voice Platform

Appendixes

GDGIGMW A Installing GVP Manually (Windows)

GDGIGML B Installing GVP Manually (Linux)

GDGDMMCP C Deploying Multiple Media Control Platforms

GDGDGMSE D Deploying GVP Multi-Site Environments

GDGRMHA E Resource Manager High Availability

GDGRSHA F Reporting Server High Availability

GDGCAPP G HTTP Caching and Performance Planning

DGAGCF H GVP Call Flows

DGASAS I Specifications and Standards