Jump to: navigation, search

ASR ports

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

Metric specification

Billable item Cloud Contact Center ASR port peak usage and Cloud Contact Center TTS port peak usage.
Unit of measure Port peak usage
Metric name gvp_asr_ports
Metric frequency Daily
Metric scope Region
Metric definition Peak usage of ASR treatment / TTS treatment applied to calls within the Genesys Voice Platform (GVP). 
Data source GVP Reporting Server (RS) database; Genesys Info Mart database
Deployment model Instance of GVP Reporting Server database per location (shared between tenants or individual); one global instance of Genesys Info Mart database per 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.
  • Credentials — 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 Genesys Info Mart database.
    • gvpdb: the default credentials to access the GVP Reporting Server database. 
  • 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 in the globals section).
  • GVP Reporting Server database — The globally defined GVP Reporting Server database parameters for each location and default credentials are propagated down to the tenant level, but you can override them at the tenant level. In addition:
    • Each tenant has a shared_gvp flag that defaults to true. In premise deployments, always set shared_gvp to false.
    • A shared_gvp_alias parameter is not used to configure premise tenants. Leave this parameter empty.
  • MCP configuration — Configure the Media Control Platform (MCP) as follows:
    • Configure MCP to send the required events to the Reporting Server. Genesys does not validate the configuration, but it is a prerequisite:
      [ems]
      dc.default.metricsfilter=..,148-151.
    • Validate the availability of the events based on the retention period of event records, as configured in the GVP Reporting Server:
      [dbmp]
      rs.db.retention.events.default=7

Resulting data file details

  • The number displayed in the resulting file (MessageSize field) represents the number of concurrently active ASR or TTS sessions.
  • The file content complies with the IT Integration Specification:
    Channel type =  3 (TTS), 1 (ASR)
    Service class =  7 (TTS), 24 (ASR)
    Activity type =  6 (TTS), 6 (ASR)
    Status = PORT
  • A separate file is produced for each region, where the tenant is deployed.
This page was last modified on April 12, 2019, at 13:16.

Feedback

Comment on this article:

blog comments powered by Disqus