Avaya CDR info when there is another CDR device

Hi, I am trying to get VNQM set up on our Avaya s8800 and can not get CDR/CQR info from the call manager. We already have CDR1 customized format configured for our reporting servers and I can't change that config. It doesn't look like there is any other way to output CDR info (i.e. both CDR1 and CDR2 use the same format). Has anyone run into this and if so how did you get around it?

The only info we are getting from the CM is a registered/unregistered extension count and IP info on the registered extensions.

Thanks in advance.

Find more posts tagged with

cdr

avaya

vnqm

format

Accepted answers

vjey

Could you please check if your CDR is customized as per the below link ?

http://knowledgebase.solarwinds.com/kb/questions/5780/How+to+configure+an+Avaya+Call+Manager+for+VoIP+and+Network+Quality+Manager

Also, please check if your Avaya setup is a load balancer.

All comments

vjey

Could you please check if your CDR is customized as per the below link ?

http://knowledgebase.solarwinds.com/kb/questions/5780/How+to+configure+an+Avaya+Call+Manager+for+VoIP+and+Network+Quality+Manager

Also, please check if your Avaya setup is a load balancer.

FormerMember

Unfortunately, we can't change the data items list because of pre-existing CDR reporting. We will be putting VNQM in production shortly and will change the data items to match what it requires (and replace the existing CDR reporting), so hopefully that will resolve it. Thanks.

phoneman7

Do you have 2 instances already programmed? If so then your out of luck, correct, if only one is, then you can do a second.

humejo

You seem to be in the know about the load balancer. I have a client who has a High Availability setup with their Avaya Call Managers. We can see the CDR records coming in from the procr's VIP, but we are monitoring the two physical Call Manger servers in VNQM. Solarwinds solution is to simply add the VIP of the Procr in as a VNQM node... Well, unless their is some config on the Call Manager I am not aware of, the Avaya procr model doesn't just forward any old traffic from the VIP address to the current primary physical Call Manager server (like SNMP traffic on port 161 for instance), so SNMP tests in Orion fail when trying to add the procr as a SNMP node. And since VNQM does not allow you to add a node as a Call Manager node unless SNMP is working, we have no way to do this. We also tried setting the Call Manager to send the CDR data from the Physical server's IP address instead of the procr's VIP, but were unable to do this as well. Are we missing something completely obvious, or are we just out of luck?

Thanks,

Jordan