Voicemail Not Picking Up

[h382]

406v2 on 4.1.95011 (patched last week to try and resolve issue)
VM Server on 4.1.27


Older site I had upgraded to a new 406v2(403 previously)

They have Voicemail Pro running on XP, that I recently changed over to 2K3 to try and fix this issue.

The issue is simple, after so long, could be 20 minutes, could be 1 day, the voicemail service is still started, but won't pickup. Callers will hear busy/dead-air.

This wasn't an issue until we upgraded them from a 403 and 3.0 to a 406v2 and 4.1

To fix the issue, I have to restart the Voicemail Pro Service. The licenses show valid. I have an incoming call route pointed to Voicemail to test, and when they are experiencing this issue, the call doesn't even show up in System Status.

Any ideas?

 

[h382]

Well.. 2 weeks after upgrading to 4.1.40, this happened AGAIN. I thought I was past this, now it seems the fight is not over. Worked great for 2 weeks to the day.. *sigh*

 

[jreingold]

Hmmm...

I had this happening to two (2) accounts. One as often as 1 to 5 times per day. On both those accounts, we implemented the workaround to disable time sync on the IP Office in Manager, setting TIME server to 0.0.0.1, as well as turning off time sync in Windows on the VM Pro PC.

The problem hasn't recurred in 3 weeks, and we've been gun shy to apply the upgrade - the customer went through enough pain long enough, and I wanted to leave well-enough alone.

However, we did withing the last 7-10 days install a new system running 4.1.40, as well as upgrade a 3.2 install to 4.1.40, both without the time-sync work-around, and knock wood - so far so good...

Any chance your problem today was something else?

Do you have time sync enabled, or disabled?

-Jeff

 

[h382]

This VM Pro 2k3 server doesn't have an option for time sync. The last server did before it got replaced via the end of the lease(it was XP). All of our servers get their time from the Domain Controllers, and from what a previous poster mentioned the reason for not having the tab is because it is part of a domain..

I did however just change the time server on the IPO to 0.0.0.1

I guess I'll have to wait and see now if this continues to happen. I have put in a couple sites since this one, and it has not been a problem either.

 

[Westi]

sorry to hear that your site is still acting up, mine are both fine after disabling of the time server, I didn't even do the 0.0.0.1 option in the phone system, just the Vm pro computer. One of them I upgraded to 4.1.40 because they had other issues and it is still fine the other one is still on the old version. So far all good here.

Joe W.

FHandw., ACA, ACS

If you can't be good, be good at it!

 

[TheOldMan346]

Hi guys,

Did you ever get a resolution to this from Avaya? I have VM Pro running 4.1.27 and am experiencing the same issue. I installed 4.1.40 initially and did not have this problem but had to roll back to .27 because of a bug with personal greetings. I disabled the time server in the IP Office last night and it happened again today. The customer's 2K3 server is part of a domain and unfortunately they have domain configuration issues (not part of our relationship) as far as time synchronization goes. There are no network connectivity or IP addressing issues. The stalls are happening at least once a day sometimes 2 and 3 times a day. I created a command file to reset the service and scheduled it to run at 7 AM and 9 PM which has helped somewhat but does not help if it stalls during the day.

I've got a ticket open with an associated BP to determine if the 4.2 version resolves both issues but have not heard anything back. Any insights would be greatly appreciated.

What goes around - comes around.
The Old Man

 

[tlpeter]

4.1.40 is already replaced with 4.1.42 for the personal greeting problems
That problem is solved and you can go to 4.1.15 with 4.1.42 or 4.2

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[h382]

I set the Time Server on the IP Office to the sites Router, and we haven't had the issue since. It happened every week from January-March, and hasn't happened since.

 

[TheOldMan346]

Excellent guys. Thanks very much.

What goes around - comes around.
The Old Man

 

[ZebrAYA]

definitive solution for the buggy congestion count on vmpro
two things boys:
the thing was caused by the 4.0 (14) 4,1 or possibly later releases
I have vm pro 3.2 (28) and not planning to update it by now (because of the bugs on the multi language greetings)

1 ) the problem could be corrected with a new release or hot fix regardless of the vmpro version or the vmpro gotta be updated at all.
2 ) Is there trouble if uploading the hotfix to a private website to get a little easier without going by L2, L3 and L4?


[Always Close your threads for avoiding other people to entangle]