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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Does anyone have any ideas? 1
- Thread starter colec12
- Start date
-
1
- #3
- Thread starter
- #5
Sorry, this was the original post;
colec12 (TechnicalUser)
(OP)
30 Mar 20 14:57
Missed calls are off an hour when using my 1x communicator client software. Working well other then that.
H.323
avaya 6.2
kyle555 (TechnicalUser)
30 Mar 20 16:41
you mean the timestamp on the call?
if you stat your station when logged in, what network region are you in?
if you display ip-network-region X where X = your network region, do you have a location in the top left?
if you display location X where X is your location, is there a time offset for that location?
CM's server time is the reference time for the network. So, if your main server was in NY, it might be GMT -5 in Linux and your LA failover server might be GMT -8 in Linux, but in CM, the location for procr/the main server has time offset 0 and LA would have -3. It'd be up to your config to get subnets into regions into locations that align to that.
colec12 (TechnicalUser)
(OP)
30 Mar 20 18:00
I looked and it is correct. That still does not explain that the timestamp is only off on missed calls.
Very odd.
Thanks for your response.
colec12 (TechnicalUser)
(OP)
30 Mar 20 14:57
Missed calls are off an hour when using my 1x communicator client software. Working well other then that.
H.323
avaya 6.2
kyle555 (TechnicalUser)
30 Mar 20 16:41
you mean the timestamp on the call?
if you stat your station when logged in, what network region are you in?
if you display ip-network-region X where X = your network region, do you have a location in the top left?
if you display location X where X is your location, is there a time offset for that location?
CM's server time is the reference time for the network. So, if your main server was in NY, it might be GMT -5 in Linux and your LA failover server might be GMT -8 in Linux, but in CM, the location for procr/the main server has time offset 0 and LA would have -3. It'd be up to your config to get subnets into regions into locations that align to that.
colec12 (TechnicalUser)
(OP)
30 Mar 20 18:00
I looked and it is correct. That still does not explain that the timestamp is only off on missed calls.
Very odd.
Thanks for your response.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question