Basic Service Availability - DNS

Scenario

The 

Background Information

• The Integrated Access Device (IAD) is registered with an Application Server (AS).
• The AS is protected by an
  Unable to show "metadata-from": No such page "_space_variables"
  . The IAD discovers the
  Unable to show "metadata-from": No such page "_space_variables"
  via DNS resolution and the
  Unable to show "metadata-from": No such page "_space_variables"
  discovers the AS by pre-configured routing or external DB dip (e.g. ENUM).
• Once registered, the IAD communicates with a specific
  Unable to show "metadata-from": No such page "_space_variables"
  , and the
  Unable to show "metadata-from": No such page "_space_variables"
  forwards requests to the specific AS (address was stored during registration).
• For calls terminating to the IAD, the IADs register their AORs.
• IAD has been registered by two paths and can afford for one path to fail and still receive service on the other, when it supports outbound. In a normal scenario where the IAD registers through one path and is unable to refresh the register, it moves on to an alternate
  Unable to show "metadata-from": No such page "_space_variables"
  from DNS.

Description

Basic Service Availability- DNS

1. The IAD is configured with a FQDN identifying a set of
   Unable to show "metadata-from": No such page "_space_variables"
   s.
2. The DNS supplies multiple
   Unable to show "metadata-from": No such page "_space_variables"
   IP addresses (local, remote or a combination of both).
3. Basic geo-redundancy and load balancing between the
   Unable to show "metadata-from": No such page "_space_variables"
   s are enabled. With geo-redundancy, if an
   Unable to show "metadata-from": No such page "_space_variables"
   fails, the IAD re-registers through a different path.