My Oracle Support Banner

Design Studio Creates Broken Parameters For Dynamic Routing Network Element Templates (Doc ID 2025477.1)

Last updated on MARCH 28, 2019

Applies to:

Oracle Communications Design Studio - Version 7.2.2 and later
Information in this document applies to any platform.

Symptoms

Default values for communication parameters are not available to Connection Handler code using getCommParam for "Generic Message Based" line type.  The fault is that Design Studio creates a communication configuration that places the wrong device type in the tbl_comm_parm For Dynamic Routing Network Element Templates.

To resolve this issue, the device type (dev_type) in tbl_comm_parm needs to be changed manually from 'G' (Generic Terminal Based Connection) to 'M' (Generic Message Based Connection) for each of the parameters in the dynamic NE template.  After this change in tbl_comm_param the default values became available to Connection Handler code using getCommParam.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.