What is more likely the problem is that your IP communicator is not able to download it's TFTP file.
Things to check:
-If you're using CME, make sure 'type' is under the ephone config
-Under the preferences options on the IPC, make sure you have the correct IP address. If the CIPC isn't able to register to it's primary IP address, it will try to register with it's default gateway and it won't pull the config down.
-Make sure that tftp ( UDP 69 ) isn't being blocked by your firewall. If it can't download the config file it will be 5 hours off.
Short story - your phone isn't downloading it's .cnf.xml file that has the timezone in it, and it's trusting that the CUCM/CME is sending the correct time in GMT.
We have just started using IPC and find that our time is off by 6 hours also. Time on all our IP phones is correct. We have a ntp server set, referenced by our date\time group, which our device pool points to. So....IPC and phones should all have the same time, but they don't. The IPCs are off exactly 6 hours (ahead). We are on CM 6.1.2 and our IP Communicators are on 184.108.40.206. Anyone had any other ideas on this issue?
I do support for our users using IPC so don't use it very often. After getting your email I popped into IPC and it now shows the correct time!! We haven't done any upgrades on any of our CM servers so I don't know why it shows the correct time now. I did notice that when we experienced this problem before (over a year ago) we were in standard time and not daylight saving time. So since the change is this weekend, we'll see if that makes any difference.
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...