Through its service
access points, HP OpenCall SS7 processes the requests received from an
API to exchange signaling information with a peer application. The
application is expected to send and receive signaling information
via opened and scheduled stack connections
using the respective functions provided by the SS7 stack APIs.
Receiving
Signaling Information |
 |
Only when the three scheduling phases are completed can the application
request an API to receive signaling information on its behalf. This
is necessary because the active stack connections and internal timers
must be serviced.
The receive functions provided
by HP OpenCall SS7 are non-blocking, and must be repeatedly called until
there is no more information to be received for the particular connection.
A receive function returns a primitive, its associated signaling
data or message and the number of messages waiting to be received.
For example, if the application wants to receive the information
from MTP3, you must ensure that the application calls the receive
function provided by the MTP3 API.
Sending
Signaling Information |
|
Once scheduling is completed, the application can request
the API to send signaling
information on its behalf. Each of the HP OpenCall SS7 send functions
are non-blocking.
All messages and primitives
are sent with respect to a connection.
Printable version
