Professional Documents
Culture Documents
566-013-09
Revision C
SS7 1 January 2001
Copyright
Warranty
Some terms or steps in the procedures are italicized to make them more
visible.
When creating scripts, instructions, or portions of instructions, that you have to
type are indicated in bold, and icons that you have to click on in order to
insert lines of code are indicated in regular font style.
This tutorial is provided for self-paced training. For more in-depth information
on the HammerSS7 configuration files and low level programming please refer
to the HammerSS7 On-line Help and the NMS web site:
Exchange Exchange
1 2
SS7 circuits
The SS7 circuits are separate from the voice circuits and are used solely for
switching data messages, for connecting telephone calls and maintaining the
signaling network.
SS7 was originally defined as Common Channel Signaling and was first
introduced in the U.S.A. in the 1960s.
The SS7 network and protocols are used for:
- call setup, management, and tear down
- local number portability (LNP)
- 800/888/877 and 900 calls
- enhanced call features (call forwarding, caller ID, three-way calling etc)
- wireless services for roaming, subscriber authentication
SSP - switches where the calls originate or terminate (local exchange). SSP sends
messages to other SSP to setup, manage, and release voice circuits, performs database
queries for additional information routing (800/888/877 and 900 calls). It requires ISUP
and TCAP layers.
STP - serves as a router in the SS7 network. All SS7 packets travel from one SSP to
another through STP. STP also performs global title translation. There are three levels of
STPs:
- National STP - transfers messages using the same national standard of protocol (e.g.
ANSI)
- International STP - same as national STP, but uses the international SS7 standard (ITU-
TS)
- Gateway STP - provides protocol conversion from a national standard to ITU-TS and
serves as the interface into another network.
SCP - serves as an interface to telephone company database (information about
subscriber’s services, 800/888/877 and 900 numbers, calling card validation and fraud
protection). SCP uses TCAP for database queries. The most commonly used databases
are: Call Management Services Database (CMSDB), Line Information Database (LIDB),
Business Services Database (BSDB), Home Location register (HLR), and Visitor
Location register (VLR).
SSP, STP, and SCP are called signaling points, SP.
Signaling Links - 56 or 64 kbps digital links, A through F.
Local
SSP STP
B STP SSP
F C C
SSP STP
B STP SSP
Signaling links are logically organized according to their use in the SS7 network.
There is no difference between the various links, only in the way the links are
utilized during message transfer and the way network management interacts with
the links.
A - Access links between end points (e.g. an SCP or SSP) to an STP
B - bridge links connect an STP to another STP. Typically, a quad of B links
interconnect peer STPs (e.g. STPs from one network to the STPs of another
network).
C - Cross links connect STPs performing identical functions into a mated pair.
D - Diagonal links connect mated pairs of STPs at different hierarchical level.
E - Extended links connect SSps to a remote STP pair. E links privide an alternate
signaling path if an SSP’s home STP cannot be reached via an A link.
F - Fully associated links connect two signaling end points (e.g. SSps and SCPs).
Signaling Path
STP STP STP
Non-associated signaling - uses a separate logical path from the actual voice.
There are multiple nodes involved to reach the final destination although the
voice signal may have a direct path to the destination number.
Quasi-associated signaling - uses a minimal number of nodes to reach the
final destination.
Links are placed into groups - linksets. All the links in a linkset must have the
same adjacent node.
A route is a collection of linksets used to reach a particular destination.
7 Application
I
6 Presentation T TCAP
S
U
5 Session U
P
4 Transport SCCP P
3 Network MTP Level 3
2 Data Link MTP Level 2
1 Physical MTP Level 1
ACM ALERTING
ACM
RINGTONE
OFF-HOOK
ANM
ANM
CONNECT
DISCONNECT
REL
REL
DISCONNECT
RELEASE
RLC
RLC
RELEASE
REL ACK
A Release message (REL) is sent in either direction, when either the calling
party or the called party hangs up, indicating that the circuit is released. It is
also sent in the backward direction if the called party is busy.
A Release Complete message (RLC) is sent to acknowledge the release of the
remote end of a circuit.
Two types of boards are needed to support the SS7 protocol: T1/E1 board(s)
and SS7 board(s), Tx3000.
Depending on the physical hardware configuration of your TX Series boards,
the physical SS7 link interface between Hammer SS7 board(s) and a system
under test may be:
- timeslot(s) (one or more timeslots) on one of the T1/E1 boards
- a V.35 link
In the first scenario up to four time slots can be set aside for SS7 signaling on
the Hammer system.
In the second scenario all voice channels on T1/E1 board are used for
transmitting voice and SS7 signaling is transmitted over V.35 configurable
pod.
Each Tx3000 board can support up to four links on T1/E1 board(s) and up to
three SS7 V.35 serial link interfaces.
On T1/E1 board one or more voice channels are reserved for SS7 signaling. Any
voice channel can be configured to carry SS7 signaling. Most often it’s the 24th
channel on T1and 16th channel on E1. T1/E1 board installed in a Hammer
system communicates with the outer world and not the SS7 board.
SS7 board and T1/E1 boards installed in a Hammer system communicate via
MVIP bus.
Up to four T1/E1 channels are used for SS7 signaling between a Hammer
system and the SS7 portion of the SUT. The rest of the T1/E1 channels are
used for voice transmission.
V.35 outlet
V.35
V.35 board is a daughter board to SS7 board. It has its own socket and it is
connected to V.35 configurable pod. SS7 signaling is transmitted over the SS7
cable. Once the voice channels are assigned, voice signals are transmitted over
T1 line.
V.35 is used from a data service unit to the SS7 signaling point. It provides
data rates up to 56 or 64 kbps.
Three physical links (from one SUT or from three SUTs) can be connected to
one V.35 pod.
To set the pod jumpers for DCE, remove the outer screws form the V.35 pod.
DTE
The picture of the jumpers settings for DCE and DTE is shown in the slide.
The V.35 Configurable Pods allow you to configure the connectors to match
the equipment.
Each port on the pod is configurable to suit the equipment it is connected to by
setting jumpers inside the V.35 box.
The slide illustrates the position of the jumpers for DTE and DCE
Configuration.
Continue
Hammer
T1 Boards
SS7 Board
T1/E1 Voice
Boards
MVIP
Link
SS7 Linkset
Board SS7
V.35 V.35
Circuit Group - a group of voice channels that connect one Hammer system
with a SUT.
Link - channel that transmits SS7 signals between a Hammer system and a
SUT.
Linksets - groups of links.
Adjacent node
for Node 1.1.2
AG.cfg - specifies whether a board connects to the MVIP bus, communications protocols that
are used, how is clock defined for the board.
ClockRef = OSC: master clock is generated from the board
ClockRef = MVIP: the clock is taken from the MVIP bus
ClockRef = NET1: the clock is taken from the network
The first board, Board 0, always provides clocking => for Board 0 ClockRef = OSC/NET1.
All additional boards must have ClockRef = MVIP.
When a new board is added to the system, a new board definition must be added to AG.cfg.
You can add new boards, but be aware that software/hardware not supplied by
Hammer Technologies should not be added to the system; doing so voids the system
warranty. Consult with Hammer technical support.
If your HammerSS7 has been configured and you do not want to make any
changes in the configuration, you don’t run Board Utility when you are
bringing your Hammer up.
To start HammerSS7:
1. Make sure that the Database is on (if it is on, ht_servername in the Windows
NT Taskbar is displayed).
2. If it’s not displayed, click
Start -> Programs -> Hammer -> Database Server Start
3. Click ht_server name icon in the Windows NT Taskbar and you will get the
dialog shown in the slide.
Continue
SS7 27 January 2001
TxAlarm
Continue
5. Wait for “Now accepting requests” to show in the Messages section of the
DB dialog.
6. Double-click the Telephony Loader icon, or click Start on the Windows
NT taskbar:
Start -> Programs -> Hammer -> Telephony Loader
7. Bring the Hammer up
Start -> Programs -> Hammer
or double-click the Hammer icon.
Continue
TESLA
PUPIN
SAVA
Continue
If you want to configure your HammerSS7, you have to run Board Utility
when you are bringing your Hammer up.
To start HammerSS7:
1. Make sure that the Database is on (if it is on, ht_servername in the Windows
NT Taskbar is displayed).
2. If it’s not displayed, click
Start -> Programs -> Hammer -> Database Server Start
3. Click ht_server name icon in the Windows NT Taskbar and you will get the
dialog shown in the slide.
4. In order to monitor the Hammer processes bring the Alarm utility up:
Start -> Programs -> NMS INDC -> TxAlarm
5. Wait for “Now accepting requests” to show in the Messages section of the
DB dialog.
6. Double-click the Telephony Loader icon, or click Start on the Windows
NT taskbar:
Start -> Programs -> Hammer -> Telephony Loader
Continue
7. Double-click the Board Utility icon, or click Start on the WindowsNT taskbar:
Start -> Programs -> Hammer ->Board Utility
and the Board Configuration Utility dialog is brought up.
The SS7 check boxes appear to the left of each board listing. These boxes let you specify that
a resource board is enabled for SS7.
8. To enable SS7 functions: Click and highlight the appropriate board, which is used for
SS7 signaling in your Hammer system, listed in the Resource Boards list box. A check
appears in the box to the left of the board listing.
Click until the appropriate function appears to the right of the board type.
9. If you specify a resource board as an SS7 board, the SS7 Signaling Only check box
becomes active. This check box lets you specify whether the selected board is to be used
exclusively for SS7 signaling:
- Check this box if the selected resource board is to be used for SS7 signaling only
- Do not check this box if the board is to be used for both T1 and SS7 signaling
10. You can save the configuration you want using the Board Utility dialog. The list of
various saved configurations is displayed when you click the arrow in the Configure System
As... field.
11. To save the Current configuration click the Save Configuration button.
Continue
12. Save Configuration As… dialog is displayed. Type in the name of your
configuration.
13. Click OK.
14. The BrdUtil dialog is displayed, click Yes.
15. The Registry Editor dialog is displayed, click OK.
At this point you don’t have to run Telephony Loader, it will be run by Board Utility.
16. Click the SS7 Configuration button and the Configure SS7 dialog is displayed.
Continue
The SS7 Configuration Tool is used to configure all Tx3000 boards. Buttons ISUP, TUP,
SCCP,TCAP are enabled/disabled according to the Hammer SS7 license. Clicking each of the
buttons you bring up a dialog to configure an SS7 layer. When the configuration tool is used
on the system where Hammer SS7 configuration files have not been created, the following
files are created:
ht_tdmcp<SS7 board number>.txt – the TDM files for each SS7 board installed;
ht_Mtp3cp<SS7 board number>.cfg – the MTP files for each SS7 board installed;
ht_Isup<SS7 board number>.cfg – the ISUP files for each SS7 board installed (if licensed);
ht_Tup<SS7 board number>.cfg – the TUP files for each SS7 board installed (if licensed);
ht_Sccp<SS7 board number>.cfg – the SCCP files for each SS7 board installed (if
licensed);
ht_Tcap<SS7 board number>.cfg – the TCAP files for each SS7 board installed (if
licensed);
ht_SS7load< SS7 board number>.bat – the SS7 load batch files for each SS7 board.
Users should not change the names of these files.
Automatic Responses - enable this box if you want your Hammer system to respond to the
SUT’s circuit management messages (Block, Unblock, Circuit Group Block, etc).
Send Block Messages - enable this box if you want the initial state of your Hammer System
to be Blocked.
Trace Messages into File - (not recommended because it affects the performance) if enabled
trace messages are saved in the C:\Hammer\LogMsgs directory.
1. Click the MTP button. Board utility checks how many Tx3000 boards are installed in the
Hammer system.
2. The Configure MTP Layer dialog is displayed. The installed Tx3000 boards are listed in
the Select SS7 Board section.
The Local Nodes section displays a Local Node identification code assigned to the Tx3000
board selected in the Select SS7 board section. If MTP files are not available because they
have not been created, the Local Nodes list is empty. The Add button enables users to add a
node, the Remove button enables users to remove the node selected in the list.
The All Nodes section displays all the SS7 Nodes available – local, adjacent and non-
adjacent. The Add button enables users to add a node, the Remove button enables users to
remove the node selected in the list.
The SS7 Link can be created between a Local Node and any other node, different from
Local. The latter node is an adjacent node to the Local Node.
The Create Link button enables users to create links between a node in the Local Nodes list
and nodes in the All Nodes list.
The Remove Link button enables users to delete a selected link.
The Routes section displays all the Routes, created and/or initialized from the MTP file, if
available.
The Remove Route button enables users to remove a route from the list of routes.
3. Highlight a board in the Selected SS7 Board list for which you want to add a local node.
Continue
4. To add a node to the list of Local Nodes click the Add button in the Local Nodes section. The
Add Node dialog is displayed.
5. Type in the point code for the node you are adding (e.g. 1.1.10). In the Hammer system, the
point code parameter can be entered in hexadecimal (e.g. 0x1234) or in dotted notation (e.g.
98.124.21). We will use dotted notation in our examples.
6. Click OK.
7. If you want to remove a node from the list, highlight the node and click the Remove button in
the Local Nodes section.
8. Highlight the second board in the Select SS7 Board list (if you have more than one SS7
boards) and repeat steps 4 through 6. The point code for the second Hammer node will be
different, e.g. 1.1.2)
9. Now we have to add adjacent and non-adjacent nodes to the list of All Nodes. Click Add in
the All Nodes section and the Add Node dialog displays.
10.Type in the point code for the node you are adding (e.g. 1.1.9).
11. Click OK.
12.Repeat steps 9 - 11. Point code will be different for other nodes.
13.Next we have to create Links. Highlight one node in the Local Nodes section and one in the
All Nodes section if these two nodes are going to be physically connected.
14.Click the Create Link button.
15.The Create Link dialog displays.
Continue
If you are using T1/E1 boards for SS7 signaling, proceed to the next step. If you are using
V.35 for SS7 signaling, go to the next page.
16. If you are using the ANSI standard accept the default values in the dialog.
17.If you are using the ITU-T standard in the Link Type field select ITU-T, in the DPC
Length field select the value appropriate for your system(14 or 24), and in the SSF field select
INTERNATIONAL.
18.In the Links, Physical Resources section all the T1 boards channels are displayed. You
have to highlight a channel on the corresponding T1 board (the channel which will be used
for SS7 signaling). Highlight timeslot 0. Click OK.
19. If you want to remove a link from the list, highlight the link and click the Remove button
in the Links section of the Configure MTP layer dialog.
20.For the selected Local Node and a node, which has no Link to the selected Local Node, the
user can create a Route. In order to create a Route the user has to:
a) Highlight a Local Node;
b) Highlight a node from the All Nodes list, other than a local node, selected in a)
c) Highlight a Link through which the node, selected in b) will be reached;
21. Click the Create Route button. The Routes list displays all the Routes, created and/or
initialized from the MTP file.
22.If you want to remove a Route from the list highlight the Route in the Routes list and click
the Remove Route button in the Routes section of the Configure MTP layer dialog.
23. Click OK in the Configure MTP layer dialog.
16. If you are using the ANSI standard accept the default values in the dialog.
17.If you are using the ITU-T standard in the Link Type field select ITU-T, in the DPC
Length field select the value appropriate for your system(14 or 24), and in the SSF field select
INTERNATIONAL.
18.In the Links, Physical Resources section all the T1 boards channels are displayed and V.35
ports.You have to highlight a V.35 port for signaling. Highlight port 1. Enable DCE or DTE
Interface Type radio button, depending on the function of your Hammer. Click OK.
19. If you want to remove a link from the list, highlight the link and click the Remove button
in the Links section.
20.For the selected Local Node and a node, which has no Link to the selected Local Node, the
user can create a Route. In order to create a Route the user has to:
a) Highlight a Local Node;
b) Highlight a node from the All Nodes list, other than a local node, selected in a)
c) Highlight a Link through which the node, selected in b) will be reached;
21. Click the Create Route button. The Routes list displays all the Routes, created and/or
initialized from the MTP file.
22.If you want to remove a Route from the list highlight the Route in the Routes list and click
the Remove Route button.
23. Click OK in the Configure MTP layer dialog.
If you want to edit a link double click on the link in the Links section of the
Configure MTP layer dialog. The dialog Edit Link… is displayed.
In the Configure SS7 dialog click the ISUP button and the Configure ISUP
layer dialog is displayed.
To create a circuit group you highlight two nodes that are connected with
voice channels, one in the Local Nodes list another in the All Nodes list, and
click the Create Circuit Group button.
To remove a circuit group from the Circuit Groups list, highlight the group in
the list and click the Remove Circuit Group button.
When the Create Circuit Group dialog is displayed you select the channels
that belong to that circuit group, type in CIC for the first voice channel in
your circuit group, and in the Switch Type field select the standard that is
pertinent to your system.
In the Configure SS7 dialog click the TUP button and the Configure TUP
layer dialog is displayed.
This layer is not used in ANSI standard.
When the Create Circuit Group dialog is displayed you select the channels
that belong to that circuit group, type in CIC for the first voice channel in
your circuit group, and in the Switch Type field select the standard that is
pertinent to your system (standard for China or ITU-T).
If you want to edit your circuit group, both for ISUP and TUP, double click on
the circuit group in the Circuit Groups list in the Configure ISUP/TUP layer
dialog, and the Edit Circuit Group dialog is brought up.
To delete the configuration, right click on the configuration name -> Delete.
For the following three exercises you have to stop your server.
1. Right-click on the empty space of the Windows NT Taskbar and the Task
Manager dialog is brought up -> Processes.
2. If in the list of Processes you see htserver.exe, highlight it and click the End
Process button.
Circuit group
SUT
Hammer T1
Link Node 2.1.1
Node 1.1.1
T1 channel(s)
for SS7 signaling
or V.35
1. Click the SS7 Configuration button in the Board Utility dialog to start with SS7
configuration.
2. Click the MTP button. Board utility checks how many Tx3000 boards are installed in the
Hammer system.
3. The Configure MTP Layer dialog is displayed. The installed Tx3000 boards are listed in
the Select SS7 Board section.
4. To add a node to the list of Local Nodes click the Add button in the Local Nodes section.
The Add Node dialog is displayed.
5. Type in the point code for the node you are adding, 1.1.1
6. Click OK.
7.To add nodes other than local nodes to the list of All Nodes click the Add button in the All
Nodes section and the Add Node dialog displays.
8. Type in the point code 2.1.1.
9. Click OK.
10.To create links between nodes 1.1.1 and 2.1.1 highlight 1.1.1 in the Local
Nodes section, then highlight 2.1.1 in the All Nodes section.
11.Click the Create Link button and the Create Link dialog is displayed.
Continue
12.If you are using the ANSI standard accept the default values in the dialog.
13.If you are using the ITU-T standard in the Link Type field select ITU-T, in the DPC
Length field select the value appropriate for your system(14 or 24), and in the SSF field
select INTERNATIONAL.
14.In the Links, Physical Resources section all the T1 boards channels are displayed.
You have to highlight a channel on the first T1 board (the channel which will be used
for SS7 signaling). Highlight timeslot, e.g., 0.
15.Click OK.
If you are using V.35 for SS7 signaling, follow the instructions on page 39 (Create
Link with V.35).
Route for these two adjacent nodes is automatically created as the following slide
illustrates.
Continue
Once you configure the MTP layer, the Configure MTP layer dialog will look
like the one in the slide.
1. In the Configure SS7 dialog click the ISUP button and the Configure ISUP
layer dialog is displayed.
2. Highlight 1.1.1 in the Local Nodes section.
3. Highlight 2.1.1 in the All Nodes section.
4. Click the Create Circuit Group button.
Continue
5. Select the channels that belong to that circuit group. Highlight, e.g.,
channels 1 - 23.
6. Type in CIC for the first voice channel. For our example CIC will be 1.
7. In the Switch Type field select the standard that is pertinent to your system.
8. Click OK.
Circuit Group which carries voice signals between nodes 1.1.1 and 2.1.1 is
added.
Continue
The Configure ISUP layer dialog will look as it is shown in the slide once you
finish creating circuit groups.
Skip this and the following slide if you are using ANSI standard.
1. In the Configure SS7 dialog click the TUP button and the Configure TUP
layer dialog is displayed.
2. Highlight 1.1.1 in the Local Nodes section.
3. Highlight 2.1.1 in the All Nodes section.
4. Click the Create Circuit Group button.
Continue
5. Select the channels that belong to that circuit group. Highlight, e.g.,
channels 1 - 23.
6. Type in CIC for the first voice channel in the circuit group. For our example
CIC will be 1.
7. In the Switch Type field select the standard that is pertinent to your system.
8. Click OK.
Circuit Group which carries voice signals between nodes 1.1.1 and 2.1.1 is
added.
Route
STP
Link Node 3.1.1
Hammer SUT
1. Click the SS7 Configuration button in the Board Utility dialog to start with SS7
configuration.
2. Click the MTP button. Board utility checks how many Tx3000 boards are installed in the
Hammer system.
3. The Configure MTP Layer dialog is displayed. The installed Tx3000 boards are listed in
the Select SS7 Board section.
4. Highlight Tx3000 Board 1 in the Selected SS7 Board list .
5. To add a node to the list of Local Nodes click the Add button in the Local Nodes section.
The Add Node dialog is displayed.
6. Type in the point code for the node you are adding, 1.1.1
7. Click OK.
8. To add nodes other than local nodes to the list of All Nodes click the Add button in the All
Nodes section and the Add Node dialog displays.
9. Type in the point code 2.1.1.
10. Click OK.
12.Repeat steps 8 through 10 for point code 3.1.1.
Continue
Continue
13.To create links between nodes 1.1.1 and 3.1.1 highlight 1.1.1 in the Local Nodes
section, then highlight 3.1.1 in the All Nodes section.
14.Click the Create Link button.
15.If you are using the ANSI standard accept the default values in the dialog.
16.If you are using the ITU-T standard in the Link Type field select ITU-T, in the DPC
Length field select the value appropriate for your system(14 or 24), and in the SSF field
select INTERNATIONAL.
17.In the Links, Physical Resources section all the T1 boards channels are displayed.
You have to highlight a channel on the first T1 board (the channel which will be used
for SS7 signaling). Highlight timeslot 0.
18.Click OK.
If you are using V.35 for SS7 signaling, follow the instructions on page 39 (Create
Link with V.35)
Route for the adjacent nodes is automatically created as the following slide illustrates.
Continue
At this point in the Configure MTP layer dialog we see the list of Hammer SS7 boards,
local nodes (Hammer SS7 boards point codes), the list of all nodes (adjacent to the local
node and non-adjacent) the list of links between the local node and its adjacent node, as
well as the list of routes between the local node and its adjacent node.
17. Now we have to create routes between the local node, 1.1.1 and 1.1.2, and node 4.1.1.
18. Highlight 1.1.1 in the Local Nodes list and highlight 2.1.1 in the All Nodes list.
19. Highlight 1.1.1=>3.1.1 in the Links section of the dialog.
20. Click the Create Route button. New route between the local node 1.1.1 and non-
adjacent node 2.1.1 is created.
21. Click OK.
Continue
The slides shows the Configure MTP layer dialog after the MTP layer files
have been configured.
1. In the Configure SS7 dialog click the ISUP button and the Configure ISUP
layer dialog is displayed.
2. Highlight 1.1.1 in the Local Nodes section.
3. Highlight 2.1.1 in the All Nodes section.
4. Click the Create Circuit Group button.
Continue
5. Select the channels that belong to that circuit group. Highlight, e.g.,
channels 1 - 23.
6. Type in CIC for the first voice channel. For our example CIC will be 1.
7. In the Switch Type field select the standard that is pertinent to your system.
8. Click OK.
Circuit Group which carries voice signals between nodes 1.1.1 and 2.1.1 is
added.
Continue
Skip the slides related to the TUP layer Configuring if you are using ANSI
standard.
1. In the Configure SS7 dialog click the TUP button and the Configure TUP
layer dialog is displayed.
2. Highlight 1.1.1 in the Local Nodes section.
3. Highlight 2.1.1 in the All Nodes section.
4. Click the Create Circuit Group button.
Continue
5. Select the channels that belong to that circuit group. Highlight, e.g.,
channels 1 - 23.
6. Type in CIC for the first voice channel in the circuit group. For our example
CIC will be 1.
7. In the Switch Type field select the standard that is pertinent to your system.
8. Click OK.
Circuit Group which carries voice signals between nodes 1.1.1 and 2.1.1 is
added.
Follow the procedure similar to procedures in Exercises 1 and 2 and define a local node,
all nodes, links, and routes.
Continue
When you finish the procedure of configuring the MTP layer files the
Configure MTP Layer dialog should look like the one in the slide.
Once you bring your HammerSS7 up you can monitor the ISUP messages
exchanged between the Hammer and a SUT:
1. Start -> Programs -> Command Prompts
2. At the C prompt type in commands given with bold letters:
C:\>isupmgr
isupmgr[1]>trace data on
3. Hit Enter
4. isupmgr[1]>q
5. Hit Enter
6. isupmgr[1]>Hit Enter
7. C:\>txtrace
8. Hit Enter
The messages are in the hex format:
10:57:26.0 ISUP.1 <-- 0.0.1:
02 00 16
10:57:37.0 ISUP.1 <--0.0.1:
02 00 14
02 - Channel #; 00 14 message type in hex format; 0.0.1 is the point code of
the equipment.
Unlike regular telephony channels, the Hammer SS7 link is hidden from users.
This link is used to send out SS7 messages for all regular telephony channels in its
circuit group. When the Hammer SS7 link receives incoming SS7 messages, it
does not process these messages, it forwards the SS7 messages to the appropriate
voice channels.
High-level programming is used with applications which do not require that the
details of the SS7 protocol be understood or implemented by the tester or
programmer. The commands such as placeCall, releaseCall, answerCall,
rejectCall, startProtocol, stopProtocol are used.
Low-level programming is used with applications which require detailed
information about call progress in order to implement a successful test by the
tester or programmer. With low-level programming the script handles the sending
and receiving of all SS7 messages.
Low-level function calls (messages used to send and receive Hammer SS7
messages through the SS7 links) SS7IsupMsg. It is used in the following way:
dim x as SS7IsupMsg
x.initSS7IsupMsg (msg Type)
where msgType can be HTTSS7ISUP_ConnectReq, HTTSS7ISUP_ReleaseReq,
HTTSS7ISUP_DataReq, HTTSS7ISUP_StatusReq etc.
initSS7IsupMsg
buildSetupRQ
buildConnRS
buildReleaseRS
Get
GetMsgType
Set
SetMsgType
GetCode
sendSS7IsupMsg
getSS7IsupMsg
buildBlockRQ
buildBlockRS
buildUnblockRQ
buildUnblockRS
buildResetRQ
To see more about the functions click:
Help -> Hammer SS7 -> Find -> Type in SS7IsupMsg.
9. pause 2,HT_SECONDS
18. Wend
stopProtocol
Continue
16. Wend
17. stopProtocol
continue
SS7 84 January 2001
6.logMsg "Get incoming call..."
logMsg "prepare address complete message..."
addrMsg.initSS7IsupMsg HTSS7ISUP_AddrCompleted
logMsg "send SS7 address complete message..."
sendSS7IsupMessage addrMsg
logMsg "prepare connection confirm message..."
conMsg.buildConnRS msgBuffer
logMsg "send SS7 connection confirm message..."
sendSS7IsupMessage conMsg
BLA cic(1)
BLA cic(n)
Circuit management
Start party RLC
UBA protocol
Release call
RSC
UBL
Start
BLO
protocol UBA RLC
Circuit management
IAM BLA
Call setup
ACM RSC
Release call
BLO
ANM
BLO
RLC
Voice BLA
BLA
The message exchange between the Hammer and SUT (calling and called
party) is illustrated in the slide.
UBL - unblock
UBA - unblock acknowledged
IAM - initial address message
ACM - address complete
ANM - answer
REL - release
RLC - release complete
RSC - reset circuit
The SS7 and CCS protocols send the UBL and UBA messages automatically.
The NOCC protocol doesn’t send these messages and users have to include
them in their scripts.
The purpose of the SS7 Toolbars is to simplify Hammer low level SS7
scripting. These toolbars allow a user to develop a SS7 script using ISUP
signaling to place and receive calls.
1. Open a new script and name it, e.g., icons_SS7.
2. In the main menu click Toolbars -> SS7 Management and SS7 Call
Control
3. The SS7 Management and SS7 Call Control Toolbars are displayed.
4. Click on each of the toolbars to see the code lines inserted in your script.
Do not compile this script, since you are not going to run it, we need it only to
see the lines of code behind each of the SS7 icons.
ReceiveSS7ISUPMessage is a function used by both SS7 toolbars to wait for a particular SS7
ISUP message. The syntax used for this function is:
ReceiveSS7ISUPMessage( Timeout, Expected Message, Receive Buffer)
Timeout - the amount of time in seconds before the function times out. The SS7 Toolbars use a
default timeout of 5 seconds, which can be changed by manually editing this field in the script.
Expected Message - the SS7 acronym for the message the Hammer is waiting for. This can be
one of the following: ACM, ANM, BLO, BLA, CGB, CGBA, CQM, CQR, GRS, GRA, CGU,
CGUA, IAM, REL, RLC, RSC, RES, SUS, UBL, and UBA.
Receive Buffer - the SS7IsupMsg object that the receive message will be stored in. The SS7
Call Control Toolbars default to recSS7MsgBuf. WARNING: Do not change the receive
parameter as some other toolbar items will use these receive buffers in creating outgoing
messages.
NOTE: When running this function, if other SS7 ISUP messages are received by the Hammer
while waiting for an expected message, the type of ISUP message will be displayed, but the
Hammer will continue to wait for the message it was expecting until timeout occurs or the
message arrives. This can be handled by creating error handling within the script.
When the function executes the following messages may be displayed in the default view
multiple times:
‘getNextEvent: not completed in time’ and ‘getNextEvent: completed successfully’
These messages do not indicate that the function has failed or succeeded, but are function calls
within the ReceiveSS7ISUPMessage Function. Disregard these messages.
1. Create two new scripts - one for the originating call, one for the terminating
call.
2. Turn on SS7 Management and SS7 Call Control toolbars.
3. Using the toolbars create your SS7 scripts.
Continue
Wait for
10. Select Receive REL
11. Select Send RLC
disconnect
Release
9. Select Send REL
10. Select Receive RLC
call
’******************************************************************
’ The areas between HAMMER BEGIN... and
’ HAMMER END... are used by the enhanced editor.
’ Do NOT edit in these areas.
’******************************************************************
Call StartProtocol(HT_PROTO_NOCC,,)
Continue
Continue
StopProtocol
setScriptResult HT_SUCCESS
goto done
TelError:
setScriptResult HT_FAILURE
...
’******************************************************************
’ The areas between HAMMER BEGIN... and
’ HAMMER END... are used by the enhanced editor.
’ Do NOT edit in these areas.
’******************************************************************
Continue
StopProtocol
setScriptResult HT_SUCCESS
goto done
TelError:
setScriptResult HT_FAILURE
...