libsua/sualibrary/docs/en/index-3.html

139 lines
3.5 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>The Sualibrary Handbook: Usage </TITLE>
<LINK HREF="index-4.html" REL=next>
<LINK HREF="index-2.html" REL=previous>
<LINK HREF="index.html#toc3" REL=contents>
</HEAD>
<BODY>
<A HREF="index-4.html">Next</A>
<A HREF="index-2.html">Previous</A>
<A HREF="index.html#toc3">Contents</A>
<HR>
<H2><A NAME="s3">3. Usage </A></H2>
<P>
<H2><A NAME="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.
Lets assume, your application is named app and consists of the file app.c. If you use gccas compiler,
it is sufficient to issue the command
host:˜> gcc -o app app.c -lsctp lglib -lsua
in order to compile your application. Note though, that FreeBSD calls the glib-library by default
libglib12, since it exists both in several versions (i.e. glib version 1.0 would be called libglib10
under FreeBSD (and possibly other BSD unixes). So under this platform, you would use
BSDhost:˜> gcc -o app app.c -lsctp -lglib12 lsua
Some features are selectable, see sua_debug.h for a overview of the switches.
Switches include the displaying debug msg on the screen,
Dumping SUA msg and debug info into a file, optional use of SUA ASP management, etc…
<P>
<P>
<P>
<H2><A NAME="ss3.2">3.2 Features of the implementation</A>
</H2>
<P>
<P>
The implementation is able to do the following:
<P>
Statically and dynamically setup of SCTP association for the transport of the SUA messages
<P>
Connectionless : CLDT message transfer
<P>
Connectionoriented: CORE, COAK, RELRE, RELCO, COREF & CODT message transfer
<P>
Adressing options: use of Ipv4 and Ipv6 addresses, SS7 pointcodes, hostname
<P>
SUA ASP management(optional)
<P><P>
It has been tested with implementations of 4 companies in the first SUA bakeoff.
<P><P>
The following flags are recognized when reading a configuration file for SUA:
<P>
-s : source address<P>
-l: source portnumber (optional, default is set at 14001)<P>
-d : destination address(optional)<P>
-r : destination portnumber(optional, default is set at 14001)<P>
-n : subsystem number to be used<P>
-a : Application server number(optional)<P>
-t : number of streams in & out(optional, default is set at 1)<P>
-7d : SS7 destination pointcode(optional)<P>
-7s : SS7 source pointcode(optional)<P>
-sn: Source hostname<P>
-dn: Destination hostname<P>
<P>
example of a association<P>
-s 10.0.1.1 -7s 1 -d 10.0.3.1 -7d 66051 -r 14001 -n 255 -a 1 -t 16<P>
example of a local listener<P>
-s be.atea.sua01 n 255 a 1 t 2 <P>
<P>
<P>
<P>
<H2><A NAME="ss3.3">3.3 What is missing.</A>
</H2>
<P>
<P>
Features to be included in future version:
<P>
- Relaying functionality<P>
- SUA management: ASP , AS management, etc<P>
<P>
Features not to be included:
<P>
- NIF/interworking with classical SS7 SCCP<P>
- Routing keys<P>
- Registration of Applications<P>
<P>
Probably there is some more. Additions, comments, bug-reports and bug-fixes as welll as patches,
patches, and patches are always welcome !
<P>
<P>
<P>
<HR>
<A HREF="index-4.html">Next</A>
<A HREF="index-2.html">Previous</A>
<A HREF="index.html#toc3">Contents</A>
</BODY>
</HTML>