Search results for query: *

The garbled text can be caused by the video color depth being set to 256 color. Do you notice in manager if your licenses are valid for VM Pro?

Finally a tech came and replaced the 406 unit. Before he did the swap, they downgraded the FW to 3.1.658902 becasue there is an outstanding issue with clocking that hasn't been fixed yet. They recommended not to upgrade until those binaries for 3.2 were released. That didn't fix the problem...

What kind system is this on? On our 406v1 I had to do the same as was suggested in going to 3.1.65 which was shut off the system, disconnect all modules, T1, PRI, power on and upgrade from a PC connected directly to the 8 port switch. Then after a successful upgrade, power off, reconnect...

It was shortly after having the system installed in 2002, so probably 1.3 or 1.4, I'm not 100% sure. Like I said we ended up replacing those phones since we had others that worked OK. The AT&T phones were model #821 I believe, I don't have any left but that # sticks in my head. Hope this helps.

We had a similar problem using $20 AT&T analog phones. Switched to $20 GE phones and that solved the problem.

The VM Pro server is a Windows XP SP2 PC and I tried it on a Windows 200 Server SP4 as well. The Avaya tech downloaded a file from the web site you linked to above to test the HW lock and it tested OK on the Win XP box. I tried the Win2k box just to eliminate the XP system as the problem...

It is a hardware issue. Running monitor this is the first thing it shows: ********** Warning: TEXT Logging to File STOPPED on 23/8/2006 17:37:08 ********** 1mS PRN: Monitor Started IP=172.26.6.201 IP 406 3.2(17) Voith Paper 1mS PRN: LAW=U PRI=2, BRI=0, ALOG=0, ADSL=0 VCOMP=0...

Yes I was at 3.1.65 and no issues other than this 1

OK, I tried everything and nothing works. I have just installed the dongle on a Wndows 2000 server I have and loaded the admin suite on it as well, changed the licensing server to match that machine and verified the Key Server is running on the new machine. The licenses are still showing...

My email is ncipollini at comcast dot net. I ran through your other suggestions with reboots and still invalid. I have the virus protection off for now until this issue is fixed. It was working anyways. I think I found the firewall bat file on the DOC 3.2 CD in a zip file, but I would...

ipofficeinfoDOTcom, Sorry for my ignorance, where do I find the Avaya firewall batch file? I will try your suggestions asap. Thanks.

The dongle is the same as before. We bought the system 10/2002 running 1.2 and then quickly to 1.4 I believe. Then our vendor decided to drop Avaya products and support and I've dealt with it ever since. The PC is the same and both keys are invalid. Bummer about offline.

OK I have rebooted 4 times, re entered the license #s, removed the dongle and put it back, rebooted the VM server, re entered the IP of the license server under system, and changed the port on our main network switch that the IPO is connected to and still have invalid licenses. If someone told...

IPGuru, license server IP is correct, and deleting and reinserting did not work. I will try ipofficeinfoDOTcom's solution when there's no one on line.

If I open a config file I have from 7/31 in 3.1.65 offline, the licenses show as valid.

Yes I can ping it from the VM PC. That PC is connected to the IP Office switch and has a static IP address. The VM IP is configured under system in manager correctly. There is no firewall running on the VMPro PC. The feature key is a parallel port device.

Who can I contact to resolve this? Can I contact Avaya directly or do I have to call a Avaya Vendor, or am I completely up a creek?

Firewall is off and the the key server sees the dongle. In manager the license for VMPro 4 Port shows instances of 255 instead of 4 as well as invalid. The additional 4 Ports shows the correct quantity.

I forgot to say this is a IPO 406v1 with 8 port VMPro (at least last week it was)

Late last week, VMPro was dropping offline, but the service was running and no errors in event viewer, so I checked the system out and thought it was an incompatability with 1 or several MS updates released. Long story short is I came in the office Tuesday and decided to upgrade the system to...