VM service running but no VM

[yeehaababy]

What would cause the service to show that it is running but when trying to access any VM features nothing there.like when its turned off.

 

[JeSTeROCK]

Maybe a firewall

Is the license valid ?

 

[IPhello]

what os are you using on the vm pro machine? I have found that I have to add ports 50791 and 50793 if it is on windows xp with service pack 2. Seems to clear up the problem.

 

[JeSTeROCK]

http://support.avaya.com/elmodocs2/ip_office/emea/emea_techtip_049_Windows_XP_service_pack_2.pdf

on the last page of this tech tip there is picture of a paper clip, right click on this and save.

This batch file will open the necessary ports for ipo applications you have installed on your pc with the windows firewall

 

[yeehaababy]

Its runing ona server, 2000 not xp

 

[bwilch]

Are you running a corporate anti-virus/firewall combo on the server?

Does the license show valid in manager?

 

[intrigrant]

If you get "Busy" in your display then it is a connection problem, if you get "dead air" then it is a license problem.
Both can be checked using sysMonitor with the option "Development tracing" enabled.
You will have a menu option called "Status", there you can find an opsion called "Voicemail sessions".
it will open a new window were you can see if IP Office recognises your VM engine and you can see if the licenses are there.
Both problems can have a number of reasons for failure, you should check at least your hardware ( NIC half-duplex etc. ) and software ( firewall etc. ) and manager settings ( IP Address VM Server etc. )
Because the great number of possible reasons for not working this is as far as i can help you.

 

[sizbut]

1) Has the server created folders for the mailbox accounts, greetings, etc? a good clue that the VMPro and switch are talking.

2) Look in the VMPro help file for details of running the server as a console. Monitor will let you see what the IP Office is doing, console mode will let you see what the VMPro is doing.

3) Make seem checky, but run the VMPro GUI and save/make live. It shouldn't be necessary but I've seen it spark systems into life.

?What control unit type ?What kit between it and the PC runnong VMPro. ?What licenses and their status.

 

[deltaserver403]

I have exactly the same problem, it gives me "Busy" in the display, i checked the NIC it auto neg 10/100, all windows XP firewall has been removed.

I can ping the IPO from the VM Pro PC, evne in the monitor application it shows the License.

In IPO licensed is valid.

still i am unable to debug the problem, i fell i am missing something,

 

[JeSTeROCK]

Go back to the start.

Is the IPO and the voicemail server on the same lan subnet?

Is the voicemail set to pc and the correct ip address or broadcast (set to ip address to be sure) and no passwords set?

Has the voicemail pro & vm pro db service started up correctly?

In voicemail pro can you add a group or user and select from the list ?

I would be trying to installing it on another pc if all this has failed

 

[Francis999]

Change the voicemail pro service to Local System and check the "Allow interact with desktop" box. Then restart the service and click RUN in the window that appear. The first few lines to appear will tell you if vmpro see the license correcly from the phone system.

That will give you a console window in wich you can see whats going on inside voicemail pro.

an alternative to that is looking directly at the voicemail pro log file located in C:\DBGOut.txt but the other way is much easier to understand.

 

[joeOctel]

Did you check to make sure the voicemail password in Manager matches the VMPro?

 

[Stramec]

Hi, I have exactly the same problem, IPO 406 V3/ VMPro V3(13)everything looks like it is running but I get silence when going to VM. Also I get a message saying VM Server is down when going into the wizard.

I have checked via manager, wizard and sysmonitor that my license was valid. I have also followed the above pdf, which seemed to resolve one issue where VMPro Client wouldn't go into preferences due to a COM error.

Delta is seeing the switch (VM & Delta run on the same XP machine)

Now the bad part, this all stopped working after having to do a reboot for a Norton LiveUpdate. From what everyone is saying I am convinced this has knackered something. So I threw caution to the wind and uninstalled Norton Security, disabled windows firewall ....and still no joy.

I noticed the following from the sys output when I try and do a reboot.

VMAIL - Down Server 0a860166
108713mS PRN: TFTPServer::RRQ(from 10.134.1.102) deltaconfig/vmail/BDF=
108714mS PRN: FilesysReader for deltaconfig/vmail/BDF=
108719mS PRN: Could not open file:deltaconfig/vmail/BDF=


The VM Server is saying:

23:20:48.031 - BulkInfoRequest 10.134.1.101 3
23:20:48.031 - PBX Requesting ALaw companding
23:20:48.031 - Initialize Sequencer tx_seq=0, rx_seq=1
23:20:48.031 - TFTPLoadFile 10.134.1.101
23:20:48.031 - 0 mailboxes were open (but not active) when flushed
23:20:48.031 - DevIO::StartTask 10.134.1.101
23:20:48.062 - DevIO:rocessReceiveBuffer 10.134.1.101
23:20:51.921 - DevIO::RxAbort 10.134.1.101
23:20:51.921 - DevIO:etach 10.134.1.101
23:20:51.937 - DevIO:etach 10.134.1.101
23:21:18.093 - BulkInfoRequest 10.134.1.101 3
23:21:18.093 - PBX Requesting ALaw companding
23:21:18.093 - Initialize Sequencer tx_seq=0, rx_seq=1
23:21:18.093 - TFTPLoadFile 10.134.1.101
23:21:18.093 - 0 mailboxes were open (but not active) when flushed
23:21:18.093 - DevIO::StartTask 10.134.1.101
23:21:18.125 - DevIO:rocessReceiveBuffer 10.134.1.101
23:21:21.984 - DevIO::RxAbort 10.134.1.101
23:21:21.984 - DevIO:etach 10.134.1.101
23:21:22.000 - DevIO:etach 10.134.1.101

Please guys, any ideas??

Thanks

 

[IPGuru]

General VM Debuging advice

Engaged tone = No VM running or network error (disconnected firewall etc.)

Silence = VM Pro Licence invalid

 

[Stramec]

Well no idea what caused it, but I ended up doing a back up of VM and reinstalling the software.

Restart of teh IP office and a quick restore and it all came back up, copied over teh backed up wav files and all was back to normal.

Not exactly a nice work around, but was at leats reasonably quick.