Problem with Auto Attendant

[johnO1234]

We are having a problem with our Auto Attendant/voicemail computer in one of our offices. The voicemail works fine, but our AA dies, rebooting the phone system does not solve the problem and we have to reboot the voicemail computer to get it back up and running. The auto attendant is setup with a scheduler that goes to an asst'd transfer to a small hunt group. Out going calls work from the operator phone but cannot recieve incoming calls. Just get dead air, no phone ringing, no music on hold, just dead air until we reboot the computer. Any ideas would be greatly apreciated?
Thanks,
John

 

[IPhello]

Try this.

What to check On the Voice Mail Pro Server Top ten list
Set the Lan Adapter to 100 Half Duplex Prevents Auto-negation
Turn Off Screen saver OpenGl takes system resources
Turn PC Power Management (Monitor, hard drive, standby, hibernate) Turned off power management
Check for other applications running on VM server NetDect,Virus Protection
Task Manager, check CPU usage (<100) 2 to 4%
Uncheck Allow PC to turn off power to Lan Card to save power Found on Lan adapter tab
Uncheck Windows Automatic Updates System Admin can check Manually
VM Pro installed as a service versus a program Restarts VM Pro in case of Power Reset
Pentium 200 with 128 MB Ram VM Pro Only
Pentium 300 with 256 Mb Ram VM Pro using Campaigns/IMS



What to check On Manager when running Voice Mail Top ten list

License Server set to specific Address Versus 255.255.255.255 Prevents Broadcast
Voice Mail Server set to Specific Address versus 255.255.255.255 Prevents Broadcast
License Server set blank on remote nodes
User and Hunt Group names should be short with no punctuation Prevents application errors
The full name in User form should not have punctuation except for a space between first and last name. This only shows on sets display
If Voice mail is set to forward under user tab make sure that voicemail to email is set up properly. If not set properly you will not get an email or a voice mail.
If you want the message light to light for a hunt group put H and the hunt groups name in the source number tab of the user form (i.e. HMain)
For Callback (Outcalling) to an outside telephone number…if you are using 9 to dial out, make sure to put the 9 before the telephone number. (i.e. P99043333333) this goes in the source number tab for the user who wants their mailbox to outcall.
If you are using analog trunks and the voice mail is having volume issues you can go to the analog tab of the trunk form and change the voicemail volume to high.
To make sure that time is consistent with manager and voicemail when related to time stamping, you can specify a specific time sever for accuracy.
XP Pro edition – Disable Internet Firewall Option Could cause un-explained vmpro service outages.

 

[johnO1234]

Thank you for your response. I am looking into what you suggested andmaking changes where they are needed.
I have noticed when playing around with the machine when this problem is occuring if you stop and restart the voicemail pro service the problem will resolve itself. The service still shows as if it is running but stopping and restarting solves the issue. I have set the service to automatically restart upon failure but i am not sure what is happening registers as a failure (i.e. nothing in event log that shows a problem).
The machine is xp pro, P4, 512 RAM, new machine w/ nothing else on it except manger, monitor, vm pro and antivirus.

 

[sizbut]

?How soon after a restart does it fail - if 2 hours, then its a license issue.

The VMPro will run for that time unlicensed. If that turns out to be the case, check that the License Server IP Address in the IP Office config matches the IP address of the Voicemail Pro PC.

 

[bigjohn8210]

You have Voicemail Pro

How Many Ports unlimited or standard 4 ports this could be your problem..


How many Users on the system

 

[intrigrant]

Recapulate the question/problem:

VM Pro is used
VM Pro will never stops working ( VM Boxes are always there ) so no licensing issue
VM Pro Auto attendant ( = Menu ) stops working
to be more precisely : the assisted transfer stops working

possible resolution:
Do NOT use assisted transfer! solves the problem?
If not try/check these
Check the used names in VM Pro : unique? not longer then 12 chars?

Open the VM Pro service with interaction with desktop and look what the messages tells you.
Enabling the interaction:
Go to services, select the VoicemailPro Service properties, go to the Log On tab and select Allow service to interact with the desktop ( only available if the Log on is a local system account ), restart the service.

 

[johnO1234]

I believe we were able to find the solution to the problem. It appears to have been a licensing issue. we have resolved the issue and the system has been running good since then.
Thanks for all your help.