BAIC — Provisioning in direct mode over TCP socket

User Interfaces Release 9.1 Subscriber Provisioning Reference Manual Error messages If an error occurred in processing the request or with the format of the message, an error result code will be sent as shown below: 1. Message error="0" -> normal, request transaction was sent and processed. 2. Message error ="0" but the message content has " res error = error code number". This implies there is a problem with the content of the request message (e.g., a problem with format or value out of range). The Error code numbers are generated by the SDM. For details on the error code numbers, refer to Error Notifications in the SDM Monitoring, Maintaining, Troubleshooting-Reference Manual . 3.

Message error="10" -> Communication problem, unable to process the request transaction. Example of a Response message with an error code returned: xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> soapenv:mustUnderstand="0" xsi:type="soapenc:string" xmlns:ns1="tekelec.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">admin soapenv:mustUnderstand="0" xsi:type="soapenc:string" xmlns:ns2="tekelec.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">admin error="10" > For more details on the logic used by the SDM when generating replies and the error responses, refer to System Replies and Error Codes .

Soap service URL Specify the URL for the SOAP service, as follows: http:// :8080/axis/services/MessageService The external IP address of the SDM must be specified as the destination IP address. When sending messages, the destination IP address must be specified along with the content of the SOAP message. Provisioning in direct mode over TCP socket Using XML over a TCP connection is very similar to using the SOAP interface with two differences: 1. When connecting directly through TCP, the first request sent must be an authentication request 29 910-6701-001 Revision A, June 2013