Jump to: navigation, search

Route Unavailable Wakeup

Return to Supplement Table of Contents


The Problem: Previously, when both Resource Managers (RMs) were marked offline, the MCP waited until the value of transport.routerecoverytime had expired, then tried the RMs again. The result was an unnecessary delay.

The Solution: Now, if both RMs are marked offline (i.e., "this route is unavailable"), MCP ignores the route transport.routerecoverytime setting (default=30 seconds) and immediately tries again, one RM at a time.

The Technical Description: The Route Unavailable Wakeup feature controls the availability of static route groups and DNS SRV domains. "Unavailable" is a self-explanatory state, except that it may not always be true, or not true yet. When enabled (the recommended—and default—setting) this feature ignores both the RM's state of "unavailability," and the pre-set route recovery wait time, no matter what value either holds.

Enable and disable this feature by setting the configuration options sip.transport.unavailablewakeup and transport.unavailablewakeup:

Option: sip.transport.unavailablewakeup
Application: Resource Manager
Section: proxy
Valid values: true (default and recommended setting) or false
Takes effect: After restart.
This option affects Resource Manager for all SIP requests, and mostly commonly applies to requests of a SIP Server that was configured using the DNS SRV domain.

Option: sip.transport.unavailablewakeup
Application: Media Control Platform
Section: vrmrecorder
Valid values: true (default and recommended setting) or false
Takes effect: After restart.
This option affects Media Control Platform for SIP requests for third-party recording only.

Option: transport.unavailablewakeup (Note: No "sip" in this option name)
Application: Media Control Platform
Section: sip
Valid values: true (default and recommended setting) or false
Takes effect: After restart.
This option affects Media Control Platform for all SIP requests except third-party recording.

For All Three Options:
  • Set to true to enable (when one or more static route groups, or one or more DNS SRV domains, are also configured; and only if all the resources are unavailable when a new request is received). All destinations corresponding to the static route group(s) or DNS SRV domain(s) are marked available for new requests, before sip.transport.routerecoverytime expires.
    (Previously, they were unavailable until after sip.transport.routerecoverytime expired.)
  • Set to false to disable this feature. All destinations corresponding the static route group(s) or DNS SRV domain(s) are marked unavailable, and they remain unavailable until after sip.transport.routerecoverytime expires.

How are these options different from each other? They specify where the Unavailable Wakeup functionality is enabled—and that is determined by which of the parameters is set.

  • If the parameter is set in the vrmrecorder section, then it applies to third party recording requests.
  • If the parameter is set in the sip section, then it applies to other SIP requests.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on August 28, 2014, at 13:32.