UC110 11.1 issues with connecting inbound calls to Voicemail Pro 1

[1ntegrationman]

I have a customer that was upgraded about a month ago and moved to 11.1. Installed a UC110v1 from scratch and all was happy for about 3 weeks, then the system quit answering calls. The Voicemail Pro services are running. And if I connect via Voicemail Pro Client, look at a Module built for Auto Attendant, I can click the saved recorded announcement and play it on a system phone.

The only problem I can identify is through the Web Interface to the UC Module on port 7071. The VOICEMAIL logs are presenting a couple of messages that may be an indication of the trouble so I thought I would bring them to this community and see if anyone has seen this and found a fix. Here are the messages that are getting presented;

Voicemail 16/01 14:21:13.503 vmpro (00,?) 11c4,b65747c0,04548: > UpdateNetworkSettings(change = true)
Voicemail 16/01 14:21:13.505 vmpro (00,?) 11c4,b65747c0,04548: Unable to determine current /proc/sys/net/core/rmem_max value - error 13 (Permission denied)
Voicemail 16/01 14:21:13.505 vmpro (00,?) 11c4,b65747c0,04548: < UpdateNetworkSettings(change = true)
Voicemail 16/01 14:21:13.506 vmpro (00,?) 11c4,b65747c0,04548: > UpdateNetworkSettings(change = false)
Voicemail 16/01 14:21:13.506 vmpro (00,?) 11c4,b65747c0,04548: Unable to determine current /proc/sys/net/core/rmem_max value - error 13 (Permission denied)
Voicemail 16/01 14:21:13.507 vmpro (00,?) 11c4,b65747c0,04548: < UpdateNetworkSettings(change = false)
Voicemail 16/01 14:24:21.162 vmpro (00,?) 5dab,b65c57c0,23979: > UpdateNetworkSettings(change = true)
Voicemail 16/01 14:24:21.166 vmpro (00,?) 5dab,b65c57c0,23979: Unable to determine current /proc/sys/net/core/rmem_max value - error 13 (Permission denied)
Voicemail 16/01 14:24:21.167 vmpro (00,?) 5dab,b65c57c0,23979: < UpdateNetworkSettings(change = true)
Voicemail 16/01 14:24:21.167 vmpro (00,?) 5dab,b65c57c0,23979: > UpdateNetworkSettings(change = false)
Voicemail 16/01 14:24:21.168 vmpro (00,?) 5dab,b65c57c0,23979: Unable to determine current /proc/sys/net/core/rmem_max value - error 13 (Permission denied)

I've done some searches on these messages and it looks like they are Linux issues that I don't understand.

I've done a Full backup through Voicemail Pro Client, and moved a copy off of that UC Module using WinSCP, plus a fresh export of call flows and the configuration, so if I load the software fresh I think I will be able to do perform a fresh install of the ISO via USB, ignite then restore from backup, but that requires me to be on site which is difficult.

Any ideas?

 

[CarGoSki]

Could be corruption of a file.
When looking at the dbgtrail file in verbose do you see standard traces including housekeeping and call flows? There is an entry point for calls and callers that define the session number and other call information.
Do you see the sixty second updates that are between a row of equal signs:
======================================================================

======================================================================
In SSA is the drive full when when viewed?

I usually find that when VMPro shows active but calls are not answered then the security password for vmail has been changed or corrupted.

 

[cdiris]

Tech Bulletin 215 came out today with version 11.1.2 and lists multiple vmpro fixes
IPOFFICE-160844 VMPRO system crash
IPOFFICE-161304 Voicemail Pro version is stopping and is not recording calls
IPOFFICE-160337 Frequent VMPro crashes
I understand services are still running in your case. However might be worth looking into.

 

[1ntegrationman]

Thanks CarGoSki. I still don't know what it is. And the drive is not full... running with 65% storage available. One thing I noticed once I got on site today was that the linux home screen had an error stating that Eth0 did not have an ip address assigned to it. Though it showed up in the Web interfaces thought ports 7070 & 7071. I don't know Linux so I tried (unsuccessfully)to load another C110 with 11.1

Ultimately ended up loading App Server on a PC, and it came up. But then none of the passwords that I had just set on the App Server worked. So I reset security settings on the IP Office, and after about 15 minutes the systems started talking to each other.

But now none of my passwords work for getting into either system.

It was a tough day in the field.

I'll go back tomorrow with my USB- Serial adapter and reset security settings again and see if I can get it to work.

And thanks cdiris. If resetting the security settings doesn't work, I'll upgrade to 11.1.2

 

[critchey]

Most techs hate the UC modules... especially the V1. They had high failure rates and seemed to essentially do whatever they wanted to do (in my experience). I have heard V2s are a lot better nowadays, so if possible maybe upgrade to a V2, but honestly you are much better off with an application server.

The truth is just an excuse for lack of imagination.

 

[John563]

Those particular errors you are seeing are probably a permissions issue caused by vmpro running as the "vmpro" user, not root. SOLN355908. As a temporary fix, you can login to root and run service vmpro restart. I don't think this workaround would help your actual problem though. The article only indicates that it causes issues with SMTP.