You configure the CGIN RA frontend for the Simulated ITU TCAP stack by managing resource adaptor entity properties.
You can manage the CGIN RA configuration the same as you would any other resource adaptor entity configuration — for example, using rhino-console’s createraentity command.
|
The Simulated TCAP Stack is included with the CGIN Connectivity Pack. When you unpack the CGIN Connectivity archive, the Simulated TCAP stack will be in the cgin-unified-ra deployable unit, in the du directory.
|
Below are details of the following parameters you can set, and an example.
Properties for configuring the Simulator
Click for details of the following parameters.
| Parameter | Description | Format | Requirements/Options |
|---|---|---|---|
|
mandatory |
||
addresses to listen on |
comma-separated list, in format |
mandatory |
|
remote addresses to connect to |
comma-separated list, in format |
mandatory |
|
SCTP implementation to use |
|
1 option: |
|
global title translation table |
|
mandatory |
|
maximum simultaneously active dialogs |
|
optional |
|
local SCCP address |
|
mandatory |
|
default activity timeout |
|
||
maximum number of worker threads |
|
optional |
tcapsim.listen-addresses
This property is a comma-separated list of <host>:<port> values.
Optionally, a host:port value may be prefixed by <nodeID>,<nodeID>,… to have that address be applied on the given nodes only.
For example, the value:
{101}host1:1234,{102}host1:1235
causes node 101 to listen on host1:1234, and node 102 to listen on host1:1235.
To listen on all available network interfaces, use a <host> of 0.0.0.0
The <nodeID> parameter is only required if multiple Rhino nodes are running on a single host. When this parameter is specified, an RA entity will only create a listening socket on the specified host and port if the node that the entity is running on is equal to <nodeID>.
tcapsim.remote-addresses
This property is a comma-separated list of <host>:<port> values.
Optionally, a host:port value may be prefixed by <nodeID>,<nodeID>,… to have that address be applied on the given nodes only.
For example, the value:
{101}host1:1234,{102}host1:1235
causes node 101 to connect to host1:1234, and node 102 to connect to host1:1235.
It is unlikely that the <nodeID> parameter will be required as generally every node in a cluster should make connections to the same remote endpoints.
tcapsim.sctp-stack
This property controls the SCTP implementation used by the SUA stack. Currently the only option is tcp.
tcp is a proprietary SCTP-ish protocol running over TCP. This is used as Java 1.6 and earlier do not support the use of native SCTP.
tcapsim.gt-table
This parameter is the full path to the file containing the global title translation table.
The ITU TCAP Simulator includes basic Global Title Translation support. Global titles can be mapped to a PC/SSN for routing according to the routing table. The format of the global title translation table is as follows:
# For all address types the first column contains the GlobalTitleIndicator. # # Then, for C7 (ITU-T), the format is: # 1 C7 AddressDigits PC SSN NatureOfAddress # 2 C7 AddressDigits PC SSN TranslationType # 3 C7 AddressDigits PC SSN TranslationType NumberingPlan # 4 C7 AddressDigits PC SSN TranslationType NumberingPlan NatureOfAddress # # And, for A7 (ANSI), the format is: # 1 A7 AddressDigits PC SSN TranslationType NumberingPlan # 2 A7 AddressDigits PC SSN TranslationType # # The J7 (Japanese) format is the same as for C7 (ITU-T), excepting that 'C7' is # replaced with 'J7'. # # A match will only be returned if the GTI-specific parameters match and the # leading digits of the address match the rule. In the case of multiple # matching rules the most specific address match will be returned. # # ITU-T Examples # # ITU-T SCCP address, gti=1, digits=123456*, na=1, pc=2, ssn=221 # 1 C7 123456 2 221 1 # ITU-T SCCP address, gti=1, digits=1234*, na=1, pc=2, ssn=221 # 1 C7 1234 2 211 1 # ITU-T SCCP address, gti=2, digits=98131*, tt=122, pc=1, ssn=232 # 2 C7 98131 1 232 122 # ITU-T SCCP address, gti=3, digits=78341*, pc=7183, ssn=6, tt=1, np=4 # 3 C7 78341 7183 6 1 4 # ITU-T SCCP address, gti=4, digits=81931239, pc=4, ssn=200, tt=89, np=1, na=1 # 4 C7 81931239 4 200 89 1 1 # # ANSI Examples # # ANSI SCCP address, gti=1, digits=73737*, tt=10, np=4, pc=2-123-42, ssn=6 # 1 A7 73737 2-123-42 6 10 4 # ANSI SCCP address, gti=2, digits=12345*, tt=42, pc=1-1-1, ssn=221 # 2 A7 12345 1-1-1 221 42 # # J7 Examples # # Japanese SCCP address, gti=1, digits=123456*, na=1, pc=2, ssn=221 # 1 J7 123456 2 221 1 # Japanese SCCP address, gti=1, digits=1234*, na=1, pc=2, ssn=221 # 1 J7 1234 2 211 1 # Japanese SCCP address, gti=2, digits=98131*, tt=122, pc=1, ssn=232 # 2 J7 98131 1 232 122 # Japanese SCCP address, gti=3, digits=78341*, pc=7183, ssn=6, tt=1, np=4 # 3 J7 78341 7183 6 1 4 # Japanese SCCP address, gti=4, digits=81931239, pc=4, ssn=200, tt=89, np=1, na=1 # 4 J7 81931239 4 200 89 1 1
tcapsim.max-dialogs
The maximum number of dialogs that may be active simultaneously. This may be any positive 32-bit integer value. The default is 10000.
local-sccp-address
Provides a local calling party SCCP address to use for outgoing TC-BEGIN messages, if not explicitly provided by the SBB. The address should be formatted in the format that com.opencloud.slee.resources.cgin.SccpAddressParser expects. This parameter is mandatory.
This address is also the address used in dynamic routing configuration; it is the address this node advertises to another node when connecting to it.
|
See SCCP Address Format in the CGIN Installation and Administration Guide. |
default-activity-timeout
Configures the default timeout, in milliseconds, for tcapsim dialog activities. Each dialog has an activity timer associated with it. If no activity is seen on the dialog before the timer expires the dialog will be aborted and the associated SLEE activity ended. Sending or receiving messages on the dialog will reset this timer.
This is not to be confused with invoke timeouts, which apply to individual operations sent on a dialog.
Sample configuration
For example, the diagram in About the ITU TCAP Simulator shows a configuration with the following properties:
Node 101 and Node 102:
stack=tcapsim
local-sccp-address="type=c7,ri=pcssn,pc=1,ssn=221"
tcapsim.gt-table=/home/user/rhino/rhino/cgin/gtt.txt
tcapsim.listen-addresses="{101}0.0.0.0:10221,{102}0.0.0.0:10231"
tcapsim.remote-addresses="127.0.0.1:10222"
tcapsim.max-dialogs=60000
default-activity-timeout=300
Scenario Simulator:
stack=tcapsim local-sccp-address="type=c7,ri=pcssn,pc=2,ssn=222" tcapsim.gt-table=/home/user/rhino/rhino/cgin/gtt.txt tcapsim.listen-addresses="127.0.0.1:10222" tcapsim.remote-addresses="127.0.0.1:10221,127.0.0.1:10231"
