User Interfaces Release 9.1 Subscriber Provisioning Reference Manual ent=" EntityName " ns=" Namespace "/> affected="count"> 7 For XML examples of a delete request for the HLR, SIP and HSS, refer to chapter Examples of XML Templates for Subscriber Provisioning in the SDM Subscriber Provisioning – User Guide . Authentication Operation Every file loaded by the Command File Loader must absolutely contain an Authentication request, which is an Operation Type request. The XML format of the request must be as follows: System Replies and Error Codes The system replies to the XML requests by adding specific tags as follows: ... Body...
Request* The system replies to the received XML provisioning transaction using the following logic: In the case where the XML transaction is invalid due to an XML error syntax, the system parses the XML requests in the same order as received in the transaction until it detects the XML syntax error, at which point it stops parsing the transaction and sends back an XML reply that includes the following: Requests that each include the valid request* that has been parsed prior to detecting the XML syntax error, along with an error response with error code "1" to indicate that the request has been validated but has not been processed.
A last request that only includes the response error (res error) with an error code to indicate that there has been an XML parsing error. Refer to the “Error Notifications” chapter of the SDM Monitoring, Maintaining, Troubleshooting – Reference Manual for a description of each error code that can be generated by the system. 37 910-6701-001 Revision A, June 2013