IPO / App Server weird time condition issue

[Greybeard191]

Scenario:

IPO 500V2 6.1.12, Linux App Server running VM Pro/One-X.

Time on the phones shows as correct, and matches the time shown via webcontrol in the server.

But, the VM Pro callflow is being shifted in and out of service (afterhours) with a one hour shift from the displayed time. And the time displayed on the phone has apparently shown out by the same one hour, randomly.

Any ideas on where this random one hour shift is coming from? The obvious guess would be something isn't daylight saving time-shifted, and the call flow is being shifted according to that time, but why doesn't the server and phones match (the erroneously shifted time)?

 

[tlpeter]

Is the time on the server OK?
I have had issues with Linux where the time did not update very well.
I am not sure why this happens to some Linux installs.
Login on the server by web or console
By web go to the time settings.
By console type date.


BAZINGA!

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

 

[Greybeard191]

yeah, the time on the server appears OK, but I agree, mucking around in the webcontrol doesn't exactly fill me with confidence that the server is doing what you're asking.

Questions:

1) What actually drives the time condition... e.g. if you set the office to close at 16:00 hours, where si the 16:00 derived from? The IPO or the VM Pro server?

2) If it's the IPO, can something else override the VM Pro server if the IPO is set for VM Pro/Manager for time? And how exactly does this work?

GB

 

[tlpeter]

1) server
2) see 1


BAZINGA!

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

 

[Greybeard191]

So possibly have a PC on the network running Manager (with the PC set to the wrong time) won't muck things up?

I don't even necessarily know this to be the case, just wondering.

GB

 

[mititelu]

maybe try and switch NTP Server to on (if you had it off) or vice versa, see if it fixes issue.

Also you may want to check if IPO time matches linux.
If daylight savings occured and you haven't restarted system since then, you could try restarting it

 

[hairlessupportmonkey]

I suspect there is something else on the network disrupting the flow of TIME - oh dear, bad geek pun.

anyway. with rel 6.1+ I always tend to set the external NTP time source even if voicemail pro exists!

the APP server also uses an NTP time source - this is set by default on my rel 7 app server

Datetime
Date:
Time:
:
Timezone:
Enable Network Time Protocol
NTP Servers:
0.centos.pool.ntp.org
1.centos.pool.ntp.org
2.centos.pool.ntp.org
Synchronize system clock before starting service
Use local time source

so you could always just point the IPO to the App server or to the same NTP time source.

But if the two differ, you might find they offer out different daylight savings times!




ACSS - SME

 

[Greybeard191]

ended up by getting around this by finding an internal server in the building that was acting as a NTP source to other devices, pointed the app server at that server, IPO at app server, all is good.

GB