My Oracle Support Banner

Service Specific Info AVPs Are Not Present In Diameter CCR-T Request From IN SLC ( For Failure SMS ) (Doc ID 2864082.1)

Last updated on MAY 02, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.1 and later
Information in this document applies to any platform.


Given the below scenario on Network Charging and Control (NCC) 6.0.1:

- external billing engine (Online Charging System - OCS) is integrated with NCC via DCD (Diameter Charging Driver)
- Messaging Manager (MM) is responsible for delivery of SMS (Short Message Service) message
- "SUBMIT SMS" is received by xmsTrigger
- MM is opening a call in ACS (Advanced Control Services) with service_key=11 (CCS_SM_MO ACS service)
- SMCB feature node used for charging part of the call; Credit Control Request - Initial (CCR-I) sent to OCS via DCD
- OCS is responding with Result-Code=DIAMETER_CREDIT_LIMIT_REACHED in Credit Control Answer - Initial (CCA-I)
- it can be seen slee_acs debug CCR-T message is constructed here and sent to OCS via DCD, but it doesn't include Service-Specific-Info AVPs in Multiple-Service-Credit-Control(MSCC)

Expectation is that CCR-T message sent by NCC to OCS will include Service-Specific-Info AVPs in MSCC.

Is this behavior as per design, or it is a bug?


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

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