(Scripted ISUP Emulation)
SS7 (Signaling System Number 7) defined by the International Telecommunication Union (ITU- T) is a globally adopted
protocol for out-of-band signaling systems.
The network elements involved in SS7 networks are SSPs (Signaling Switching Points), STPs (Signaling Transfer Points)
and SCPs (Signaling Control Points). These elements ensure signaling integrity and availability even if one or more signaling links fail.
The SS7 network manages calls by identifying end-to-end addressing and from there controls all the routing
judgments necessary for a seamless operation.
ISUP is a part of the complex signaling system SS7 that are used to set up and release calls through the PSTN.
ISUP end-to-end signaling is transported directly over MTP3 or SCCP levels.
GL's Message Automation & Protocol Simulation (MAPS™) designed for SS7 simulation over TDM (T1E1) can simulate Service Switching Point (SSP). The ISUP signaling specification conforms to ITU-T and ANSI standards. The tester supports testing network elements, error tracking, regression testing, conformance testing, load testing/call generation and generation of high volumes of ISUP traffic. MAPS™ SS7 functionality covers the ITU and ANSI variant of SS7 implementing MTP2, MTP3, and ISUP protocols. It is able to run pre-defined test scenarios against ISUP test objects in a controlled & deterministic manner.
The application is available as
- MAPS™ SS7 Emulator (Item # XX649)
- MAPS™ SS7 Conformance Scripts (Item # XX647)
MAPS™ SS7 Conformance Scripts (XX647) is designed for conformance tests and functional tests, where test objects can be accurately, reliably and comfortably validated for compliance with ITU-T standard Q.761-764 and Q.784. It is suitable for manufacturers, network operators and service providers to address all stages of the development cycle, regression testing through to type approval, acceptance testing.
The application gives the users the unlimited ability to edit SIP messages and control scenarios (message sequences). "Message sequences" are generated
through scripts. "Messages" are created using message templates
With the purchase of additional licenses (xx610, xx620, xxFT0) traffic can be simulated over T1/E1 interfaces. Supported traffic includes transmission and detection of TDM digits, voice files, single tone, dual tone, speech and FAX. Also supports various traffic events simulation during the course of a call, which is listed below:
TDM Traffic Events – digits, tones, files, speech, fax
- Send, and Detect Tones, Digits, File, Test Tone, Silence and verify speech bearer
- Stop Send Digits, File, Tone
- Stop Send - Stops Transmission of Tone
- Detect different tone types - dial tone, special dial tone, stutter dial tone, special information tone, call waiting, call in progress tone, reorder tone, busy tone, congestion tone, confirmation tone, howler tone, and ring-back tone
- Set region for call progress tones (Busy, Call Waiting, Dial, Ring, Congestion, Special Dial, Special Information) detection
- Send /Receive fax image (TIFF format) file from/to the specified location.
GL also provides an independent GUI based SS7 protocol analyzers (optional application –
xx120) for online capture and decode of the signaling in real-time both during tests and as a stand-alone tracer for live
Supported Protocol Standards
||Standard / Specification Used
||ITU - Q.761, Q.762, Q.763 and Q.764
||Ministry of Posts and Telecommunications of the People's Republic of China, Technical Specification of ISUP, 1996
||ANSI - T1.113.1 to T1.113.4
|Test & Network Management Messages (ITU, China)
||ITU-T Q.703, Q.704
|Test & Network Management Messages (ANSI)
||ANSI T1.111.4, ANSI T1.111.7
||EN 300 356 -1 V3.2.2(1998-08)Part 1
- SS7 (SSP) simulation over TDM (E1/T1)
- Supports transmission and detection of TDM traffic - digits, voice file, single /dual tones
- Multiple E1/T1 line interfaces supported
- User-friendly GUI for configuring the SS7 MTP Layers
- User Configurable Signaling Links
- User-configured Circuit Mapping, i.e defines Circuit Identification Codes (CIC) and map these CICs to Timeslots/Trunks in order to enable Voice/Data traffic
- Supports MTP2 and MTP3 protocol machine
- Multiple MTP links
- Access to all ISUP Message Parameters Initial Address, Subsequent Address, Release messages, and more
- User controlled access to optional ISUP parameters such as timers
- Subsequent Address Message (SAM) configurations available
- Fully Supported Continuity Testing (COT) that includes both COT messages
- Supports conformance testing with additional license (XX647)
- Logging of all SS7 Messages in real time. Each SS7 message displays CIC values defined within the message
- Impairments can be applied to messages to simulate error conditions
- Supports customization of call flows and message templates using Script editor and Message editor.
- Supports scripted call generation and automated call reception.
- Provides protocol trace with full message decoding, and graphical ladder diagrams of call flow with time stamp
- Script based & protocol independent software architecture.
- Provides call statistics with associated captured events and error events during call simulation
A test bed setup is configured to use a pre-defined XML profile file. The multiple profiles created in the default profile (XML) selected in Test Bed Setup are accessible from the call generation and reception windows.
The test configuration window allows users to configure the necessary parameters in order to establish communication between MAPS™ and the DUT.
It includes the T1/E1 (GL) server and MTP Server parameters along with MTP signaling parameters. Once the MTP layer is configured properly, ISUP messages
can be transmitted and received over MTP layer.
For T1 E1 based protocols, MAPS™ test bed should be setup with mandatory T1 E1 server, port, channel, and sub-channel port parameters have to be set, in addition to Source & Destination Port and Address to establish connection with DUT
Screen Shot of ISUP Testbed Setup Configuration
Call Generation option allows the user to simulate outgoing communications where an outgoing call is initiated by sending call control messages using
proper scripts and profiles. The profile allows necessary parameters of call control messages to be changed during runtime.
ISUP Call Flow Scenario
Testing STPs (Signaling Transfer Points)
The MAPS™ SS7 acts as Caller (Signaling Point - SP) and initiates the call flow by sending Initial Address (IAM) to the Network (DUT). The DUT on
receipt of an IAM message sends a ACM and ANS message in response.
Call Generation at SSP Node
Call generated from other entity can be automatically detected in call reception window by pre-setting the required scripts in the Incoming Call
Testing SPs (Signaling Points)
MAPS™ - SS7 is considered as the DUT (Network) to process the call flow by receiving the Initial Address (IAM) message from the Caller
(Signaling Point – SP).
Screenshot of Call Reception at STP Node
Bulk Call Simulation
MAPS™ supports Bulk Call Simulation and Stress/Load Testing capabilities through Load Generation feature. Load Generation window helps users
configure Stress/Load Testing parameters such as Call per second (CPS) or Busy hour call attempts (BHCA), Max Simultaneous Calls and Burst Size
Screenshot of Load Generation Parameters
Customization of Call Flow and Messages Using Pre-Processing Tools
- Script Editor - The script editor allows the user to create / edit scripts and to define variables for the protocol fields. The script uses pre-defined
message templates to build call flow and perform send and receive actions. Script editor provides options to run the test for multiple iterations in sequential
or random flow. Commands allow retransmission of messages with specific interval. It also includes traffic commands to send and monitor voice, tones, digits, on the created sessions. It includes raw commands (send/monitor signaling bits, monitor power level, set idle code, and end task) to send WCS commands directly from MAPS™ to the server. . It also includes traffic commands to send and monitor voice, tones, digits, on the created sessions. It includes raw commands (send/monitor signaling bits, monitor power level, set idle code, and end task) to send WCS commands directly from MAPS™ to the server.
Screenshot of Script Editor
- Profile Editor - Profiles are used to provide the user configured values to the fields in the Messages (i.e Message Template in MAPS™)
through variables which are going to change during the course of a call. It is now possible to quickly create multiple profiles with varying parameters and each call instance in call generation can be configured to use any of the pre-configured profiles to suit the test scenario.
Screenshot of Profile Editor
- Message Editor - The Message Template is a *.HDL file that comprises of protocol encoding parameters with preset values. It is required to
create a message template for every message in a protocol. The message templates are called within the scripts to perform scenario based testing.
Screenshot of Message Editor
Call Flow & Script Execution Control
Message Sequence - MAPS™ provides protocol trace with full message decoding, custom trace, and graphical ladder diagrams of call
flow with time stamp while simulation is running. Call flow graph allows to easily verify the messages exchanged between MAPS™ and DUT.
See Call Generation and Call Reception for details
Script Contents & Script Flow - The Scripts Contents window displays the contents of the script selected for call generation or reception.
The Script Flow window displays the set of statements successfully executed by MAPS™ to help users in troubleshooting a particular the call scenario.
Events & Event Profile Editor - User-defined events allow redirection of script execution on-the-go. The custom parameters in the events can
also be changed during script execution using Event Profiles.
Screenshot of Script Contents and Script Flow
Screenshot of Event Config
Call Statistics, Events, Link Status
Call Statistics & Status - By default, all call handling scripts (irrespective of the type of the functions) are assessed by MAPS™ to provide statistical information about Total Calls, Active Calls, Completed Calls, Passed Calls, Failed Calls, and Calls/Sec . It is also possible to characterize the statistical information under different groups of call handling scripts under a unique heading. In addition, Call Generation and Call Reception windows provide useful call status & script execution results.
Screenshot of Call Statistics and Status
Events Reporting – MAPS™ provides Event Log, Error Events, and Captured Errors windows that log the captured events and errors
encountered during the progress of the call.
Screenshot of Event Log
Link Status - Link Status window indicates transport related information of the protocol, for example, if SCTP is used as transport, it indicates
if the Association is UP or DOWN in the Link Status window.
Screenshot of Link Status
Please Note: The XX in the Item No. refers to the hardware platform, listed at the bottom of the Buyer's Guide, which
the software will be running on. Therefore, XX can either be ETA or EEA (Octal/Quad Boards), PTA or PEA (tProbe Units),
UTA or UEA (USB Units), HUT or HUE (Universal Cards), and HDT or HDE (HD cards) depending upon the hardware.
Specifications are subject to change without notice.
Back to Message Automation & Protocol Simulation