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 successfully reads three NAI routing entities.
<readSubscriberNaiRequest> <naiList> <host>oracle.com</host> <user>John.Smith</user> <user>Jane.Doe</user> <user>Mike.Jones</user> </naiList> </readSubscriberNaiRequest>
<ns3:readSubscriberNaiResponse> <result affected="3" error="0"> </result> <resultSet> <nai host=”oracle.com” user=”John.Smith”> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_1</ltehss> <aaa>AAA_Texas</aaa> </nai> <nai host=”oracle.com” user=”Jane.Doe”> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_4</ltehss> <pcrf>PCRF_Ohio</pcrf> <aaa>AAA_Texas</aaa> </nai> <nai host=”oracle.com” user=”Mike.Jones”> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_4</ltehss> <pcrf>PCRF_Ohio</pcrf> <aaa>AAA_Texas</aaa> </nai> </resultSet> </ns3:readSubscriberNaiResponse>
This example successfully reads two NAI routing entities. Other NAI values are not found.
<readSubscriberNaiRequest> <naiList> <host>oracle.com</host> <user>John.Smith</user> <user>Ann.Jones</user> <user>Jane.Doe</user> <user>Mike.Jackson</user> </naiList> </readSubscriberNaiRequest>
<ns3:readSubscriberNaiResponse> <result affected="2" error="0"> </result> <resultSet> <nai host=”oracle.com” user=”John.Smith”> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_1</ltehss> <aaa>AAA_Texas</aaa> </nai> <nai host=”oracle.com” user=”Jane.Doe”> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_4</ltehss> <pcrf>PCRF_OHIO</pcrf> <aaa>AAA_Texas</aaa> </nai> </resultSet> </ns3:readSubscriberNaiResponse>
This example fails because no NAI subscribers are found.
<readSubscriberNaiRequest> <naiList> <host>oracle.com</host> <user>Kevin.Smith</user> <user>John.Doe</user> </naiList> </readSubscriberNaiRequest>
<ns3:readSubscriberNaiResponse> <result description=”nai not found” affected="0" error="2009"> </result> </ns3:readSubscriberNaiResponse>