<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<METANAME="GENERATOR"CONTENT="SGML-Tools 1.0.9">
<TITLE>The Sualibrary Handbook: Usage </TITLE>
<LINKHREF="index-4.html"REL=next>
<LINKHREF="index-2.html"REL=previous>
<LINKHREF="index.html#toc3"REL=contents>
</HEAD>
<BODY>
<AHREF="index-4.html">Next</A>
<AHREF="index-2.html">Previous</A>
<AHREF="index.html#toc3">Contents</A>
<HR>
<H2><ANAME="s3">3. Usage </A></H2>
<P>
<H2><ANAME="ss3.1">3.1 General usage of the SUA library</A>
</H2>
<P>
If you compile the entire project, and install the files sua.h in the directory /usr/local/includeand libsua.ain /usr/local/lib(by simply copying these from the libsua/sua/ subdirectory to their repective destinations: this is done automatically by the the make during installation), it is trivial to compile an application.
Let<EFBFBD>s assume, your application is named app and consists of the file app.c. If you use gccas compiler,
<H2><ANAME="ss3.4">3.4 SUA configuration file commands.</A>
</H2>
<P>
<P>
The following Commands can be used in the SUA configuration file:
<P>
REMARK: Spaces are used to clarify the commands only. They are not allowed or not recognized correctly in the actual configuration file!!!! See example configuration file in the package under sualibrary/testup/pcg729.sua</P>
<P>Provides the IP addres(ses) and portnumber of the destination to which to set up a association. Each association requires a different association_id. The init flag indicates if the implementation should setup the association immediatly(active assoc setup) or wait for a incomming association from remote node with those particular parameters(passive assoc setup or listening mode).</P>
<P>
- cr orgpc: pc = cccc, host_id = j;</P>
<P>Provides the originating SS7 pointcode for the own node with host_id j.</P>
<P>If a destname is provided, then a cr destip must be done as the translation of the hostname or global title will yield a IP address , which is subsequently used to find the correct association to send the msg out on. The IP address of the cr destip and the ip address of one of the cr assoc's must be the same. Do not forget to do a cr route also for the IP address.</P>
<P>A node can have both a PC or/and a IP address. If both are present then the dest_id must be the same for that particular node.</P>
<P>Provides the Destination Global Title for the remote node with dname_id i. tt = translation identifier, na = Nature of address, np= Numbering plan, digits= digits of the Global Title(Do not forget to do a cr destip)</P>
<P>Make the link between a Destination(PC/IP addr) and a association. Destination dest_id j(created via cr destpc or destip) can be reached via the association assoc_id i(created via cr assoc).</P>
<P>Make the link between a Destination(GT/Name) and a association. Destination dname_id j(created via cr destname) can be reached via the association assoc_id i(created via cr assoc).</P>