Some of the following examples are based upon previous requests. The order of the requests can be important.
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.
This example creates three new NAI routing entities and sets their destination values to the specified values. This example assumes that the host and destination values already exist.
<updateSubscriberNaiRequest timeout="10"> <naiList> <host>oracle.com</host> <user>John.Smith</user> <user>Jane.Doe</user> <user>Mike.Jones</user> </naiList> <destinationList> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_1</ltehss> <aaa>AAA_Texas</aaa> </destinationList> </updateSubscriberNaiRequest>
<ns2:sdsResult affected="3" error="0"> </ns2:sdsResult>
The result of this request is that the specified NAI routing entities are updated with specified values.
<updateSubscriberNaiRequest timeout="10"> <naiList> <host>oracle.com</host> <user>Jane.Doe</user> <user>Mike.Jones</user> </naiList> <destinationList> <ltehss>LTE_HSS_4</ltehss> <pcrf>PCRF_Ohio</pcrf> </destinationList> </updateSubscriberNaiRequest>
<ns2:sdsResult affected="2" error="0"> </ns2:sdsResult>
This example fails to update existing NAI routing entities with new destination values because the destination does not exist.
No changes are made to the database because the request failed.
<updateSubscriberNaiRequest timeout="10"> <naiList> <host>oracle.com</host> <user>Jane.Doe</user> </naiList> <destinationList> <ltehss>junk</ltehss> </destinationList> </updateSubscriberNaiRequest>
<ns2:sdsResult description=“destination not found” affected="0" error="2006"> </ns2:sdsResult>