Cisco Headend System Release 2.5 Release Notes
SR 2.8 at a Glance
4019364 Rev B
11
Also, the DHCT UI now includes a field to show the OpenCable ID.
RPC API Version Communication
Beginning with SR 2.8, reset commands are now transmitted from the DNCS to the
target GQAM through RPC API version 3 calls.
target GQAM through RPC API version 3 calls.
In earlier versions of code, the DNCS supported RPC API version 2. SR 2.8
introduces support for RPC API version 3 so that the DNCS can perform more
advanced RPC communications.
introduces support for RPC API version 3 so that the DNCS can perform more
advanced RPC communications.
The GQAM supports RPC API version 3 beginning in the GQAM 4.2 family of code.
When the DNCS first attempts to communicate with a GQAM, it uses RPC API
version 3 calls. If the communication fails, the DNCS marks the GQAM as not
supporting version 3. In that case, the DNCS uses version 2 APIs for all future
communications until either the GQAM or qamManager is rebooted. At that point,
the DNCS will attempt once again to communicate using version 3 calls.
When the DNCS first attempts to communicate with a GQAM, it uses RPC API
version 3 calls. If the communication fails, the DNCS marks the GQAM as not
supporting version 3. In that case, the DNCS uses version 2 APIs for all future
communications until either the GQAM or qamManager is rebooted. At that point,
the DNCS will attempt once again to communicate using version 3 calls.