To administer the CGIN resource adaptor entity, set the CGIN RA’s configuration properties.

For example:

$rhino-console> updateraentityconfigproperties cginra local-sccp-address=auto

Most configuration properties may be changed at any time, and will take immediate effect if the resource adaptor entity is active. A few properties, such as the type of TCAP stack used, will not take immediate effect if changed while the resource adaptor entity is active. In this case, an alarm will be raised to warn that changes will only take effect when the entity is next activated.

The RA has a set of universal properties that apply to all CGIN RA entities, and stack-specific properties that depend on the stack that a particular entity is using:

Information on specific configuration properties for each TCAP stack is available for:

For universal configuration properties, see below.

Universal configuration properties

These are the CGIN RA universal configuration parameters:

Parameter Default Value Usage and description

Short name of the TCAP stack to use. Can be one of

  • ocss7 - for the OpenCloud OCSS7 TCAP stack

  • signalware - for the Signalware TCAP stack

  • tcapsim - for the simulated TCAP stack.

Note Changes to this property will only take effect when the entity is next activated.

The list of protocols enabled in the RA; for example:


The default dialog activity timeout, measured in milliseconds. This specifies the initial dialog activity timeout used for newly created dialogs.


The default TCAP Invoke Timeout, measured in milliseconds. This specifies the invoke timeout for operations where the service has not provided an invoke timeout value.


The TCAP variant to use: ITU or ANSI


The TCAP version to assume when this cannot be automatically determined. This may be the case for:

  • Inbound dialogs where the Dialogue Portion is absent, or there is no Protocol Version field in the Dialogue Portion. For example, MAP phase 1.

  • Outbound dialogs where a TCAP version has not been specified in the issueOpenRequest API call.

Valid options are:

  • ITU TCAP: 2000

  • ANSI TCAP: 2000 and 1988

When in 1988 mode, ANSI TCAP will:

  • Use Reject-in-Response to report transaction portion problems.

  • Format Reject components using the 1988-style formatting. i.e. ParamSet instead of ParamSequence

  • Dialog.sendUserAbort will send a Response without pending components instead of an Abort package.


Used for outgoing TC-BEGIN messages if no local SCCP address is explicitly provided by an SBB.

The address should be formatted in the format that com.opencloud.slee.resources.cgin.SccpAddressParser expects.
If this property has the value auto, then the TCAP stack will automatically determine an address to use.

Note See also SCCP Address Format details.

Boolean value specifying whether to relax the BER decoding rules to allow certain types of malformed data.


For dialogs where CGIN is the dialog responder, configures the CGIN RA to accept the external application context name as a synonym for the internal application context name. Comma-separated list of values in <external OID>:<internal ASN.1> format.

<external OID> may be specified in one of two forms:

  • Where there is a TCAP dialog portion containing an application context it shall be specified as an object identifier. For example,

  • Where there is no TCAP dialog portion, and therefore no application context name, {} is used.

<internal ASN.1> can be in one of two forms:

  • When mapping to a specific internal application context, the <protocol>.<application-context-name> form is used. For example, etsi_inap_cs1.core-INAP-CS1-assist-handoff-SSP-to-SCP-AC.

  • Some protocols (notably those where no TCAP dialog portion is included in the dialog open request) may provide an interceptor to determine an appropriate application context. In these cases the <internal ASN.1> is the name of the interceptor. For example map.phase-1 or cdma.allOperationsAC.


A complete list of supported application context names for each protocol can be found in the CGIN JavaDoc in that protocol’s ApplicationContexts class documentation.

For example, ETSI INAP CS1’s supported application context names can be found in the JavaDoc for the com.opencloud.slee.resources.cgin.etsi_inap_cs1.metadata.CS1ApplicationContexts class.

Note that any underscores (_) in the application context name must be replaced with dashes (-). For example, core_INAP_CS1_assist_handoff_SSP_to_SCP_AC becomes core-INAP-CS1-assist-handoff-SSP-to-SCP-AC.

The protocol name is as in the class package heirarchy, above cgin and below metadata. i.e. for ETSI INAP CS1 (com.opencloud.slee.resources.cgin.etsi_inap_cs1.metadata.CS1ApplicationContexts) it is etsi_inap_cs1. The protocol name retains any underscores.


Comma-separated list of values in <internal ASN.1>:<external OID> format. For dialogs where CGIN is the dialog initiator, configures the CGIN RA to write the external OID in place of the internal application context name. A given internal ACN can be mapped to only one external OID. Several different internal ACNs can be mapped to the same external OID.

<external OID> is specified as an object identifier. For example,

<internal ASN.1> is specified in <protocol>.<application-context-name> format. For example, etsi_inap_cs1.core-INAP-CS1-assist-handoff-SSP-to-SCP-AC.

See acn-inbound-aliases for details on locating protocol and application context names.


(ANSI TCAP only) Boolean value specifying whether to enforce permission to release when sending and receiving a Query package.


Boolean value specifying whether to relax the linked invocation checks to allow linked invokes to be received without a correlation ID, or to permit sending and receiving of invokes with correlation IDs where this is not expected.

Note The following configuration properties configure the thread pool used to process incoming traffic. The parameters correspond to configuration of a java.util.concurrent.ThreadPoolExecutor instance. The default values are suitable for moderate load, but may need increasing for heavy load, or when dialog correlation is used. Monitor the CGIN.<entityname>.tcap-fibers stats parameter set to check the performance of the thread pool.

The maximum number of threads in the thread pool. If zero, then no thread pool is used.


The maximum size of the queue used to store work waiting for processing by the thread pool. If the queue is full, then work is executed directly in the calling thread.

Previous page Next page