The <deleteSubscriberResp> response returns the result of the request to delete subscriber routing entities. There is a single result that applies to all routing entities supplied. Either all subscriber and/or routing entities were successfully deleted, or no deletes are made.
If applying all of the delete changes results in no routing entities being deleted (because the database already did not contain the specified values), the NO_UPDATES error code is returned and the number of affected records is 0. If a subscriber is successfully deleted, the description field contains lists of deleted IMSI and MSISDN values.
When a routing entity does not exist, this means that the affected rows count is not incremented for that IMSI/MSISDN.
lengthInBytes
<deleteSubscriberResp [id="id"]>
[
originalXMLRequest
]
<res error="error" affected="affected" [description="description"]/>
</deleteSubscriberResp>
The parameters for all of the XML response commands are shown in XML Response Messages.
| Error Code | Description |
|---|---|
| SUCCESS | The delete request was successfully completed. |
| NO_UPDATES | The records were already deleted from the database. |
| TOO_MANY_ADDR | Too many address values supplied. |
| MISSING_PARAMETER | A mandatory parameter is missing. |
| MULTIPLE_SUBSCRIBERS | Specified parameters refer to multiple subscribers. |
| ROUTE_TYPE_MISMATCH | Standalone and subscriber routes are not allowed in same command. |
| DEL_ROUTE_NOT_PERMITTED | Cannot delete last route from subscriber. |