Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

GVP Minutes

This page provides information about how the GVP Minutes metric is defined and calculated, and describes the key values used to designate these metrics in the billing files.

GVP Minutes is a usage metric.

Metric specification

Billable item Cloud Contact Center GVP port minutes
Unit of measure port usage time
Metric Name gvp_minutes
Metric frequency daily
Metric scope Region
Metric definition Duration of GVP treatment applied to calls within GVP platform
Data source GVP Reporting Server database, Genesys Info Mart database
Deployment model Instance of GVP Reporting Server DB for each location (shared between tenants or individual). One global instance of Genesys Info Mart DB for each tenant.

Configuration

Define the following:

  • 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. 
    • Each location within a tenant contains a list of switch names valid for that location, within the switches parameter.
  • In the GVP section:
    • For each location, define the shared GVP deployment details within the gvp section:
      • Configuration Server coordinates
      • GVP Reporting Server database coordinates
      • Credentials (inherited from the gvpdb section under the globals section)
    • 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.  
    • For each tenant:
      • A "shared_gvp" flag that defaults to true;
      • An optional parameter "shared_gvp_alias", which you can use specify a name of the tenant as defined in Shared GVP CME, if required.
    • 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:
      [dbmp]
      rs.db.retention.cdr.default=30

Metric datasets

  • gvp_cdrs_db — statement executed for the GVP RS DBs in each location that tenant has enabled to extract day worth of RM CDRs.

Resulting data file details

  • Each record in the resulting file represents a call undergoing a GVP treatment, with the duration of the treatment presented in milliseconds.
  • File content complies with the IT Integration Specification.
  • A separate file is produced for each region in which the tenant is deployed.
This page was last edited on April 12, 2019, at 20:16.

Feedback

Comment on this article:

blog comments powered by Disqus