1. ENUM User Guide
  2. ENUM Queries Handling
  3. vENUM Response for Enum Queries
  4. NAPTR ENUM Query Flow

3.3.2 NAPTR ENUM Query Flow

ENUM application provides flexibility to operator to perform either of the following options:
  • To provision the regex record on UDR with all required values such as RN-context, user=phone, and so on.
  • To use MNP data, where ENUM application builds regex using MNP data, domain name and service configured on UDR.
    In this case, support for only below three services is provided.
    PSNTEL ->"E2U+pstn:tel"
PSTNSIP ->"E2U+pstn:sip"
SIP ->"E2U+sip"

    Here, Regex is built using domain name and service is configured in UDR and RNContext (for PSTNTEL service only) and EXCLUDESP configured in EnumOptions MO. For Ported out numbers, MNP entity data is used.

NAPTR Query Steps

  1. Retrieve the DN from the ENUM query and lookup UDR for required DN.

    If DN is not found in UDR, then apply ENUM default action, otherwise proceed with next step.

  2. If ENUM Record is found in UDR for retrieved DN, then check if NAPTR record is present in UDR response.
    If no NAPTR record is provisioned, then apply default action, otherwise proceed with next step.

    Note:

    If service parameter is not provisioned on UDR for NAPTR then assume that NAPTR record as not found.
  3. For NAPTR record, if regex is provisioned in UDR, use the service, regex, flag, order and preference value provisioned on UDR while generating the ENUM response, otherwise go to next step.

    No validation on NAPTR field’s value is performed by ENUM MP. If flag, order or preference value is not present in NAPTR record then use value “u”, 100 and 10 respectively while generating response.

    Note:

    Operator should provision the regex record on UDR with all required values like RN-context, user-phone. ENUM MP on VENUM does not perform validation on NAPTR record values. The NAPTR record values is used in response as it is provisioned on UDR.
  4. If regex value is not present, then use domain name, service, flag, order and preference value, RN provisioned on UDR and build regex values to generate ENUM response.

    Note:

    • If NAPTR’s regex is configured in UDR for ported out number, then provide ‘RN’ in the NAPTR Regex for that number in UDR.
    • For ENUM queries, if NAPTR record is not present in UDR, then the default NAPTR profile data is sent in response (if configured in EnumOption MO). NS domain information is not sent in response.