CAP3GPRS Crashes when Decoding the ChargingID Field
(Doc ID 2013955.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (OCNCC or NCC), the Customized Applications for Mobile networks Enhanced Logic (CAMEL) Application Part version 3 General Packet Radio Service (CAP3GPRS) gateway randomly crashes when decoding the ChargingID parameter upon receiving the Initial Detection Point (IDP) message using Extended UnitData (XUDT) as the Message Type.
Details from cap3GprsControlAgent.log file:
- User Datagram Protocol (UDP) -based Data Transfer Protocol (UDT) message - used by Signalling Connection Control Part (SCCP) to send data in connectionless mode using connectionless protocol Class 0 and Class 1. UDT messages are commonly used for Transaction Capabilities Application Part (TCAP) communication within Intelligent Network (IN) services. In Global System for Mobile Communications (GSM) cellular networks, UDT messages are used by the Mobile Application Part (MAP) protocol to send its messages.
- XUDT - Used by SCCP to transmit data with optional parameters, using connectionless classes 0 and 1.
- Signalling Connection Control Part (SCCP) - SCCP is a network layer protocol that provides extended routing, flow control, segmentation, connection-orientation, and error correction facilities in Signaling System 7 (SS7) telecommunications networks. SCCP is defined in International Telecommunication Union - Telecommunication Standardization Sector (ITU-T) recommendations Q.711-Q.716 [58–63] and for North American markets in American National Standards Institute (ANSI) T1.112 .
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