01-21-2014 06:05 AM - edited 03-16-2019 09:21 PM
Hi All,
We are facing timetamp issue in 3905 SIP Phones . We have configure the proper time , NTP server reference (Which is same Router ) , timezone , datetime format.
But Phone is showing different timestamp rather than "show clock" output from router. While CME responding the register message for SIP Phone it's sending the wrong time other than Router time. Suspecting this is the reason why phone is displaying the wrong time.
What could be the issue ? What is the resloution for this.
Thanks in Advance...
01-21-2014 06:35 AM
Hi.
Please post your CME config as soon as you can.
Thanks
Regards
Carlo
01-21-2014 10:05 PM
01-21-2014 10:45 PM
Hello,
Can you please confirm is this problem related to time format which is displaying wrong on the phones or diference in the timing ahead or delay?
Br,
Nadeem
Please rate all useful post.
01-21-2014 10:56 PM
Hi Nadeem,
We are getting wrong time in the Phone. We configured the IST timezone & NTP Server in the Voice register pool.
NTP also same CME router which is configured with IST timezone. When i see the Register ACK message CME is sending with " GMT" timezone . That is the reason it's diaplying the GMT time in phone instead of IST.
Date: Wed, 22 Jan 2014 05:58:45 GMT
Call-ID: 6TJ6-edUiMO18J41sCcKIBE58UneBoC1
Server: Cisco-SIPGateway/IOS-15.2.4.M4
CSeq: 46755 REGISTER
Supported: X-cisco-cme-sis-1.0.0
Supported: X-cisco-srtp-fallback
Contact: <1019>;expires=1200;x-cisco-newreg1019>
01-21-2014 11:29 PM
look like you are hitting below bug
3905 IP Phones always display GMT Time
Symptom:
3905 IP Phones registered to CME always show the GMT time instead of the configured timezone.
Conditions:
* The phone always show GMT time even when we have a timezone configured globally or under 'voice service global' or even when a NTP clock source is configured.
* Phone's web page shows the correct timezone name but the time displayed is always GMT hours/minutes
Br,
Nadeem
Please rate all useful post.
01-22-2014 12:13 AM
Hi ,
I have fixed the issue as per the workaround given in "https://supportforums.cisco.com/thread/2142828" . It's working now.
Thanks to everyone for the support.
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