Cisco Headend System Release 2.7 Installation Guide
What's Fixed?
4023372 Rev B
3
What's Fixed?
Introduction
This section provides a description of the CRs implemented in MQAM 2.6.18.
CR 71660: Third-Party MUX Devices No Longer Cause MQAM Reboots
Previously, when system operators used a third-party MUX device in conjunction
with the MQAM, an issue was identified where the MUX device used the entire
reserved bandwidth rate to send the Program Allocation Table (PAT) to the MQAM,
which caused multiple MQAM reboots. A PAT filter was added in the field
programmable gate array (FPGA) code to limit the extract processing at a low level.
Note: If you use a third-party MUX device, make sure that you limit its reserved
Note: If you use a third-party MUX device, make sure that you limit its reserved
bandwidth rate to our recommended bandwidth of 10 to 15 kpbs. You can also
configure the MUX device so that it does not use the reserved bandwidth feature.
CR 71660 corrects this issue.
CR 71660 corrects this issue.
CR 71988: Adaptation Headers No Longer Cause MQAMs to Lose Sessions
Certain content feeds include adaptation field parameters in the Program Map Table
(PMT). MQAM software version 2.6.18 includes an enhancement to handle cases
found when adaptation field data is included in PMT packets. This fix allows the
MQAM to successfully handle the adaptation field parameters and establish the
session. CR 71998 corrects this issue.
CR 76306: MQAMs No Longer Re-Boot When They Receive Bad MPEG Data
Previously, an MQAM could re-boot if it received bad MPEG packets. MQAM
software version 2.6.18 was enhanced to detect and drop bad MPEG packets instead
of processing them. CR 76303 corrects this issue.