The configuration file for the TCAP Forwarding application is located in the /usr/sipxpress/config directory on each Application Server.
The configuration file will need to be edited on each Application Server independently. In most deployments, the files will be identical on each server.
The TCAP Forwarding application will receive a trigger and then generate an identical trigger to send to the STP, it will change the Called Party Address in the SCCP Layer of the incoming trigger based on the configuration file.
The configuration file determines which fields in the Called Party Address to change. Therefore, the resulting Called Party Address of the new ‘forwarded’ trigger will be whatever is in the original Called Party Address overridden by whatever is in the configuration file.
The following example configuration file will change the Translation Type of the Global Title in the Called Party Address to 247 and every other field will stay the same:
{
"default_address": { "global_title": { "tt": 247 } },
"address_map":[{}]
}
The following example configuration file will change the Point Code in the Called Party Address to 0x010203 and every other field will stay the same:
{
"default_address": { "point_code": "0x010203" },
"address_map":[{}]
}
The default address is the main section. If there is not a match in the address map, then this is the configuration to use.
The address map section allows you to set specific changes to the Called Party Address based on the original Called or Calling Party Address. If you do not need to do this, leave the address map section empty.
{
"address_standard": "ANSI",
"default_address": {
"point_code": "0x0B141E"
},
"address_map": []
}
{
"default_address"; {
"natl_intl_bit": 1,
"point_code": 0x010203,
"routing_bit": 1,
"signaling_point_code_bit": 1,
"subsystem_bit": 1,
"subsystem_number": 245,
"global_title_indicator": 2,
"global_title": {
"digits": "",
"es": 0,
"nai": 0,
"np": 0,
"tt": 247
}
},
"address_map": [{
"called_match": {
"tt": 247
},
"point_code": 0x010202
},
{
"calling_match": {
"ssn": 247
}
},
{
"match": {
"pc": ""
}
},
{
"match": {
"pc": "",
"ssn": 147
}
}
]
}
To mitigate having any potential errors in the configuration file, you can use the command line tool to verify all changes made to the file. This command line tool was developed in Java so that code can be shared with the Drop To Java code that reads and validates the configuration for the call flow.
The command line tool can be run anywhere on the machines with the user signed in as root.
Enter the following code when signed in as root to see if the configuration file is valid:
tcap-fkconfig
If the configuration file is valid, the following response will be shown:
The tcap_forwarding.json configuration file is valid; no issues where detected.
There are two arguments that can be added in the command line tool: –help (-h) and –verbose (-v).
Using the help argument will show the following response.
tcap-fkconfig --help
Usage: [-v|--verbose] [-h|--help]
Using the verbose argument will show a full stack trace along with the human readable error report.