This article describes when Avaya call metrics are not being gathered from VNQM, but it is configured on the Avaya interface to export. Avaya's call data contains call metrics just as Cisco's call manager does, just in a different manner. For Avaya, the data is presented as RTCP data, which is the equivalent to CMR data from Cisco. Data collection is the same as the CDR data for Avaya (gathered off listening on UDP port 5005). VNQM will accept the data if the sender's IP address is recognized as an IP address from an Avaya phone from VoipCcmPhones table or an Avaya based gateway from VoipCcmGateways table. These are gathered from the CLI polling conducted on the Avaya call manager directly to obtain this information.
Messages pertaining to when the data is collected and when the data is skipped is shown in the IPSLA Businesslayer logs:
The following are two examples of collecting RTCP data:
2015-12-09 14:42:24,717  DEBUG BusinessLayer.RtcpServer (null) - RR 396965863 (10.38.133.102) processed. Phone: 27626 (ID: 760). Details: [ DataSourceSSRC = 1106452945, AT = 09/12/2015 08:42:24 p.m., LsrAT = 09/12/2015 08:42:22 p.m., Jitter = 10, PacketsLost = 0, PacketsSent = 918, DLSR = 162616 (2481 ms) ]
2015-12-09 14:42:24,717  DEBUG BusinessLayer.RtcpServer (null) - RR 85064679 (10.64.7.12) processed. Gateway Id: 34. Details: [ DataSourceSSRC = 577467730, AT = 09/12/2015 08:42:24 p.m., LsrAT = 09/12/2015 08:42:22 p.m., Jitter = 4, PacketsLost = 0, PacketsSent = 8889, DLSR = 146407 (2233 ms) ]
The following are examples of dropping RTCP data:
Note: Neither of these IPs can be tracked to the VoipCcmGateways or VoipCcmPhones tables:
2015-12-09 14:42:24,748  DEBUG BusinessLayer.RtcpServer (null) - RR 805826337 (10.32.9.22) skipped.
2015-12-09 14:42:24,764  DEBUG BusinessLayer.RtcpServer (null) - RR 197473833 (10.67.8.81) skipped.
The cause of the missing data may be any of the following issues: