Guest

Preview Tool

Cisco Bug: CSCzr00962 - ASI Outputs stuck in mute state after uplink group assignment

Last Modified

Feb 03, 2012

Products (1)

  • Digital Receivers/Decoders

Known Affected Releases

D1.18.10JC

Description (partial)

Symptom:
A group assignment change was performed using the IBCC. It was reported that out of 23 MTRs expected to act upon the group assignment change, 2 MTRs ended with ASI outputs stuck in a muted state. The remaining 21 MTRs were successfully tuned with ASI outputs operating normally.
Conditions:
The situation occurs when new RF carriers are deployed. 
Some of the MTRs in the network could be in state where they never been tuned to a one of the new RF carriers.  
As a consequence, the MTR's CTT (Combined Transport Table) has no entries for combined transports that are present in the new RF carrier. 
When the MTR is assigned to a group that configures the MTR to decombine one or more transports from the new carrier, the outputs are initially muted
The outputs are expected to unmute when the MTR tunes the new RF carrier and finds the required combined transports
If the tuning setup is part of the same group configuration as the ASI output settings then an application flaw creates a statistical chance for the outputs to remain stuck in teh mute state
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.