How to Prepare an Avaya Environment › Enable CDRs and Configure the Collector as a CDR Recipient

Enable CDRs and Configure the Collector as a CDR Recipient

Because most Avaya metrics come from RTCP reports, UC Monitor does not require you to enable Call Detail Records (CDRs). However, RTCP reports do not include the following information:

• The origin of the call.
• The dialed number when a call transverses a gateway.

When you enable CDRs, the UC Monitor collector correlates the CDRs with the RTCP data to determine call direction and the dialed number.

Use the Avaya Communication Manager System Access Terminal (SAT) to enable CDRs and configure the collector as a CDR recipient. For more information, consult the documentation for your version of Avaya Communication Manager.

Follow these steps:

1. Associate the IP address of the collector to a node name.
   1. Run the following command:

      ch node-names ip
      

   2. Enter the appropriate node name:
      • For S8300 servers, the default node name is procr.
      • For S8700 or S8500 servers, the node name is clan1 or clan2.
2. Define the CDR link between Avaya Communication Manager and the collector.
   1. Run the following command:

      ch ip-services
      

   • Complete the following fields:
     • Service Type: Enter CDR1 as the primary CDR link.
     • Local Node: Enter the name of the node that terminates the CDR link on the Avaya Communication Manager: either procr or clan1.
     • Remote Node: Set to the node name you defined with the ch node-names ip command.
     • Remote Port: Must match the port that the collector uses, which is 9000 by default.
     • Reliable Protocol: Set to n to disable the use of the Avaya Reliable Session Protocol for CDR transmission.
3. Set the parameters and the format of the CDR data.
   1. Run the following command:

      h system-parameters cdr
      

   2. Complete the following fields:
      • Primary Output Format: Unformatted.
      • Primary Output Endpoint: CDR1.
        Note: If the collector is the second of two CDR recipients, set the Secondary Output Format field to unformatted. Set the Secondary Output Endpoint field to CDR2.
      • Use Legacy CDR Formats: Set to y to support 3.x systems.
      • Intra-switch CDR: Set to y to enable call records for internal calls involving specific stations.
      • Record Outgoing Calls Only: Set to n to enable incoming and outgoing trunk calls to appear in the CDRs.
      • Outg Trk Call Splitting: Set to y to enable a separate call record for any portion of an outgoing call that is transferred or conferenced.
      • Suppress CDR for Ineffective Call Attempts: Set to n to prevent blocked calls from appearing in CDRs.
      • Inc Trk Call Splitting: Set to y to enable a separate call record for any portion of an incoming call that is transferred or conferenced.
        Note: The default values are acceptable for all other fields.
4. Define the extensions for CDR collection.
   1. Run the following command:

      ch intra-switch-cdr
      

   2. Complete the Assigned Members field. Enter specific extensions whose usage is tracked with a CDR. Add an entry for each extension you want to track.
      Note: Avaya provides a utility to help you perform large-scale configuration changes for multiple extensions. Contact your Avaya account representative and request a license for the Intra-Switch CDR by COS feature.
5. Verify that CDR reporting is enabled for the trunk groups whose CDRs you want to monitor.
   1. Run the following command, where n is the trunk group number:

      ch trunk-group n 
      

   2. Complete the CDR Reports field. Set to y. This setting applies to all trunk group types.