Short Message Notifications Fail to be Sent With 'Internal Consistency Error: Received non-BEGIN TCAP primitive" or "TCAP_BEGIN/TCAP_UNI event received for already registered dialog/handler." Errors (Doc ID 1324214.1)

Last updated on OCTOBER 20, 2011

Applies to:

Oracle Communications Network Charging and Control - Version: 4.4.0 and later   [Release: 4.4 and later ]
Information in this document applies to any platform.

Symptoms

Short Message Notifications, that are generated on the Service Logic Controller (SLC), fail to be sent to the end subscriber and either of the following two errors are reported in the SLC's xmsTrigger log file (/IN/service_packages/XMS/tmp/xmsTrigger.log):
1.  Internal Consistency Error: Received non-BEGIN TCAP primitive (primitive type: X)

This error is thrown by the MAP (Mobile Application Part) adapter in xmsTrigger.  It implies that a Short Message (SM) event has been routed to it for processing in a Transaction Capabilities Application Part (TCAP) message that is not a TCAP BEGIN (the actual TCAP primitive received will be shown in the error in place of the "X").  A MAP Short Message should never arrive in a TCAP UNI primitive because there is no TCAP ID (TID) present in these primitive message types.  This means xmsTrigger has no destination TID to correlate a potential returnResult with.

2.  TCAP_BEGIN/TCAP_UNI event received for already registered dialog/handler.

This error is also thrown by the MAP adapter in xmsTrigger.  This error implies that a TCAP UNI or a TCAP BEGIN has arrived on a internal SLC dialog that is already open.  TCAP BEGIN and TCAP UNI messages are used to establish new internal dialogs and should never be sent over existing open dialogs.

Changes

1. Control plan changes that utilize the Send Short Message Notification (SSMN) node.

2. Changes to the eserv.config file on the SLC, specifically the XMS.macroNodes.SendShortMessageNode.tcapDestAddr parameter:
XMS = {
...
macroNodes = {
...
SendShortMessageNode = {
...
tcapDestAddr = { }
...
}
...
}
...
}

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms