Charging and Control Applications (MOSC)

MOSC Banner

how do they get the sessionId of a request that is not going to reach any plugin ?

edited Apr 13, 2016 5:32AM in Charging and Control Applications (MOSC) 1 commentAnswered

Customer is using OCSG 5.1 OneAPI for Payment Services. For Prepaid Customers OCSG is connected to a Diameter based charging system using the payment plugin, the response of a Payment API is well constructed.

However, for Postpaid Customers OCSG is not connected to any plugin on the southbound. OCSG customizations ensure that a CDR is explicitly written to OCSG database and later CDRs processed by the client. The response of such a Payment API request is *missing* the ResourceURL. So, decided to manually construct it.

From visible investigation on the structure of this ResourceURL response parameter they have noticed that it is made up of RequestURI+"/"+SessionId+"-"+Timestamp in millisec. Is that correct ? If so, how do they get the sessionId of a request that is not going to reach any plugin ?

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center