(Page 1 of 1 in this chapter)

Chapter 6

SCCP Sample Applications

6.1 The SCCPDEMO Sample Application
6.1.1 Acting as a receiver
6.1.2 Acting as a sender
6.1.3 Troubleshooting
6.1.4 Using SCCP ITU-T Addressing
6.1.5 Adding Subsystem Numbers
6.2 The SCCPCFG Sample Utility
6.3 The SCCPMGR Sample Utility

6.1 The SCCPDEMO Sample Application

The SCCPDEMO sample application included with the SCCP distribution disk illustrates the use of the TX Series SCCP layer to implement a file transfer over an SCCP connection. The SCCPDEMO sample defaults to 24-bit ANSI addressing, but can optionally support 14-bit ITU addressing.

SCCPDEMO can act as either a file receiver or a file sender. The file receiver is started first, followed by the file sender. The file sender initiates the SCCP connection, and sends the contents of a file to the reciever.

The SCCPDEMO syntax is:

SCCPDEMO [options] pointcode filename

where options are:
Option

 Description

-b n

 n is the TX2000 board number (default 1, max 8).

-t

 use 14-bit ITU addressing (default:24-bit ANSI addressing)

-s

 size of each segment sent (default:512, max:1200)

pointcode

 specifies the pointcode of the file receiver (only used by sender).

filename

 name of file to be sent (only used by sender).

6.1.1 Acting as a receiver

To start SCCPDEMO as a file receiver, type the following from the c:\tektx\samples\sccp\sccpdemo directory:

SCCPDEMO -b 2



In this case, SCCPDEMO binds to TX2000 board 2. Since no point code is specified, SCCPDEMO acts as a file receiver, waiting for a sender to initiate a connection.


Note:  The SCCPDEMO receiver must be started in a different directory from the sender. When a file is received, the receiver opens a file with the same name and fills it. This does not work correctly if the sender is running from the same directory.


To stop the receiver, press any key.






6.1.2	 Acting as a sender





To start SCCPDEMO as a sender, type the following from the c:\tektx\samples\sccp\sccpdemo directory:


SCCPDEMO -b 1 1.1.2 file.txt


In this case, SCCPDEMO binds to TX2000 board 1. Since a point code and file name is specified, SCCPDEMO acts as a sender, and immediately initiates a connection with point code 1.1.2. Once the connection is established, the sender sends the contents of file.txt in 512-byte chunks. The receiver rebuilds the file in its directory. 


Note:  The SCCPDEMO receiver must be started in a different directory from the sender. When a file is received, the receiver opens a file with the same name and fills it. This does not work correctly if the sender is running from the same directory.


To stop the sender, press any key.


 






6.1.3	 Troubleshooting





If an SCCP connection isn't established, there are several things to check.







6.1.4	 Using SCCP ITU-T Addressing





If ITU-T addressing is desired for SCCP, the \tektx\config\itu\sccpcp1.cfg file can be used as a model. The ITU version of the SCCP configuration file can either be copied to the \tektx\config directory (being careful to save the ANSI version), or else the SS7LOAD file can be modified so the SCCPCFG line points to the \tektx\config\itu directory.



By using the -t option, SCCPDEMO will send its requests specifying ITU-T type addressing. 



If two TX Series boards are being used, then the \tektx\config\sccpcp2.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 SCCPCFG Sample Utility





The SCCPCFG configuration utility used to download the SCCP 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 SCCPCFG source illustrates use of the SCCP Management API primitives for developers who wish to integrate configuration of the TX Series SCCP layer into their own configuration management systems.  The SCCPCFG utility can be found in the c:\tektx\samples\sccp\sccpcfg directory.


 






6.3	 The SCCPMGR Sample Utility





The SCCPMGR utility program is also distributed in both source and executable form. The SCCPMGR utility provides a simple command line interface for managing and monitoring the status of the SCCP layer. The SCCPMGR utility can be found in the c:\tektx\samples\sccp\sccpmgr directory.  It supports the following commands. 





 Command Line



 Description




 ALARMLVL <0..3>



 sets the current alarm output level.




 TRACE ON | OFF



 turns buffer tracing ON or OFF.




 GENERAL STATS [RESET]



 retrieves general statistics and optionally resets them to zero after fetch.




 NSAP <sapno> STATS [RESET]



 retrieves statistics on a network sap and optionally resets them to zero after fetch.




 USAP <sapno> STATS [RESET]



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




 USAP <sapno> STATUS



 retrieves status on an application sap.




 BOARD <board>



 switches to a new target board.




 ? [COMMAND]



 lists available commands or parameters of a specific command.




 QUIT



 quits application.
















The SCCPMGR source illustrates the use of the SCCP Management API primitives for developers who wish to integrate management of the TX Series SCCP layer into their own configuration management systems.











 
    (Page 1 of 1 in this chapter)




 




tech_support@nmss.com



Copyright © 1999, Natural MicroSystems, Inc.   All rights
reserved.