My Oracle Support Banner

Unable To Pass Correct Value For AVP 3GPP-MS-Timezone Through Custom SLAs In OCSG5.0 (Doc ID 1276519.1)

Last updated on JUNE 25, 2018

Applies to:

Oracle Communications Services Gatekeeper - Version: 5.0.0 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Symptoms

Trying to pass the Diameter AVP 3GPP-MS-TimeZone through custom SLAs, but instead of value 8000(which is set as the default value in the custom SLA XML file), it is being sent as 38303030.

Example of custom SLA:
<avpAttribute code="23" vendorId="10415" name="3GPP-MS-TimeZone" type="String" flag="1"></avpAttribute>
<avpValue avpName="3GPP-MS-TimeZone" defaultValue="8000"/>

The value sent in the Diameter Credit-ControlRequest:
AVP: Secondary-Charging-Collection-Function-Name(23) l=16 f=VM- vnd=TGPP val=38303030

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Cause
  Solution
  References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.