Voicemail Pro on Server 2008 losing connectivity 5

[Inder38]

IP Office 7.0.31 with VM Pro 8.0.1009 on Server2008 R2 SP1.

The IP office System Status application when looking at the Voicemail Status screen shows Voicemail Type: NONE with Total Number of Voicemail Ports = 4 and Total Number of Voicemail Ports in use = 0.When this situation happens the Auto Attendant obviously will fail back to the secondary destination.

Server is a dual core CPU desktop PC with 4 GB of RAM. Firewall is disabled and there is no antivirus software installed on it. The two boxes are connected through brand new Linksys (Cisco) router switch ports.

A manual restart of the Voicemail Pro Service in the Windows Services MMC will reconnect the two boxes. As a temporary fix, I've written a batch file to restart the service and a Scheduled Task to run it every hour.

I've tried every fix I could find on this site, as well as others but none have fixed this particular problem. Any suggestions anyone would have regarding this would be appreciated.

Thanks
Craig

 

[amriddle01]

Sounds like a missing or invalid licence, what does licences say

 

[amriddle01]

Also, VM and system need to be on the same release, you can't mix and match

 

[Inder38]

License is valid. Avaya tech support wasnt concerned about the version mix.

 

[NYSTECH]

you can be 1 version differnt between IPO and VM.. but, not recommended

 

[tlpeter]

No you cannot be one version off.
Only SCN can be one version off.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Telecomboy]

Downgrade your vmpro to match your IPO, Avaya may not have been concerned with that, but they also appear to not have fixed your issue.

 

[amriddle01]

Avaya talk a lot of Bollo**s sometimes, I have reported issues heard nothing back but found the problem/fix myself then they asked me what it was becuase they didn't have a clue. They also give conflicting advice depending on who you talk to

 

[Inder38]

Ok, I am sold on the idea to downgrade my Voicemail Pro. Is there an easy way to do this and keep my Auto Attendant and mailboxes? Or do I need to uninstall the current version from my server and rebuild everything from scratch?

 

[hairlessupportmonkey]

just make sure you back up the call flows and copy off the greetings, accounts and any custom wavs you have, and try a downgrade by running the installer, other wise simply uninstall, restore the folders, files and call flow.

ACSS - SME
General Geek

 

[Inder38]

Ok the IPO is now running 7.0.31 and VM Pro is at 7.0.32

For future reference, it installed the 7.0.32 alongside the 8.0.1009. Then I just went into add/remove programs and removed 8.0.1009. Auto attendant and mailboxes remained intact. I've disabled my hourly restart service task and will monitor for a few hours to see if the problem is resolved. Stars all around for the responders!

Thanks again

 

[Inder38]

Another update:

After all troubleshooting checks and release matching, I still have the original problem. After about two hours the IP Office box lost track of the VM Pro server. In the SSA application I saw Voicemail Type: none with no ports in use. I dialed into the system and the auto attendant failed back to the secondary destination.

The only thing that I can see in manager that may still cause this is that after downgrading the VM Pro to 7.0.32 my license is showing ??? but the status is still valid. I deleted and re-added the license but it is still showing ???. Any thoughts?

 

[tlpeter]

What does monitor show when it stops working?
Do you have a trace when it happens?


BAZINGA!

I'm not insane, my mother had me tested!

 

[Inder38]

To be honest, this is a Nursing Home medical facility. So when they call I am more interested in getting them back up and running. It is happening ramdonly every two or three hours so I really can't sit and wait for it. Right now I have a scheduled task to restart the Voicemail Pro Service in Windows to keep it up and alive.

 

[tlpeter]

So you do not want to solve the problem but just restart the service once in a while.
When somebody is in the VMPro script and gets kicked out because of the restart is worse.

It is only a couple of hours and a one time trace.

So set up a trace and let VMPro stop working and then start your script again.
There must be something wrong.


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

Was the system originally on R8? If so you probaqbly have a R8 VM Pro/Preferred licence, it will not be valid in R7 and so the system will treat is as unlicenced and shut it down every 2 hours

 

[tlpeter]

I am thinking the same Andy.
The original post is about ipo on 7.0 but vmpro on 8.0
That is why i want to see a trace, it will show this.


BAZINGA!

I'm not insane, my mother had me tested!

 

[FocusTechnology]

Just off the wall but try bypassing the Cisco with another switch temporarily.
I know it sounds weird but i have had major problems in the past with Cisco kit and reliable connectivity as they sometimes try and be too intelligent.
The issue in my case was the new Cisco router had something called ARP Proxy enabled and connectivity across the board between PC's, Servers, Phones and the IPO was erratic.

 

[SoGaIPO]

I'm thinking the same as tlpeter, instead of "downgrading" the VMPro, why not "upgrade" the IPO?
R8 license for VM should stay R8. Upgrade IPO to R8.

 

[Telecomboy]

Also, a little on the basic side, but check your power settings on the vmpro pc to make sure the network port ins't set to hibernate after 2 hours or the pc itself hibernates.