Skip Headers
Oracle® Communications Service Broker System Administrator's Guide
Release 6.1

Part Number E29444-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

11 Starting and Stopping the SS7 Process

This chapter explains how to start and stop the SS7 process on Signaling Servers.

About the SS7 Process

The SS7 process is a native SS7 stack wrapper, required in every solution in which Service Broker communicates with entities in the SS7 network. The SS7 SSU sends and receives SS7 traffic through the SS7 process.

The process is included in all Service Broker packages, excluding the Policy Controller that does not require SS7 connectivity.

The SS7 process needs to run on each of the servers where the SS7 SSU is deployed. In a clustered split domain (that is, when deploying separate Signaling and Processing domains), you run the SS7 process on each of the Signaling Servers in the Signaling domain. In a basic single domain deployment, you run the SS7 process on each of the servers in the domain.

There are two types of SS7 processes, one for each type of SS7 network: SIGTRAN and TDM. For each network type, there are two process binaries, one for Linux and another for Solaris.

The binaries of the SS7 process are located in the following directory:


Starting the SS7 Process for SIGTRAN

To start the SS7 process for SIGTRAN networks:

Starting the SS7 Process for TDM

To start the SS7 process for TDM networks:

Stopping the SS7 Process

To stop the SS7 process, use the relevant commands of the operating system (for example, kill).