XML Notification Not Sent and DAP Interface (dapIF) Reports "ERROR: XML request template ID xxxx contains invalid destination URL" Message (Doc ID 1315165.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 3.1.0 and later
Information in this document applies to any platform.

Symptoms

Introduction

DAP (Data Access Pack) provides the capability to send requests to external ASPs (Application Service Provider) and optionally receive responses. Amongst other things, DAP can trigger:

It can therefore interact with external servers using XML or SOAP formatted messages.

The dapIF (DAP Interface) is responsible to accept DAP requests and triggers and handles the external communication over HTTP(S). Requests to an ASP are based on a DAP template. These originate from an ACS (Advanced Control Services) Control Plan, using the DAP ACS Feature Node:

The ASP definition configures the URL to be connected, and dapIF parses that URL to make sure it is valid before it initiates the connection.

The dapIF process is a SLEE (Service Logic Execution Environment) interface and typically uses:

Symptoms

  1. The ACS DAP Feature Node generates the HTTP(S) based DAP request to the dapIF:
    dapSendActionHandler.cc   54    dapChassisActions      received action request
    dapSendActionHandler.cc   59    dapChassisActions      creating dialogue to SLEE i/f dapIF
    ...
         acsChassisEvent.cc   69       acsChassisSLEE        actionType=1030, serviceDomain=1, eventType=DapResponseEvent, dialog=c02972a8
    ...
              acsChassis.cc 1951       acsChassisSLEE   Not ending dialog, call proc=1, num components =0, TcapDialog=-1071025936
              acsChassis.cc 1971       acsChassisSLEE   Checking for TCAP messages to send
              acsChassis.cc 2021       acsChassisSLEE   Checking for TCAP IP messages to send
              acsChassis.cc 2099       acsChassisSLEE   acsSLEEChassis_t::checkForCompletion()
              acsChassis.cc 2101       acsChassisSLEE    Dialog for TCAP is OPEN
              acsChassis.cc 2065       acsChassisSLEE   Dialog for TCAP is OPEN
  2. As it parses the URL, dapIF reports it as invalid does not send the XML or SOAP message.
    Apr 13 12:59:55.603061 dapIF(24400) ERROR: XML request template ID 51 contains invalid destination URL

    Note 1: This message will not only appear in the dapIF DEBUG log, but will also appear in the normal logging level.

    Note 2: This message is a catch all for invalid URL issues. This article focuses on one simple syntax problem that is not obvious to spot: the mandatory trailing "/".
  3. And the ACS DAP Feature Node receives an internal TCAP-ABORT, without having sent the XML or SOAP message. Depending on the Control Plan design, the ACS processing may go on.
    acsChassis.cc 568 acsChassisSLEE acsSLEEChassis_t::main--(Start)CallID=85432
    ...
    acsChassis.cc   988    acsChassisSLEE   TCAP Primitive Received
    acsChassis.cc   995    acsChassisSLEE   Recevied TCAP Primiitive: TCAP Primitive:TCAP_ABORT
    acsChassis.cc   995    acsChassisSLEE   ==============
    acsChassis.cc   995    acsChassisSLEE   (TCAP_PROTO_UNDEFINED,PROTO_UNDEFINED)
    acsChassis.cc   995    acsChassisSLEE   Abort info: U_ABORT cause(0) [ ]

    ...

Changes

The ACS DAP node generates the DAP request to the dapIF based on a DAP operation, also called a template in earlier versions of the software. This operation is linked to an ASP, which configures the end point for that template, based on the HTTP(S) URL.

  1. Firstly, this problem could occur is if the URL itself was changed in the ASP configuration:

    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