The SES (Subscriber Event Service) Application Allows More Requests Than Its rejectLevel Parameter

(Doc ID 1388161.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version: 2.2.0 to 4.4.0 - Release: 2.2 to 4.4
Information in this document applies to any platform.


The Subscriber Event Service (SES) application enables a service provider to send text messages to roaming subscribers (both their own and foreign subscribers) when they roam in and out of their network.

In some cases, SES can also be used for "query balance" and "voucher redeem" via the XML TCAP interface.

There is a throttling parameter described in the SES technical guide which allows limiting the number of messages sent over a defined time frame to avoid overloading the other applications and/or the complete system, eventually leading to core dumps.

This parameter can be defined in eserv.config for each adapter configured for SES and is named rejectLevel - This parameter should limit the number of messages sent.

Example eserv.config section (irrelevant parts have been removed for readability) :

The eserv.config configuration file is usually located at /IN/service_packages/eserv.config

SES = {
     sesTrigger = {
         adapters = {
               xml_subscriber = {
                  rejectLevel = 300
                  rejectLevelReportPeriod = 6

SES appears as if it was ignoring this parameter, and the symptoms are obvious, SES reports in its log file a number of requests above the rejectLevel and 0 rejected ones.

Example entry in the sesTrigger (Usually found in /IN/service_packages/SES/tmp ) log file with parameter defined to 300 :

Mar 7 12:00:00.000024 sesTrigger(7528) NOTICE: XML TCAP Rate Limits: Period=60; Requests=645; Rejected=0, Unknown=0

For more information about the SES application, please refer to the SES User & Technical guide. A document describing how to download Network Charging and Control documentation is listed in the references of this document.


No particular changes cause this issue to appear.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms