The processing of the U-SBR results by the DCA app
indicate that the DCA app is overly CPU-intensive. The alarm may also be the
result of the DCA app sending too many U-SBR queries per Diameter message,
which may be avoided by storing variables in the Diameter transaction context.
In both cases the business logic shall be reviewed and optimized.
If no additional congestion alarms are asserted, the
DSR Application Task may be experiencing a problem preventing it from
processing messages from its U-SBR Event Message Queue. Examine the alarm log
from
.