Examples

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

Delete Stand-Alone Routing Entities

This example deletes stand-alone IMSI and MSISDN routing entities.

Request:

<deleteSubscriberRequest>
  <addressList>
    <imsi>111111111100021</imsi>
    <imsi>111111111100022</imsi>
    <msisdn>8004605520</msisdn>
  </addressList>
</deleteSubscriberRequest>

Response:

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

Delete Several Routing Entities

This example successfully deletes two stand-alone IMSI routing entities. Other IMSI values were not found and were not deleted.

Request:

<deleteSubscriberRequest>
  <addressList>
    <imsi>777777777777777</imsi>
    <imsi>111111111100001</imsi>
    <imsi>111111111100002</imsi>
    <imsi>888888888888888</imsi>
  </addressList>
</deleteSubscriberRequest>

Response:

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

Delete Routing Entities Assigned to the Same Subscriber

This example deletes IMSI and MSISDN routing entities that are assigned to the same subscriber. The example assumes that the subscriber has at least one more routing entity other than the specified values.

Request

<deleteSubscriberRequest>
  <addressList>
    <imsi>111111111100002</imsi>
    <msisdn>8004605500</msisdn>
  </addressList>
</deleteSubscriberRequest>

Response:

<ns2:sdsResult affected="2" error="0”>
</ns2:sdsResult>

Delete Last Routing Entity for a Subscriber (success)

This example successfully deletes the subscriber and all IMSI and MSISDN routing entities assigned to the subscriber. Any of the subscriber's Account ID, MSISDN or IMSI values can be specified. In this example, all of the IMSI and MSISDN values are specified even though only 1 value is required.

Request:

<deleteSubscriberRequest timeout="10" group=”y”>
  <addressList>
     <imsi>111111111100001</imsi>
     <imsi>111111111100002</imsi>
     <msisdn>8004605500</msisdn>
  </addressList>
</deleteSubscriberRequest>

Response:

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

Delete Last Routing Entity for a Subscriber (failure)

This example attempts to delete IMSI and MSISDN routing entities that are assigned to the same subscriber. The example fails because the subscriber does not have any more routing entities.

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

Request:

<deleteSubscriberRequest timeout="10">
  <addressList>
    <imsi>111111111100001</imsi>
    <imsi>111111111100002</imsi>
    <msisdn>8004605500</msisdn>
  </addressList>
</deleteSubscriberRequest>

Response:

<ns2:sdsResult description=”cannot delete the last route from subscriber"
affected="0" error="2027">
</ns2:sdsResult>

Delete a Subscriber (success)

Request:

<deleteSubscriberRequest timeout="10" group=”y”>
  <addressList>
    <accountId>80044400001234567890111112</accountId>
  </addressList>
</deleteSubscriberRequest>

Response:

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