Telco Tech Notes
Telco Tech Notes
The combination of the point code plus the SSN identifies a specific application in
the network. Applications direct messages to one another across the network by
inserting the appropriate point code and SSN in an SS7-formatted message.
But what if you want to identify a group of service applications on mated nodes by
the same point-code/SSN combination? Or your network does not provide GTT, but you
want to support mated service applications? Or what if you want to communicate with
a system that is not an SS7 node?
All of these scenarios can be implemented using the Gateway feature. The Gateway
feature allows you to define �virtual� point codes and SSNs to represent a group of
service applications that reside on multiple nodes, or they can represent systems
that are not true SS7 nodes.
Assigning a Gateway Virtual Point Code (GVPC) to a system that is not part of the
SS7 network causes it to appear to be an SS7 node. Its SS7 access is provided via
the INS.
On the INS, an application is defined to represent the system in the SS7 network;
the application is called a Gateway application. (For information on creating a
Gateway application, refer to the Application Development Guide.) The Gateway
application must know both the addressing method and the message protocol used by
the system and must perform any necessary translation to and from that protocol.
In all of the scenarios mentioned above and described on the following pages, the
GVPCs are considered to be �beyond� the INS. Therefore, in the SS7 network, the INS
is seen as an STP via which the GVPCs can be reached. Because the INS is
functioning as an STP for the GVPCs, it will generate network management messages
about the availability status of the GVPCs. Links between the INS and the nodes
that send messages to the GVPCs should be configured as B links. This is necessary
because some STPs screen (discard) network management messages received on A links.
The point code addresses of non-adjacent nodes that should be notified when the
status of the local subsystem changes. Concerned point codes can reside in any of
the configured networks.
3) The SCCP layer of the SS7 protocol allows for message routing by point code
address or by global title. A global title is a set of digits (for example, a
dialed 800/888 number) that represents a particular destination. Usually, an STP
node performs Global Title Translation (GTT) to convert the digits to an explicit
point code and SSN address so that the message can be routed to its proper
destination.
In some networks, it may be more desirable to have GTT performed at a node other
than an STP. For example, an SCP may be able to perform more extensive translation
functions than an STP can (for example, 10-digit translation as opposed to 3- or 6-
digit translation). In these networks, the service application that performs GTT
can reside on a pair of SCP nodes instead of STP nodes. In all other respects, the
implementation is the same�the SCPs are assigned a single alias point code to
represent the GTT function.
If the INS will be used to provide GTT services in the manner described above, you
must identify the service application that will perform GTT and associate it with
one or more alias GTT point codes that will represent the local node. When a
message
requiring GTT arrives at the INS, the MTP software will determine that the
Destination Point Code (DPC) in the message is an alias for the local node. If the
routing indicator in the Called Party Address (CDPA) shows that the message is to
be routed on global title, the SCCP software will forward the message to the SSN
that has been defined as performing GTT for the alias point code specified in the
message.
4) Note: Do not confuse alias GTT point codes with the alias point codes that can
be assigned to the local node as part of configuring the local node identity (see
Task 1: Configuring the Local Node Identity on page 2-3). The alias GTT point code
represents only the GTT function performed by a service application on the local
node.
5) Note: The INS acts as an STP for messages addressed to a virtual point code such
as an alias GTT point code. Adjacent nodes that send message traffic to the virtual
point code should therefore configure their links to the INS as they would links to
an STP (for example, an adjacent STP node would configure links to the INS as B
links).
Normally, message routing is based on the full Destination Point Code (DPC)
contained
in the message. ANSI, China SS7, and Japan SS7 networks may make use of the
hierarchical structure of the point code address to allow for partial point code
routing�
that is, routing on just the network number or on the network and cluster numbers
in the
DPC.
Partial point code routing means that when you configure remote nodes, you have the
option of entering only a network number or a network and cluster number for all
nodes
that share that network number or network and cluster number. For example, you
might
define only a network number if you know that all messages destined for a
particular
network are transmitted over the same route. When the INS transmits a message to
that
network, it needs to examine only the network number in the Destination Point Code
(DPC) to determine how to route the message. When an intermediate node receives the
message, it examines the appropriate portion of the DPC to determine where the
message should be transmitted next.
DS0 64 Kbps 1
DS1 1.544 Mbps 24 T1
2.048 Mbps 32 E1
DS2 6.312 Mbps 96 T2
8.448 Mbps 128 E2
34.368 Mbps 512 E3
DS3 44.736 672 T3
8) Adjunct (AD). An element or entity within the SS7 network that is attached to
one or more
signal switching points and performs the same functions as a service control point.
10) Alias Point Code: An alias address for a node that allows the node to handle
messages in some alternate way not possible if its standard point code were used.
For Example....???
11) Bipolar Eight-Zero Substitution (B8ZS): A T1 line coding scheme, also known as
Clear
Channel, that operates at 64Kbps by sending a string of eight zeros with a
deliberate
bipolar violation which maintains line synchronization.
12) Extended Destination Control Table (XDCT): A table stored within the Extended
Memory
Manager process and used by the Message Transfer System to locate and route
messages
to appropriate servers within the INS.
13) Global Title Translation: Capability supplied with SCCP Class 1 for addressing
an
application without specifying the total point code address.
15) Link: The physical connection between one network node and another. Sometimes
referred to as a channel. The high-speed transmission facility that T1 or E1 lines
connect to is
called a facility link.
16) Link Set: A logical grouping of links having the same physical origin and
destination. This grouping makes it possible to assign certain characteristics to
all links at once. Further grouping is possible to form a combined link set or a
route set. A combined link set is a logical grouping of two link sets of equal
ranking that provides alternate paths to the
same node. A route set is a logical grouping of link sets or combined link sets to
provide
redundant routing paths to remote nodes.
Each trunk circuit is assigned a Circuit Identification Code (CIC). The CIC is a
14-bit
(ANSI) or 12-bit (ITU, China SS7, and Japan SS7) code that can uniquely identify up
to
16,384 (ANSI) or 4,096 (ITU, China SS7, and Japan SS7) trunks. Because the CIC
alone cannot uniquely identify every trunk in the network, CICs are unique only
between two adjacent switches. Both switches use the same CIC value to identify a
particular trunk.
Typically, ISUP is used for communication between SS7-capable switches that have
voice trunk connections. The ISUP protocol requires that each trunk be identified
by a
unique point code and CIC combination. However, because an SCP-switch is not a true
switch, it has no physical interfaces to manage trunk circuits. If the SCP-switch
is to
handle ISUP traffic, it must be able to simulate the presence of trunks. The trunks
needed by the SCP-switch are provided by the remote switches via �loopback trunks.�
Loopback trunks are trunks that have both ends connected to the same switch.
To the switch, each end of the loopback trunk appears to be an independent trunk
circuit. The outbound trunk from the switch is associated with an SCP-switch
VSPC(A) for receiving calls. The inbound trunk to the switch is associated with an
SCP-switch VSPC(B) for originating calls. VSPC(A) must be different from VSPC(B).
The two VSPCs are required in order to eliminate the need to administer CIC values
at the SCP-switch. This allows the switch to add or remove loopback trunks without
informing the SCP-switch.
20)
Language COnstructs and etc...
==============================
1) _tal ====> In a C Program if you wanna call a TAL procedure (function for me...)
then you need to use this construct which allows you to call the tal function in
your 'C' program.....
If the C module needs full access to the C run-time library, you can either:
Specify a C MAIN routine that calls the original TAL main routine as follows.
In the TAL module, remove the MAIN keyword from the TAL main routine and
remove any calls to the INITIALIZER or ARMTRAP system procedure. The TAL
module must also meet the requirements of the C run-time environment.
// TAL COde
INT status := 0;
INT .EXT array[0:4];
PROC talmain;
BEGIN
array[2] := 2;
status := cfunc (array);
END;
============================
/* Code C Code */
The #line directive tells the preprocessor to change the compiler's internally
stored line number and filename to a given line number and filename. The compiler
uses the line number and filename to refer to errors that it finds during
compilation. The line number usually refers to the current input line, and the
filename refers to the current input file. The line number is incremented after
each line is processed
3) Vector:
The STL vector class is a template class of sequence containers that arrange
elements of a given type in a linear arrangement and allow fast random access to
any element. They should be the preferred container for a sequence when random-
access performance is at a premium