Demonstrates how the SCCP service sends and receives connection-oriented messages. It can be run as the client that initiates an SCCP connection and transmits data over the connection, or as the server that receives the connection and any data transmitted.
sccodemo [options] called address [calling address]
A computer with a TX board installed
Windows or UNIX
Natural Access
NMS SS7
Use this procedure to run sccodemo:
Step |
Action | ||||||||||||||||||||||||
1 |
From the command line prompt, navigate to the \nms\tx\samples\sccp\ directory under Windows or /usr/bin directory under UNIX. | ||||||||||||||||||||||||
2 |
Connect two TX boards back-to-back. In this example, both boards are installed on the same PC, with board 1 configured with point code 1.1.1 (ANSI), and board 2 configured with point code 1.1.2 (ANSI). | ||||||||||||||||||||||||
3 |
Enter the following command: sccodemo [options] called address [calling address] where options include:
The called address and calling address are specified as:
| ||||||||||||||||||||||||
4 |
Start the server side application first with the following syntax: sccldemo -b 1 -p 0 -n 254 -s This application uses TX board 1 (-b 1), SAP ID 0 (-p 0), and listens on subsystem 254 (-n 254). The -s option specifies that it is acting as a server and not sending any messages. | ||||||||||||||||||||||||
5 |
Start the client side application with the following syntax: sccldemo -b 2 -p 0 -n 254 1.1.1:254 This application uses TX board 2 (-b 2), SAP ID 0 (-p 0), and listens on subsystem 254 (-n 254). The called address specifies that a message is sent to point code 1.1.1, subsystem 254. Since no calling address is specified in the command line, the default address is used, and the SCCP message contains a calling address with the point code and subsystem (1.1.2, subsystem 254). The client side application shows the following output: Sending Connection Request The server side application shows the following output: Sending Indication Received If the server side application does not receive the message, refer to the Details section for suggestions. |
Each SCCP connectionless message contains a destination address (the called address) and a source address (the calling address). The client application must specify a destination for the message, which is the called address. The most common address consists of a point code and a subsystem.
If no calling address is specified, then the message is sent with a default calling address of the client application point code and subsystem.
sccodemo uses SCCP management to determine the address type (ANSI or ITU) of the SAP ID in use. It adjusts the called and calling addresses appropriately.
Troubleshoot as follows:
Use the txalarm utility to confirm that the two TX boards have active links between them.
Check the SCCP configuration file to confirm that the correct destination point code and subsystem are configured.
If using a global title for a called address, try a simple point code/subsystem combination first, and then try a global title.