Cisco DNCS System Release 2.8.1 3.8.1 4.3.1 User Guide
Session Signaling Parameter Settings
The following table describes each field in the DSM-CC tab and provides the range of values that we
recommend.
recommend.
Field
Description
DHCT Session Signaling Parameters
Send 'Session in
Progress' Every
Progress' Every
Enter a time (in minutes) that defines how often a DHCT tells the DNCS that a
VOD event is in progress. The Session in Progress (SIP) message prevents the
system from tearing down sessions while a DHCT receives an event.
VOD event is in progress. The Session in Progress (SIP) message prevents the
system from tearing down sessions while a DHCT receives an event.
Warning: A reduction in VOD performance may occur when a large number of SIP
messages are generated at the same time.
messages are generated at the same time.
We recommend that you generate SIP messages at least every 120 minutes, but
no more than 180 minutes.
no more than 180 minutes.
Retry Requests
Up To
Up To
How many times a DHCT should send a session request to the DNCS .
We recommend that you set this value to 1 for one, but no more than 2 retries.
Setting this value to two or more times results in subscribers having to wait longer
for a response. In most cases, if the request fails, retries do not resolve the issue,
and subscribers have to wait longer for failure notification. If the session request is
successful, a retry never occurs.
for a response. In most cases, if the request fails, retries do not resolve the issue,
and subscribers have to wait longer for failure notification. If the session request is
successful, a retry never occurs.
Stop Waiting For
Network
Response After
Network
Response After
How long (in seconds) a DHCT should wait for confirmation that the DNCS is
processing the session request
processing the session request
We recommend that you set this to at least 5, but no longer than 10 seconds.
Network Session Signal Parameters
Send 'Setup
Proceeding'
Every
Proceeding'
Every
How long (in seconds) a DHCT must wait to receive confirmation from the DNCS
that it is processing the session request that the DHCT sent.
that it is processing the session request that the DHCT sent.
We recommend that you set this to at least 5, but no longer than 10 seconds.
Retry Requests
Up To
Up To
How many times the DNCS should request tuning information from the VOD server
for a particular event.
for a particular event.
We recommend that you set this value to be equal to or greater than the Retry
Requests Up To parameter for DHCTs.
Requests Up To parameter for DHCTs.
Setting this value to two or more times results in subscribers having to wait longer
for a response.
for a response.
In most cases, if the request fails, retries do not resolve the issue, and subscribers
have to wait longer for failure notification. If the session request is successful, a
retry never occurs.
have to wait longer for failure notification. If the session request is successful, a
retry never occurs.
Stop Waiting For
User Response
After
User Response
After
How long (in seconds) the DNCS should wait for the VOD server to respond after
the tuning information is requested.
the tuning information is requested.
We strongly recommend that you set this parameter to be greater than the Stop
Waiting For Network Response After parameter for DHCTs. Doing so ensures
that a DHCT initiates the teardown of a session before the DNCS does.
Waiting For Network Response After parameter for DHCTs. Doing so ensures
that a DHCT initiates the teardown of a session before the DNCS does.
Highest Program
Bandwidth
Bandwidth
The maximum allowable bandwidth for VOD sessions.
Reuse Expired
How long (in seconds) the system must wait to reuse a session ID after the ID has
Page 1393