Voicemail Congestion

[Devolution]

Hi Guys,

I have a IP500 ver 4.2(14) with VMPro ver 4.2 (27). There are 8 ports available for VMPro but every now and then the System Status tool show congestion on these ports and the VM service has to be restarted. The service has to be restarted several times in some cases.

They use the VMpro for a basic AA on the main number and also a conf bridge.
The IT guy onsite monitors the congestion issues and notices the problem can occur if only a few people are accessing their mailboxes.

I have run the debug tool in an attempt to find the issue but I think I'm missing something as nothing stands out at me. The download link for this is:

http://dc35.4shared.com/download/105137585/3ef5b654/VM_log_file_05132009_110000__139_.txt

The customer said they noticed the VM went down at 11.24 and he restarted the service at 11.37.
The VMpc is Win2003ServerSP2 and they have no firewall set.

Has anyone had a similar issue or could suggest a possible fix?

Thanks, stephen.

 

[Westi]

CQ78631

VM locks up when message left for H/G that is then to be broadcast to all members.

4.2.27

this is the only caveat for now on that release so you might want to check if you have that, I looked into the debug file but that is a bit to much for me. Best way to open a ticket with Avaya and see if they can sort thruogh that debut trace.

Joe W.

FHandw., ACS

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

 

[Devolution]

Thanks for your suggestion. They have 5 hunt groups and none of them have the broadcast option set. In fact there is only the reception phone that has access to more than one mailbox. The mailbox is added via the sourcenumbers tab.

 

[ChristianFrench]

Upgrade it Steve, you know you want to.

 

[Chedzz]

I saw this issue once before and it was due to a loop in the VMPro modules. Basically the VM was sending the call through this loop because a VM module had the same name as a hunt group. So when a call came in it was using multiple voicemail channels as it went around the loop

 

[Devolution]

Thanks for your suggeation Chedzz. Unfortunately, there are no conflicts of HuntGroup names & Modules.
Avaya have looked at the logs and have said they need more info. They want a new log from the debug tool and sysmonitor when the fault occurs again.

I got the customer to try to congest the vm ports themselves but the vmpro acted perfectly and no faults occured.

 

[Chedzz]

VMPro!!! It knows when you are watching!!!!!!!!!!!!!!