Guest

Preview Tool

Cisco Bug: CSCuw54202 - Need a better way to handle unknown values from UCM in Trunk GSU

Last Modified

Apr 28, 2016

Products (1)

  • Cisco Prime Collaboration

Known Affected Releases

10.6(1)

Description (partial)

Symptom:
== Thiis defectis related to Trunk GSU, not RTMT, but we don't have module = GSU, so it is under RTMT module for now ===

In an European customer site, it is been noticed that we are showing T1 trunks in this customer deployment. Since there are no T1s available in European deployment, it caused customer confusions.
Per investigation results, GSU module assumes data records from CUCMs are for T1s if data values = 0 (which means unknown).

This kind of "assumptions" is invalid in an E1 only deployment which customer confusions when they saw T1 trunk usages shown in usage reports. It must be addressed in PCA future release.

Conditions:
== Thiis defectis related to Trunk GSU, not RTMT, but we don't have module = GSU, so it is under RTMT module for now ===

In an European customer site, it is been noticed that we are showing T1 trunks in this customer deployment. Since there are no T1s available in European deployment, it caused customer confusions.
Per investigation results, GSU module assumes data records from CUCMs are for T1s if data values = 0 (which means unknown).

This kind of "assumptions" is invalid in an E1 only deployment which customer confusions when they saw T1 trunk usages shown in usage reports. It must be addressed in PCA future release.
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.