6.1.1 Configuring ENUM for UDR

Configuring ENUM feature for UDR involves adding vENUM MP(s) to UDR and then configuring UDR on the ComAgent server.

Assumptions:
  • The user is aware of UDR and ComAgent functionality.
  • UDR is already installed, and UDR topology is already configured.
Perform the following steps to configure ENUM for UDR:
  1. Add details about the vENUM MP on the ComAgent Remote Servers screen as a client. Navigate to Communication Agent, select Configuration, select Remote Servers, and click Insert on an active OCUDR NOAMP.
  2. Select the OCUDR server group from the Available Local Server Groups that need to communicate with vENUM MP.
  3. From the active OCUDR GUI, navigate to Communication Agent, select Maintenance, select Connection Status and verify if the connection is InService.
  4. From the active OCUDR GUI, navigate to Communication Agent, select Maintenance, select Routed Services Status and verify if the STPDbSvc status is Normal.
  5. From an active DSR NOAM, navigate to Communication Agent, select Configuration, select Remote Servers, and click Insert.
  6. Add the UDR NO IP in the ComAgent Remote Server screen as a Server.
  7. Select the STP MP server group from the Local SG that needs to communicate with UDR.
  8. Also, add the Standby and DR NOs to the Local SG.
  9. Navigate to Communication Agent, select Configuration, select Connection Groups, select STPSvcGroup and click Edit.
  10. Add all available UDR NO servers.
  11. Navigate to Communication Agent, select Maintenance, then Connection Status, then the server name, and check the connection status.
Output: UDR Configuration: SOAP Provisioning Request for MSISDN

Steps to Enable ENUM Feature on UDR:

Enable ENUM feature on UDR by running the enableEnumSec loader on the Active NOAM Server console. Follow the below steps:
  1. Go to the path: /usr/TKLC/udr/prod/maint/loaders/upgrade
  2. On the path, run the enableENUMSec script.

For Subscriber data, user must configure Subscriber first and then add or attach Entity Type as ENUM with that Subscriber.

The following snippet provides an example of provisioning Subscriber data with the Entity Type as ENUM.

Subscriber Profile:
<subscriber>
    <field name="MSISDN">5555555555</field>
    <field name="CLDBL">1</field>
    <field name="CLNBL">1</field>
    <field name="PType">1</field>
    <field name="ASD">abcd</field>
    <field name="SPRNID"/>"685477777"</field>
    <field name="GRNID"/>12000"</field>
<![CDATA[<?xml version="1.0" encoding="UTF-8"?>
    <ENUM ID="ENUM">
        <ns_domain>ns.abc1.com</ns_domain>
        <cname_domain>abc1.com</cname_domain>
        <naptr1_order>100</naptr1_order>
        <naptr1_pref>50</naptr1_pref>
        <naptr1_flag>u</naptr1_flag>
        <naptr1_service>E2U+sip</naptr1_service>
        <naptr1_regex>!^.*$!sip:info@example.com!</naptr1_regex>
        <naptr1_domain> </naptr1_domain>
        <naptr2_order>10</naptr2_order>
        <naptr2_pref>50</naptr2_pref>
        <naptr2_service>PSTNSIP</naptr2_service>
        <naptr2_regex> </naptr2_regex>
        <naptr2_domain>Gw3.nptrexample.com</naptr2_domain >
    </ENUM>]>
</subscriber>

The following snippet provides an example of provisioning Entity data with ENUM.

Entity data:
<MnpSPRN>
   <Type>RN</Type>
   <EDigit>685477777</EDigit>
   <RI>0</RI>
   <PC>111-222-444</PC>
   <PCDom>ansi</PCDom>
   <SSN>3</SSN>
   <SRFIMSI>111111111</SRFIMSI>
   <DigAct>INSERTENTITYID</DigAct>
   <ns_domain>ns.abc1.com</ns_domain>
   <cname_domain>abc1.com</cname_domain>
   <naptr1_order>100</naptr1_order>
   <naptr1_pref>50</naptr1_pref>
   <naptr1_flag>u</naptr1_flag>
   <naptr1_service>E2U+sip</naptr1_service>
   <naptr1_regex>!^.*$!sip:info@example.com!</naptr1_regex>
   <naptr1_domain> </naptr1_domain>
   <naptr2_order>10</naptr2_order>
   <naptr2_pref>50</naptr2_pref>
   <naptr2_service>PSTNSIP</naptr2_service>
   <naptr2_regex> </naptr2_regex>
   <naptr2_domain>Gw3.nptrexample.com</naptr2_domain>
</MnpSPRN>

The following snippet provides an example of provisioning GRN data with ENUM.

GRN data:
<MnpGRN>
        <ns_domain>ns.abc1.com</ns_domain>
        <cname_domain>abc1.com</cname_domain>
        <naptr1_order>102</naptr1_order>
        <naptr1_pref>50</naptr1_pref>
        <naptr1_flag>u</naptr1_flag>
        <naptr1_service>E2U+voicemsg:sip</naptr1_service>
        <naptr1_regex>!^.*$!tel:+1-215-555-0123!</naptr1_regex>
        <naptr1_domain>Gw3.nptrexample.com</naptr1_domain>
        <naptr2_order>101</naptr2_order>
        <naptr2_pref>51</naptr2_pref>
        <naptr2_flag>u</naptr2_flag>
        <naptr2_service>E2U+pstn:sip</naptr2_service>
        <naptr2_regex>!^.*$!sip:+1-215-555-0123;npdi@gw.example.com;user=phone!</naptr2_regex>
        <naptr2_domain>Gw3.nptrexample.com</naptr2_domain>
</MnpGRN>]]>