| Oracle® Communications Subscriber Database Server Provisioning Interface Release 8.4 F12314 |
|
![]() Previous |
![]() Next |
Below are examples of how to use the
<readDomain> request and likely response.
Read Domain
This example successfully reads 3 Domain Identifiers.
<readDomain ent=”subscriberRouting” ns=”dsr” id=”101”> <domain>tekelec.com</domain> <domain>oracle.com</domain> <domain>cgbu-oracle.com</domain> </readDomain>
<readDomainResp id=”101”>
<res error=”0” affected=”3”/>
<rset>
<domain=”tekelec.com">
<imshss>IMS_HSS_1</imshss>
<ltehss>LTE_HSS_1</ltehss>
<aaa>AAA_Texas</aaa>
</domain>
<domain=”oracle.com">
<imshss>IMS_HSS_1</imshss>
<ltehss>LTE_HSS_4</ltehss>
<pcrf>PCRF_Ohio</pcrf>
<aaa>AAA_Texas</aaa>
</domain>
<domain=”cgbu-oracle.com">
<imshss>IMS_HSS_1</imshss>
<ltehss>LTE_HSS_4</ltehss>
<pcrf>PCRF_Ohio</pcrf>
<aaa>AAA_Texas</aaa>
</domain>
</rset>
</readDomainResp>
Read Domain
This example successfully reads 2 Domain Identifiers, but other domain identifier is not found.
<readDomain ent=”subscriberRouting” ns=”dsr” id=”102”> <domain>tekelec.com</domain> <domain>oracle.com</domain> </readDomain>
<readDomainResp id=”102”>
<res error=”0” affected=”2”/>
<rset>
<domain=”tekelec.com">
<imshss>IMS_HSS_1</imshss>
<ltehss>LTE_HSS_1</ltehss>
<aaa>AAA_Texas</aaa>
</domain>
<domain=”oracle.com">
<imshss>IMS_HSS_1</imshss>
<ltehss>LTE_HSS_4</ltehss>
<pcrf>PCRF_Ohio</pcrf>
<aaa>AAA_Texas</aaa>
</domain>
</rset>
</readDomainResp>
Read Domain (Failure)
This example fails because no Domain Identifiers are found.
<readDomain ent=”subscriberRouting” ns=”dsr” id=”103”> <domain>tekelec.com</domain> <domain>oracle.com</domain> <domain>cgbu-oracle.com</domain> </readDomain>
<readDomainResp id=”103”> <res error=”2032” affected=”0” description=”domain id not found” /> </readDomainResp>