Implements a single request and response transaction using the TCAP layer.
Separate samples are included for ITU-T TCAP and ANSI TCAP.
This program... |
Uses... |
Defaults to... |
Optionally supports... |
ansi800 |
ANSI TCAP messages |
24-bit addressing |
14-bit ITU addressing |
itu800 |
ITU-T TCAP messages |
14-bit ITU-T addressing |
24-bit ANSI addressing |
find800 uses NMS TCAP to send and receive 800 number translation requests. find800 can act as an 800 number server, or as an 800 number client requesting an 800 number translation. Both utilities can be found in the \tektx\samples\tcap\ directory.
find800 [options] pointcode:subsystem phonenum
A computer with a TX board installed
Windows or UNIX
Natural Access
NMS SS7
To run find800:
Step |
Action | ||||||||||||||||||||
1 |
From the command line prompt, navigate to the tektx\samples\tcap\find800 directory under Windows or the /usr/bin directory under UNIX. | ||||||||||||||||||||
2 |
Enter the following command: find800 [options] pointcode:subsystem phonenum where options include:
pointcode:subsystem specifies the pointcode and subsystem number of the 800 number server that is used by clients. phonenum indicates the 800 number to be translated that is used by clients. |
Note: If multiple instances of find800 are bound to the same TX board, the SAP ID (-s) and the subsystem number (-n) must be unique for each instance.
To start find800 as an 800 number server:
Step |
Action |
1 |
Enter the following command: find800 -b l -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] Additional 800 numbers can be added, as long as they are listed after the [800 Numbers] section header and they conform to the following 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. |
2 |
To stop the server, press any key. |
To start find800 as a client:
Step |
Action |
1 |
Enter the following command: 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. |
2 |
To stop the client, press any key. |
If TCAP messages are not sent, check the following:
By default, the TCAP configuration is set up for ANSI-protocol messages. Ensure that you are using the ansi800 version of find800.
Structures used by TCAP must be packed on 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 demonstration program uses subsystem number 254. However, the SCCP layer is initially configured with only subsystem numbers 3 and 4. Use the -n 3 command line option on both the client and the server of find800.
The following code is an example of starting find800 as a client using subsystem number 3:
find800 -b 2 -p 1 -n 3 1.1.1:3 8001234567
To use the TCAP ITU protocol, modify the tcapcp1.cfg file. Change the SWITCH_TYPE parameter to ITU88, ITU92, or ITU97 and modify as many SAP IDs 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 used, modify the tcapcp2.cfg file.
To define new subsystem numbers, modify the sccpcp1.cfg file. The following code is an example of a subsystem definition section:
#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
Either change the SSN field or copy the definition section and define new subsystem numbers. If two TX boards are used, modify the sccpcp2.cfg file.