Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Time Settings at Remote Site are Wrong

Status
Not open for further replies.

cipher7836

Technical User
Dec 20, 2010
100
US
IP OFFICE V5

At our second location the phones come up one hour off since last week's time change. That location says that it's looking at vmpro from location #1 for the correct time. However, vmpro has the correct time on it. I looked at the help files but couldn't find the best way to correct this. Could someone please help?
 
Point the time server ip address of the remote IPO to the main IPO and not to the VMPro.

Remote -> Main -> VMPro

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Make sure the time offset is 00:00

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
I made the change, but the clocks are the same. I did a "merge". Should I have done an "immediate" instead?
 
the offset might have to be 'something' if the two IPO were in different time zones, wouldn't it?

GB
 
I would think so. Luckily they're in the same timezone in my case.
 
Do you check the time on the remote site with system status?
Sometimes the time in system status doesn't correspond with the time on the handsets.
 
Indeed SSA is often way off, for example the system and handsets and my PC all say 13:00 and SSA will often say 05:00 or something way out from everything else, using monitor time stamps is the best way of checking remotely :)

NTE-wave-logo-for-a4-header.jpg
 
Where are you checking the Time?
If that is in the systemstatus SSA, then it might be a bug.
Call the customer and ask them what they see in the display.
Does the VMPro has the correct time?
And indeed check the offset, after chaging you might need to reboot, or wait for max 60 minutes. The time is set every hour.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
I'm checking the time on the phones themselves. The remote site was set to look at vmpro for its time. But the time is correct on vmpro. Here's what I did to resolve, but I think this may cause problems in the future:

Changed the following settings in order to correct the time:

1. Under "system" within the Avaya Manager and under "Time Setting Config Source" set it to none.
2. Local time offset from UTC = -8.00

This corrected the time, but it may not be the correct way to do this. What do you all think?
 
The IPO should be able to synch its time to the remote VM (the preferred option)
does the IPO have a data route to the remote VM Pro? if not it will not be able to update the time.
Is there any port blocking on the data network? the IPO uses the older rfc868 time protocol if this is blocked (port 37) on the link then it will not be able to update the time.

The time offset is really for use when the 2 IPO's are in different time zones

on the the other hand if it works...
just make sure one handset has a key to manual set the time


Computers are like Air conditioners:-
Both stop working when you open Windows
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top