call.sipsessioncleanupwait
How to treat leftover calls.
When the Voice Browser service loses communication with the Telephony Session service, it cannot be instructed to terminate a call session when the caller disconnects the call. This may lead to loss of a browser instance if the Telephony Session service drops too many calls. The value assigned to this service property determines how the Voice Browser service handles a leftover call that the Telephony Session service appears to have dropped:
- -1—The loss of communication is ignored and ongoing calls continue. Caller attempts to disconnect can lead to sustained loss of a browser instance.
- 0 (internal default)—The active call is disconnected for clean up immediately.
- an integer value (minutes)—The active call is disconnected for clean up after the specified number of minutes if the Telephony Session service does not send an UPDATE in the interim.
When the value is 0 or a positive integer, active calls may last an additional grace period of up to ten minutes, as this is the maximum interval allowed between UPDATE messages from the Telephony Session service to the Voice Browser service.
For example, if the Telephony Session service fails five minutes after sending the last UPDATE, the Voice Browser service waits an additional five minutes before it misses the next expected UPDATE and begins counting down the call.sipsessioncleanupwait period.
