REST Interface error RESPONSE Trouble Shooting Information for OCUDR

Asset ID:	1-75-2214042.1
Update Date:	2016-12-15
Keywords:

Solution Type Troubleshooting Sure

Solution 2214042.1 : REST Interface error RESPONSE Trouble Shooting Information for OCUDR

Applies to:

Oracle Communications User Data Repository - Version UDR 10.0 and later
Tekelec

Purpose

This Document will help the Administrator/User of "Customer Provisioning System" to take Corrective action for error codes received in Provisioning RESPONSE over REST interface

Troubleshooting Steps

What are REST Provisioning Interface Functions?

The REST provisioning interface provides following data manipulation commands:
Subscriber/Pool:

• Profile create/retrieve/modify/delete
• Profile field add/retrieve/modify/delete
• Opaque data create/retrieve/modify/delete
o Quota, State, and Dynamic Quota
• Subscriber transparent data create/retrieve/modify/delete
o Quota, State and Dynamic Quota
• Reset of a row within Subscriber Quota transparent data

How Many Maximum Simultaneous REST Connection Are Supported in OCUDR?

100

Additional References

For more information, reference the UDR REST Provisioning Interface Specification Document by selecting the appropriate release at the Oracle Help Center, Communications Industry, and then select User Data Repository. (http://docs.oracle.com/en/industries/communications/user-data-repository/index.html)

Error Scenarios

In Typical Scenario 'Customer Provisioning Server' Will Going to Send a REST REQUEST and based on REST HTTP Request ,RESPONSE is returned from OCUDR,if that RESPONSE contain the Following Errors ,Customer Can take Preventive Action so there Request are Processed Successfully Without Any Error.

Example Error Scenario-1

Request #1 from CUSTOMER PROVISIONING SERVER ----->

A subscriber is created, with MSISDN and IMSI keys. The BillingDay and Entitlement fields are set. A subscriber already exists with the given IMSI.

Request URL: POST {baseURI}/msr/sub
Request Content:
<?xml version="1.0" encoding="UTF-8"?>
<subscriber>
<field name="MSISDN">5141112223334</field>
<field name="IMSI">184126781612121</field>
<field name="BillingDay">2</field>
<field name="Entitlement">DayPass</field>
<field name="Entitlement">DayPassPlus</field>
</subscriber>

Response #1 from OCUDR <--------

The request fails. The error code indicates the key already exists.

HTTP Status Code: 400
Response Content:
<?xml version="1.0" encoding="UTF-8"?>
<error code="MSR4003">errorText</error>

MSR4003:A key is detected to be already in the system for another subscriber/pool

Corrective Action : Resend the Request from "Customer Provisioning System" by changing the value of IMSI or delete the IMSI profile in OCUDR and resend the Request from CPS

Example Error Scenario-2

Request #2 from CUSTOMER PROVISIONING SERVER ---->

A subscriber is created. The BillingDay and Entitlement fields are set. No key values are supplied.

Request URL: POST {baseURI}/msr/sub
Request Content:
<?xml version="1.0" encoding="UTF-8"?>
<subscriber>
<field name="BillingDay">2</field>
<field name="Entitlement">DayPass</field>
</subscriber>

Response #2 from OCUDR <--------

The request fails because no key values were supplied.

HTTP Status Code: 400
Response Content:
<?xml version="1.0" encoding="UTF-8"?>
<error code="MSR4004">errorText</error>

MSR4004:Unique key not found for subscriber/pool

Corrective Action : Resend the Request from "Customer Provisioning System" by adding atleast one Supported Key Value MSISDN/IMSI/AccountID/NAI

REST Error Code Description

Error Code	Description
MSR4000	Invalid content request data supplied
MSR4001	Subscriber/pool not found
MSR4002	Subscriber/pool/data field is not defined
MSR4003	A key is detected to be already in the system for another subscriber/pool
MSR4004	Unique key not found for subscriber/pool
MSR4005	Field does not support multiple values and value for field already exists
MSR4049	Data type is not defined
MSR4050	Unknown key, the key provided in the request is invalid
MSR4051	The value provided for the field is invalid
MSR4053	Subscriber/pool exist, but the field value is incorrect
MSR4055	Subscriber is a member of a pool
MSR4056	Field is not updatable
MSR4057	Request only contains one field to update
MSR4058	Data type not found
MSR4059	Data row does not exist
MSR4060	Number of pool members exceeded
MSR4061	Specified pool does not exist
MSR4062	Subscriber is not a member of the pool
MSR4063	Entity cannot be reset
MSR4064	Occurrence constraint violation
MSR4065	Field is not set
MSR4066	Field value already exists
MSR4067	Multiple matching rows found
MSR4068	Free system memory is low
MSR4069	At least one key is required
MSR4070	Operation not allowed
MSR4097	Request rejected due to system congestion
MSR4098	Provisioning is disabled
MSR4099	Unexpected server error has occurred
MSR4100	Maximum number of Subscribers in a Basic Pool has been exceeded
MSR4101	Enterprise to Basic Pool Conversion failed threshold exceeded
MSR4102	Provisioning Request Timeout, as no response was received from Remote UDR

COMMAND LOGS

REST Request/Response Can be viewed in OCUDR system after login into NO VIP GUI

Navigate to UDR->Maintenace->Command Log

they Can also be Exported to External Export Server if Configured in OCUDR

Attachments

This solution has no attachment