The Alias Point Code feature allows the HP OpenCall SS7 product
itself to be part of one or more aliases as defined by the Bellcore
standard GR-82-CORE Issue 1, June 1994.
Local Alias |
 |
You can define one or more aliases, whose constituents are HP OpenCall SS7 nodes.
An HP OpenCall SS7 node can belong to at most 4 aliases. Therefore,
an HP OpenCall SS7 node can have a maximum of 4 aliases.
Each node of the network can then access the HP OpenCall SS7 node either
by using its LPC or by using one of its aliases. The goal is to
allow a remote node to reach an HP OpenCall SS7 node other than by using
its LPC.
The local alias is visible only up to the MTP3 level. The
applications above MTP3 are not aware of its existence and just
see the LPC.
Figure 1-3 “Example of an Incoming Message for a Local
Alias ” shows an
example of how an incoming message for an alias is handled.
The diagram shows a pair of HP OpenCall SS7 nodes (A and B) with
an alias c defined for them.
The remote node D sends a message with DPC
= c.
The STP E selects one of the constituents of the alias
(let us say A).
E routes the message to A.
The message enters the MTP3 level of A with DPC = c.
The message exits the MTP3 level of A with DPC = a.
The application on A receives the message DPC = a.
The existence of the alias has no effect on outgoing messages
from A. Such messages are sent with OPC = a. The alias c does not
appear in such messages.
Printable version
