setting timezone on CME

-
The issue I faced today was quite weird.
My IP phones showing correct timing, but my CME doesn't as a result of which night-service wasn't working correctly.

Here is the snippet of my config-

CONFIG (Version=8.6)
=====================
Version 8.6
Max phoneload sccp version 17
Max dspfarm sccp version 18
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_series_home.html

protocol mode default
ip source-address 10.39.32.10 port 2000
ip qos dscp:
 ef (the MS 6 bits, 46, in ToS, 0xB8) for media
 cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
 af41 (the MS 6 bits, 34, in ToS, 0x88) for video
 default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-pickup
service dnis overlay
service dnis dir-lookup
load 7916-12 B016-1-0-4.SBN
load 7916-24 B016-1-0-4.SBN
load 7937 apps37sccp.1-4-4-0
load 7941 SCCP41.9-1-1SR1S
load 7942 flash:SCCP42.9-1-1SR1S
load 7945 SCCP45.9-1-1SR1S
load 7965 SCCP45.9-1-1SR1S
max-ephones 110
max-dn 300
max-conferences 8 gain -6
dspfarm units 3
dspfarm transcode sessions 0
dspfarm 1 iosconf
dspfarm 2
dspfarm 3
conference hardware
privacy
no privacy-on-hold
hunt-group report delay 1 hours
hunt-group logout DND
max-redirect 10
voicemail 5000
cnf-file location: flash:
cnf-file option: PER-PHONE
network-locale[0] NO   (This is the default network locale for this box)
network-locale[1] US
network-locale[2] US
network-locale[3] US
network-locale[4] US
user-locale[0] NO    (This is the default user locale for this box)
user-locale[1] US
user-locale[2] US
user-locale[3] US
user-locale[4] US
srst mode auto-provision is OFF
srst ephone template is 0
srst dn template is 0
srst dn line-mode single
phone service videoCapability 1
phone service webAccess 0
time-format 24
date-format dd-mm-yy
timezone 28 Central Europe Standard/Daylight Time
secondary-dialtone 0
url directories http://x.x.x.x/localdirectory
call-forward pattern .T
call-forward system redirecting-expanded
transfer-pattern .T
night-service day Sun 08:00 07:59
night-service day Mon 16:00 07:59
night-service day Tue 16:00 07:59
night-service day Wed 16:00 07:59
night-service day Thu 16:00 07:59
night-service day Fri 16:00 07:59
night-service day Sat 08:01 07:59
night-service weekday 16:00 07:59
keepalive 30 auxiliary 30
timeout interdigit 10
timeout busy 10
timeout ringing 180
timeout transfer-recall 0
timeout ringin-callerid 8
timeout night-service-bell 12
caller-id name-only: enable
web customize load flash:webadmin.xml
edit DN through Web:  enabled.
edit TIME through web:  enabled.
background save interval 10 minutes
Log (table parameters):
     max-size: 150
     retain-timer: 15
create cnf-files version-stamp Jan 01 2002 00:00:00
transfer-system full-consult
transfer-digit-collect new-call
local directory service: enabled.
Extension-assigner tag-type ephone-tag.

#show clock
.09:21:17.810 CET Wed May 2 2012

Here is the command to set right timezone on the CME-
(config)#clock timezone GMT+1 1
(config)#clock summer-time GMT+2 recurring
#show clock
.10:36:05.199 GMT+1 Wed May 2 2012


Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more