lspacing=0 width=100%>
Yahoo! is not affiliated with the authors of this page or responsible for its content.
Seagull - OpenCall TCAP Seagull - OpenCall TCAP
Table of contents
1
TCAP protocol details................................................................................................................................ 2
2
Compiling Seagull with OCTCAP support................................................................................................ 2
3
Getting started with TCAP......................................................................................................................... 2
3.1
First try...................................................................................................................................................2
3.2
First try explained.................................................................................................................................. 3
4
Using Seagull............................................................................................................................................. 9
4.1
Transport protocols and channels for TCAP......................................................................................... 9
4.2
TCAP specific parameters management.............................................................................................. 10
4.2.1
Invoke id..........................................................................................................................................10
4.2.2
Dialogue portion (ITU only)........................................................................................................... 11
5
Configuration files....................................................................................................................................14
5.1
Generic configuration.......................................................................................................................... 14
5.2
TCAP dictionary.................................................................................................................................. 15
5.2.1
Types............................................................................................................................................... 15
5.2.2
Header............................................................................................................................................. 15
5.2.3
Body................................................................................................................................................ 17
5.2.4
Dictionary........................................................................................................................................ 18
5.2.5
Configuration parameters................................................................................................................ 19
5.3
Actions in scenario commands for TCAP........................................................................................... 20
6
Reference..................................................................................................................................................20
6.1
Generic configuration reference.......................................................................................................... 20
6.1.1
TCAP configuration........................................................................................................................ 20
Copyright © 2006 HP OpenCall Software All rights reserved. 1. TCAP protocol details
The TCAP implementation in Seagull consist in the full implementation and support of
HP OpenCall SS7
(http://www.hp.com/go/opencall/) TCAP API. This implementation supports both TCAP over
SS7/E1/T1/J1/V35 and also TCAP over SIGTRAN / M3UA or SUA.
Both ITU and ANSI flavors are supported. A Seagull dictionary is available for each of those.
Warning:
For ANSI, Seagull only supports ANSI90 (HP OpenCall SS7 does not officially support ANSI96). It uses TCAP_API100 compile flag and must be
linked to first version of the libSS7utilsAAA.so library (libSS7utilAAA.so.1) if several versions of this library exist on the system (refer to
Generic
configuration
section).
2. Compiling Seagull with OCTCAP support
By default, OCTCAP support is disabled when compiling Seagull. To enable OCTCAP support, you must
uncomment the "HP OC TCAP transport library" section in build.conf file and recompile Seagull.
In addition, OCTCAP include files must be present on the system on which Seagull is compiled. It is
advised to compile Seagull on the OCSS7 platform.
3. Getting started with TCAP
3.1. First try
Note:
As
HP OpenCall SS7
(http://www.hp.com/go/opencall/) is a pre-requisite for TCAP support in Seagull, an OCSS7 compliant platform must be
selected.
So that you can get familiar with Seagull, here is an example that will launch one TCAP server (a server
expects a message as the first scenario command) and one TCAP client (a client sends a message as the first
scenario command). The scenario is the following:
Open two terminal sessions. Terminal 2 will be the server and Terminal 1 the client. Examples are located in
the "run" directory. So the first thing you need to do is to go in this directory (in both terminal windows):
cd run
In Terminal 2 window type:
./start_server_itu.ksh
In Terminal 1 window type:
./start_client_itu.ksh
Seagull - OpenCall TCAP
Page 2
Copyright © 2006 HP OpenCall Software All rights reserved. On Terminal 2 (server side), you will see:
|------------------------+---------------------------+-------------------------|
| Start/Current Time
|
2005-12-14 10:04:11 |
2005-12-14 10:06:53 |
|------------------------+---------------------------+-------------------------|
|
Counter Name
|
Periodic value
|
Cumulative value
|
|------------------------+---------------------------+-------------------------|
| Elapsed Time
| 00:00:01:008
| 00:02:41:596
|
| Call rate (/s)
|
75.397
|
41.505
|
|------------------------+---------------------------+-------------------------|
| Incoming calls
|
76
|
6707
|
| Outgoing calls
|
0
|
0
|
| Msg Recv/s
|
149.802
|
82.985
|
| Msg Sent/s
|
149.802
|
82.979
|
| Unexpected msg
|
0
|
0
|
| Current calls
|
3
|
0.019
|
|------------------------+---------------------------+-------------------------|
| Successful calls
|
75
|
6704
|
| Failed calls
|
0
|
0
|
| Refused calls
|
0
|
0
|
| Aborted calls
|
0
|
0
|
| Timeout calls
|
0
|
0
|
|------------------------+---------------------------+-------------------------|
| Last Info
| Incomming traffic
|
| Last Error
| No error
|
|--- Next screen : Press key 1 ----------------------- [h]: Display help ------|
You can take a look at the log files, which contain the TCAP messages exchanged. By default, those files
are respectively
client.date.log
and
server.date.log
, suffixed with the date and time at which
traffic started.
How easy was that? Now let's jump to the next section to learn how all that works.
3.2. First try explained
Here is the script (start_client.ksh) that launched the client in our example:
#!/bin/ksh
export LD_LIBRARY_PATH=/usr/local/bin
seagull -conf ../config/conf.client-itu.xml -dico ../config/octcap-itu-dictionnary.xml
-scen ../scenario/client-itu.xml -log ../logs/client.log -llevel ET
Note:
On some systems, you might need to include the path to the HP-OC SS7 api into the environment variable SHLIB_PATH : "/opt/OC/lib/" for SS7 3.x
and "/opt/HP-AIN/SS7_WBB/sharedlib" for SS7 2.x . Add the following export in your Seagull script: "export
SHLIB_PATH=$SHLIB_PATH:/opt/OC/lib/" for HP-OC SS7 3.x or "export SHLIB_PATH=$SHLIB_PATH:/opt/HP-AIN/SS7_WBB/sharedlib/"
for HP-OC SS7 2.x .
Note:
On some HP-UX systems, you might need to include the following export in your Seagull script: "export SHLIB_PATH=/usr/local/bin".
This example is based on one client that sends the TC_BEGIN and exchanges TC_CONTINUE messages
with one server that receives a TC_BEGIN and answers by TC_CONTINUE messages, until it sends the
TC_END message.
Both sides are relying on the TCAP dictionary provided with the tool. We take the example of an ITU
configuration. The dictionnary is: octcap-itu-dictionnary.xml Refer to
dictionary configuration
section for
Seagull - OpenCall TCAP
Page 3
Copyright © 2006 HP OpenCall Software All rights reserved. more information on the format of this dictionary. The dictionary is specified using the
-dico
parameter on
the
command line
.
The generic configuration (including network and other parameters) is different for the client and the server.
The client uses
conf.client-itu.xml
and the server uses
conf.server-itu.xml
. The
configuration file is specified using the
-conf
parameter on the
command line
.
Here are both files:
conf.client-itu.xml
conf.server-itu.xml
<?xml version="1.0"
encoding="ISO-8859-1"?>
<configuration name="Simple TCAP
Client Conf">
<define entity="transport"
name="trans-octcap"
file="libtrans_octcap.so"
create_function="create_ctransoctcap_instance"
delete_function="delete_ctransoctcap_instance"
init-args="flavour=WBB">
</define>
<define entity="channel"
name="channel-1"
protocol="octcap-itu"
transport="trans-octcap"
open-args=
"
class=SS7_Stack_2;ossn=20;
application=2;instance=2">
</define>
<define entity="traffic-param"
name="call-rate"
value="1">
</define>
<define entity="traffic-param"
name="display-period"
value="1">
</define>
<def