Options	Description
`-b` *board*	Board number to which the TCAP configuration is downloaded (default = 1).
`-f` *filename*	Name and location of the TCAP configuration file to be downloaded.

Version

Chapter 6

TCAP Sample Applications

6.1 The find800 Sample Application

6.1.1 Using the find800 Program

: Acting as a 800 number server
: Acting as an 800 number client
: Troubleshooting
: Using TCAP ITU-T Protocol
: Adding Subsystem Numbers

6.2 The TCAP Configuration Utility

: 6.2.1 Using the TCAP Configuration Program

6.3 The TCAP Manager Program

: 6.3.1 Using the TCAP Manager Program

6.1 The find800 Sample Application

The find800 sample application included with the TCAP distribution software illustrates the use of the TCAP layer to implement a simple request/response transaction. Separate samples are included for ITU-T TCAP and ANSI TCAP. The ansi800 sample uses ANSI TCAP messages and defaults to 24-bit addressing. The ansi800 sample can optionally support 14-bit ITU addressing as well. The itu800 sample uses ITU-T TCAP messages and defaults to 14-bit ITU-T addressing. The itu800 sample can optionally support 24-bit ANSI addressing as well.
The find800 program uses the TCAP API to send and receive 800 number translation requests. find800 can act as an 800 number server, or as a client requesting an 800 number translation. Both utilities can be found in the \tektx\samples\tcap\ directory.

6.1.1 Using the find800 Program

Option	Description
`-b` *board*	TX board number (default = 1). Valid range is 1 to 8.
`-p` *sapno*	Service access point ID to be used (default = 0). Valid range is 0 to 255.
`-n` *number*	Subsystem number to be used (default = 254). Valid range is 0 to 255.
`-i` *iterations*	Number of times transaction is repeated (default = 1). Valid range is 0 to 32000.
`-j` *delay*	Delay, in ms, between transaction repetition (default = 5000). Valid range is 1 to 65536.
`-d`	Activates detailed dump of each packet sent/received.
`-t`	Uses ITU addressing. The `ansi800` program defaults to ANSI addressing.
`-a`	Uses ANSI addressing. The `itu800` program defaults to ITU addressing.
`-s`	Causes `find800` to act as an 800-number server. The `find800` program acts as a client by default.

Acting as a 800 number server

To start find800 as an 800 number server, type: find800 -b 1 -p 0 -n 255 -s
In this case, find800 binds to TX board 1, uses SAP ID 0, and uses subsystem number 255. Since -s is specified, find800 acts as a server, and waits for an 800 number request to arrive.
When a request arrives, find800 takes the received 800 number and compares it to the numbers found in the numbers.800 file. Note: The numbers.800 file must be in the same directory as the find800.exe file.
The numbers.800 file looks like this: [800 Numbers] 8001234567=3122456789 8004561234=8477069700
Additional 800 numbers may be added, as long as they are listed after the [800 Numbers] section header, and they conform to the syntax: 800nnnnnnn=yyyyyyyyyy
If a matching 800 number is found, the FIND800 server returns the translated number in a RETURN_RESULT [last] component.
If no matching 800 number is found, the find800 server returns a RETURN_ERROR component.
The find800 server continues to listen for and respond to requests indefinitely. To stop the server, press any key.

Acting as an 800 number client

To start find800 as a client: find800 -b 2 -p 1 -n 254 1.1.1:255 8001234567
In this case, find800 binds to TX board 2, uses SAP ID 1, and uses subsystem number 254. Since -s is not specified, find800 acts as a client, and immediately sends an 800 number request to pointcode 1.1.1, subsystem 255. The 800 number to be translated is 8001234567.
After sending the 800 number request, find800 waits for a response.
After a response is received, find800 continues to run, but no further requests are sent. To stop the client, press any key.

Troubleshooting

If TCAP messages aren't being sent, there are several things to check. By default, the TCAP configuration is set up for ANSI-protocol messages. Be sure you are using the ansi800 version of find800. Structures used by the TCAP must be packed an one-byte boundaries. The default in most compilers is packing on 8-byte boundaries. For both Windows and UNIX systems, the -Zp compiler flag must be set. The sample code makefile shows how this flag is properly set. By default, the find800 demo program uses Subsystem number 254. However, the SCCP layer comes initially configured with only Subsystem number 3 and 4. Use the -n 3 command line option on both the client and the server of find800. For example, starting find800 as a client using Subsystem number 3: find800 -b 2 -p 1 -n 3 1.1.1:3 8001234567

Using TCAP ITU-T Protocol

In order to use the TCAP ITU protocol, the \tektx\config\tcapcp1.cfg file must be modified. Change the SWITCH_TYPE parameter to one of ITU88, ITU92, or ITU97 and modify as many SAP ID's as needed: # # User SAP configuration for 1st application # USER_SAP 0 # Sap number start at 0 SWITCH_TYPE ITU92 # one of ITU92, ITU88, ANSI92, ANSI88 END # User application 0 Note: ANSI-style point code addressing is still used (1.1.1).
If two TX boards are being used, then the \tektx\config\tcapcp2.cfg file must also be modified.

Adding Subsystem Numbers

In order to define new subsystem numbers, the \tektx\config\sccpcp1.cfg file must be modified. A subsystem definition section looks like this: #define all subsystems of interest at 1.1.1 (up to 8) SSN 3 # first subsystem at 1.1.2 SSN_SNR TRUE # normal routed SSN_ACC TRUE # initially accessible #SSN_BPC x.y.z # this subsystem not currently replicated # concerned point codes - other nodes to be notified when # status of this SSN at this node changes - must have a # route for any point code listed here #CONC_PC q.r.s # 1st concerned point code #CONC_PC q.r.t # 2nd concerned point code END # of route 1.1.2, SSN 3
Simple change the SSN field, or copy the definition section and define new subsystem numbers.
If two TX boards are being used, then the \tektx\config\sccpcp2.cfg file must also be modified.

6.2 The TCAP Configuration Utility

Once the TCAP configuration file has been created, run the TCAP Configuration (tcapcfg) utility to download it to scan the ASCII text file and download the configuration to the TCAP task on the TX board.

6.2.1 Using the TCAP Configuration Program

Name

tcapcfg

Purpose

Downloads the TCAP configuration to the TX board at boot time.

Usage

tcapcfg options

Prerequisites

Requires a single computer with a TX 2000, TX 3000, TX 3220, or TX 3220C board installed, in addition to the following software: Windows NT 4.0, Windows 2000, UnixWare, Intel Solaris, or SPARC Solaris Natural Access 1999-4 or later

Procedure

To run tcapcfg:

From the command line prompt, navigate to the \tektx\samples\tcap\tcapcfg directory under Windows, or the /usr/bin directory under UNIX.

At the command line, enter the following:

tcapcfg options
where options include:

Options

Description

-b board

Board number to which the TCAP configuration is downloaded (default = 1).

-f filename

Name and location of the TCAP configuration file to be downloaded.

The TCAP Configuration program scans the information in the ASCII file (specified with the -f option) and downloads this information to the task on the TX board.

Notes

The TCAP Configuration program is available in both source code and executable formats. The source code illustrates the use of the TCAP management API primitives for developers who wish to integrate management of the SS7 TCAP layer into their own configuration management systems.

6.3 The TCAP Manager Program

After downloading the TCAP configuration to the TX board with tcapcfg, run the TCAP Manager (tcapmgr) to monitor the status of the TCAP layer. The TCAP Manager provides a command line interface from which alarm levels can be set, buffers can be traced, and TCAP statistics can be viewed and reset.

6.3.1 Using the TCAP Manager Program

Name

tcapmgr

Purpose

Monitors and manages the status of the TCAP layer.

Usage

tcapmgr -b board

Prerequisites

Requires a single computer with a TX 2000, TX 3000, TX 3220, or TX 3220C board installed, in addition to the following software: Windows NT 4.0, Windows 2000, UnixWare, Intel Solaris, or SPARC Solaris Natural Access 1999-4 or later

Procedure

From the command line prompt, navigate to the \tektx\samples\tcap\tcapmgr directory under Windows, or the /usr/bin directory under UNIX.
At the command prompt, enter the following:
tcapmgr -b board
where board is the TX board number to open.

The tcapmgr program supports the following commands:


Command	Description
ALARMLVL *options*	Sets the current alarm output level. Valid range for *options* is 0 to 3.
CONFIG SAP *sapno* \| GEN	Displays current general or SAP configuration parameter values.
STATS *sapno* *[RESET]*	Retrieves statistics on an application service access point (*sapno) and optionally resets them to zero (RESET*) after fetch.
STATUS	Retrieves the general status of the TCAP task.
TRACE ON \| *OFF*	Turns buffer tracing ON or OFF.This feature is not currently supported.
BOARD *board*	Switches to a new target board (*board*).
? *[COMMAND]*	Lists available commands or parameters of a specific command (*COMMAND*).
Q	Quits the application.

Notes

The TCAP Manager program is available in both source code and executable formats. The source code illustrates the use of the TCAP management API primitives for developers who wish to integrate management of the SS7 TCAP layer into their own configuration management systems.

Version

Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com