Policy Deny Code Issues In OCSG
(Doc ID 1405943.1)
Last updated on JULY 28, 2023
Applies to:
Oracle Communications Services Gatekeeper - Version 5.0.0 and laterInformation in this document applies to any platform.
Symptoms
OCSG is throwing unknown Policy Deny Code 44 but alarm showing application quota limit exceeded. The Policy deny Code 44 not defined in documentation. As per the documentation 14 is used for application quota limit exceeded, 7 for application request limit exceeded.
Now sending 44 for quota limit reached.
1. Testing quota using PTE with the following composed Service Contract.
<composedServiceName>SendMultimediaMessaging</composedServiceName>
<service>
<serviceTypeName>MultimediaMessaging</serviceTypeName>
<method>
<scs>com.bea.wlcp.wlng.px21.plugin.SendMessagePlugin</scs>
<methodName>sendMessage</methodName>
</method>
</service>
<startDate>2012-01-12</startDate>
<endDate>2040-01-30</endDate>
<rate>
<reqLimit>100</reqLimit>
<timePeriod>1000</timePeriod>
</rate>
<quota>
<qtaLimit>2</qtaLimit>
<days>3</days>
<limitExceedOK>false</limitExceedOK>
</quota></composedServiceContract>
Sent the 3rd MT MMS and got "Error while starting engine: A policy error occurred. Error code is '44' (POL0001)." and error message as below.
Alarm with PolicyDenyCode: 44
PolicyInfo: Application request limit exceeded, the request limit for Composed Service:SendMultimediaMessaging was reached by: default_provider app_domain1
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 |