Voicemail Pro transfer action breaks?

[qtelcom]

I have now seen this on 2 systems. One on R10.1 and one on R11FPSP1, these are voicemail pro on windows Intuity mode. Any transfer (assisted or blind) action in any call flow will just present dead air and the call is still connected. It’s just the transfer actions from voicemail pro to an extn, group extn, a short code, anything. Users can still check and leave messages. Auto attendants still all work (except any transfer action).

System status shows the call still in the same call flow.

A restart of the voicemail pro service fixes it and then the problem will come back within a day or a week.

Anyone have any ideas what would cause it to fail?

(Ip500v2s with vmpro on windows.)

One OS on windows was server 2012 and the other is windows 7 pro.

Firewall is disabled on both and no 3rd party antivirus or firewall.

 

[qtelcom]

anyone seen this behavior?

 

[joe2938]

Are these sites connected via an SCN?

 

[qtelcom]

No, single site and we just replaced the voicemail server with a brand new one. Ran fine for 1 month and the problem is back again. Appears to happen weekly. All voicemail pro functions work fine except for the transfer actions, the call stays in the call flow and never transfers.

 

[Nutritional_Info]

Do the machines need to print?

If so, start printing from another machine and disable printerspooler in services.
If not, disable printerspooler in services.

The windows service utilizes a port (i dont recall which one) that voicemail pro also utilizes. Sometimes you'll find them fighting over the port and both services result in weird behavior.

 

[qtelcom]

Never heard of printer spoooler service causing an issue. It doesn’t need to print so I can try that.

 

[Nutritional_Info]

Give it a shot. Leave it disabled at start-up, then restart VM services and monitor as you have been.