A place to ask questions, connect with others, and stay in the know
Originally posted by shurla5;36799where we are puling the time from, primary IC server, has the correct time, but the phone have jumped ahead a week early it seems. How\where do we check to determine when the phones are to spring forward?
Originally posted by GGanahl;36801I would first look at DHCP to see if Option 004 (Time Server) or Option 042 (NTP/SNTP server) is set to tell the phone where to get it's time setting.
The Location settings under Regionalization also have a setting to tell entities whether to get their time from the IC server or another source, so check that setting in IA as well.
Also, on the phone itself, press the Menu button, Status, TCP/IP Parameters, and scroll down to the SNTP Address - that should tell you where the phone is getting its time from.
Originally posted by GGanahl;36804I forgot to ask what version of IC...I have a memory of there being a problem withing the past few years of phones shifting to DST early...vague memory...
Originally posted by GGanahl;36803What does the GMT Offset show on the phone? Is that correct? (In Status just below the SNTP Server info)
Originally posted by GGanahl;36807That just means they are not set by DHCP. So, it would go back to the Time Zone setting on the Managed IP Phone configuration and the Time Server setting in the Location.
Originally posted by tcannon;36809We have this too 2016 R4 P5. As I understand this is fixed in patch 6 (or any other upgrade).
I don't know the number of the KB article, but here is an excerpt:
What is occurring is some versions of CIC are passing an incorrect value for Daylight Savings Time (DST) to the phone:
This has been resolved IC-140435, where the parameter is changed to an 8 indicating the second Sunday of the month:
Originally posted by nofon4u;36810Where would I find these settings? I can see them in our stand alone phones, but where does the provisioning server hold these settings?
Originally posted by llneely;36814Every Year we have this can we please get a resolution
Originally posted by shurla5;36816AMEN to that!
Originally posted by llneely;36818If they wait a week we will forget about it :)
Originally posted by GGanahl;36832As mentioned by tcannon earlier in the thread, it was already fixed long ago. You have to upgrade to a newer patch or release.
Originally posted by swilliams164;36813We are running 2018 R1 Patch 5 and had the same issue, so i don't think it is corrected in a higher version. To correct in our network i simple did a reload from Managed IP Phones, which pushed the correct time, without causing any active calls to drop or the phone to reboot.
Originally posted by nofon4u;368372018 R1 had the same issue? Just a reload fixed it? No adjustment to time zone offset?
Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources
Every year, Genesys® orchestrates more than 70 billion remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.