Charging and Control Applications (MOSC)

MOSC Banner

Translating Diameter Ro result codes to Payment webservice faults

edited Jun 29, 2018 3:57PM in Charging and Control Applications (MOSC) 5 commentsAnswered
 I am unable to translate diameter Ro server's result code to payment communication service faults. Specifically i want the web service caller to know about following conditions:

// Diameter result codes

 DIAMETER_USER_UNKNOWN = 5030  //in case of post-paid user
 DIAMETER_CREDIT_LIMIT_REACHED = 4012   //pre-paid account limit reached
 DIAMETER_END_USER_SERVICE_DENIED = 4010 //

But in all of above cases payment communication service throws fault with PAYMENT00001 or PAYMENT00002. At least there should be some distinction at web service caller end either by different code (which seems difficult due to parlayx compliance) or by error message.

Any workaround to this? Thanks

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center