TCAP Handover Node Missing Application-Context-Name Parameter in TCAP TC-BEGIN, Resulting in RAP Disconnect

(Doc ID 1377448.1)

Last updated on FEBRUARY 06, 2012

Applies to:

Oracle Communications Network Charging and Control - Version: 4.0.0 and later   [Release: 4.0.0 and later ]
Oracle Communications Network Charging and Control - Version: 2.2.0 to 4.3.0   [Release: 2.2 to 4.3]
Information in this document applies to any platform.

Symptoms


Overview:

Definitions:
  • INAP : Intelligent Network Application Part
  • CAMEL: Customized Applications for Mobile Networks Enhanced Logic
  • IDP : Initial Detection Point
  • TCAP : Transaction Capabilities Application Part
  • ACS : Advanced Calling Services

ACS "TCAP Handover" Feature Node:


Principle:

The TCAP Handover constructs an INAP/CAMEL(IDP) message encapsulated in a TCAP(TC-BEGIN) based on the existing ACS context. It then sends this TC_BEGIN(IDP) message to an external network entity through the TCAP interface.

The following IDP parameters can be configured in the node to use a specific ACS termination number or buffer:
  • Calling Party Number
  • Called Party Number
  • Redirecting Party ID
  • Location Number
  • Additional Calling Party Number
It is important to understand that:
  1. All other fields in the constructed IDP (INAP layer) are copied from the calling information of the original call.
  2. The TCAP layer of the constructed message is entirely based on the original message, and is build based on TCAP values of the incoming message

There is a known problem in the Network Charging and Control (NCC) product with the TCAP hand-over node. The message is rejected due to a missing application-context-name parameter in the TCAP layer of the message.

The new created IDP, encapsulated in a TC-BEGIN message is forwarded, but could for instance be rejected by the Re-originating Application (RAP) (example: call forward scenario).

Example from decoded trace:

Original IDP

begin
  Source Transaction ID
     Transaction Id: 6A0001EE
   oid: 0.0.17.773.1.1.1 (id-as-dialogue)
   dialogueRequest
     Padding: 7
     protocol-version: 80 (version1)
       1... .... = version1: True
     application-context-name: 0.4.0.0.1.0.50.1
(CAP-v2-gsmSSF-to-gsmSCF-AC)
   components: 1 item


New IDP

begin
   Source Transaction ID
     Transaction Id: 6A0001EE
   components: 1 item


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