Voicemail Pro unavailable

[Chedzz]

Hi all,

I've got a 406 V2 running 4.2.14 with the latest VMPro release running on a Windows 2003 machine. Upgraded about 3 weeks ago. Since yesterday Voicemail is unavailable. A reboot sorts it but it then happens again shortly afterwards. Nothing has changed on the network. System Status reports that port allocation fails. Any advice?

Thanks

Chedz

 

[Westi]

are your licenses still valid, if not then you might need to reboot the IPO if the keyserver was unavailable for a longer period of time.

Joe W.

FHandw., ACS

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

 

[amriddle01]

Did you also upgrade the feature key server? As sometimes when you upgrade the key server get's messed up and so your licences go invalid, is this the case?

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[Chedzz]

No, Key server was upgraded and all Voicemail Pro licenses (6 Ports)show valid. Monitor picks up the Valid Voicemail during it's initial search/check.

 

[Westi]

Do you get a busy signal when you call the voicemail or just silence.
There was in earlier releases something that the service needed to get restarted to make hte voicmeail answer again and unchecking the time update over the internet on the server solved that.

Joe W.

FHandw., ACS

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

 

[Chedzz]

They actually just get ring tone and no reply?????? We've stopped and restarted the voicemail service but no change. Yesterday we even rebooted the voicemail server but again there was no change. Only a reboot of the IPO did the trick

 

[Westi]

ringing means it thinks that it gets the calls through, try a different port on the IPO switch, also make sure there is no other device hogging the IP address of the voicemail or the IP Office (I guess that is more important even)

Joe W.

FHandw., ACS

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

 

[amriddle01]

I seem to remember that about a year ago on here someone had a similiar issue and as odd as it sounds he had to get the licences changed, as Avaya tracked it down to that causing the issue. Don't take that as gospel though

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[Chedzz]

Well there is no IP conflict. Rebooted the IPO on Friday night. Voicemail ran continuously right through the weekend (made about 20 test calls at various intervals). Then sure enough, this morning, when the client got up to the usual call volumes at about 10ish, voicemail became unreachable again, reporting congestion on all ports.

Various traces have gone off to Avaya as distributor tech support hasn't got a clue.

Will let you know the outcome.

Thanks everyone for your contributions.

 

[tlpeter]

If it worked in the weekend and stopped today i also think it is an ipconflict

someone turnes on it's pc and there you go

pull the patchcable form the vmpro server and ping the address and see what happens

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

 

[CarGoSki]

If there is an IP conflict on the windoze box then you would see it in the event logs. If it is a IP conflict on the IPO lan port then net services on IPO would stall and you can not ping the port. It would then take a reboot or power cycle of IPO to restore net services.

 

[Westi]

I would think it is probably the IPO that has a duplicate IP address as the server would complain and tell you in the task bar that somebody has the same IP address but try either one.
ping the ip office and see the mac address of it starts with the usual Avaya mac scheme 00-e0-

Joe W.

FHandw., ACS

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