Jump to: navigation, search

GVP ports

Metric specification

Billable item Cloud Contact Center Genesys Voice Platform (GVP) port peak usage.
Unit of measure

Port peak usage

Metric Name


Metric frequency


Metric scope Region
Metric definition

Peak usage of GVP treatment applied to calls within GVP.

Data source

GVP Reporting Server DB; Genesys Info Mart (GIM) DB 

Deployment model Instance of GVP Reporting Server DB per location (shared between tenants or individual); one global instance of GIM DB per tenant.

Configuration details

  • Regions and locations
    • Within each tenant configuration, define a set of regions and locations in which the tenant is enabled.
  • In the globals section, define credentials at the top level in the following sections:
    • cme_credentials: the credentials to access all the Configuration Servers.
    • gimdb: the default credentials to access the GIM DBs.
    • gvpdb: the default credentials to access the GVP Reporting Server DBs. 
  • GVP section
    • Each location at the top level has a gvp section with details that define the shared GVP deployment details:
      • Configuration Server parameters
      • GVP Reporting Server database parameters
      • Credentials (inherited from the gvpdb section under the globals section)
  • GVP Reporting Server database
    • Globally defined GVP Reporting Server database parameters for each location and default credentials are propagated down to the tenant level, and can be overridden at the tenant level.  
    • Within each location, a list of billable IVR Profiles DBIDs can be defined (ivr_usage_profiles: ['000'] - default value meaning all IVR Profiles are billable).
    • You must configure the GVP Reporting Server to store CDRs table:

Resulting data file details

  • The number displayed in the resulting file (MessageSize field) represents the number of concurrent GVP sessions within the region.
  • The file content complies to the IT Integration Specification:
    Channel type =  1
    Service class =  20
    Activity type =  6
    Status = PORT
  • A separate file is produced for each region, where the tenant is deployed.


Comment on this article:

blog comments powered by Disqus
This page was last modified on June 27, 2018, at 11:27.