Charging and Control Applications (MOSC)

MOSC Banner

OCSG 5.0: Problem defining custom AVP configuration for Parlay X 3.0 Payment Plugin

edited Jul 6, 2011 3:18AM in Charging and Control Applications (MOSC) 14 commentsAnswered ✓
Hi

I wanted to define the passing of optional Diameter AVPs like service-id which is currently not passed in default in current Parlay X 3.0 Payment plugin.

We have followed the steps outlined in Platform Studio Developers Guide to configure the AVPs but are clueless on the specific XSD to be sued for the custom SLA.

We tried following the steps as below:

1. Created the sample AVP SLA XML for the service-id Attribute

2. Tried uploading it in OCSG using loadGlobalSLAByType:

type=payment_diameter_avp

sla=xml string

3. This gave an error that type not found

Now I have following queries:

- Is the custom SLA xsd definition for ParlayX 3.0 Payment/Diameter interface pre-loaded in OCSG?

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