Cisco Model 6109 6 MHz Off-Air Reference (NTSC) Guide De Montage
USRM Web Interface - Resource Manager
4039132 Rev B
137
Parameter
Description
HeadendName
The name of the headend. The name is limited to a
maximum of four characters. The Comcast activity log
specification requires that service group names are
hierarchical. The format is servicegroup.hub.headend.
maximum of four characters. The Comcast activity log
specification requires that service group names are
hierarchical. The format is servicegroup.hub.headend.
Note: This parameter must be populated if the
Applications.SdvSM.Activity log.ActivityLogFormat is
set to Comcast.
Applications.SdvSM.Activity log.ActivityLogFormat is
set to Comcast.
HubName
The global hub name used to form the hierarchical
service group name for logs. The name is limited to five
characters maximum. The hub name can also be
configured in a hub name table for cases where the
USRM spans more than one hub site.
service group name for logs. The name is limited to five
characters maximum. The hub name can also be
configured in a hub name table for cases where the
USRM spans more than one hub site.
Note: This parameter must be populated if the
Applications.SdvSM.Activity log.ActivityLogFormat is
set to Comcast.
Applications.SdvSM.Activity log.ActivityLogFormat is
set to Comcast.
SessionUserDataFormat
The configured format for the user data field of a session.
The USRM manages all sessions with a 10-byte sessionId.
RTSP protocols require tagging sessions with other forms
of a sessionId that cannot be contained in a 10-byte
sessionId. These identifiers are referred to as the non-
native sessionId. This information is maintained in the
UserData field for a session. Devices that use the NGOD
R6 or S6 protocols require an OnDemandSessionId that is
formed as a 128-bit IETF universal identifier. The "UUID"
state causes the UserData to be presented on the web
interface as a universal identifier. Other RTSP protocols
(VERM, CableLabs) require an OnDemandSessionId
formed as a character string. The "String" state causes the
UserData to be displayed as a character string.
The USRM manages all sessions with a 10-byte sessionId.
RTSP protocols require tagging sessions with other forms
of a sessionId that cannot be contained in a 10-byte
sessionId. These identifiers are referred to as the non-
native sessionId. This information is maintained in the
UserData field for a session. Devices that use the NGOD
R6 or S6 protocols require an OnDemandSessionId that is
formed as a 128-bit IETF universal identifier. The "UUID"
state causes the UserData to be presented on the web
interface as a universal identifier. Other RTSP protocols
(VERM, CableLabs) require an OnDemandSessionId
formed as a character string. The "String" state causes the
UserData to be displayed as a character string.
MinimumTransaction
Timeout
Timeout
The minimum value to be used for all edge device
transaction timeouts. The TransactionTimeout is the
maximum time to wait for a reply from an edge device.
This value is configured for each edge device. The
MinimumTransactionTimeout provides a way to globally
increase the TransactionTimeout. When communicating
with an edge device, the software will use the lower of
the MinimunTransactionTimeout or the
TransactionTimeout configured for the device.
transaction timeouts. The TransactionTimeout is the
maximum time to wait for a reply from an edge device.
This value is configured for each edge device. The
MinimumTransactionTimeout provides a way to globally
increase the TransactionTimeout. When communicating
with an edge device, the software will use the lower of
the MinimunTransactionTimeout or the
TransactionTimeout configured for the device.
Note: This field is editable in version 1.6.x.