The user can change this configuration on the fly. In this case, the new value of the adjustment-threshold is used when the next sample is obtained. The user is not expected to use this option too frequently. If an adjustment is already pending based on the previous adjustment-threshold, the adjustment is made.
Typically, the values of the threshold increase with the bandwidth. This means that as the ceiling value of bandwidth increases, the threshold value also increases. There is no restriction on this behavior. If the user sets a lower adjustment-threshold value for a higher range of bandwidth, a warning message displays. Consider the case below. If the user configure it this way, the configuration is accepted but a warning message displays.
| Range | Threshold |
|---|---|
| 0-10 kbps | 2000 kbps |
| 10 - 1000 kbps | 3000 kbps |
| 1000 - 10000 kbps | 2000 kbps << The threshold is less than the previous threshold |
| 10000 kbps + | 10000 kbps |
Does not trigger any immediate event. The new values are considered from the next sample onwards. When an adjustment is already pending based on the previous adjustment-threshold, the adjustment is done.
Does not trigger any immediate event. The new values are considered from the next sample onwards. When an adjustment is already pending based on the previous underflow-limit value, the adjustment is done.
When the user disables sample-recording for an LSP or a template, the sample-recording is stopped and no further samples are recorded. Sentinels are added to indicate that the sample-recording was stopped due to user configuration.
When the user clears the sample history for an LSP, the recorded sample history is deleted completely from the memory. To completely remove the recording behavior, the user must un-configure the sample recording followed by clearing the sample-record history.