Cisco DNCS System Release 2.8 3.8 4.3 Technical References

 

 

 

Field Notice: 
EAS Force-Tune Setup for SR 4.3 

 

System Release (SR) 4.3.x was designed so that the Emergency Alert System (EAS) 
force-tune channel has to use the SAM Service ID. 
Although SRs 5.0 and later offer an option for setting the EAS force-tune channel 
without using the SAM Service ID, this is a feature that did not exist when  
SR 4.3.x was developed. This means that in order to accomplish an EAS force-tune 
without using the SAM Service ID in SR 4.3.x, the Source ID for the force-tuned 
channel must be equal to the SAM Service ID.   
Note:  Additionally, the SAM Service ID must be greater than 200 because Source 
IDs in the range of 1 to 200 are reserved by the DNCS. 

There are several types of STBs and third-party devices operating on SR 4.3.x 
systems. Each device places constraints upon implementation of EAS  
force-tuning.   

 

Legacy DCHTs that do not support CableCARD modules. These devices use 
the samserviceId parameter in Cisco proprietary messaging to force-tune if they 
are using the SARA resident application. 

 

Hosts with CableCARD modules. These devices use out-of-band SCTE-18 
messaging for force-tuning, and therefore use the Source ID. 

 

Hosts that support CableCARD modules but do not have one. These devices 
use in-band SCTE-18 messaging for force-tuning, and therefore use the Source 
ID. 

 

PowerKEY® Digital Terminal Adapter 170 (pkDTA 170) devices. These 
devices expect the Source ID for force-tuning in Cisco proprietary messaging, 
but currently are receiving the samserviceId (this is the same messaging as the 
legacy DHCTs.) To change the proprietary messaging for the pkDTA 170 
devices would break the messaging for the legacy DHCTs.