Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > Avaya Missing CDR/Call Records

Avaya Missing CDR/Call Records

Table of contents

Updated October 18, 2018

Overview

Investigate missing Call Records (CDR) for an Avaya Call Manager

Environment

  • VNQM 4.2 +

Detail

If call quality data is missing please use this article: Missing call metrics from Avaya based calls

 

  1. Verify the Avaya Call Manager is setup per the guide below. 
  2. Verify the Solarwinds Server is open on TCP port 50000 and no other applications are bound to that port.
  3. Use Wireshark to look for traffic from the Avaya Call Manager on TCP port 50000.
  4. If there are records coming in then look in the IPSLABusinessLayer.logs for errors/issues.
    • You can search this for RTCP to see calls matching up or not.
  5. If you find RTCP data without errors check the IP of the data in the text to the VOIPCCMPhones table.
  6. Then see if you can find Call data for that phone in the VOIPCDR or VOIPCDRdetails tables.

 

An important thing to note regarding the CDR data from Avaya in regards to VNQM: VNQM tracks the calls based off the phone ID, not the agent ID. Any calls that are tracked via this method will not be understood by VNQM and are dropped. This is by design and we recommend to contact SolarWinds Support to submit a Feature Request if you would possibly like to see it tracked by agent ID as well.

Last modified

Tags

Classifications

Public