CAP3_GW Always Retuns ConnectSMS Instead of ContinueSMS for InitialDPSMS
(Doc ID 2886659.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.5.0.0 [Release 6.0 to 12.0.0]Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.5.0.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 12.0.5.0, the Customized Applications for Mobile Network Enhanced Logic (CAMEL) Application Part 3 Gateway (CAP3_GW or capgw) process never returns a Continue Short Message Service (ContinueSMS) back to the network. Even if all the criteria is met for a ContinueSMS to be returned, a ConnectSMS is returned instead.
If debug is enabled in Advanced Control Services (ACS or slee_acs), the following lines can be observed:
The capgw process itself only converts a Connect to a ConnectSMS and a Continue to a ContinueSMS. It cannot convert a Connect to a ContinueSMS or a Continue to a ConnectSMS.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |