I know that this question is quite old. However, I think that it isstill relevant today. I have a CIPC version 2.1.0 and have run it againstversion 7.1 and version 8.0 of CUCM and got the same results: clockshowing GMT.
I have a specific issue with central time (GMT -6). I had configured GMT -6 Americas/Winnipeg and ran into the clock issue.
I tried GMT -6 Americas/Regina and my CIPC would not even register...wouldget past "Updating Locale".
The one that worked for me was GMT -6 Americas/Chicago...this one is compatible with older phone loads and did the trick for me.
Seems a bit flaky so try different setting for your Date/Time group and hopefully you will eventually get the right one.
Ran into the same issue, had to switch to one of the time zones with the +- at the end so that it worked for older version loads (as listed under DateTime). Once I changed to one of those, I was fine, but when I used one like Toronto that doesn't have the indicator, it didn't work for my IP Comm.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...