Guest

Preview Tool

Cisco Bug: CSCul56410 - Cannot add a location with CMLocal Date/Time Group

Last Modified

Jan 12, 2014

Products (1)

  • Cisco Hosted Collaboration Solution (HCS)

Known Affected Releases

8.1(3)

Description (partial)

Symptom:
Details:
Seems to be an ongoing problem across multiple releases.  Fails on 8.1.0er2 as
well as 8.1.2

XML    
2977 Request Failed     AddLocation
    =>  Entered at: 2013/08/22 16:15:08 EDT  (10.5.20.2)

      TimeZone [CMLocal] provided is not supported
    => Started at: 2013/08/22 16:15:08 EDT
          => End at: 2013/08/22 16:15:08 EDT


ipt=> select * from ccm_datetime_group;
 id |                 pkid                 |  name   | providername |
ccmclustername  | available
----+--------------------------------------+---------+--------------+-----------------+-----------
  1 | 9ec4850a-7748-11d3-bdf0-00108302ead1 | CMLocal | Tenet-SMH    |
SMH-CCM-Cluster | t
  2 | 5bb6f7cd-a30f-76ab-06c8-c17fcb87dcb0 | EST5EDT | Tenet-SMH    |
SMH-CCM-Cluster | t
(2 rows)


Steps to Reproduce:
1. Import the Date/Time Groups from CUCM
2. Attempt to bulk-load a location using CMLocal as the 'timezone' - really
this should not even be called timezone since it looks for the CUCM date/time
group.
3. 
4.
5.
6.
Actual Results:  
TimeZone [CMLocal] provided is not supported


Workaround Available: No


Seems VOSS looks at Date/Time Group and Timezone as the same entity when
building a location.  If you specify Africa/Abidjan timezone for example, it
will look for the Africa-Abidjan Date/Time Group in CUCM (note '/' changes to
'-' since CUCM does not support '/' in the DTG name).  There are problems with
that logic.  VOSS needs to separate timezone and datetimegroups - as timezone
names are fixed in CUCM, but datetimegroups can be called just about anything. 
I can have a DTG called Florida with EST timezone in CUCM and VOSS will never
be able to add that location because the DTG called 'EST' does not exist in
CUCM.

Conditions:
Details:
Seems to be an ongoing problem across multiple releases.  Fails on 8.1.0er2 as
well as 8.1.2

XML    
2977 Request Failed     AddLocation
    =>  Entered at: 2013/08/22 16:15:08 EDT  (10.5.20.2)

      TimeZone [CMLocal] provided is not supported
    => Started at: 2013/08/22 16:15:08 EDT
          => End at: 2013/08/22 16:15:08 EDT


ipt=> select * from ccm_datetime_group;
 id |                 pkid                 |  name   | providername |
ccmclustername  | available
----+--------------------------------------+---------+--------------+-----------------+-----------
  1 | 9ec4850a-7748-11d3-bdf0-00108302ead1 | CMLocal | Tenet-SMH    |
SMH-CCM-Cluster | t
  2 | 5bb6f7cd-a30f-76ab-06c8-c17fcb87dcb0 | EST5EDT | Tenet-SMH    |
SMH-CCM-Cluster | t
(2 rows)


Steps to Reproduce:
1. Import the Date/Time Groups from CUCM
2. Attempt to bulk-load a location using CMLocal as the 'timezone' - really
this should not even be called timezone since it looks for the CUCM date/time
group.
3. 
4.
5.
6.
Actual Results:  
TimeZone [CMLocal] provided is not supported


Workaround Available: No


Seems VOSS looks at Date/Time Group and Timezone as the same entity when
building a location.  If you specify Africa/Abidjan timezone for example, it
will look for the Africa-Abidjan Date/Time Group in CUCM (note '/' changes to
'-' since CUCM does not support '/' in the DTG name).  There are problems with
that logic.  VOSS needs to separate timezone and datetimegroups - as timezone
names are fixed in CUCM, but datetimegroups can be called just about anything. 
I can have a DTG called Florida with EST timezone in CUCM and VOSS will never
be able to add that location because the DTG called 'EST' does not exist in
CUCM.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.