Issues with Avaya CDR after Solarwinds Upgrade

Question

Hi All,

I have had a ticket logged with helpdesk for months, but Dev are not able to resolve issue.

CDR has stopped working, (was working great before, but upgraded Solarwinds) and will only function if the CDR ip-service primary reliable protocol is toggled in Avaya CM

This action will result in CDR date being processed for 9 hours, then it stops

On testing the cdr in both SolarWinds and Avaya, both pass successfully.

Have done test, logs and traces with solarwinds support and dev but no closer

No windows firewall running on Orion, dot net 4.6.2 has been installed.

Any body had similar issues?

CM 6.3 S88xx HA

Cheers

Patrick

wattersp · Answer

Well worked for a while, but stopped after 5 days 100 pages of CDR logs.

wattersp · Answer

**All Resolved**

Hi All,

When I was looking at the ipslam logs with Solarwinds Dev last week, I saw that two ip address were being pinged. From the logs it looked like the active server was trying to open a port, while the backup was working ok.

I then disabled the CDR option on the backup server, and the CDR started to flow through on the active CM.

We have a CM HA environment and previous to the upgrade both the main CM and the ESS server had CDR enabled.

So if you have the same setup, you will need to disable the CDR on the non active CM.

Cheers

Patrick

ding · Answer

I will check on this for you!  Stay tuned.....