(Page 1 of 1 in this chapter)

Chapter 6

TCAP Sample Applications

6.1 The FIND800 Sample Application

: 6.1.1 Acting as a 800 number server
: 6.1.2 Acting as an 800 number client
: 6.1.3 Troubleshooting
: 6.1.4 Using TCAP ITU-T Protocol
: 6.1.5 Adding Subsystem Numbers

6.2 The TCAPCFG Sample Utility

6.3 The TCAPMGR Sample Utility

6.1 The FIND800 Sample Application

The FIND800 sample application included with the TCAP distribution software illustrates the use of the TX Series 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 c:\tektx\samples\tcap directory.
The FIND800 syntax is:
FIND800 [options] pointcode:subsystem phonenum
where options are: Option Description -b n where n is the TX2000 board number (default 1, max 8). -p n where n is the SAP ID to be used (default 0, max 255). -n n where n is the subsystem number to be used (default 254, max 255). -d set debug flag for additional information to be output. -t use ITU addressing (ANSI800 sample only). -a use ANSI addressing (ITU800 sample only). -s act as an 800 number server (default: act as a client).
pointcode:subsystem specifies the pointcode and subsystem number of the 800 number server (only used by clients).
phonenum is the 800-number to be translated (only used by clients).
Note: If multiple instances of FIND800 are bound to the same TX2000 board, the SAP ID (-s parameter) and the subsystem number (-n parameter) must be different.

Option	Description
`-b n`	where `n` is the TX2000 board number (default 1, max 8).
`-p n`	where `n` is the SAP ID to be used (default 0, max 255).
`-n n`	where `n` is the subsystem number to be used (default 254, max 255).
`-d`	set debug flag for additional information to be output.
`-t`	use ITU addressing (ANSI800 sample only).
`-a`	use ANSI addressing (ITU800 sample only).
`-s`	act as an 800 number server (default: act as a client).

6.1.1 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 TX2000 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: [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.

6.1.2 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 TX2000 board 2, uses SAP ID 1, and uses subsystem nuber 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.

6.1.3 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 NT, UnixWare, Solaris 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

6.1.4 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(i.e. 1.1.1).
If two TX Series boards are being used, then the \tektx\config\tcapcp2.cfg file must also be modified.

6.1.5 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: #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 accessable #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 Series boards are being used, then the \tektx\config\sccpcp2.cfg file must also be modified.

6.2 The TCAPCFG Sample Utility

The TCAPCFG configuration utility used to download the TCAP configuration to the TX Series board at boot time (see the Signaling System 7 (SS7) Installation and Configuration Manual) is also distributed in source form. The TCAPCFG source illustrates use of the TCAP Management API primitives for developers who wish to integrate configuration of the TX Series TCAP layer into their own configuration management systems. This TCAPCFG utility is located in the c:\tektx\samples\tcap directory.

6.3 The TCAPMGR Sample Utility

A TCAPMGR utility program is also distributed in both source and executable form. The TCAPMGR utility provides a simple command line interface for managing and monitoring the status of the TCAP layer. It supports the following commands:

Command

Description

ALARMLVL <0..3>

sets the current alarm output level.

TRACE ON | OFF

turns buffer tracing on or off.

STATS <sapno> [RESET]

retrieves statistics on an application sap and optionally resets them to zero after fetch.

BOARD <board>

switches to a new target board.

? [COMMAND]

lists available commands or parameters of a specific command.

Q

quits application.
The TCAPMGR source illustrates use of the TCAP Management API primitives for developers who wish to integrate management of the TX Series TCAP layer into their own configuration management systems. The TCAPMGR utility is located in the c:\tektx\samples\tcap directory.

Command	Description
ALARMLVL <0..3>	sets the current alarm output level.
TRACE `ON \| OFF`	turns buffer tracing on or off.
STATS <sapno> [`RESET`]	retrieves statistics on an application sap and optionally resets them to zero after fetch.
BOARD <board>	switches to a new target board.
? [COMMAND]	lists available commands or parameters of a specific command.
Q	quits application.

(Page 1 of 1 in this chapter)

tech_support@nmss.com