The Label of the ASAP Communication Parameter Gets Corrupted if the Label Size Is More Than 64 Characters (Doc ID 1902233.1)

Last updated on JULY 04, 2014

Applies to:

Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.

Symptoms

We have problems in recovering some communication parameters, even if the length of their name does not exceed 80 characters.

I'm using the self-generated method in the connection class:

  public String getParameter(String arg0) {

  return this.getCommParam(arg0);

  }

What we see in the file JNEP diagnostic are "dirty" characters.

For example in tbl_comm_param I'm able to select the parameter by name NOTIFY_SERVED_USER_ON_OUTBOUND_CALL_ACTION_ADD_ADVANCED_STAR_PKG_INTL with length equal to 69

In JNEP diagnostic file I can see the following log:

NOTIFY_SERVED_USER_ON_OUTBOUND_CALL_ACTION_ADD_ADVANCED_STAR_PKG0?X = activated

The ASAP version is 7.0.2. The parameters are not printed by a custom implementation but by the superclass JProcessor, I believe with method dumpParms(). In the JNEP diag I can find the log "Communication Parameters:" and then the list of communication parameters and any with dirty characters.


As a result, I'm not able to get the parameter value if I use the param label stored in tbl_comm_param.

In the NEP diagnostic it is the same.

Adding Communication parameter NOTIFY_SERVED_USER_ON_OUTBOUND_CALL_ACTION_ADD_ADVANCED_STAR_PKG(ÑP with value activated and value hint N
Adding Communication parameter NOTIFY_SERVED_USER_ON_OUTBOUND_CALL_ACTION_ADD_ADVANCED_STAR_PKG(Ñx with value activated and value hint N




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