Insert Subscribers Examples

Below are examples of how to use the <insertSubscriberrequest> request and likely response. Some of these examples are based on previous requests; therefore, the order of the requests could be important.

These examples show the SDS provisioning request and response contents that are stored within the <soapenv:Body> or <SOAP-ENV:Body> tags. See the Start Transaction Examples for examples of the entire SOAP request/response text.

Insert new Add Stand-Alone Routing Entities (Success)

This example inserts new stand-alone IMSI and MSISDN routing entities and sets their destination values to the specified values.

The result of this request is:

New IMSI and MSISDN routing entities are created.
All of the destination values for each routing entity are set to specified values.

Request:

<insertSubscriberRequest>
          <insertAddressList>
             <imsi>111111111100001</imsi>
             <imsi>111111111100002</imsi>
             <imsi>111111111100003</imsi>
             <msisdn>8004605500</msisdn>
             <msisdn>8004605503</msisdn>
          </insertAddressList>
          <destinationList>
             <ltehss>LTE_HSS_1</ltehss>
          </destinationList>
        </insertSubscriberRequest>

Result:

<ns2:sdsResult affected="5" error="0" 
</ns2:sdsResult>

Insert Existing Stand-Alone Routing Entities with Different Destinations Failure

This example inserts existing stand-alone IMSI and MSISDN routing entities with new destination values.

This request will fail with error code 1014 and the IMSI and MSISDN routing entities are not updates with the specified values.

Request:

<insertSubscriberRequest>
  <insertAddressList>
    <imsi>111111111100001</imsi>
    <imsi>111111111100002</imsi>
    <imsi>111111111100003</imsi>
    <msisdn>8004605500</msisdn>
  </insertAddressList>
  <destinationList>
    <ltehss>LTE_HSS_4</ltehss>
    <aaa>AAA_4</aaa>
  </destinationList>
</insertSubscriberRequest>

Result:

<ns2:sdsResult affected="0" error="1014"
</ns2:sdsResult>

Create Subscriber Using Existing Routing Entities (Success)

This example inserts a subscriber using new routing entities that all have the same destination values.

After this request is completed:

A new subscriber is created and all of the routing entities are assigned to that subscriber
A new subscriber is created with the specified Account ID, IMSI, and MSISDN values
New IMSI and MSISDN routing entities are created with the specified destinations

Request:

<insertSubscriberRequest group=”y”>
  <insertAddressList>
     <accountID>11111222223333344444555556</accountId.
     <imsi>111111111100001</imsi>
     <imsi>111111111100002</imsi>
     <msisdn>8004605500</msisdn>
  </insertAddressList>
  <destinationList>
  </destinationList>
      <ltehss>LTE_HSS_4</ltehhs>
      <aaa>AAA_4</aaa>
  <destinationList>
</insertSubscriberRequest>

Result:

<ns2:sdsResult affected="1" error="0">
</ns2:sdsResult>

Create Subscriber Using New Routing Entities without Destination (Failure)

This example fails when creating a subscriber using new routing entities without specifying the destination values.

No changes are made to the database because the request failed.

Request:

<insertSubscriberRequest group=”y”>
           <insertAddressList>
             <accountId>1111122222</accountId>
             <imsi>333333333300093</imsi>
             <imsi>333333333300094</imsi>
             <msisdn>9198675399</msisdn>
    </insertAddressList>
    <destinationList>
    </destinationList>
 </insertSubscriberRequest>

Result:

<ns2:sdsResult affected="0" error="2013" description= 
”at least one destination must be specified”>
</ns2:sdsResult>

Create Subscriber Using Existing Routing Entities (Failure)

This example inserts a subscriber using existing routing entities.

The result of this request is that the request fails with error code 1014.

Request:

<insertSubscriberRequest group=”y”>
           <insertAddressList>
             <imsi>111111111100001</imsi>
             <imsi>111111111100002</imsi>
             <msisdn>8004605500</msisdn>
         </insertAddressList>
         <destinationList>
            <ltehss>LTE_HSS_4</ltehss>
            <aaa>AAA_4</aaa>
         </destinationList>
        </insertSubscriberRequest>

Result:

<ns2:sdsResult affected="0" error="1014">
</ns2:sdsResult>

Add Account ID to Existing Subscriber (Failure)

This example adds an Account ID to an existing subscriber. Any of the subscriber IMSI or MSISDN values can be used. For this example, the MSISDN value is used.

The result of this request is that the request fails with error code 1014.

Request:

<insertSubscriberRequest group=”y”>
  <insertAddressList>
    <accountId>80044400001234567890111112</accountId>
    <msisdn>8004605500</msisdn>
  </insertAddressList>
  <destinationList>
  </destinationList>
</insertSubscriberRequest>

Result:

<ns2:sdsResult affected="0" error="1014">
</ns2:sdsResult>

Modify Destinations for Existing Subscriber (Failure)

This example modifies one of the destination values for an existing subscriber. Any of the subscriber's IMSI, MSISDN or Account ID values can be used. For this example, an IMSI value is used.

The result of this request is that the request fails with error code 1014.

Request:

<insertSubscriberRequest>
  <insertAddressList>
    <imsi>111111111100002</imsi>
   </insertaddressList>
   <destinationList>
     <ltehss>LTE_HSS_99</ltehss>
   </destinationList>
</insertSubscriberRequest>

Response:

<ns2:sdsResult affected="0" error="1014"
</ns2:sdsResult>