Examples

Delete Stand-Alone Routing Entities

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

Request:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”101”>
  <imsi>111111111100021</imsi>
  <imsi>111111111100022</imsi>
  <msisdn>8004605520</msisdn>
</deleteSubscriber>
Response:
deleteSubscriberResp id=”101”>
  <res error=”0” affected=”3”/>
</deleteSubscriberResp>

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:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”102”>
  <imsi>777777777777777</imsi>
  <imsi>111111111100001</imsi>
  <imsi>111111111100002</imsi>
  <imsi>888888888888888</imsi>
</deleteSubscriber>
Response:
<deleteSubscriberResp id=”102”>
  <res error=”0” affected=”2”/>
</deleteSubscriberResp>

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:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”103”>
  <imsi>111111111100002</imsi>
  <msisdn>8004605500</msisdn>
</deleteSubscriber>
Response:
<<deleteSubscriberResp id=”103”>
  <res error=”0” affected=”2”/>
</deleteSubscriberResp>

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 one value is required.

Request:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”105” 
                  timeout=”10” group=”y”>
  <imsi>111111111100001</imsi>
  <imsi>111111111100002</imsi>
  <msisdn>8004605500</msisdn>
</deleteSubscriber>
Response:
<deleteSubscriberResp id=”105”>
  <res error=”0” affected=”1”/>
</deleteSubscriberResp>

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:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”104” timeout=”10”>
  <imsi>111111111100001</imsi>
  <imsi>111111111100002</imsi>
  <msisdn>8004605500</msisdn>
</deleteSubscriber>
Response:
deleteSubscriberResp id=”104”>
  <res error=”2028” affected=”0” description=
  ”cannot delete the last route from subscriber”/>
</deleteSubscriberResp>

Delete 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, the Account ID is specified.

Request:
<deleteSubscriber ent=”subscriberRouting” ns=”dsr” id=”106” group=”y”>
  <accountId>80044400001234567890111112</accountId>
</deleteSubscriber>
Response:
<deleteSubscriberResp id=”106”>
  <res error=”0” affected=”1”/>
</deleteSubscriberResp>