[cdr]

call-timeout

Call Timeout

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

Valid values

An integer from 1 - 1440 inclusive

Default value

180

Takes effect at start/restart

call-timeout-batch-size

Batch Size for Call Timeout Processing Service

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

Valid values

An integer from 1 - 1440 inclusive

Default value

10

Takes effect at start/restart

call-timeout-window

Grace Period for Call Timeout Processing Service

Specifies a window of time, in hours, for any late CDR to be still eligible for processing by the timeout service

Valid values

An integer from 1 - 1440 inclusive

Default value

24

Takes effect at start/restart

db-maintenance-batch-size

Batch Size for DB Maintenance Service

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

Valid values

An integer from 1 - 1440 inclusive

Default value

30

Takes effect at start/restart

max-page-count

Max Page Count

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

Valid values

An integer from 1 - 100 inclusive

Default value

10

Takes effect at start/restart

max-page-size

Max Page Size

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

Valid values

An integer from 1 - 10000 inclusive

Default value

100

Takes effect at start/restart

[dbmp]

rs.db.retention.cdr.default

Data Retention Default for CDRs

The number of days for which Call Detail Records data will be retained in the database.

Valid values

An integer greater than 0

Default value

30

Takes effect immediately

rs.db.retention.events.default

Data Retention Default for Upstream Events

The number of days for which call log events (upstream logs) data will be retained in the database.

Valid values

An integer greater than 0

Default value

7

Takes effect immediately

rs.db.retention.operations.5min.default

Data Retention Default for 5-minute OR Data

The number of days for which 5-minute operational data will be retained in the database.

Valid values

An integer greater than 0

Default value

1

Takes effect immediately

rs.db.retention.operations.daily.default

Data Retention Default for Daily OR Data

The number of days for which daily operational data will be retained in the database.

Valid values

An integer greater than 30

Default value

90

Takes effect immediately

rs.db.retention.operations.hourly.default

Data Retention Default for Hourly OR Data

The number of days for which hourly operational data will be retained in the database.

Valid values

An integer greater than 0

Default value

7

Takes effect immediately

rs.db.retention.operations.monthly.default

Data Retention Default for Monthly OR Data

The number of days for which monthly operational data will be retained in the database.

Valid values

An integer greater than 30

Default value

1095

Takes effect immediately

rs.db.retention.operations.weekly.default

Data Retention Default for Weekly OR Data

The number of days for which weekly operational data will be retained in the database.

Valid values

An integer greater than 30

Default value

364

Takes effect immediately

rs.db.retention.var.5min.default

Data Retention Default for 5-minute VAR Data

The number of days for which for 5-minute Call Summary and IVR Action Summary data will be retained in the database.

Valid values

An integer greater than 0

Default value

1

Takes effect immediately

rs.db.retention.var.daily.default

Data Retention Default for Daily VAR Data

The number of days for which for daily Call Summary and IVR Action Summary data will be retained in the database.

Valid values

An integer greater than 30

Default value

90

Takes effect immediately

rs.db.retention.var.hourly.default

Data Retention Default for Hourly VAR Data

The number of days for which for hourly Call Summary and IVR Action Summary data will be retained in the database.

Valid values

An integer greater than 0

Default value

7

Takes effect immediately

rs.db.retention.var.monthly.default

Data Retention Default for Monthly VAR Data

The number of days for which for monthly Call Summary and IVR Action Summary data will be retained in the database.

Valid values

An integer greater than 30

Default value

1095

Takes effect immediately

rs.db.retention.var.weekly.default

Data Retention Default for Weekly VAR Data

The number of days for which for weekly Call Summary and IVR Action Summary data will be retained in the database.

Valid values

An integer greater than 30

Default value

364

Takes effect immediately

[log]

all

Output for level all

Specifies the outputs to which an application sends all log events. The log output types must be separated by a comma when more than one output is configured.

Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application's working directory.
  • Default value

    (blank)

    Takes effect immediately

    debug

    Output for level debug

    Specifies the outputs to which an application sends the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application's working directory.
  • Default value

    (blank)

    Takes effect immediately

    expire

    Log Expiration

    Determines whether log files expire. If they do, sets the measurement for determining when they expire, along with the maximum number of files (segments) or days before the files are removed.

    Valid values

  • false No expiration; all generated segments are stored.
  • [number] file or [number] Sets the maximum number of log files to store. Specify a number from 1-100.
  • Default value

    false

    Takes effect immediately

    interaction

    Output for level interaction

    Specifies the outputs to which an application sends the log events of the Interaction level and higher (that is, log events of the Standard and Interaction levels). The log outputs must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application's working directory.
  • Default value

    (blank)

    Takes effect immediately

    message_format

    Log messages format

    Specifies the format of log record headers that an application uses when writing logs in the log file. Using compressed log record headers improves application performance and reduces the log file's size. With the value set to short:
  • A header of the log file or the log file segment contains information about the application (such as the application name, application type, host type, and time zone), whereas single log records within the file or segment omit this information.
  • A log message priority is abbreviated to Std, Int, Trc, or Dbg, for Standard, Interaction, Trace, or Debug messages, respectively.
  • The message ID does not contain the prefix GCTI or the application type ID.
    A log record in the full format looks like this:
    2002-05-07T18:11:38.196 Standard localhost cfg_dbserver GCTI-00-05060 Application started
    A log record in the short format looks like this:
    2002-05-07T18:15:33.952 Std 05060 Application started
  • Valid values

    • short
    • full
  • short An application uses compressed headers when writing log records in its log file.
  • full An application uses complete headers when writing log records in its log file.
  • Default value

    short

    Takes effect immediately

    segment

    Log Segmentation

    Specifies whether there is a segmentation limit for a log file. If there is, sets the mode of measurement, along with the maximum size. If the current log segment exceeds the size set by this option, the file is closed and a new one is created.

    Valid values

  • false No segmentation is allowed.
  • [number] KB or [number] Sets the maximum segment size, in kilobytes.
  • [number] MB Sets the maximum segment size, in megabytes. Default is 10MB.
  • Default value

    false

    Takes effect immediately

    standard

    Output for level standard

    Specifies the outputs to which an application sends the log events of the Standard level. The log output types must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application's working directory.
  • Default value

    network

    Takes effect immediately

    time_format

    Time format for log messages

    Specifies how to represent, in a log file, the time when an application generates log records.
    A log record's time field in the ISO 8601 format looks like this:
    2001-07-24T04:58:10.123

    Valid values

    • time
    • locale
    • ISO8601
  • time The time string is formatted according to the HH:MM:SS.sss (hours, minutes, seconds, and milliseconds) format.
  • locale The time string is formatted according to the system's locale.
  • ISO8601 The date in the time string is formatted according to the ISO 8601 format. Fractional seconds are given in milliseconds.
  • Default value

    time

    Takes effect immediately

    trace

    Output for level trace

    Specifies the outputs to which an application sends the log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels). The log outputs must be separated by a comma when more than one output is configured.

    Valid values

  • stdout Log events are sent to the Standard output (stdout).
  • stderr Log events are sent to the Standard error output (stderr).
  • network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database.
  • [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application's working directory.
  • Default value

    (blank)

    Takes effect immediately

    verbose

    Verbose Level

    Determines whether a log output is created. If it is, specifies the minimum level of log events generated. The log events levels, starting with the highest priority level, are Standard, Interaction, Trace, and Debug.

    Valid values

    • all
    • debug
    • trace
    • interaction
    • standard
    • none
  • all All log events (that is, log events of the Standard, Trace,Interaction, and Debug levels) are generated.
  • debug The same as all.
  • trace Log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels) are generated, but log events of the Debug level are not generated.
  • interaction Interaction level is not mapped and will have the same effect as none
  • standard Log events of the Standard level are generated, but log events of the Interaction, Trace, and Debug levels are not generated.
  • none No output is produced.
  • Default value

    trace

    Takes effect immediately

    [messaging]

    activemq.broker

    JMS Broker URI

    The URI of the ActiveMQ JMS broker that receives Reporting Server messages

    Valid values

    A URI for the JMS Message Broker

    Default value

    tcp://localhost:61616

    Takes effect at start/restart

    activemq.dataDirectory

    JMS Data Directory

    The full path of the directory that ActiveMQ uses for persistent queuing

    Valid values

    A directory path

    Default value

    $InstallationRoot$/data/activemq

    Takes effect at start/restart

    [persistence]

    hibernate.local.dbDirectory

    Local Database Directory

    The local database working directory, which is used for temporary storage when the remote database is unavailable

    Valid values

    A directory path

    Default value

    $InstallationRoot$/data/derby

    Takes effect at start/restart

    hibernate.remote.dialect

    Database Dialect

    The dialect Hibernate should use when interacting with the database

    Valid values

    • org.hibernate.dialect.SQLServerDialect
    • org.hibernate.dialect.Oracle10gDialect
    org.hibernate.dialect.SQLServerDialect or org.hibernate.dialect.Oracle10gDialect

    Default value

    org.hibernate.dialect.SQLServerDialect

    Takes effect at start/restart

    hibernate.remote.xaDataSourceClassName

    Database Driver

    The XA transaction compatible driver that Hibernate should use when interacting with the database

    Valid values

    • com.microsoft.sqlserver.jdbc.SQLServerXADataSource
    • oracle.jdbc.xa.client.OracleXADataSource
    com.microsoft.sqlserver.jdbc.SQLServerXADataSource or oracle.jdbc.xa.client.OracleXADataSource

    Default value

    com.microsoft.sqlserver.jdbc.SQLServerXADataSource

    Takes effect at start/restart

    hibernate.remote.xaDataSourceProperties

    Database URL

    The JDBC URL that Hibernate should use to connect with the database

    Valid values

    A JDBC URL

    Default value

    URL=jdbc:sqlserver://localhost:1433;databaseName=reporting;user=reporting;password=reporting;

    Takes effect at start/restart

    [reporting]

    rs.query.limit.5min

    Maximum configured units of 5-minute period for all reports with 5-minute granularity

    The maximum number of 5-minute periods that are included in any report with granularity of 5-minutes.

    Valid values

    An integer greater than 0

    Default value

    288

    Takes effect immediately

    rs.query.limit.day

    Maximum configured units of day period for all reports with day granularity

    The maximum number of days that are included in any report with granularity of day.

    Valid values

    An integer greater than 0

    Default value

    92

    Takes effect immediately

    rs.query.limit.hour

    Maximum configured units of hour period for all reports with hour granularity

    The maximum number of hours that are included in any report with granularity of hour.

    Valid values

    An integer greater than 0

    Default value

    168

    Takes effect immediately

    rs.query.limit.month

    Maximum configured units of month period for all reports with month granularity

    The maximum number of months that are included in any report with granularity of month.

    Valid values

    An integer greater than 0

    Default value

    36

    Takes effect immediately

    rs.query.limit.week

    Maximum configured units of week period for all reports with week granularity

    The maximum number of weeks that are included in any report with granularity of week.

    Valid values

    An integer greater than 0

    Default value

    53

    Takes effect immediately

    [schedule]

    quartz.rs.calltimeout

    Call Timeout Process

    The CRON schedule that Quartz should use to execute the Call Timeout Process. This process is responsible for timing out RM/MCP/CCP and VAR Call Data Records.

    Valid values

    Refer to http://www.opensymphony.com/quartz/api/org/quartz/CronExpression.html for more detail

    Default value

    0 50 * * * ?

    Takes effect at start/restart

    quartz.rs.dbMaintenancePeriod

    RS DB Maintenance Process

    The CRON schedule that Quartz should use to purge old data according to each application's data retention policy.

    Valid values

    Refer to http://www.opensymphony.com/quartz/api/org/quartz/CronExpression.html for more detail

    Default value

    0 0 1 * * ?

    Takes effect at start/restart

    quartz.var.summarization

    VAR Update Process

    The CRON schedule that Quartz should use to update VAR summary statistics.

    Valid values

    Refer to http://www.opensymphony.com/quartz/api/org/quartz/CronExpression.html for more detail

    Default value

    0 0/5 * * * ?

    Takes effect at start/restart

    [transaction]

    atomikos.log.dir

    Transaction Log Directory

    The full path of the directory Atomikos uses for distributed transaction logs

    Valid values

    A directory path

    Default value

    $InstallationRoot$/logs

    Takes effect at start/restart

    atomikos.working.dir

    Transaction Working Directory

    The full path of the directory Atomikos uses for distributed transaction locks

    Valid values

    A directory path

    Default value

    $InstallationRoot$/data/atomikos

    Takes effect at start/restart