1. ENUM User Guide
  2. ENUM Queries Handling
  3. vENUM Response for Enum Queries
  4. Default ENUM Profile

3.3.5 Default ENUM Profile

The section provides the default values on ENUM MP for the optional ENUM Domain Name System (DNS) resource record fields on User Deposit Repository (UDR).

A default ENUM profile is allowed in the ENUMOPTS table on ENUM MP with the following default values:
  • Default Congestion Notification = yes

    Note:

    Traffic above 5k is not accepted when Congestion Notification is set to "No".
  • Max Data Networking (DN) Digits = 15
  • Default Regex, Default flag and Default Service parameters must be provided for Default Name Authority Pointer (NAPTR) profile.
  • Default Profile Order (DPODR) = 100 (Hard coded)
  • Default Profile Preference (DPPREF) = 10 (Hard coded)
  • Default Network Server Domain parameter must be provisioned for Default NS profile.
  • CNAME default profile cannot be provisioned. In case of CNAME query, NXDOMAIN error is sent in the ENUM response.
The default ENUM profile is used by ENUM MP to generate ENUM responses for following scenarios:
  • If DN is not found in individual DN or DN range subscriber profile table.
  • If an ENUM profile record appropriate for the DN in incoming ENUM query (NAPTR, NS, CNAME) is associated neither with individual DN or DN range subscriber profile nor with MNP entity data.
The following rules are followed to generate ENUM responses during above scenarios:
  • In case of query type and default profile type mismatch, RCODE 3(Non-Existent Domain) is sent to the client.
  • In case they are matched, correct response with RCODE 0 is sent to the client.

If QTYPE is CNAME, then send an ENUM error response message with RCODE=3 (Non-Existent Domain).