HP OCMP SS7 Product and Software Dev Guide

HP OpenCall SS7 Release 3.
1 on Linux
Product and Software Developer's Kit
Release Notes
Edition 5, July 2003
Manufacturing Part Number:
5971-3501
E0703
NOTE
A monthly HP OpenCall SS7 Software Status Bulletin for release 3.1 on Linux will be available.
This bulletin lets you know all the news about HP OpenCall SS7 release 3.1 on Linux.
If you want to receive this bulletin, send an e-mail to majordomo@tidweb.grenoble.hp.com,
with "subscribe ocssbss7_3" in the message body.
3.1 on Linux, July 2003
Legal Notice
The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material,
including, but not limited to, the implied warranties of merchantability and fitness
for a particular purpose. Hewlett-Packard shall not be liable for any errors
contained herein, or for incidental or consequential damages in connection with
the furnishing, performance or use of this material.
This document contains proprietary information which is protected by copyright. All
rights reserved. No part of this document may be photocopied, reproduced, or
translated into another language without the prior written consent of HewlettPackard Company.
Copyright Hewlett-Packard Company 2000-2003. All rights reserved.
Trademarks
The following are trademarks or registered trademarks of Hewlett-Packard: HP-UX.
Linux is a registered trademark of Linus Torvalds.
RedHat is registered trademark of Red Hat, Inc.
Debian is a registered trademark of Software in the Public Interest, Inc.
Java and all Java-based marks are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States and other countries.
Microsoft Windows and Microsoft Internet Explorer are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
All other names and trademarks are the property of their respective owners.
Hewlett-Packard Company
OpenCall Business Unit
38053 GRENOBLE Cedex 9
France
Publication History
The following release note editions have been shipped for HP OpenCall SS7 release
3.1 on Linux:
January 2003 (HP OpenCall SS7 on Linux release 3.1)
First Edition:
Second Edition:
Third Edition:
Fourth Edition: June 2003 (HP OpenCall SS7 on Linux release 3.1)
Fifth Edition:
February 2003 (HP OpenCall SS7 on Linux release 3.1)
April 2003 (HP OpenCall SS7 on Linux release 3.1)
July 2003 (HP OpenCall SS7 on Linux release 3.1)
Conventions
Release
A release means a software version that has been released. The initial release
evolves by adding-on new packages. Its description and evolution history is
documented in the Release Notes.
Discontinued
Features or products no longer shipped but still supported
Obsolete
Features or products no longer shipped, no more supported
Contents
Conventions ........................................................................................................................................................ 3
1 Finding HP OpenCall Documentation ................................................................................................ 6

Whats in This Chapter? ..................................................................................................................................... 6
Where Do I Begin?.............................................................................................................................................. 7
Where to Find the Documentation .................................................................................................................. 8
Whats in This Document? ................................................................................................................................. 8
Whats in the Remaining Chapters? ................................................................................................................ 9
2 Whats New at a Glance .................................................................................................................... 10

Whats in This Chapter? ................................................................................................................................... 10
Whats New in the Initial HP OpenCall SS7 release 3.1 on Linux? ............................................................... 11
Section 1 : Release Information ............................................................................................................. 13

3 Features ............................................................................................................................................... 14
New features..................................................................................................................................................... 15
Protocol .......................................................................................................................................................... 15
Operation & Support .................................................................................................................................... 15
Performance .................................................................................................................................................. 18
Software Developer's Kit .................................................................................................................................. 19
Features incorporated from HP-UX releases ................................................................................................. 20
Protocol .......................................................................................................................................................... 20
Application Framework ................................................................................................................................ 20
Installation & Operation ............................................................................................................................... 21
Scalability and Performance ....................................................................................................................... 21
4 Supported Hardware and Operating Systems ................................................................................ 22

Supported Servers and Workstations.............................................................................................................. 23
Recommended Servers ................................................................................................................................... 23
Supported Linux Distributions........................................................................................................................... 24
Number of Supported TSUs and TSCs ............................................................................................................. 24
Number of Supported Links per Platform....................................................................................................... 25
Multiple LPCs Support....................................................................................................................................... 25
SS7 Hardware References ............................................................................................................................... 25
Hardware Requirements for Software Developers Kit.................................................................................. 26
5 Compatibility....................................................................................................................................... 27
Differences between HP-UX and Linux releases ........................................................................................... 28
Comparing Linux with HP-UX ........................................................................................................................... 29
Tools ................................................................................................................................................................ 29
Paths ............................................................................................................................................................... 29
OpenCall tools............................................................................................................................................... 30
Linux Resources.............................................................................................................................................. 30
Supported Configuration, maximum parameter settings and constraints ............................................... 31
APIs compatibility ............................................................................................................................................. 32
6 Software Description, Installation and Configuration ..................................................................... 34

Software Description ........................................................................................................................................ 35
List of packages delivered with HP OpenCall SS7 release 3.1 on Linux.................................................. 35
List of packages delivered with HP OpenCall SS7 release 3.1 Software Developers Kit on Linux ....... 37
Required Operating System......................................................................................................................... 37
Required OS patches (or patches superseding them)............................................................................. 37
Required applications .................................................................................................................................. 38
HP OpenCall patch dependencies............................................................................................................ 38
HP OpenCall patch conflicts ....................................................................................................................... 38
Customer application relink......................................................................................................................... 38
Customer application recompilation ......................................................................................................... 39
Installation.......................................................................................................................................................... 39
Installation from Scratch............................................................................................................................... 39
Offline Upgrade for 1 or 2-host cluster platform ........................................................................................ 40
Security and default passwords .................................................................................................................. 41
Pre-defined configurations.............................................................................................................................. 42
List of pre-defined configurations................................................................................................................ 43
Getting Started ................................................................................................................................................. 47
Generate and choose the predefined configurations ............................................................................ 47
Discover and configure the SS7 hardware ................................................................................................ 48
Starting the platform ..................................................................................................................................... 49
Configuration .................................................................................................................................................... 50
Configuring ISUP Loopback ......................................................................................................................... 51
7 Developer............................................................................................................................................ 52
Supported Libraries........................................................................................................................................... 53
API Modifications .............................................................................................................................................. 53
8 Defects ................................................................................................................................................. 54
Known Limitations ............................................................................................................................................. 55
New Known Problems ...................................................................................................................................... 55
Previously known Problems.............................................................................................................................. 55
Driver and Firmware ...................................................................................................................................... 55
Installation/Configuration............................................................................................................................. 57
Operation, Administration and Maintenance........................................................................................... 58
Stack ............................................................................................................................................................... 58
Libraries (APIs) ................................................................................................................................................ 60
ISUP.................................................................................................................................................................. 60
Conformance ................................................................................................................................................ 60
1 Finding HP OpenCall Documentation

Whats in This Chapter?
The purpose of this chapter is to help you to use these Release Notes more
efficiently. The following topics are covered:
Where Do I Begin?
Whats in This Document?
Whats in the Remaining Chapters?
Back to contents
Where Do I Begin?
The HP OpenCall SS7 release 3.1 on Linux Release Notes editions give up-to-date
information in addition to documentation guides. It also describes what is new, has
changed, or has become obsolete compared with the HP OpenCall SS7 releases
on HP-UX.
If for HP OpenCall SS7 release 3.1 on Linux, you need to have up-to-date
information in order to
find out what has changed since HP OpenCall SS7 release 3.1 on HP-UX,
know which defects exist on HP OpenCall SS7 on Linux release 3.1,
then have a look at these HP OpenCall release notes.

For other information, refer to the existing documentation on this release by using
the table below,
Application Developers
Guide
Conformance and
Compliance Statements
Glossary
Operations Guide
Troubleshooting Guide
TSU and TSC Starter Sheet
Release Notes
Welcome Guide
Describes the platform APIs.

Outlines platform conformance and compliance to ANSI, ITU-T
and other protocols.
Defines the terms used in the documentation set.
This guide contains procedures for installing,
HP OpenCall SS7 on Linux release 3.1 from scratch, configuring
the platform and SS7, how to start, stop and monitor the
platform, and how to use the platform management tools.
The guide also includes SS7 hardware (TSC, TSU) installation and
maintenance procedures, as well as platform expansion
procedures.
It lists and briefly describes the available graphical and
command line tools. It contains reference information for the
SS7 Monitor, configuration files, and the SNMP traps generated
by the platform.
Contains fault-finding and recovery information.
Describes the safety regulations and conformance to
international standards for TSUs and TSCs.
Contains release-specific information.
In particular, it contains details of the HP OpenCall SS7
packages, the servers and Linux distributions supported and
the installation/configuration instructions.
Describes the technical features of the platform
Back to
contents
Where to Find the Documentation
On the OpenCall software CD-ROM under: /hpdocs/doc_pdf or

/hpdocs/doc_htm. It can be read from Linux, HP-UX or MS Windows,
On the installed platform under: /usr/share/doc/hpoc-ss7
On the web at www.docs.hp.com (Telecom Infrastructure > SS7 Signaling

Platform)
Back to contents
Whats in This Document?

This document consists of two major sections.
The first section gives an up-to-date description of whats new, has changed or has
become obsolete on HP OpenCall SS7 release 3.1 on Linux, compared with the HPUX release, HP OpenCall SS7 release 3.1 (on HP-UX).
This also includes a list of up-to-date known defects, compatibility and developer
information. In addition, it gives information on how to install HP OpenCall SS7
release 3.1 on Linux.
Back to contents
Whats in the Remaining Chapters?

Here is a list of the remaining chapters of these Release Notes.
Chapter 2, Whats New at a Glance, provides a quick overview of the

changes to HP OpenCall SS7 release 3.1 on Linux compared with HP-UX
version of OpenCall SS7.
Chapter 3, Features, the purpose of this chapter is to describe which

features are new on the Initial HP OpenCall SS7 release 3.1 on Linux, which
features are incorporated compared with HP-UX version, or have changed.
Chapter 4, Supported Hardware and O.S., the purpose of this chapter is to

describe the supported and recommended hardware and the supported
Linux distributions.
Chapter 5, Compatibility, the purpose of this chapter is to mention

potential compatibility issues with respect to HP OpenCall SS7 on HP-UX
releases, or other applications running on the same platform.
Chapter 6, Software Description & Installation, the purpose of this chapter is

to describe the initial software delivery and how it needs to be installed.
Where needed documentation references are made.
Chapter 7, Developer, contains information for the developer community.
Chapter 8, Defects, gives an up to date list of known defects on the HP

OpenCall SS7 release 3.1 on Linux.
Back to contents
2 Whats New at a Glance

The purpose of this chapter is to give you a quick overview of the changes
introduced by the HP OpenCall SS7on Linux release 3.1 in comparison with HP-UX
releases.
Details of the changes are given in other chapters, which are cross-referenced.
Back to contents
10
Whats New in the Initial HP OpenCall SS7 release 3.1 on

Linux?
The following list includes changes in comparison with HP-UX releases of OpenCall
SS7.
Chapter 3: Features
Support for IA32 servers
Support for Linux distributions with 2.4.x kernel
Protocols: Chinese ISUP, TUP, facility to pivot (ANSI)
Operation and support
Software Developer's Kit
Platform configuration tools
CIC-based ISUP Distribution
Drop & Insert for E1 TSCs
Process management tools
Web management (to come)
SNMP TCAP Agent
New ocadmin user
New file system layout
On-line documentation
Performance figures
Chapter 4: Supported Hardware and Operating System
11
Supported hardware architecture: IA32 servers and Workstations. Supported

Operating System: Linux for Intel IA32 processors with kernel 2.4.x.
Chapter 5: Compatibility
64 links
SAM tool is replaced by Command-line tools
Comparing Linux with HP-UX tools
API Compatibility
Chapter 6: Software Description & Installation
HP Opencall SS7on Linux is customer installable
Software Description
Installation
Pre-defined configurations
Getting started
Configuration
Chapter 8: Defects
Up-to-date list of known problems for HP OpenCall SS7on Linux release 3.1
Back to contents
12
Section 1 : Release Information

This section gives an up-to-date description of whats new, has changed or has
become obsolete on HP OpenCall SS7 release 3.1 on Linux, compared with the HPUX releases.
This also includes a list of up-to-date known defects, compatibility and developer
information. In addition, it gives information on how to install and configure HP
OpenCall SS7 release 3.1 on Linux.
Back to contents
13
3 Features
The purpose of this chapter is to describe the features of the Initial HP OpenCall
SS7on Linux release 3.1, features which are incorporated or have changed from
HP-UX releases. For information on features discontinued or obsolete from HP-UX
releases, refer to chapter 5, Compatibility.
The following topics are covered:
New Features,
Features coming from OpenCall SS7 3.1 on HP-UX,
Back to contents
14
New features
Compared with the OpenCall SS7 3.1 on HP-UX release, new features are:
Protocol
NOTE
Chinese ISUP
TUP
Facility to pivot (ANSI)
British ISUP is not supported
Operation & Support
Supported Operating System: Linux for Intel IA32 processors, kernel 2.4.x.
Supported hardware architecture: Intel IA32 servers and workstations
Product installation
Product is able to be installed by customers. However for complex configurations,
such as high available platforms, it is strongly recommended to use the Factory
Integration Services - please contact your sales representative.
A SDK is available for development purpose. See section for detailed information.
Platform Configuration tools

The configuration is done with command-line interface tools.
A new set of command-line tools is now available to configure and manage the
platform configuration (see the man pages and the Operation Guide for further
details):
cfgPlatform: This command-line tool enables you to change the platform license,
to add/remove a Back End Host, to add/remove Application Guardians, to
add/remove an OC-LAN configuration, and to add/remove an SNMP or TCAP
Agent on a selected platform.
cfgMgr is a script used to manage the platform configuration and to generate predefined configurations. This tool can be used to copy, remove or view the platform
configurations. It may also be used to create or reset pre-defined configurations.
See the description list of the pre-defined configurations in Software Description,
Installation and Configuration.
15
cfgSs7Hw: This command-line tool is used to complete a platform configuration

discovery by cfgSs7HwCreate command-line tool, and after to manage the
hardware configuration.
cfgMtp: This command-line tool is used for adjusting the MTP3 parameters for the
chosen LPC on a selected platform configuration.
cfgTcap: This command-line tool is used for adjusting the TCAP parameters or
tuning the TCAP performance for the choosing LPC on a selected platform
configuration.
cfgSccp: This command-line tool is used for adjusting the SCCP parameters for a
chosen LPC on a selected platform configuration.
cfgIsup/cfgTup: This command-line tool is used to create configure and modify an
ISUP or TUP application.
cfgPropagate: This command-line tool is used to propagate the SS7 configuration
to all the systems of the OpenCall Platforms. Compared to HP-UX versions of
OpenCall, this has been simplified and updated to also propagate the OC-LAN
configuration.
Process management tools

ocftstatus: This tool gives information on the processes managed by the Fault
Tolerance Controller
ocftcontrol: This tool is used to perform actions on the processes managed by the
Fault Tolerance Controller (Start/Stop/Switchover)
Please refer to the Operations Guide and man pages for more information on
these tools.
Web based management

With HP OpenCall SS7 on Linux release 3.1, a set of Web based management
interfaces is available. These interfaces allow you to monitor the state of the
signaling resources (e.g. TSC and TSU) and a set of performance indicators (e.g.
TCAP Tps). This allows the use of standard Web browsers to monitor the overall state
of the platform. Full featured web management tool will be available later. (See
the configuration in Chapter 6)
SNMP Trap and TCAP Agent

SNMP traps generation can be configured to send alarms to alert the operator on
events like Link failure, MTP no longer ACTIVE, etc. A TCAP SNMP MIB is now
available for get-operation types, to monitor the TCAP performance statistics of
the platform
Back to contents
16
New default user ocadmin

This user replaces the default user of the previous releases (ss7admin). It is a
member of the group ocadmin. This change is done for the sake of homogeneity
across all products of the HP OpenCall family.
New file system layout
In order to have a common directory tree across all products of HP OpenCall
product family, the file-system layout of HP OpenCall SS7 Release 3.1 on Linux has
been changed with respect to previous releases.
Directory
/etc/opt/OC
/var/opt/OC/working_config
/opt/OC/include
/opt/OC/lib
Contents
Running configuration
Saved configurations
Include files
Libraries
On-line Documentation
Please refer to chapter 1 Finding HP OpenCall SS7 on Linux release 3.1

documents for detailed information.
The documentation is available on the HP OpenCall SS7 software CD-ROM. It

can be read from Linux, HP-UX or MS Windows.
The documentation is available on the web.
New simpler documentation structure.
Back to contents
17
CIC-Based ISUP Distribution

Up to 100 applications can be simultaneously connected to the same ISUP user
part of MTP on the same signaling stack, providing connectivity for up to 100 000
Circuit Identification Codes. You can connect either different applications or
several instances of the same application.
Incoming ISUP traffic is routed towards the application that handles the ISUP circuit
defined in its configuration. The circuit is identified by a couple [DPC value, CIC
value]. At any one time, a CIC can be assigned to just one primary instance. That
is, a circuit cannot be assigned simultaneously to several primary instances. To
enable flexible operation, a circuit can be dynamically reassigned to another
application.
MTP management messages are broadcast to applications. For example, all
applications would receive a message concerning the availability of the
MTPservice.
CIC-based distribution does not affect routing of outgoing messages.
NOTE
In a configuration with multiple ISUP applications, the applications must be started at

3seconds intervals.
Drop & Insert for TSCs
TSCs can be connected in a daisy-chain. This feature is also called Drop&Insert. This
allows the platform to increase the number of timeslots that it can use on the
network. Alarm propagation can be enabled for E1 TSCs. See the Operations
Guide.
NOTE
When alarm propagation is enabled for E1 TSCs and if the E1 link currently used for routing
the traffic is disconnected, an RAI message is sent on the other, chained link before the
anticipated AIS message.
Back to contents
Performance
18
On this initial release, OpenCall SS7 3.1 on Linux supports up to 4 TSCs and 2
TSUs. This corresponds to 64 T1/E1links or 16 V35 links.
HP OpenCall SS7 3.1 on Linux supports 2400 TCAP Transactions per second
(on a ProLiant DL 380G2 system).
HP OpenCall SS7 3.1 on Linux supports 1000 ISUP Calls per second (on a
ProLiant DL 380 G2), thanks to the new SS7 Parallel Engine technology
associated to the efficient Input /Output subsystem.
Multiple point code: there is no binding constraint. HP OpenCall SS7 3.1 on

Linux supports multiple point codes on a single processor. It is the target
application's responsibility to ensure that the hardware server configuration
will be able to drive the traffic capacity.
Back to contents

A free-of-charge Software Developer's Kit (SDK) is available for development/test
purposes only. The following features are not available with the SDK version:
Hardware connectivity,
High Available configuration,
Pre-defined configurations using hardware are not available (only stubbed

predefined configurations are available).
Back to contents
19
Features incorporated from HP-UX releases

The following list describes features that have been incorporated in the initial HP
OpenCall release 3.1 on Linux from HP-UX releases.
For details on these features, refer to the HP OpenCall SS7 Welcome Guide.
For information on discontinued or obsolete features, refer to chapter 5,
Compatibility.
Protocol
MTP, SCCP, and TCAP conform to ANSI 96 standard (Telcordia Test & Analysis
report available)
Support for Japanese (TTC) MTP
Support for a reverse-hybrid stack (ANSI TCAP over ITU SCCP & MTP), and
support for a hybrid stack.
Support for the major international versions of ISUP:
ISUP ANSI 95 & Telcordia 96: GR-246-core, GR-317-core, GR-394-core
ITU-T 88, 93, 97 recommended
ETSI V2 recommended
Japanese TTC2 standard
Support for national variants of the international ISUP standards: French

SSURN, Spain TESA, Italy International, Singapore
Application Framework
Only extended APIs are supported
32-bit APIs are supported
Support of Shared libraries
API source compatibility for applications developed on HP OpenCall SS7 on

HP-UX platforms : fully source compatible with HP OpenCall SS7 3.1 on HP-UX,
backward source compatibility with HP OpenCall SS7 2.X on HP-UX for SCCP
and TCAP APIs.
Support of Posix.1c Thread-Restricted level B
Redundant API connection to improve the total-failure recovery time
Back to contents
20
Installation & Operation
Product packaging allowing easy installation
Addition of Back-End system online.
Support for DNS: see Software installation and configuration for detailed
information.
Usability and operability enhancements in capability to configure the

platform with cfgSs7HwCreate
An automatic hardware discovery enables easier SS7 hardware

management. The following operations are now easily performed:
First configuration and update of a platform
Replacing a TSU or a TSC
Adding a TSU or a TSC
Replacing a LAN card in TSU
When running the tool, the hardware information is automatically discovered and
updated, the operator just has to accept and commit the configuration.
NOTE
When the operator updates the hardware part of the running configuration, messages are
displayed requesting the operator to run the command-line ss7HwLoad in order to take into
account the changes. Refer to the Operations Guide for more information.
Tools
ss7CheckPoint to save the network configuration
ss7DiagStart to manage SS7 hardware (old or new hardware)
ss7TcapTune to apply configuration changes related to an

expandability operation. This command is supported only on MTPbased platforms, and cannot be launched from the platform
manager (this issue will be fixed in a next patch).
SNMP traps to monitor the system using industry-standard network

management tools.
Scalability and Performance
Scalability of the TCAP stack on multi-processor systems.
Ability to share the TCAP processing load on a 2-host cluster.
Support of 2.x Active/Standby mode.
Back to contents
21
4 Supported Hardware and Operating Systems

The purpose of this chapter is to describe the Supported Hardware and Operating
Systems. for the OpenCall SS7 on Linux release 3.1 product (The last section applies
only to the SDK)
Supported servers and workstations
Recommended servers
Supported Linux distributions
Number of supported TSUs and TSC cards
Number of supported SS7 links per platform
Multiple LPCs support
SS7 hardware references
Hardware Requirements for Software Developers Kit
Back to contents
22
Supported Servers and Workstations

HP OpenCall SS7 on Linux 3.1 supports any type of Intel IA32 servers provided that:
The hardware is certified for distribution supported by HP OpenCall SS7 3.1 on

Linux.
The server has PCI slots for "TSC in system" configuration.
The server has 100BT LAN cards for TSU.
A minimum of 256 MB of RAM per LPC, please refer to the Operations Guide.
A supported Linux distribution is installed.
Disk space is available for:
The Linux distribution,
Additional Open Source components: depending of the distribution

can be up to about 200 MB,
HP OpenCall SS7 on Linux release 3.1 software: about 50 MB,
HP OpenCall SS7 3.1 on-line documentation: about 50 MB.
Back to contents
Recommended Servers
Server Type
TSC-in-TSU
HP cc2300
HP cc3300
ProLiant DL360G2
No
1-host (simplex)
ProLiant DL380G2 2-host (failure-resilient)
TSC-in-System
1-host
ProLiant DL380G3
This list will evolve on time. Please contact your HP sales representative for a
detailed and updated list of recommended servers (compatibility matrix).
Back to contents
23
Supported Linux Distributions

Distribution Name
Distribution
Version
Kernel Version
2.1
2.4.9
7.3
3.0
2.4.18-3
2.4.18-3
Red Hat
Advanced Server
(RHAS)
Red Hat
Debian
This list will evolve on time. Please contact your HP sales representative for a
detailed and updated list of supported distributions (compatibility matrix).
Back to contents
Number of Supported TSUs and TSCs

Systems
Cc2300
cc3300
DL360G2
DL380G2,
DL380G3
1-host
1-host
2-host
1-host
2-host
1-host
2-host
TSC in
system
Number of TSCs
N/A
N/A
N/A
Number of TSUs
Number of
E1/T1/J1
TSCs per
TSU
V35
TSC in
TSU
NA
NA
NOTE
1) Mixing of different types of TSCs (V35 or E1/T1/J1) is not supported.
NOTE
2) Maximum number of TSC in TSU on a platform is 4 with a maximum of 2 TSC per TSU for 2host cluster (failure-resilient).
Back to contents
24
Number of Supported Links per Platform
TSC in system
TSC in TSU
E1/T1/J1
V35
E1/T1/J1
cc2300
16
4
0
cc3300
16
4
64
Systems
DL360G2
16
4
64
V35
16
16
DL380G2, DL380G3
32
8
64
16
Back to contents
Multiple LPCs Support

Multiple MTP-based LPCs:
Front End
TSC-in-TSU
TSC-in-System
cc 2300
1 LPC
cc 3300
Up to 2 LPCs
1 LPC
DL 360 G2
DL 380 G2
Up to 4 LPCs
1 LPC
Up to 2 LPCs
Back to contents
SS7 Hardware References
TSU: J3401A
E1/T1 TSC: J3527A
V35 TSC: J3528A
Back to contents
25
Hardware Requirements for Software Developers Kit
Processor : IA32. Pentium 2 or higher is recommended
Memory : a minimum of 196 MB of RAM for one SS7 LPC, add 64 MB per
additional SS7 LPC
Disk space needed:
/opt/OC
500 MB
/etc/opt/OC 10 MB
/var/opt/OC 1 GB
Back to contents
26
5 Compatibility
The purpose of this chapter is to mention potential compatibility issues with respect
to previous HP OpenCall SS7 releases, or other applications running on the same
platform.
27
Differences between HP-UX and Linux releases.
Supported Configuration maximum parameter settings and constraints
APIs compatibility
Differences between HP-UX and Linux releases

The following list describes features, which have not been included and limitations
in the Initial HP OpenCall release 3.1 on Linux, compared with HP-UX versions.
SAM tool is replaced by command-line tools.
Maximun of 64 links.
Application Guardian is replaced by PIC/Application Guardian.

The aim of this replacement is to provide a common API across the different
products of HP OpenCall product family. PIC/Application Guardian also
brings the Plug in Communication API providing a message oriented
communication interface between application guardian instances.
ss7License command line interface is replaced by an option of cfgPlatform

(common to HP OpenCall family products). Please refer to the man page for
more details.
Use cfgPlatform tool to configure the OC-LAN (You do not need to edit
/etc/hosts file).
64 bits API are not supported on IA 32 architecture
Replication APIs are not available
Archive mode libraries are not available
Guardian Angel is not available
Loopback on a single TSC is not available
Scalability of ISUP application uses CIC-based distribution mechanism.
When the clock is moved backward or forward, the Open Call timer services
are shifted accordingly and therefore the opened timers are affected. This
may lead to HA processes being killed by the FTC or the FTC detecting a
scheduling problem and closing itself down.
Recommendation:
- Do not change the date on a running system: this should be done off-line
- ntp configuration must be done so that no clock jump is generated (-x
option)
Back to contents
28
Comparing Linux with HP-UX

Tools
HP-UX
lanscan
what
whence
whodo
glance
chatr
bdf
swinstall
swlist
/sbin/init.d/apache start
Lan configuration
hpterm
ksh
Linux
ifconfig -a
ident
which
who u (Red Hat)
who a (Debian)
top (terminal), gtop (X11), sar and
slmon
ldd
df
rpm (Red Hat, ...) or dpkg (Debian)
rpm qa (Red Hat)
dpkg l (Debian)
/etc/init.d/httpd start (Red Hat)
/etc/init.d/apache start (Debian)
systemconfigurator
xterm
bash
Paths
HP-UX
/etc/rc.config.d/netconf
/etc/hosts
/etc/nsswitch.conf
/etc/yp.conf
/etc/SnmpAgent.d/snmpd.conf
/var/adm/syslog/syslog.log
/var/adm/sw/swagent.log
Linux
Use systemconfigurator tool
/etc/snmp/snmpd.conf
/var/log/messages
/var/log/daemon.log
/var/opt/OC/audit/audit.log
/var/adm/nettl.LOGxx
/var/log/rpmpkgs (Red Hat)
/var/lib/dpkg (Debian)
Back to contents
29
OpenCall tools
HP-UX
easyConfig or
SS7 Platform
Configuration
FT_Monitor
ss7license
/etc/nettl
Linux
cfgInstall to install a platform
configuration.
cfgMgr to manage the platform
configuration.
cfgPropagate to propagate the
configuration to all the systems of the
platform
cfgSs7Hw to configure the SS7 hardware
parameters
cfgPlatform to configure platform
parameters
cfgMtp, cfgTcap, cfgSccp, cfgTup,
cfgIsup to configure protocols/applications
parameters
Do not modify yourself the configuration files:
you must use these tools!
ocftstatus to display information on the FTC
processes
ocftcontrol to perform actions on the
processes managed by the FTC
cfgPlatform license
/usr/sbin/nettl
Note:
ocftstatus man page displays some options that are not of use for standard HP
OpenCall process monitoring. The useful options are the following:
-C <processClass>
-refresh, to have the display of ocftstatus refreshed automatically.
If on a 2-host platform the stack is started simultaneously on the two front-end
hosts, ocftstatus will show the state of the two stacks as Mixed instead of Active.
This Mixed state is the result of some standby processes on both hosts instead of
having them all on the same host. It has absolutely no impact on the platform
operations.
Linux Resources
http://www.linuxhq.com/guides/index.html
http://www.tldp.org/
http://www.tldp.org/HOWTO/Online-Troubleshooting-HOWTO/index.html
http://www.ibiblio.org/pub/Linux/
Back to contents
30
Supported Configuration, maximum parameter settings

and constraints
MTP
1024 DPC (512 ANSI cluster) support
16 links per linkset
32 linksets per LPC
64 links. HP OpenCall SS7 3.1 Linux can support up to 64 signaling links (E1/T1
initially) on 4 TSCs and 2 TSUs.
SCCP/TCAP
31
64 GT tables for ANSI / ITU
2048 GT entries per LPC
4096 GT destinations per LPC
30 local SSN per LPC
16 active SSN per LPC
512 Concerned PCs per LPC in ANSI / ITU
Preferred/Next Preferred feature (10 DPC per GT) in ANSI
Primary/Secondary (2 DPC per GT) in ITU
32 TCAP connections
Support of digits A to F in SCCP Global Title Address Information in ANSI / ITU
Out of sequence reassembly in ANSI / ITU
ISUP
1024 DPC
100,000 circuits
up to 128 CIC ranges per application
4096 circuits per DPC according to ITU version
16384 circuits per DPC according to ANSI version
up to 100 ISUP primary applications
possibility of one secondary application per primary application
ANSI specific
Alias Point Code
8 bits SLS
XUDT/XUDTS
Message priority
Back to contents
APIs compatibility
32-bit APIs in shared mode.
API source compatibility with HP OpenCall SS7 3.1 on HP-UX.
Backward source compatibility with HP OpenCall SS7 2.X on HP-UX for SCCP
and TCAP APIs.
With HP OpenCall SS7 release 3.1 on Linux, the APIs are delivered in shared mode.
The benefit of the shared mode is that applications are no longer bound to the
library version, which allows HP to provide patches for the library without requiring
application recompilation and re-linking. In addition, shared libraries are the way
HP will provide compatibility in the future.
Back to contents
32
HP OpenCall SS7 release 3.1 on Linux libraries
Library
TCAP
ISUP
SCCP
OA&M
32-bit
X
X
X
X
64-bit
No
No
No
No
Archive
Shared
No
No
No
No
X
X
X
X
Thread Posix
X
X
X
X
Different linker command line: refer to the Application Developer's Guide for more
information.
Back to contents
33
6 Software Description, Installation and Configuration

The purpose of this chapter is to describe the initial software delivery and how it
needs to be installed. Where needed documentation references are made.
34
Installation
Configuration
List of packages delivered with HP OpenCall SS7 release 3.1 on Linux
NOTE
This section does not apply to SDK
Red Hat Advanced Server
Description
This package contains the configuration software for OpenCall

SS7
This package contains the High Availability software for OpenCall
SS7
hpocisup-3.1.74-1.redhatAS2.1.i386.rpm
This package contains the ISUP component for OpenCall SS7
hpocpic-3.1.74-1.redhatAS2.1.i386.rpm
PIC package
hpocpins-3.1.74-1.redhatAS2.1.i386.rpm
PINS package
hpocsecurity-3.1.74-1.redhatAS2.1.i386.rpm This package contains security software for OpenCall SS7
hpocss7-3.1.74-1.redhatAS2.1.i386.rpm
This contains ss7 APIs and Libraries need by hpocss7-hw-enabled
or hpocss7-sdk-enabled
hpoc-ss7-documentation-0.3-118.noarch.rpm This packages contains the user documentation in PDF and HTML
formats
hpocss7drivers-kernel-space-3.1.74This package contains the kernel space components for TSC in
1.redhatAS2.1.i386.rpm
system/TSU drivers for OpenCall SS7
hpocss7drivers-user-space-3.1.74This package contains the user space components for TSC in
system/TSU drivers for OpenCall SS7
hpocss7-hw-enabled-3.1.74This package contains the SS7 software for OpenCall with can
work TSC and TSU hardware
hpoc-ss7-linux-wrapper-3.1.74This package contains code that brings HP-UX specific
functionality on Linux
hpoc-ss7-nettl-3.1.74-1.redhatAS2.1.i386.rpm This package contains user space NetTL package
hpocss7-sdk-enabled-3.1.74This package contains the SDK software for OpenCall SS7.
hpocsupportability-3.1.74This package contains the supportability (logging/tracing)
software for OpenCall SS7
This package contains the TUP component for OpenCall SS7
hpoctup-3.1.74-1.redhatAS2.1.i386.rpm
hpocwebmon-3.1.74-1.redhatAS2.1.i386.rpm Web monitoring package
hpocconfiguration-3.1.741.redhatAS2.1.i386.rpm
hpocha-3.1.74-1.redhatAS2.1.i386.rpm
35
NOTE
This section does not apply to SDK
Red Hat
Debian
Description
hpocconfiguration-0.3-68.i386.deb This package contains the configuration

hpocha-0.3-70.i386.deb
This package contains the High Availability
hpocisup-0.3-118.i386.rpm
hpocisup-0.3-118.i386.deb
This package contains the ISUP component
for OpenCall SS7
hpocpic-0.3-63.i386.rpm
hpocpic-0.3-63.i386.deb
PIC package
hpocpins-0.3-63.i386.rpm
hpocpins-0.3-63.i386.deb
PINS package
hpocsecurity-0.3-63.i386.rpm
hpocsecurity-0.3-63.i386.deb
This package contains security software for
OpenCall SS7
hpocss7-0.3-63.i386.rpm
hpocss7-0.3-63.i386.deb
This contains ss7 APIs and Libraries need by
hpocss7-hw-enabled or hpocss7-sdkenabled
hpoc-ss7-documentation-0.3hpoc-ss7-documentation-0.3This packages contains the user
118.noarch.rpm
118.noarch.deb
documentation in PDF and HTML formats
hpocss7drivers-kernel-space-0.3- hpocss7drivers-kernel-space-0.3- This package contains the kernel space
67.i386.rpm
67.i386.deb
components for TSC in system/TSU drivers
for OpenCall SS7
hpocss7drivers-user-space-0.3- hpocss7drivers-user-space-0.3This package contains the user space
67.i386.rpm
67.i386.deb
components for TSC in system/TSU drivers
for OpenCall SS7
hpocss7-hw-enabled-0.3hpocss7-hw-enabled-0.3This package contains the SS7 software for
63.i386.rpm
63.i386.deb
OpenCall with can work TSC and TSU
hardware
hpoc-ss7-linux-wrapper-0.3hpoc-ss7-linux-wrapper-0.3This package contains code that brings HP64.i386.rpm
64.i386.deb
UX specific functionality on Linux
hpoc-ss7-nettl-0.3-63.i386.rpm
hpoc-ss7-nettl-0.3-63.i386.deb
This package contains user space NetTL
package
hpocss7-sdk-enabled-0.3hpocss7-sdk-enabled-0.3This package contains the SDK software for
63.i386.rpm
63.i386.deb
OpenCall SS7.
hpocsupportability-0.3hpocsupportability-0.3-68.i386.deb This package contains the supportability
68.i386.rpm
(logging/tracing) software for OpenCall SS7
This package contains the TUP component
for OpenCall SS7
hpoctup-0.3-64.i386.rpm
hpoctup-0.3-64.i386.deb
Web monitoring package
hpocwebmon-0.3-63.i386.rpm
hpocwebmon-0.3-63.i386.deb
hpocconfiguration-0.368.i386.rpm
hpocha-0.3-70.i386.rpm
Back to contents
36
List of packages delivered with HP OpenCall SS7 release 3.1 Software

Developers Kit on Linux
Red Hat
hpocconfiguration-0.335.i386.rpm
hpocha-0.3-34.i386.rpm
hpocisup-0.3-34.i386.rpm
hpocpic-0.3-34.i386.rpm
hpocpins-0.3-34.i386.rpm
hpocsecurity-0.3-34.i386.rpm
hpocss7-0.3-34.i386.rpm
hpoc-ss7-documentation-0.31.noarch.rpm
hpoc-ss7-linux-wrapper-0.334.i386.rpm
hpoc-ss7-nettl-0.3-34.i386.rpm
hpocss7-sdk-enabled-0.334.i386.rpm
hpocsupportability-0.334.i386.rpm
hpoctup-0.3-34.i386.rpm
hpocwebmon-0.3-33.i386.rpm
Description
Debian
hpocconfiguration-0.3-35.i386.deb This package contains the configuration
hpocha-0.3-34.i386.deb
This package contains the High Availability
hpocisup-0.3-34.i386.deb
This package contains the ISUP component
for OpenCall SS7
hpocpic-0.3-34.i386.deb
PIC package
hpocpins-0.3-34.i386.deb
PINS package
hpocsecurity-0.3-34.i386.deb
This package contains security software for
OpenCall SS7
hpocss7-0.3-34.i386.deb
This contains ss7 APIs and Libraries need by
hpocss7-hw-enabled or hpocss7-sdkenabled
hpoc-ss7-documentation-0.3This packages contains the user
1.noarch.deb
documentation in PDF and HTML formats
hpoc-ss7-linux-wrapper-0.3This package contains code that brings HP34.i386.deb
UX specific functionality on Linux
hpoc-ss7-nettl-0.3-34.i386.deb
This package contains user space NetTL
package
hpocss7-sdk-enabled-0.3This package contains the SDK software for
34.i386.deb
OpenCall SS7.
hpocsupportability-0.3-34.i386.deb This package contains the supportability
(logging/tracing) software for OpenCall SS7
This package contains the TUP component
for OpenCall SS7
hpoctup-0.3-34.i386.deb
Web monitoring package
hpocwebmon-0.3-33.i386.deb
Back to contents
Required Operating System

Linux with 2.4.x kernel: see the Supported Hardware and OS chapter for detailed
information.
Required OS patches (or patches superseding them)

N/A
37
Required applications
If you didnt choose the Factory integration service, you will have to install the
following packages with your Linux distribution:
Section
Application/System
Red Hat Packages Debian Packages Comments

Sysstat
sysstat
ucd-snmp-utils
Development/Languages
gcc-objc
gcc-objc
tclx
tclx
Development/System
kernel-source
Optional
Development/Libraries
ucd-snmp-devel
Optional
Development/Tools
ElectricFence
ElectricFence
Optional
dmalloc
dmalloc
Optional
rsh-server
rsh-server
System Environment/Daemons openssh-server
System Environment/Shells
Environment/Kernel
apache
apache
pdksh
pdksh
kernel-debug
Optional
kernel-bigmem
Optional
nscd
NOTE
sshd
nscd
The optional packages are not mandatory to run OpenCall but are recommended to
operate a platform.
For the SDK, please refer to the readme.txt file delivered with the kit.
Back to contents
HP OpenCall patch dependencies
N/A
HP OpenCall patch conflicts

N/A
Customer application relink

Required for all user applications.
38
Customer application recompilation

Required for all user applications.
Back to contents
Installation
CAUTION
Before installing the OpenCall packages, please check (with uname a) that the
kernel number is supported for this version of OpenCall (see the Supported
Hardware and OS chapter).
Installation from Scratch

For an installation on a system not already running HP OpenCall SS7, see HP
OpenCall SS7on Linux release 3.1 Operations Guide and following instructions.
39
Offline Upgrade for 1 or 2-host cluster platform

For an installation on a system with a previous HP OpenCall SS7 3.1 release on Linux
(This procedure does not apply to SDK).
1. Perform all the necessary backups (platform configurations)
2. Make sure that the new packages are available on the system (mount the
CD or copy the packages...)
3. Log as root user
4. Stop the user applications
5. Stop the platform: ss7Stop all
6. Only for RedHat sytems: remove the old packages (hpocconfiguration,
hpocsupportability, hpocha, hpocisup, hpoc-ss7-documentation), for
each of them:
rpm -ev --nodeps hpocXXX.rpm
7. Install the new packages (hpocconfiguration, hpocsupportability, hpocha,
hpocisup, hpoc-ss7-documentation):
For RedHat systems run one command to install all the packages:
rpm -ivh hpocconfiguration-0.3-68.i386.rpm hpocsupportability-0.368.i386.rpm . hpocisup-0.3-118.i386.rpm
Note: the hpocconfiguration and the hpocsupportability packages are
interdependent. They must be installed in the same shot.
For debian systems run the following command for each new
package:
dpkg -i hpocXXX.deb (same as dpkg --install hpocXXX.deb)
8. If needed enable the ISUP CIC-based distribution:

a. create a new configuration (using cfgCreate)
b. install the new configuration
9. Start the platform: ss7Start
10. Start the user application
Note: if the ISUP CIC-based distribution is enabled, the ISUP applications
must be designed for it, see the Application Developer's Guide for HP
OpenCall SS7 3.1 on Linux.
CAUTION
40
isupgen and ISUP tutorials enable ISUP CIC-based distribution by default. If you do
not intend to use CIC-based distribution for these applications after upgrading,
refer to the man page for details of the different options.
Security and default passwords

If you install OpenCall on a Red Hat distribution, check that the internal firewall is
disabled (please see the Troubleshooting Guide for detailed information).
The user configures and manages the platform without being logged on as root:
packages installation creates the ocadmin user and ocadmin group (home
directory /home/ocadmin). The default password for ocadmin is ocadmin.
To log in remotely as root, you must first log in from another user account (for
instance ocadmin / ocadmin) and then log in as root (type su ).
On pre-installed platforms, the default password for root is hwroot.
Back to contents
41
Pre-defined configurations
The HP OpenCall SS7 platform includes a test environment that makes application
testing easier. This environment provides either communication between two HP
OpenCall SS7 stacks or communication between a HP OpenCall SS7 stack with the
SS7 network using TSC-in-System or TSUs. Thirty pre-defined configurations are
provided, enabling either end-point or gateway-type applications for ISUP, TUP
and TCAP layers.
NOTE
42
NOTE The pre-defined configurations do not enable CIC-based ISUP distribution and do
not allow you to run an ISUP application that uses this feature. If you wish to implement CICbased distribution, you must create your own configuration. See the Operations Guide for
details.
List of pre-defined configurations

A list of the available configurations is given below. To load one of the pre-defined
configurations, see the section Installing a pre-defined configuration in the
platform configuration chapter of the Operation Guide.
MTP2 Stubbed Configurations
Platform Topologies
TCAP
TCAP
SCCP
SCCP
MTP
MTP
TCAP
TCAP
GDI
GDI
ISUP
TCAP
SCCP
ISUP
TCAP
SCCP
MTP
Platform_2
Pair of ANSI 96 stacks (AAA)

No ISUP, no TUP
Platform_3
Pair of ITU-T 92 stacks (WBB)

No ISUP, no TUP
Platform_8
Pair of ANSI-96 stacks with Application

Message Dispatcher feature
Platform_9
Pair of ITU-92 stacks with Application Message

Dispatcher feature
Platform_4
Pair of ANSI-96 stacks (AAA) on GDI layer
Platform_5
Pair of ITU-92 stacks (WBB) on GDI layer
Platform_10
Pair of ISUP ANSI stacks with message set

IsupA95 with CIC from 0 to 16383, bi-directional
Platform_11
Pair of ISUP ITU stacks with message set IsupI97

with CIC from 0 to 4095, bi-directional
Platform_12
Pair of ISUP TTC stacks with message set TTC3

Platform_16
Pair of TUP Chinese stacks (no MsgSet option)

TUP
TCAP
SCCP
MTP
Description
MTP
TUP
TCAP
SCCP
Platform Id
MTP
Back to contents
43
Gateway Configurations
TCAP
TCAP
TCAP
SCCP
SCCP
SCCP
SCCP
MTP
MTP
MTP
MTP
TCAP
Platform_1
Platform_6
TCAP
TCAP
TCAP
TCAP
SCCP
SCCP
GDI
GDI
MTP
MTP
Platform_7
ISUP
TCAP
SCCP
ISUP
TCAP
SCCP
MTP
ISUP
TCAP
Platform_13
MTP
SCCP
SCCP
MTP
Pair of ANSI 96 stacks (AAA) on GDI layer,

plus
Pair of ANSI 96 stacks
Pair of ITU-92 stacks (WBB) on GDI layer plus

Pair of ITU-92 stacks (WBB)
Pair of ISUP ANSI stacks with message set

IsupA95 (CIC from 0 to 16383, bi-directional),
plus
Pair of ISUP ITU-T stacks with message set
IsupI97 (CIC from 0 to 4095, bi-directional)
ISUP
TCAP
Pair of ANSI 96 stacks (AAA) plus

Pair of ITU-92 stacks (WBB)
No TUP, no ISUP
Platform_14
MTP

IsupI97
(CIC from 0 to 4095, bi-directional), plus
Pair of ISUP TTC stacks with message set TTC3
(CIC from 0 to 4095, bi-directional)
TCAP
TCAP
SCCP
SCCP
MTP
MTP
ISUP
TCAP
SCCP
SCCP
MTP
NOTE
44
ISUP
TCAP
Platform_15

IsupI97 (CIC from 0 to 4095, bi-directional),
plus
Pair of ITU-T 92 stacks
MTP
If you want to use only MTP2 Stubbed and/or Gateway Configurations the license option
for cfgMgr tool is not required.
Configurations with TSC (does not apply to SDK)

Default configuration:
SS7 Stack ClassName: SS7_Stack_1 (Not changeable)
Hardware configuration: these configurations should be discovered with cfgSs7HwCreate and modified
with cfgSs7Hw tool.
Note: In configurations 34 / 35 / 36 and 37, the ISUP / TUP configurations already have a set LPC and DPC
(LPC =1, DPC=2 for ITU; LPC=1.1.0, DPC=2.2.0 for ANSI).
However the associated stack does not have a predefined LPC and DPC. If you wish to use the ISUP / TUP
configurations you must set the LPC and DPC of the stack to be in accord with that on ISUP / TUP
configurations.
Note: A license codeword is required to use these configurations (not usable with SDK platforms)
Platform_31
One ANSI 96 stack (AAA)
Platform_32
One ITU-T 92 stack (WBB)
Platform_33
One ITU-TTC stack
Platform_34
One ISUP ANSI stack with message set IsupA95 with CIC
from 0 to 16383, bi-directional
Platform_35
One ISUP ITU stack with message set IsupI97 with CIC
Platform_36
One ISUP TTC stack with message set TTC3 with CIC from
0 to 4095, bi-directional
Platform_37
One TUP Chinese stack (no MsgSet option) with CIC

TCAP
SCCP
MTP
TSC
TCAP
ISUP
SCCP
MTP
TSC
TCAP
TUP
SCCP
MTP
TSC
45
Configurations with TSU (does not apply to SDK)

Default configuration:
SS7 Stack ClassName: SS7_Stack_1 (Not changeable)
Hardware configuration: these configurations should be discovered with cfgSs7HwCreate and modified
with cfgSs7Hw tool. These are duplex configurations
Note: In configurations 44 / 45 / 46 and 47, the ISUP / TUP configurations already have a set LPC and DPC
(LPC =1, DPC=2 for ITU; LPC=1.1.0, DPC=2.2.0 for ANSI).
However, the associated stack doesnt have a predefined LPC and DPC. If you wish to use the ISUP / TUP
configurations you must set the LPC and DPC of the stack to be in accord with that on ISUP / TUP
configurations.
Note: A license codeword is required to use these configurations (not usable with SDK platforms)
TCAP
Platform_41
One ANSI 96 stack (AAA)
Platform_42
One ITU-T 92 stack (WBB)
Platform_43
One ITU-TTC stack
Platform_44
One ISUP ANSI stack with message set IsupA95 with

CIC from 0 to 16383, bi-directional
Platform_45
One ISUP ITU stack with message set IsupI97 with CIC
Platform_46
One ISUP TTC stack with message set TTC3 with CIC
Platform_47
One TUP Chinese stack (no MsgSet option) with CIC

SCCP
MTP
TSU
TSC
TCAP
ISUP
SCCP
MTP
TSU
TSC
TCAP
TUP
SCCP
MTP
TSU
TSC
Back to contents
46
Getting Started
The following instructions are given to help you start your platform for the first time.
This using example is based on the predefined configurations. Please read the
Operation Guide for detailed information on the platform operation. In particular,
the Operations Guide explains how to create your own configuration.
Generate and choose the predefined configurations

These instructions are required in case you need to use the predefined
configuration (convenient for a quick start for instance with a SDK or developer
platforms). See the Operation Guide if you need to create your own configuration.
Step 1.
Log in as ocadmin on one host.
Step 2.
Generate the pre-defined configurations using cfgMgr.

Example for a duplex platform:
cfgMgr -resetTemplate all license <codeword> -host1 <foo1> -host2
<foo2>
Step 3.
Choose one of the pre-defined configurations.
Step 4.
Install the pre-defined configuration: cfgInstall from

/var/opt/OC/working_config/platform_<id>
Step 5.
If you chose a pre-defined configuration with hardware (platform_31 to 37 or 41 to

47), you may have to launch a hardware auto-discovery and then complete the
hardware configuration (see section Discover and configure the SS7 hardware).
Note: If you want to use only MTP2 Stubbed and/or Gateway Configurations, the
license option for cfgMgr tool is not required.
Back to contents
47
Discover and configure the SS7 hardware

This section is applicable only if you are using a configuration using SS7 hardware.
(does not apply to SDK) Please read the Operation Guide and man pages for
detailed information.
NOTE
Be sure that you already have installed the configuration (with cfgInstall)
before starting the auto-discovery tool (cfgSs7HwCreate)
First, determine what SS7 hardware is installed on the platform. To find the SS7
hardware, you must use the cfgSs7HwCreate tool (refer to the man pages). Then,
adjust the TSC parameters (if needed) and create the associated links. To modify
and create links for a configuration, use the cfgSs7Hw tool.
Step 1.
Log in as ocadmin
Step 2.
Launch an auto-discovery of the SS7 hardware configuration with

cfgSs7HwCreate.
See below for an example of cfgSs7HwCreate:
TSC in system:
cfgSs7HwCreate file /etc/opt/OC/SS7/ss7.hw host1 <foo1> -hwMode
TSC
TSU:
cfgSs7HwCreate file /etc/opt/OC/SS7/ss7.hw host1 <foo1> -host2
<foo2> -hwMode TSU
Step 3.
Check TSU and TSC ids:

TSC in system :
ss7TscPing v
TSU :
ss7TsuPing v
Step 4.
Modify the TSC parameters if needed with the cfgSs7Hw tool.

See the different parameters for each TSC : cfgSs7Hw view.
The following are examples of cfgSs7Hw use (refer to cfgSs7Hw manpage for more
information) :
Modify framing option on the second TSC card :
cfgSs7Hw modify -tsc 2 framing ESF
Modify clock source on the TSC 0 card :
cfgSs7Hw modify -tsc 0 clock_source internal
Step 5.
Check that changes have been made: cfgSs7Hw view
Step 6.
Create the links.

For each TSC add a link with cfgSs7Hw:
Examples of cfgSs7Hw usage to add a link to a TSC port.
48
Create link on TSC 0 on port 2 with time slot 3 (for a E1 or T1 card):

cfgSs7Hw add -link tsc 0 port 2 -timeSlot 3
Step 7.
Check that changes have been made : cfgSs7Hw view
Step 8.
To add additional links, repeat step 6.
Step 9.
Initialize the TSC/TSU with the new configuration: ss7HwInit with f option (refer
to the manpage)
Step 10.
Test the HW state :

TSC in system : ss7TscStatus L
Note: if the card is not properly configured, you will obtain a TSC status
unreachable error message.
TSU : ss7TsuStatus L
Step 11.
If you have a duplex platform, use cfgPropagate to propagate the modified

configuration.
cfgPropagate all
Back to contents
Starting the platform

Once your platform is configured, you can start it:
Step 12.
Log in as ocadmin
Step 13.
Start the SS7 stack: ss7Start
Step 14.
Wait until stacks are ready: check with ocftstatus
Step 15.
Start the SS7 management tool: ss7MgrStart
Step 16.
Use the SS7 monitor to configure the SS7 Network parameters (LPC, DPC )
(required only for HW configurations).
See the OpenCall Operations Guide for more information on platform operation
and management.
Back to contents
49
Configuration
Please refer to the HP OpenCall SS7 on Linux release 3.1 Operations Guide and the
man pages for more details on command-line tools.
This section gives additional information for platform configuration.
50
Configuring ISUP Loopback

An ISUP Loopback entry is always made in the global.conf file. If a single stack
configured on the system, this entry requires no change.
If multiple stacks are configured, then by default this entry must be configured. The
following fields will need to be updated to set the loopback on the stack you want
to use. If so desired (replace the index set to 1 for the first stack with the stack
number, CLASS_NAME of the first stack with class name of the stack):
StackId = (1)
GroupLeader = CLASS_NAME_1_ftc
Host_Address_1 = host1, ha_ss7_1
Host_Address_2 = host2, ha_ss7_1
(for duplex only)
Another change is required to the ISUP application configuration file (for both 1 or
more stacks) so that it may use the loopback. Use cfgIsup to change the stack
name and the ISUP protocol: classname=SS7_ISUP_LOOPBACK
IsupProtocol=ANSI_LOOPBACK
NOTE
ISUP loopback can only be used when CIC-based distribution is disabled.
Back to contents
51
7 Developer
This chapter covers the topics mentioned below. (For other relevant information,
also see chapter Compatibility)
Supported libraries
API Modifications
Back to contents
52
Supported Libraries
All the libraries are now under /opt/OC/lib.
All the header files are under /opt/OC/include, /opt/OC/include/ISUP,
/opt/OC/include/TUP.
API Modifications
There are no modifications with regard to release 3.1. Please refer to the
Compatibility chapter in these release notes for more details about the obsolete
features.
Back to contents
53
8 Defects
All known problems of release 3.1 on Linux are mentioned here.
NOTE
Known Limitations
Known Problems
Previously Known Problems on both HP-UX and Linux releases
Defects related to hardware are not applicable to Software Developer's Kit release.
Back to contents
54
Known Limitations
JAGae62572
Only one secondary SS7 connection per primary one is supported
Any primary connection using OpenCall API (MTP, SCCP, TCAP, ISUP, OAM ...)
supports only one secondary connection.
New Known Problems

These problems are mostly specific to HP OpenCall SS7 on Linux.
JAGae82828
ISUP dynamic config: previous modifications are replayed
When an dynamic change is done on an ISUP application (example application
number 1), a /var/opt/OC/SS7/isup.conf.diff1.tdi file is created by ss7IsupReload
CLI to update dynamically the configuration of the application. This file is never
renamed, causing a new load of this file during all other dynamic configuration of
any ISUP application.
Workaround:
Before any dynamic configuration, check that no file file
/var/opt/OC/SS7/isup.conf.diff*.tdi is present. If any, move the file
/var/opt/OC/SS7/isup.conf.diff*.tdi in /var/opt/OC/SS7/isup.conf.diff*.tdi.old (on
both hosts if 2-host cluster configuration).
JAGae57566
The CLI ss7HwCheck does not work
JAGae70593
wlog extended does not work (log windows killed just after being poped)
Back to contents
Previously known Problems

These problems are common with HP OpenCall SS7 on HP-UX.
Driver and Firmware
JAGad67398
TSC V35 boards ignore modem signals
MTP2 ensures this capability without need for level1 hardware signals.
JAGae03843
55
Errors could occur when loading a new SS7 hardware configuration

It may occur that when creating a new hardware configuration, you have
following errors and the hardware configuration isn't downloaded in the TSCs.
(firmware not changed) see the error below:
---> Executing SS7HwLoadConfig on host <host>
---> Executing SS7TsuInit on TSU 4
Firmware downloading starting on TSU 4. This operation may take up to one minute
to complete. Please wait...
Current firmware on TSU 4 up to date: no download performed SS7.hw file
successfully downloaded to TSU 4
---> Executing SS7TsuInit on TSU 1
Firmware downloading starting on TSU 1. This operation may take up to one minute
to complete. Please wait...
Current firmware on TSU 1 up to date: no download performed SS7.hw file
successfully downloaded to TSU 1
...
...
Error SIMGR_DC_E_ERROR_STREAM_FAILURE when creating Link 0 on TSC 11:
(Cause := MsgRef(11036):, Action := MsgRef(11037):)
Error CA_ERROR_STREAM_FAILURE when downloading configuration on TSC 11
Error SIMGR_DC_E_ERROR_STREAM_FAILURE when creating Link 4 on TSC 12 :
Error SIMGR_DC_E_ERROR_STREAM_FAILURE when creating Link 8 on TSC 21:
(Cause:= MsgRef(11036):, Action := MsgRef(11037):)
...
...
Error SIMGR_DC_E_ERROR_STREAM_FAILURE when creating Link 96 on TSC 44 :
End of SS7HwInit execution
General Workaround:
Use SS7HwInit -f with -u (for TSC- in-TSU) or -c (for TSC-in-System). Note that the
SS7HwInit -f resets all the links of the TSU (-u option or of the TSC (-c option),
momentarily interrupting traffic on this device. So perform this operation one TSU
per one TSU or one TSC per one TSC and only on the TSUs or TSCs that encounter
problems
Back to contents
56
Installation/Configuration
JAGad67593
Hostname discrepancy in /etc/hosts causes problems.
When there is a discrepancy between the hostname of configuration files
/etc/hosts of each FE host, the HP OpenCall SS7 platform does not function
properly.
Prevention:
Configure /etc/hosts. The SS7 processes (started with ss7Start) as well as the Node
management processes (started with ss7MgrStart) and the applications (customer
dependent) will start correctly if /etc/hosts is correct.
Copy the /etc/hosts file to the other hosts on the platform. It must be the same on
the Front-end hosts, the Platform Manager and the Back-end hosts.
JAGad67402
Proxy congestion possible if TCAP timer is inappropriately set
When the TCAP setTimerPeriod parameter is set to a value that is too close to the
maximum lifetime of a connection, a high number of connections could
potentially be closed simultaneously. This may lead to proxy congestion.
Prevention:
Increase the setTimerPeriod value with cfgTcap command line tool. This value
should be greater than the maximum lifetime of a connection.
JAGad67848
Can't set route of new APC created after removing one of 32 APCs.
When 32 APCs with one primary route for each are created and then the operator
removes one, the operator is not allowed to create a new DPC with a different
route.
JAGae04498
Japanese and ITU/ANSI hardware protocol may not be correctly set.
Sometimes, when the operator changes the standard flavor of a platform from
ITU/ANSI to TTC or from TTC to ITU/ANSI, SS7 links encounter some alignment
problems.
Workaround:
Edit and correct the /etc/opt/OC/SS7/ss7.hw file as follows:
1/ For each TSC, edit in the [TSC_] section the parameter: Protocol.
Set it to the correct value: HSL|NSL|JNSL. JNSL is reserved for the Japanese flavors.
2/ For each stack, edit in the [MTPL2_] section the parameter: RoutingLabelFormat.
Set it to the correct flavor value:
ANSI_88|ANSI_92|ITU_88|ITU_92|CHINESE|JAPANESE
57
3/ Reload the hardware configuration:

Perform ss7HwInit -f -u on each TSU or in case of TSC-in-System perform ss7HwInit -f c on each TSC.
Validation of the workaround:
To check the right hardware features are loaded:
1/ run ss7DiagStart
2/ go on any link
3/ types an info command and check the protocol type
Note: The ss7HwInit command will reset the TSU specified. So, before doing it, make
sure the corresponding HP OpenCall SS7 Stack is not running.
JAGad67882
cfgCreate - some options are not supported
By default, cfgCreate creates a configuration as RUNNING: the previous running
configuration could be scratched.
Workaround:
Always set to option of cfgCreate to the target directory.
Back to contents
Operation, Administration and Maintenance
JAGad67902
cfgCheck returns error messages even when configuration is correct.
Running cfgCheck creates the following log message, even when the
configuration is correct:
ss7TsuDownloadConfig -s returns errors: SIMGR_TSU_E_NO_ERROR while checking
the SS7.hw file on TSU
Back to contents
Stack
JAGad67915
Some TTC compliance problems
Behavior incompatible with TTC: If a MTP_PAUSE is received for a given DPC before
a MTP restart and if this DPC is restarted before MTP restarts, the DPC is stuck as a
PAUSED DPC and no more traffic can be received nor sent out on the DPC.
Periodical SRT Message sent by ITU-TT2 timer regardless TTC Flavor
Current SS7 stack sends "SRT" signal to SP periodically at each T2 timer setting. T2
timer is not defined in TTC standard (JT-Q707) but in ITU-T standard. As far as SS7
stacks is used in "TTC" mode, T2 timer capability should NOT be effective
JAGad67918
A link added to a linkset is not taken into account in the load-sharing algorithm
58
Workaround:
Deactivate the linkset and re-activate it
JAGad67920
DPC may stay in CONGESTED State after congestion at link level
Workaround:
In the SS7 Monitor, deactivate and reactivate the DPC.
JAGad67921
OutOfSequence reassembly requested for SCCP WB implementation.
JAGad67923
Requests for statistics on GT translator objects do not work
From SSCP OA&M API, the request to get statistics on GT translator object is not
correctly handled by SS7 Stack.
JAGad67924
SCCP + TCAP APIs: after congestion, uncongested notification can be lost
When receiving a status CONGESTED for a signaling point
(SC_congested/dpc_congested), the application will stop SCCP/MTP traffic and
wait for notification indicating the end of congestion (SC_uncongested
/dpc_uncongested). In the case of API congestion, this message may be
discarded by the stack and therefore never received by the application.
Prevention:
The application must not wait indefinitely to receive this notification but try to
restore traffic.
The application must not wait indefinitely for the uncongested notification but
keep on scheduling the connection without sending anything for the congested
point code for a given duration (a few seconds), and restart.
JAGad67927
Problem with linkset Out of Service due to links inhibited
When a linkset is OutOfService due to all links being inhibited (this is possible when
another route is available), a 'force uninhibit' will occur if another DPC becomes
unavailable, even though this DPC has no route configured through this linkset.
Precaution:
Keep at least one link uninhibited per linkset (normal configuration)
JAGad67934
PFT_nChannels and UFT_nchannels: not up-to-date for 32 TCAP connections
When using more than 16 TCAP connections, in the file
/etc/opt/OC/platform/global.conf, you must set:
59
PFT_nChannels to the value 60 instead of 40

UFT_nChannels to the value 32 instead of 16
Back to contents
Libraries (APIs)
JAGad67597
TCAP msg disp does not support same (appli_id, instan_id) with dif. SSN
The TCAP Application Message Dispatcher does not support the same couple
(application_id, instance_id) used with more than one SSN.
JAGad67599
The number of OA&M statistics on the HP OpenCall SS7 stack is limited
The number of statistics that HP OpenCall SS7 has to manage at one time is limited
in order to prioritize the traffic handling.
For MTP3 OAM the maximum number of occurrence or periodic statistics that can
be used at one time is 250.
For SCCP OAM the maximum number of periodic statistics used at one time is 200.
The SS7Monitor uses some OAM resources when it is started during the operation of
the HP OpenCall platform. Therefore, the operator should use it with precaution
when using a big configuration to avoid exceeding the limitations. (Read
README.OAM file in the directory /opt/OC/tutorials for more details).
Back to contents
ISUP
JAGae03880
Only one active ISUP application instance is supported
JAGad67936
Secondary ISUP application may not recover traffic after Active system failure
After a system failure, secondary ISUP application sometimes does not recover
traffic and/or Secondary application handles traffic instead of primary one.
Back to contents
Conformance
JAGad68338
Multiple DPC in the same remote cluster may conflict the congest. Level
In remote cluster mode, when multiple members (DPCs) of a remote cluster are in
congestion state at the same time with different level of congestion (depending of
the order of the TFC received), the stack may not manage the level of congestion
correctly.
Back to contents
60
Back to contents
End of the Release Notes
61

HP OCMP SS7 Product and Software Dev Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

HP OCMP SS7 Product and Software Dev Guide

Transféré par

Droits d'auteur :

Formats disponibles

HP OpenCall SS7 Release 3.

Manufacturing Part Number:

3.1 on Linux, July 2003

3.1 on Linux, July 2003

February 2003 (HP OpenCall SS7 on Linux release 3.1)

April 2003 (HP OpenCall SS7 on Linux release 3.1)

July 2003 (HP OpenCall SS7 on Linux release 3.1)

1 Finding HP OpenCall Documentation ................................................................................................ 6

2 Whats New at a Glance .................................................................................................................... 10

Section 1 : Release Information ............................................................................................................. 13

4 Supported Hardware and Operating Systems ................................................................................ 22

3.1 on Linux, July 2003

6 Software Description, Installation and Configuration ..................................................................... 34

1 Finding HP OpenCall Documentation

Whats in This Document?

Whats in the Remaining Chapters?

3.1 on Linux, July 2003

know which defects exist on HP OpenCall SS7 on Linux release 3.1,

then have a look at these HP OpenCall release notes.

Describes the platform APIs.

3.1 on Linux, July 2003

Where to Find the Documentation

On the OpenCall software CD-ROM under: /hpdocs/doc_pdf or

On the installed platform under: /usr/share/doc/hpoc-ss7

On the web at www.docs.hp.com (Telecom Infrastructure > SS7 Signaling

Whats in This Document?

3.1 on Linux, July 2003

Whats in the Remaining Chapters?

Chapter 2, Whats New at a Glance, provides a quick overview of the

Chapter 3, Features, the purpose of this chapter is to describe which

Chapter 4, Supported Hardware and O.S., the purpose of this chapter is to

Chapter 5, Compatibility, the purpose of this chapter is to mention

Chapter 6, Software Description & Installation, the purpose of this chapter is

Chapter 7, Developer, contains information for the developer community.

Chapter 8, Defects, gives an up to date list of known defects on the HP

3.1 on Linux, July 2003

2 Whats New at a Glance

3.1 on Linux, July 2003

Whats New in the Initial HP OpenCall SS7 release 3.1 on

Support for IA32 servers

Support for Linux distributions with 2.4.x kernel

Protocols: Chinese ISUP, TUP, facility to pivot (ANSI)

Operation and support

Software Developer's Kit

Platform configuration tools

CIC-based ISUP Distribution

Drop & Insert for E1 TSCs

Process management tools

Web management (to come)

SNMP TCAP Agent

New ocadmin user

New file system layout

Chapter 4: Supported Hardware and Operating System

Supported hardware architecture: IA32 servers and Workstations. Supported

3.1 on Linux, July 2003

SAM tool is replaced by Command-line tools

Comparing Linux with HP-UX tools

Chapter 6: Software Description & Installation

HP Opencall SS7on Linux is customer installable

3.1 on Linux, July 2003

Section 1 : Release Information

3.1 on Linux, July 2003

Features coming from OpenCall SS7 3.1 on HP-UX,

Software Developer's Kit