The Notification Short Message Sent from the "Send Notification" Feature Node Is Refused by Messaging Manager with "TCAP primitive without destination SSN"
(Doc ID 1371692.1)
Last updated on DECEMBER 03, 2019
Oracle Communications Network Charging and Control - Version 4.4.0 and later Information in this document applies to any platform.
Introduction The Advanced Calling Services (ACS) Feature Node "Send Notification" can be used in a Control Plan to create and send a customized notification Short Message Service (SMS) message.
As the logic applied on the transaction traverses the Send Notification node, the notification SMS message is generated and sent to its destination : it can be an external entity like a Short Message Service Center (SMSC), but also Messaging Manager (MM)*.
In this case, the system is configured to send the notification SMS message to MM.
*MM is a product part of the Oracle Communication Network Charging and Control (NCC) product suite.
The node is configured from the SMS Screens -> Services -> ACS Service -> Control Plans
The notification SMS message sent by the Send Notification node is refused by MM with the following WARNING:
xmsTrigger(27039) WARNING: TCAP primitive without destination SSN.
The ACS Control Plan that runs the transaction logic through the Send Notification node was modified.
The following section of the eserv.config configuration file was modified.