SLPIT Segmentation Fault Upon Reception Of A CapConnectSMS
(Doc ID 2016031.1)
Last updated on MARCH 08, 2019
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.1 to 5.0.1 [Release 5.0]Information in this document applies to any platform.
Symptoms
The Service Logic Program Instance Tester (SLPIT) utility, used to simulate (among others) Customised Applications for Mobile networks Enhanced Logic (CAMEL) traffic by connecting straight to the SLEE, produces a segmentation fault upon reception of a CapConnectSMS.
SLPIT should properly accept and process the CapConnectSMS.
The typical scenario involves the CAP3 SMS Gateway (CAPGW) interface, which translates CAMEL Application Part (CAP) Short Message Service (SMS) signaling into non-SMS CAP messages that the Advanced Calling Services (ACS) application understands and requires.
The Oracle Communications Network Charging and Control CAP3 SMS Gateway (capgw) is a SLEE application that translates CAP v3 SMS operations to the equivalent CAP non-SMS operations used by Advanced Control Services ACS.
The typical call flow that would reveal this problem is as follows :
A typical SLPIT script that would implement that scenario would be :
define call 001
{
CLI ?= (0) "<MSISDN>" numberplan 1
DN ?= (0) "<MSISDN>" numberplan 1
send {
initialDpSms
callingPartyNumber CLI
destinationSubscriberNumber DN
mscAddr (0) "<MSC ADDR>"
}
receive {
requestReportSMSEvent
connectSMS
}
send {
eventReportSMS
eventTypeSMS smsSubmitted
}
}
startcall 001 using once
The segmentation fault crashes the slpit utility and a core file is left behind.
Changes
Starting using CAMEL for SMS messages.
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 |
| Changes |
| Cause |
| Solution |
| References |