Configuration for UDR

5.3.2 Configuration for UDR

Configuring IDPR and MOSMS for UDR involves adding vSTP MP(s) to UDR and then configuring UDR on the ComAgent server.

Assumptions:

The user is aware of UDR and ComAgent functionality, and
UDR is already installed and UDR topology is already configured

Perform the following steps to configure IDPR and MOSMS for UDR:

Add details about the vSTP MP on the ComAgent Remote Servers screen as a client by navigating to Communication Agent, and then Configuration, and then Remote Servers and clicking Insert on an active OCUDR NOAMP.
Select the OCUDR server group from the Available Local Server Groups that needs to communicate with vSTP MP.
From the active OCUDR GUI, navigate to Communication Agent, and then Maintenance, and then Connection Status and verify connection are InService.
From the active OCUDR GUI, navigate to Communication Agent, and then Maintenance, and then Routed Services Status and verify the STPDbSvc status is Normal.
From an active DSR NOAM, navigate to Communication Agent, and then Configuration, and then Remote Servers and click Insert.
Add the UDR NO IP in the ComAgent Remote Server screen as a Server.
Select the STP MP server group from the Local SG that needs to communicate with UDR.
Also add the Standby and DR NOs to the Local SG.
Navigate to Communication Agent, and then Configuration, and then Connection Groups, select STPSvcGroup and click Edit.
Add all available UDR NO servers.
Navigate to Communication Agent, and then Maintenance, and then Connection Status, select the server name, and check the connection status.

UDR Configuration: SOAP Provisioning Request for MSISDN

Steps to Enable MNP Feature on UDR:

Enable MNP feature on UDR by running the enablevMNPSec loader on the Active NOAM Server console. Follow the below steps:

Go to the path: /usr/TKLC/udr/prod/maint/loaders/upgrade
On the path, execute the enablevMNPSec script.

Note:

To enable all the following MNP, ENUM, SPLIT, SFAPP, and DSA features together, run the following command:

"enableMNPwithSplit_Enum_SFAPP"

The following snippet provides an example of provisioning MNP data with the Type as SPRN and GRN in an individual MSISDN:

Adding GRNID:

Insert:
 
<req name="insert" resonly="y" inputType="mnpGrnId">
  <ent name="Subscriber"/>
  <set>
    <expr><attr name="GRNID"/><value val="10000"/></expr>
    <expr><attr name="MnpDataGRN"/><op value="="/>
      <cdata>&lt;![CDATA[<?xml version="1.0" encoding="UTF-8"?>
           <MnpGRN>
              <EDigit>10000</EDigit>
              <RI>1</RI>
              <PC>111-222-333</PC>
              <PCDom>ansi</PCDom>
              <SSN>3</SSN>
              <SRFIMSI>222222222</SRFIMSI>
              <DigAct>INSERTENTITYID</DigAct>
        </MnpGRN>]]&gt;
      </cdata>
      </expr>
  </set>
</req>

Adding SPRNID :

<req name="insert" resonly="y" inputType="mnpSprnId">
  <ent name="Subscriber"/>
  <set>
    <expr><attr name="SPRNID"/><value val="685477777"/></expr>
<expr>
<attr name="MnpDataSPRN"/><op value="="/>
      <cdata>&lt;![CDATA[<?xml version="1.0" encoding="UTF-8"?>
          <MnpSPRN>
              <Type>RN</Type>
              <EDigit>685477777</EDigit>
              <RI>0</RI>
              <PC>111-222-444</PC>
              <PCDom>ansi</PCDom>
              <SSN>3</SSN>
             <SRFIMSI>111111111</SRFIMSI>

Adding MNP Subscriber with SPRNID & GRNID:

<req name="insert" resonly="y" inputType="mnpSubscriber">
  <ent name="Subscriber"/>
   <set>
       <expr><attr name="MSISDN"/><value val="222222222333"/></expr>
       <expr><attr name="CLDBL"/><value val="1"/></expr>
       <expr><attr name="CLNBL"/><value val="1"/></expr>
       <expr><attr name="PType"/><value val="1"/></expr>
       <expr><attr name="ASD"/><value val="abcd"/></expr>
       <expr><attr name="SPRNID"/><value val="685477777"/></expr>
       <expr><attr name="GRNID"/><value val="10000"/></expr>
    </set>
</req>

Enabling Split feature and Self Heal feature for MNP on UDR:

Enable Split feature and self heal on UDR by running the enableSplitFeature and enableMNPwithSplit loaders on the Active NOAM Server console with the following steps:

Navigate to the /usr/TKLC/udr/prod/maint/loaders/upgrade path on the Active NOAM Server console.
Execute the enableSplitFeature and enableMNPwithSplit scripts.

Note:
There is no need to restart any of the servers after running the loader.

The following snippet shows an example of provisioning MNP data with the Type as SPRN and GRN in an individual MSISDN:

<req name="insert" resonly="y" inputType="mnpSubscriber" type=”range”>
<ent name="Subscriber"/>
<set>
<expr><attr name="MSISDN"/><value val="222222222000"/></expr>
<expr><attr name="MSISDN"/><value val="222222223000"/></expr>
<expr><attr name="CLDBL"/><value val="1"/></expr>
<expr><attr name="CLNBL"/><value val="1"/></expr>
<expr><attr name="PType"/><value val="1"/></expr>
<expr><attr name="ASD"/><value val="abcd"/></expr>
<expr><attr name="SPRNID"/><value val="685477777"/></expr>
<expr><attr name="GRNID"/><value val="10000"/></expr>
<expr><attr name="Split"/><value val="1"/></expr>

</set>
</req>

The enableSplitFeature Feature Flag Behavior

The enableSplitFeature Feature flag behavior for different scenarios is described as follows:

When the Feature flag is enabled:
- When no value is set: By default Split field with value 1 is added to subscriber profile.
- Split field value is 0: Subscriber profile with Split field value 0 (non splitable range) is inserted.
- Split field value is 1: Subscriber profile with Split field value 1 is inserted.
When the Feature flag is disabled:
- When no value is set: Subscriber profile will not have split field.
- Split Field with value is 1: Create or Update requests are rejected with invalid XML error message.
- Split Field with value is 0: Create or Update requests are rejected with invalid XML error message.