Jump to: navigation, search

cdr Section



  


call-timeout

Default Value: 180
Valid Values: An integer from 1 - 1440 inclusive
Changes Take Effect: at start/restart


Specifies the amount of time, in minutes, until a call is considered 'timed out' from the perspective of VAR and CDR reporting

db-maintenance-batch-size

Default Value: 5
Valid Values: An integer from 1 - 1440 inclusive
Changes Take Effect: at start/restart


Specifies the maximum duration, in minutes, to process in a batch for services that support batch purging

max-page-count

Default Value: 10
Valid Values: An integer from 1 - 100 inclusive
Changes Take Effect: at start/restart


The maximum number of pages that will be returned in any given CDR or Call Events report request

max-page-size

Default Value: 100
Valid Values: An integer from 1 - 10000 inclusive
Changes Take Effect: at start/restart


The maximum number of records per page that will be returned in any given CDR or Call Events report request

media-service-cdrs.reduce

Default Value: true
Valid Values:
Changes Take Effect: at start/restart


When this option is set to true the following CDRs will not be stored to the remote database: Any RM CDR or MCP CDR with media service type set to: media, cpd, record or conference.

or-call-counting.enable

Default Value: true
Valid Values:
Changes Take Effect: at start/restart


When this option is set to true the RS will calculate peaks and arrivals for MCP VXML calls and MCP Treatment calls (without VXML).

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 24, 2017, at 01:07.