Charging and Control Applications (MOSC)

MOSC Banner

Diameter: Direct Debit request USU issue

edited Mar 17, 2011 7:59PM in Charging and Control Applications (MOSC) 2 commentsAnswered ✓
Hi,

We have observed in our logic that OCSG by default uses USU in the Diameter request for chargeAmount. The XML is as below:

<Credit-Control-Request Flags="RP" AppId="4" HopByHopId="802451266" EndToEndId="597004866">

  <Session-Id>10.187.123.131;1300087078;43</Session-Id>

  <Origin-Host>10.187.123.131</Origin-Host>

  <Origin-Realm>portal.com</Origin-Realm>

  <Auth-Application-Id>4</Auth-Application-Id>

  <Destination-Realm>portal.com</Destination-Realm>

  <CC-Request-Type>4</CC-Request-Type>

  <CC-Request-Number>0</CC-Request-Number>

  <Service-Context-Id>272@portal.com</Service-Context-Id>

  <Event-Timestamp>-785601340</Event-Timestamp>

  <User-Name>default_spa</User-Name>

  <OCSG-Application-Id>default_apa</OCSG-Application-Id>

  <Subscription-Id>

    <Subscription-Id-Type>0</Subscription-Id-Type>

    <Subscription-Id-Data>009900419000</Subscription-Id-Data>

  </Subscription-Id>

  <Used-Service-Unit>

    <CC-Money>

      <Unit-Value>

        <Value-Digits>2</Value-Digits>

        <Exponent>0</Exponent>

      </Unit-Value>

      <Currency-Code>840</Currency-Code>

    </CC-Money>

  </Used-Service-Unit>

  <Requested-Action>0</Requested-Action>

  <OSCG-Reference-Code>Dummy reference code</OSCG-Reference-Code>

</Credit-Control-Request>

According to the Diameter RFC 4006 for Credit Control Application Section 6.3 Direct Debiting instead RSU should be used for specifying the units to be debited.

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