View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Default Value: 600
Valid Values: Integers greater or equal to 30 and less than or equal to 2147483
Changes Take Effect: After restart
Works in conjunction with the frequency of EventReserved_2 heartbeats that accompany live calls from URS, specifying the frequency, in seconds, with which Stat Server checks virtual queues for stuck calls. Stat Server suspends checks for stuck calls if no calls are queued at any virtual queue that Stat Server monitors. Stuck calls result if a URS connection breaks when a live calls is completed. In this situation, Stat Server does not receive the EventReleased TEvent to indicate the end of the call, and Stat Server views the interaction as continuing.
Setting this option to a high value for large environments alleviates CPU load and helps to avoid situations where Stat Server inadvertently clears live calls due to network latency. In such situations, you should also consider resetting the call_kpl_time URS option, which measures the frequency of EventReserved_2 heartbeats, to a higher value. Small environments can set both options to relatively lower values. Also, you should be aware that setting call_kpl_time to 0 (zero) means that Stat Server will receive no EventReserved_2 events from URS. In this case, Stat Server considers all calls currently residing at the virtual queue as stuck and eliminates them from processing following the period of time specified by the check-vq-stuck-calls-frequency option. Refer to the Universal Routing Reference Manual, available on the Universal Routing page, for additional information about the call_kpl_time configuration option.
Prior to release 8.0, this functionality was not configurable. Stat Server's checks for stuck calls was internally hard-coded at 60 seconds. Beginning with the 8.0 release, the default for this option, whether explicitly set or not, is 600 seconds.
Draft Option
No draft option