You configure the CGIN RA frontend for the ITU TCAP stack by managing resource adaptor entity properties.
Manage like any other resource adaptor entity
You can manage the CGIN RA configuration the same as you would any other resource adaptor entity configuration — for example, using rhino-console’s |
The teleSys MACH7 TCAP stack supports the following configuration properties:
Property |
How to configure it |
||
---|---|---|---|
stack Controls which TCAP stack the CGIN RA entity should use. |
To use the teleSys MACH7 TCAP stack, set
|
||
mach7.backends Configures which backend processes to connect to. |
Must be specified when the teleSys MACH7 TCAP stack is used. The property is a comma-separated list of |
||
mach7.slee-cluster-id Uniquely identifies the cluster that this RA entity belongs to. |
Must be specified when the teleSys MACH7 TCAP stack is used. The property is an integer value that uniquely identifies the cluster that this RA entity belongs to. It does not need to match the SLEE’s cluster ID, but should be distinct from the value used by RA entities belonging to another cluster. |
||
mach7.sccp-bind-address Configures the SCCP bind address to be used. |
This configuration property may be used to specify the SCCP bind address. If PC and SSN fields are present in the
Any PC or SSN setting in mach7.sccp-bind-address="pc=2057,ssn=2,nwApp=0" mach7.sccp-bind-address="nwApp=1" |
||
mach7.corr-cluster-id Used for advanced routing through the AN for correlated messages. |
This configuration property is used by the ASC process to register with the AN as part of a cluster. This value is used for advanced routing through the AN for correlated messages. |
||
mach7.comm-mode Configures the frontend↔backend communication protocol. |
This configuration property controls the protocol used for communication between the frontend and backend processes. Possible values are "SCTP" and "TCP". The default value is "SCTP".
|
||
mach7.node-id Configures the Scenario Simulator node ID. |
This configuration property can only be set when using the Scenario Simulator. It is used to distinguish between multiple scenario simulator instances belonging to the same |