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 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

  • mach7 - for the teleSys MACH7 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.


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.

To configure handling of cases where there is no dialog portion and hence no external application context name, use {} as the external OID. If all such cases should be aliased to the same application context, then the particular internal ASN.1 can be named, otherwise the protocol may provide an interceptor to determine the relevant application context. For example, {}:map.phase-1 configures handling of traffic with no dialog portions using the relevant MAP phase 1 application contexts.


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.

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