IP Office not getting the time

[jeepguy267]

My IP office has 2 issues that I beleive are related. The VM Pro license is comming up as invalid and the system resets the clock to 12:00am 8/25/97 after reboot.

Since both settings are comming from my server I assume that the IP office can't see the server. I have Taken the IP office off the network and Plugged my laptop (a different machine) running vmpro, manager, and key server directly into the ip office. I have changed the license server from static to broadcast, time server from staticc to 0.0.0.0, vmpro to static or nothing in about every combination possible. i see the ip office pulling files from the ip address of my server when watching in manager. I can ping the ipoffice and I can pull the config (broadcast) from the unit.

This is a 403 2.1

any thoughts - doors open monday with no voicemail yet

 

[crashtest1000]

Did it all work OK when plugged into your Laptop?

If so you have proved the fault to be something to do with your network.

Try connecting the PC that is running as the voice mail server directly into the IPO? This will eliminate the LAN Switch
The Voicemail server will run for 2 hours without a valid license by the way.

The time issue sounds like its getting the time from a different time server. Once you get the VM running it should get the time of this machine. Is the time correct?

Check the Parallel port on the PC is set to by-directional.

Just some thoughts.

 

[jeepguy267]

I did get the voicemail to work for the two hours after a reboot of the laptop, but the time is still wrong and the voicemail license still comes up as invalid.

Without question I get 12:00am 8/25/97 after reboot. the manager reads "PRN: RTC not initialized on 0a" (Run Time Clock - the system is grounded per instuctions)

Since the voicemail did work for the two hours I feel we have proven the IPO can see the server. So our routes and the network are happy. What is up with the license???

VM, Key Server running on win2000 prof. Services are runing in task manager. An the keyserver Icon "about" menu does give the correct sn #.

I am stuck and Avaya Tech support needs to be paying this group the insane rates they feel THEY should be getting for "well did you reboot the IPO, call back into Que after you have" (hoping maybe the next guy knows what the issue is.) - soory 'bout that, spontaneous disgruntledness!

 

[crashtest1000]

Try the following

Stop start the Licence key server under services and then pull the database back and see if that helps.

By any chance were the licence keys keyed into the database or copy pasted. If they were keyed in there could be a keying error. Try and pasting the keys from the CSV file.

Try the Dongle on a different machine all you have to do is install the Key server you may have a faulty parallel port

 

[willywu]

time server from staticc to 0.0.0.0

I think set time server from static to 0.0.0.0 means you not set time server(has disabled the ip office time server)

 

[Morrack]

Actually I believe 0.0.0.0 when the licence key server is set to that means look for the dongle on the local port (serial on SO - dunno if you could use USB adapter on 403). To broadcast you want 255.255.255.255 which should find it if on the same subnet.

However, as you've established this doesn't seem to be a case of the 403 not finding the VMPro / Feature Key Server.

Sounds to me like you've eliminated everything but the actual physical dongle now - assuming you copied and pasted the licence keys. Of course Avaya (or your distributor) could have made a mistake and sent you the wrong licence key codes, although I have yet to hear of that happening.

I would see if I could install a different dongle (and the corresponding different VMPro licence) and see if that helps. Do you have a demo unit with licences?

Peter