Accessing the SS7 Stack

The aim of an API is to provide applications with SS7 network access while shielding the architecture of the platform. This abstract view of the platform allows an application to use the SS7 and management functions without being dependent on the platform configuration.

An application can access the HP OpenCall SS7 stack locally (if it runs on the FE server) or remotely (if it runs on the BE server). In both 1-host and 2-host development platforms, applications and APIs co-exist on the same computer as the SS7 stack.

Figure 3-1 Local SS7 Stack Access - Architecture

In distributed platforms the user applications run on a back-end (BE) computer and the SS7 platform runs on the front-end (FE) computer. Applications on the BEs access the SS7 network via the HP OpenCall SS7 stack(s) located at the FE(s).

Figure 3-2 Remote HP OpenCall SS7 Stack Access: Distributed Platform

Remote SS7 access enables all computers to be sized to the needs of the applications. It also eases application maintenance, since bringing down one BE for an application upgrade does not affect network service for the remaining applications. Applications that run on development platforms also run without code modification on distributed platforms.

Interaction of Multiple APIs

An application can interface with a single API or use multiple APIs. Any API combination is possible, but the guidelines on scheduling must be observed. See “Scheduling SS7 Connections”.