SIP UE Registration with AS

Scenario

A SIP User Equipment (UE) is registered with an Application Server (AS).

Background Information

• The UE may belong to a public or a private network and AS belongs to a core network.
• The
  Unable to show "metadata-from": No such page "_space_variables"
   is intermediary between the UE and the AS in the core network.
• The UE is pre configured with one or more
  Unable to show "metadata-from": No such page "_space_variables"
  addresses.
• The
  Unable to show "metadata-from": No such page "_space_variables"
  protects core network from harmful attacks and high traffic levels.
• The
  Unable to show "metadata-from": No such page "_space_variables"
  authenticates and ensures only registered subscribers or UE's access the service.
• The
  Unable to show "metadata-from": No such page "_space_variables"
  provides facilities for protocol repair and verification.
• The
  Unable to show "metadata-from": No such page "_space_variables"
  routes the UE registration request to an appropriate AS.

Description

• When the UE contacts the
  Unable to show "metadata-from": No such page "_space_variables"
  and the UE is unable to authenticate with the AS, the
  Unable to show "metadata-from": No such page "_space_variables"
  rejects the UEs request for service.
• If the UE is able to authenticate with the AS, the
  Unable to show "metadata-from": No such page "_space_variables"
  recognizes the UE and allocates the resources for that UE.

SIP UE Registration with AS