Jump to: navigation, search

MCP Real-time Summary CDR Reporting Services

This report describes a summary of the calls that are currently in-progress in the GVP Media Control Platform. Instead of listing the individual calls, this reporting service makes a summary of these calls in this report. Each report contains a manifest section.

Web Service Endpoint

This report is available at the web service endpoint /ems-rs/RT/CDRs/MCP/summary.

Input Parameters

This report accepts the following Request URI parameters:

Parameter Description
started-from This describes the starting point of the "call start" field of the CDR. It takes the DateTime format as described in the Common Input Parameter Types page. This will cause the report to return only calls started after the specified value.
started-to This describes the ending point of the "call start" field of the CDR. It takes the DateTime format as described in the Common Input Parameter Types page. This will cause the report to return only calls started before the specified value.
app-id This describes the target IVR Profile Config Server DBID. This may be specified zero or more times. All the CDRs returned in the report must belong to one of the specified IVR Profiles. This cannot be specified together with either the tenant-id or the dn parameter.
tenant-id This describes the target Tenant Config Server DBID. This may be specified zero or more times. All the CDRs returned in the report must belong to one of the specified tenants. This cannot be specified together with either the app-id or the dn parameter.
comp-id This describes the target component’s Config Server DBID. This may be specified one or zero times. All the CDRs returned in the report must have been processed on the specified component.
remote-uri This may be specified zero or more times. All the CDRs returned in the report must have a matching remote-uri. A trailing asterisk (*) may be specified in the remote-uri query to indicate a prefix-match.
local-uri This may be specified zero or more times. All the CDRs returned in the report must have a matching local-uri. A trailing asterisk (*) may be specified in the local-uri query to indicate a prefix-match.
gvp-guid This causes the report returns a single call with a matching GVP GUID. If this is specified, no other parameters should be specified.
session-id This causes the report to return a single call with a matching session-id. This must be accompanied by a comp-id parameter. If session-id is specified, no other parameters other than these two should be specified.
genesys-uuid This causes the report to return all calls with a matching Genesys Framework session id. If this is specified, no other parameters should be specified.
call-type This causes the report to contain only calls with matching call-type to be returned. Valid values are:
  • INBOUND
  • OUTBOUND
  • BRIDGED

Output Format

The output for this report consists of two lists:

  • items where each represent the summary for an IVR profiles
  • items where each represent the summary for a components

It conforms to the RelaxNG schema CDR_Summary.rng. Download the GVP RNG Schemas An example report body for this report is as follows:

  <cdr-list count="3">
    <applications>
      <application href="/applications/132" /> 
    </applications>
  </cdr-list>
  <cdr-list count="5">
    <applications>
      <application href="/applications/133" /> 
    </applications>
  </cdr-list>
  <cdr-list count="4">
    <components>
      <component href="/components/211" /> 
    </components>
  </cdr-list>
  <cdr-list count="4">
    <components>
      <component href="/components/212" /> 
    </components>
  </cdr-list>
This page was last edited on July 17, 2020, at 16:12.

Feedback

Comment on this article:

blog comments powered by Disqus