07-08-2009 09:20 AM - edited 03-21-2019 01:17 AM
Customer's UC500 system is set for US Central time, using NTP to update. Times are correct everywhere except on one 7945 phone, which displays Pacific time. How can I fix this?
07-08-2009 09:23 AM
Can you post your config and verify the firmware on the phone?
07-08-2009 10:43 AM
07-08-2009 11:05 AM
can you do this...
config t
telephony-service
no create cnf-files
create cnf-files
Reboot the phone, and see if that works
07-08-2009 12:08 PM
No, that didn't work. Still displaying Pacific time.
07-08-2009 12:26 PM
You might be running into that. Try upgrading to 8.4.1 or later.
07-08-2009 05:02 PM
I ran into a similar problem and it was a combination of problems. One was the phone loads were outdated, the other was the IOS, we ran one of the early releases of the IOS to get the one button LiveRecord feature to work. Apparently there was a conflict with this and the CCA. I ended up rolling back to the latest working IOS, upgrading to CCA 2.0.1 and uploading the latest phone builds and things are working now.
07-13-2009 05:13 PM
I've updated the phone loads for the 7945 to 8-4-2, but the phone will not update its firmware when rebooted; it remains at 8-3-5. I updated the 7945-7965 phone load files, the tftp-server commands and the load command via CLI. What did I miss to get the phone to update its firmware?
07-14-2009 12:21 PM
Found the problem with the firmware update (and probably the original time problem). The phone is connected through a switch (not a Cisco switch), causing it to be assigned a 192.168.0.x ip address, rather than a 10.1.1.x address. The phone registers and works perfectly, but the update doesn't happen. When connected to the UC520 directly, however, it gets a 10.1.1.x address and updates properly. When reconnected through the switch, it now has the correct time and firmware, even though it again has a 192.168.0.x address.
So, is there a way to have the phone automatically assigned a 10.1.1.x address, even though it's not directly connected?
07-14-2009 12:27 PM
If the switch can support trunks and that switch is connected to the expansion port, you could do it. I would have thought TFTP would still have worked here though. You might want to look into why TFTP wasn't working.
07-14-2009 12:36 PM
I'm not sure what the switch can support; I didn't install it. I believe it is connected to the expansion port, though. Where would I start looking to try to find out why tftp wasn;t working?
07-14-2009 12:44 PM
term mon
debug tftp events
debug tftp packets
See what the output is when you reboot the phone. Unfortunately, you need the phone to be trying to upgrade. You could also see if there are any ACL's on the vlan or bvi interfaces.
07-14-2009 12:49 PM
Is 192.168.0.X your UC500 Data VLAN? Assuming it's not, then the phone is getting DHCP from somewhere else. This comment is not realted to your problem, but just make sure your data DHCP server on the UC500 is disabled if you are using another one.
Marcos
07-14-2009 01:11 PM
Yes, that's the data VLAN.
07-14-2009 01:17 PM
OK, ignore my comment then.
Thanks,
Marcos
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide