VM Pro/Lite fails to connect to the Control Unit PC IP Address

[Sujeeshg]

DEAR ALL,

i have a problem with ip office 500v2 running 8.1.69 and vm pro server running 8.1.9203.ip office(192.168.42.1) not connecting to vm pro server(192.168.42.2).From vm pro sever i can ping to ip office and vm service starts without any issue.no firewalls and antivirus on vm pro.

When i checked system staus i can see a service alarm "VM Pro/Lite fails to connect to the Control Unit PC IP Address: 192.168.42.2".i connected ip office,one ip phone and vm pro server on a seperate switch and tested the same,but still the same.All the licenses are showing valid.

can anyone help me with this issue.

 

[IPGuru]

Do you have the essential & preferred edition licenses?

if so then it is a simple 2 step process

Step 1, check network settings, connections firewall & antivirus

Step 2, Repeat step 1.

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[hairlessupportmonkey]

please download and run Debug View and advise the result.

Are you running VM Pro on a Domain controller or Small Business server?

ACSS - SME
General Geek

 

[Westi]

make sure that your firewall service is not disabled as that will block pretty much everything on your machine.

What OS are you running the VmPro on?

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”

 

[Gupz]

Install VM pro on your laptop connect to system - see if this works then you can at least narrow down it is the server with the issue.

If it can ping it then it's a port issue....

99% of the time in my experience it is going to be a firewall / anti virus / spyware issue.

deactivate them all then try again.

I know your saying its not but triple check again

Avaya, Alcatel, Panasonic, 3com NBX, Swyx, 3cx
----------
Avaya ACIS SME
Alcatel ACFE

Jack of all, Master of none!

 

[Sujeeshg]

Thanks for all the responds..

I have IPO essential license and Preferred VM pro license.I have tested in my laptop and two more another desktops with Windows 7 OS.I h stopped firewall,windows defender services. It was an upgrdade from 500 (version 5) to 500V2(8.1) and we replaced old license dongle after getting duplicate licenses for the new SD card.Everything on the license tab showing "valid" only.

VM pro server is not in domain and we don't have any domain infrastructure.

When i dialed *17 from an IP phone and did a trace on system status i can see the following things.There i noticed "Disconnect from Destination End "

Trace Output - All Buttons:
02/09/13 19:13:03-994ms Extension = 605, State = Busy Wrap Up
02/09/13 19:13:03-996ms Extension = 605, Button = 2, Idle
02/09/13 19:13:05-194ms Extension = 777, Digit dialed, Digit = *
02/09/13 19:13:05-214ms Call Ref = 118, Originator State = Dialling, Type = User, Destination Type = none
02/09/13 19:13:06-275ms Extension = 777, Digit dialed, Digit = 1
02/09/13 19:13:07-065ms Extension = 777, Digit dialed, Digit = 7
02/09/13 19:13:07-067ms Call Ref = 118, Short Code Matched = System, *17
02/09/13 19:13:07-077ms My buttons = 1, Call Ref = 118, Originator State = Connected, Type = User, Destination State = Connected, Type = Mailbox
02/09/13 19:13:07-099ms My buttons = 1, Call Ref = 118, Originator State = Connected, Type = User, Destination State = Clearing, Type = Mailbox
02/09/13 19:13:07-099ms Call Ref = 118, Disconnect from Destination End
02/09/13 19:13:07-104ms Extension = 777, State = Busy Wrap Up
02/09/13 19:13:07-106ms Extension = 777, Button = 1, Idle
02/09/13 19:13:09-106ms Extension = 777, State = Idle
02/09/13 19:13:11-625ms Extension = 777, Digit dialed, Digit = *
02/09/13 19:13:11-647ms Call Ref = 120, Originator State = Dialling, Type = User, Destination Type = none
02/09/13 19:13:12-536ms Extension = 605, Button = 2, Idle
02/09/13 19:13:13-505ms Extension = 777, Switchhook, Status = On
02/09/13 19:13:13-508ms My buttons = 1, Call Ref = 120, Originator State = Clearing, Type = User, Destination Type = none
02/09/13 19:13:13-508ms Call Ref = 120, Disconnect from Originator End
02/09/13 19:13:13-509ms Extension = 777, State = Busy Wrap Up
02/09/13 19:13:13-515ms Extension = 777, Button = 1, Idle
02/09/13 19:13:15-354ms Extension = 777, Digit dialed, Digit = #
02/09/13 19:13:15-360ms Extension = 777, State = Idle
02/09/13 19:13:15-381ms Call Ref = 121, Originator State = Dialling, Type = User, Destination Type = none
02/09/13 19:13:15-965ms Extension = 777, Digit dialed, Digit = 7
02/09/13 19:13:16-345ms Extension = 777, Digit dialed, Digit = 8
02/09/13 19:13:16-347ms Call Ref = 121, Short Code Matched = System, #78
02/09/13 19:13:16-358ms My buttons = 1, Call Ref = 121, Originator State = Connected, Type = User, Destination State = Connected, Type = Mailbox
02/09/13 19:13:16-381ms My buttons = 1, Call Ref = 121, Originator State = Connected, Type = User, Destination State = Clearing, Type = Mailbox
02/09/13 19:13:16-381ms Call Ref = 121, Disconnect from Destination End
02/09/13 19:13:16-385ms Extension = 777, State = Busy Wrap Up
02/09/13 19:13:16-387ms Extension = 777, Button = 1, Idle
02/09/13 19:13:18-387ms Extension = 777, State = Idle
02/09/13 19:13:25-585ms Extension = 604, State = Busy Wrap Up
02/09/13 19:13:25-588ms Extension = 604, State = Idle
02/09/13 19:13:27-574ms Extension = 604, State = Busy
02/09/13 19:13:27-574ms Extension = 604, Button = 2, Idle




Thnks in advance for all the help.It was my first post and the response was so fast....I am thrilled...

 

[tlpeter]

Run this tool on the VMPro server:

http://marketingtools.avaya.com/knowledgebase/tools/debug/dbgview.zip

Then dial *17 and post the output here.
Also open monitor and do the same (at the same time ofcourse)

BAZINGA!

I'm not insane, my mother had me tested!

 

[teletechman]

Double check the IP addresses then try to ping both ways. From the VM Pro server to the IPO then from the SSA using the correct network port to the VM pro address make sure that both work. It sounds like a connection issue like the VM is not seeing the network. When you upgraded did you disconnect anything and then re-plug it back wrong, seems simple but seen it done. MAke sure you are in the LAN or WAN port that is the correct IP address.
Mike

 

[Sujeeshg]

Dear all,

This issue has been resolved...It was the vm pro password in the IPO security setting...

Thanks a lot for all your support...

 

[TelecomsTim]

How exactly did you resolve this as I have the same problem on our in-house system?

I am running an Avaya Application Server rather than a Windows based machine

 

[TelecomsTim]

It's okay, I've sorted it.

Needed to reset voicemail password in Security setting and then reset in VMPRO client.

Any idea what could have caused this as nothing as been changed on system or server?