CDR file Download failing on VNQM

Hi Everybody,

I have recently added 8 Call Managers in my recently installed Solarwinds Voip Module. Following is the snapshot of the recent voip events.

It seems some CDR file downloads are failing. In this case the FTP server is located on the Solarwinds Server itself.

Does some one has any idea of what could be going wrong here?

Thanks in Advance

Mian Ahmad

Find more posts tagged with

cdr

voip_poll

voip_call_management

ftp_server

Accepted answers

All comments

damienball

Hey there. That 10.48.68.158 is going to be some external FTP server from your call manager. It could be Solarwinds itself, or it could be any one. To do CAR downloads, you setup an FTP location so that call manager has a place to dump files. Then VQNM logs into that place via FTP and downloads the files. There's some issue downloading files from this FTP server. Do you manage it or does someone else in your group? I'd ask them to look at the FTP logs and see if there is any issue.

silverbacksays

I'm also seeing this exact same behaviour in my lab environment. The FTP username and password have been checked as good using a FTP client. The user's working directory is the root of where the CDR files are dumped by the Cisco 2811 Call Manager, so I know that downloading the file isn't the issue. The problem appears to be in PROCESSING the file (as per the error message).

My user settings are:

We're using verion 8.5 of CUCM and the most recent version of VNQM.

jvanderbeken

We have the problem on our 2 production Call Managers with System version: 8.5.1.11900-21

Our lab Call Manager is working fine, System version: 8.5.1.14068-1

I opend a ticket and it seems there is a bug in the software of the older version :

Answer of Solarwinds

I can confirm that the response from this CUCM is not coming back in a timely fashion. 2016-07-04 15:55:51,966 [STP SmartThreadPool Thread #1] ERROR SolarWinds.Orion.Pollers.Framework.PollerBase - CCM phone data table polling error: {0} SolarWinds.Orion.Pollers.Framework.SNMP.SnmpSubTreeResponseException: Error 31040 - Timeout This may be related to the Cisco Bug I referred to earlier. I recommend that you contact Cisco to see if there is a fix for this bug. It may require a firmware upgrade. The only workarounds available from our side are: Increase the polling interval for CCM polling (typically 2,6,12,24 hours based on need) Reboot the CUCM or at least restart the SNMP service on the CUCM

Our production Call Manager will be upgraded soon.

silverbacksays

Thanks for sharing that, jvanderbeken! I'll check with our voice guys, see if they're running that potentially buggy version

ahmed.soliman

guys, anyone had a resolution on these issues ? I am facing the same issue noadays !