ESMPP Unable to Support Over 30 Concurrent SMPP+ Messages

(Doc ID 2392393.1)

Last updated on MAY 09, 2018

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 to 6.0.1 [Release 6.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Convergent Charging Controller (OC3C), the optional component Enhanced Short Message Fee Deduction (ESMPP) component is available as an interface to Short Message Fee Deduction (SMPP+) protocol compliant Short Message Service Centers (SMSCs).

ESMPP acts as a gateway between SMPP+ and the internal Intelligent Network Application Part (INAP) protocol used by Advanced Control Services (ACS) when triggering service logic configured in Control Plans (CPs).

An Enhancement was made to ESMPP which allowed ESMPP to act as a client and initiate connections to an SMSC.  The details of this enhancement are documented in Note 2319799.1.

Due to pre-existing bug in ESMPP along with an oversight in the Enhancement,  ESMPP can not support over 30 concurrent SMPP+ messages and will fail with the following alarm:

Apr 20 12:35:45.899618 esmpp(25579) WARNING: {1091105} Maximum number of concurrent transactions (30) exceeded. Rejecting transaction <Transaction ID>, MSISDN: <MSISDN>

It is not possible to change this limit and depending on the latency of upstream processes, could severely impact performance.

Changes

 

Cause

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