Agilent Signaling Advisor: User's Manual

Agilent Signaling Advisor
Users Manual
Signaling Advisor
User's Manual
Agilent Technologies
This document relates to Release NA2.03.xx of the Signaling Advisor software. Go to Help menu About to identify the software version number. Copyright 1997-2001 Agilent Technologies UK Ltd.
Copyright 2001 Agilent Technologies UK Limited. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Information in this document may apply to products which use the VxWORKS TM software. The VxWORKS TM software was developed by Wind River systems Inc., which has copyright to it. First edition, 07/01 Part Number 37907-90229 Printed in U.K.
Documentation Warranty The information contained in this document is subject to change without notice.
Agilent Technologies makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose.
SAFETY Warning Warning denotes a hazard. It calls attention to a procedure, which if not correctly performed or adhered to could result in injury or loss of life. Do not proceed beyond a warning note until the indicated conditions are fully understood and met. Caution Caution denotes a hazard. It calls attention to a procedure, which if not correctly performed or adhered to could result in damage to or destruction of the instrument. Do not proceed beyond a caution note until the indicated conditions are fully understood and met. For details of safety, see Safety Information in the Mainframe Reference Manual.
Agilent Technologies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Agilent Technologies UK Limited Telecommunications Networks Test Division South Queensferry West Lothian, Scotland EH30 9TG
Microsoft ,Windows NT and Windows are U.S. registered trademarks of Microsoft Corp. Both the GSM logo and the GSM letter mark are trademarks of the GSM Association. Carbon Copy 32 is a registered trademark of Microcom Systems Inc.
Contents
Using Signaling Advisor 1
Introduction............................................................................................................................... 1 The Basic Steps......................................................................................................................... 2
Getting Help
Learn about Using Help ............................................................................................................ 5 How to Use On-line Documentation......................................................................................... 7
Connecting and Configuring
How to Connect Cables ............................................................................................................ 9 Learn about Configuring Automatically (Monitor Operation Only)......................................... 9 How to Configure Automatically (Monitor Operation Only) ................................................. 11 Learn about Configuring Manually in Bearer View ............................................................... 16 How to Configure Manually ................................................................................................... 21 Configuring Bearer Physical Parameters for Monitoring ......................................... 22 Configuring Physical Parameters for Emulating ...................................................... 25 Create Links ............................................................................................................. 28 Learn about Alarms ................................................................................................................ 37 How to Use Alarm View......................................................................................................... 37 Learn about the Status of Links .............................................................................................. 42 How to Use Link Status View ................................................................................................ 43 Learn about Protocol Stacks and Protocols............................................................................. 45 How to Use Protocol Stacks ................................................................................................... 47 How to Use Linksets............................................................................................................... 51 Learn about Point Code Mappings ......................................................................................... 52 How to Use Point Code Mappings.......................................................................................... 52 Learn about Point Code Formats ............................................................................................ 54 How to Use Point Code Formats ............................................................................................ 55
Capturing Traffic
59
Learn about Capturing ............................................................................................................ 59 How to Capture Traffic........................................................................................................... 59 Learn about Measurements ..................................................................................................... 60 How to Use Measurement Files.............................................................................................. 62 Learn about Triggers and Filters............................................................................................. 64 How to Use Triggers and Filters............................................................................................. 66
Signaling Advisor User's Manual Contents i
Isolating Calls
77
Learn About Isolating Calls ....................................................................................................77 How to Isolate Calls ................................................................................................................79
Gathering Statistics
85
Learn about Graphical Statistics..............................................................................................85 How to Gather Graphical Statistics .........................................................................................86 Learn about Tabular Statistics.................................................................................................92 How to Gather Tabular Statistics ............................................................................................92
Analyzing Captured Data
95
Learn about Analyzing Messages............................................................................................95 How to Analyze Captured Data...............................................................................................96 Copying...................................................................................................................101 Printing ...................................................................................................................102 Display Settings ......................................................................................................104 Displaying Columns................................................................................................106
Using Emulation (EmuLite and Conformance Tests) (Option)
109
Learn about Emulation (Option) ...........................................................................................109 How to Use EmuLite and Conformance Tests (Option) .......................................................112 Run a Conformance Test ........................................................................................113 Basic Emulate Sequences........................................................................................114 Create EmuLite Sequences .....................................................................................115 Add Messages and Commands to a Sequence ........................................................120 Edit Message Fields ................................................................................................133 Running Test Sequences .........................................................................................143 Analyze Results ......................................................................................................145 Application Programming Interface........................................................................147
Other Tasks and Self Tests
149
Other Tasks ...........................................................................................................................149 Self Tests...............................................................................................................................154
Glossary of Terms Index
157 161
ii Contents
Signaling Advisor User's Manual
Using Signaling Advisor
Introduction
Your Signaling Advisor is one of a family of Signaling Advisors, all based on a common platform. The details of the hardware are explained in full in the Mainframe Reference Manual. Three variants are available for testing SS7, GSM/GPRS and cellular/PCS signaling networks. The Signaling Advisor (a Microsoft Windows PC-based instrument) monitors signaling messages, collates statistics and traces calls. It can simultaneously monitor up to 32 duplex signaling links on up to 16 duplex bearers. EmuLite is an optional feature that lets you test new services, maintain existing services and troubleshoot problems on the signaling links by allowing you to send messages and perform actions based on the response. The EmuLite option also includes pre-defined Conformance Test sequences. Up to two interface modules can be installed in the instrument. They allow you to monitor or emulate signaling links on up to 8 duplex (E1
Signaling Advisor User's Manual Using Signaling Advisor 1
Balanced or Unbalanced, T1, DS0 or Datacom) bearers. If you use a Signaling Advisor undercradle with the instrument, a further two interface modules can be fitted which enables you to monitor or emulate on up to 16 duplex bearers. The instrument can automatically configure itself to monitor the network you are testing, or you can manually configure it using the easy-to-use Graphical User Interface (GUI). Using suitable software (such as Carbon Copy) and a modem or LAN connection you can also control the instrument remotely. A summary of the Signaling Advisors main features are listed below: ! ! ! ! ! ! ! ! ! ! Auto-configures bearers, signaling links and protocols for monitoring. Emulates test sequences using EmuLite. Provides multiple-protocol triggers and filters. Provides call traces. Auto-validates protocols and sequences. Provides graphical and tabular statistics. Monitors up to 32 signaling links simultaneously. Correlates a message sequence instantly. Extensive protocol decode library. Protocol Help.
The Basic Steps

There are three main steps to using your Signaling Advisor. More details are available in the relevant sections of this User's Manual.
Step 1 - Connecting and Configuring

Ensure that the Interface Module(s) are inserted and locked into the side of the Signaling Advisor (this should only be done when the instrument is switched off). Switch on the Signaling Advisor and connect to your network. At the Start Up screen select Real Time to configure the Signaling Advisor to monitor, or emulate, your network. Configuration's Bearer view will appear. (Alternatively, click Post Capture to open an existing *.tol file, or Resume to open the last measurement). There are two configuration methods; a simple automatic process and a detailed manual configuration based on the individual parameters for the bearer and its signaling links. shows the alarms that have been detected. By The Alarm view viewing the alarms you know which settings need to be changed when manually configuring the instrument in Bearer view ( ).
2 Using Signaling Advisor
Step 2 - Capturing
Once configured you must click in Monitor ( ) to start capturing from your configured links. The default settings capture everything.
And/Or - Emulating
Creating and Editing Test Sequences Once configured you can create and edit test sequences and messages from the EmuLite dialog box ( ! ! ):
Create and edit sequences and messages in the Sequence Editor. Edit message fields in the Message Editor.
Running Test Sequences Select the sequences to be run in the Test Manager. You can define the order the sequences will be run and how often. Once the tests have been to start selected you must close EmuLite (click OK) and click emulating. All messages will be displayed in Traffic Overview. Running Conformance Tests Select the test to be run from the Conformance Test Manager. You can select the links and edit the timer parameters to be used when running the tests.
Step 3 - Analyzing Data

To analyze the data and investigate network problems: ! ! ! ! ! Use Filters to capture or isolate only the messages you want. There are various filter types available. Analyze the captured information. Use Call Trace to group messages into calls. Use Statistics to measure the activity on your network. Save log files (*.tol) for analysis later. The configuration and measurement setup information is also saved in the log file. Caution Close the Signaling Advisor (File menu BEFORE switching off power.
Exit)
and shut down Windows
Using Signaling Advisor 3
Getting Help
Learn about Using Help

The Signaling Advisor's On-line Help is based on Microsoft Windows On-line Help. General Help or select Help menu Contents and Index to display the OnClick line Help's Contents, Index and Find tabs ! The Contents tab contains an expandable list of basic information and step-by-step instructions about each aspect of the Signaling Advisor. The Index tab contains an alphabetical list of common words and phrases. The Find tab lets you search for a word or phrase. The first time you select the Find tab you will be prompted to create the list of words used within the help system. The system builds the list for you in a few seconds. Mouse selections are shown in a different font from the rest of the text, for example, Click OK. Keyboard keys are shown in square brackets, for example, [F1],
[Shift], [Ctrl].
! !
Fonts and Symbols ! ! ! !
Multiple key inputs, where 2 keys must be pressed at the same time, is shown as [Shift]+[F1]. Menu and submenus are separated by a right arrow, for example, Help menu Contents and Index.
Protocol Help Protocol Help lets you search for more information about protocol abbreviations. Select Help menu Protocol Help from any Monitor view to display the Protocol Help window. In EmuLite's Message Editor tab right-click a field and select Protocol Help from the popup menu to display information about the field.
Getting Help 5
On Views ! Click [F1] to display detailed information about the current view. You will find out what the view does and how it should be used. Click [Shift]+[F1] or Help menu What's This? and point on the item you want more information on. Click [F1] to display detailed information about the selected object. Click in a dialog box and point to the object you want information about. Hovering over items will display a ToolTip. ToolTips provide additional information about the item. ToolTips are available on toolbar buttons and on many views, for example: . Bearer view Protocol Stack view . Call Trace view Statistics view ! . .
In Dialog Boxes ! ! Tips !
In many areas clicking the Right Mouse Button will display a menu. This menu lists all the functionality for the item on which the right-mouse button was clicked. This menu can also be displayed by pressing on the keyboard.
Information notes Information notes give some additional information about the topic. They are shown next to the Information icon in green text, for example, Information Information text Caution notes Caution notes alert you to issues that may damage the instrument, your network or may prevent the instrument working as you may expect. Caution notes are shown next to the Caution icon in violet text, for example, Caution Caution text
6 Getting Help
How to Use On-line Documentation

The User Manuals, Foreign Language Manuals, Frequently Asked Questions and so on, are available in PDF format. Click Help menu On-line Documentation to display an index of all the documentation supplied with your Signaling Advisor. Products Notes, such as Local Number Portability (LNP), Base Station Optimization Monitor, Remote Control, High Speed SS7, General Packet Radio Switch (GPRS), IS-634A/IS-41, Connecting and Configuring and EmuLite are some of the current Product Notes available within the on-line documentation suite. Web Site You can get up-to-date information about all aspects of the Signaling Advisor, including Product Notes and software options and so on, from the web site. http://www.agilent.com/comms/signalingadvisor
Getting Help 7
Connecting and Configuring
How to Connect Cables

The Signaling Advisor is connected to your network via the Interface Modules inserted into the slots on the sides of the instrument or in the undercradle. Interface Modules should never be removed or inserted when the Signaling Advisor power is on. You can connect and disconnect cables to the Interface Modules at any time. Removing cables will cause a Loss of Signal hardware alarm. The overall hardware alarm status of each bearer is indicated in the bearer graphics in Configuration's Bearer view ( ). More detail can be found in Alarm view ( ) and Link Status view ( ). By default, red indicates hardware alarms have been detected. Cabling and connecting information is described in detail in the Interface Module Reference Manuals. These manuals are available from Help menu On-line Documentation.
Learn about Configuring Automatically (Monitor Operation Only)

Auto Configure will set up everything the Signaling Advisor needs to capture from your network. Click run Auto Configure. from any Configuration view to
Connecting and Configuring 9
Auto Configure's dialog box..
Auto Configure works through 5 stages: Stage 1 Clears Hardware Alarms changes the line encoding and framing type until all hardware alarms have cleared. Impedance is only changed if the option is enabled in the Auto Configure Options. As hardware alarms clear the individual alarm status color will change. Only the selected bearers are adjusted. Stage 2 Detects Signaling looks for signaling on each alarm free bearer. Only the selected data rates will be checked. When signaling is detected the appropriate symbols will appear in the timeslot. Blue Flags represent SS7 signaling.
Green Flags represent Non-SS7 signaling (either X.25/ISDN/V.5/NS GPRS/Frame Relay). represents GSM TRAU 8K or 16K data. represents the repeated patterns that separate A yellow flag signaling units (flags). On T1 interface, a yellow flag may be displayed where empty timeslots are idling the same pattern as these flags. Stage 3 Captures Sample Data a sample of data is captured from all the detected signaling links. This data is used to validate against the selected Protocol Stacks. If only one stack is selected for each stack type then Stage 3 is not carried out and the selected stack is used. Stage 4 Validates Protocol Stacks the captured data sample is validated against the selected Protocol Stacks. The stack that gives the best validation statistics is taken as the correct stack. The first stack that verifies 100% will be used without further checks. If only one stack is selected for each stack type then Stage 4 is not carried out and the selected stack is used.
10 Connecting and Configuring
Stage 5 Creates Links when the Auto Configure dialog is closed all the detected links are automatically created. Links are not created on timeslots which have a yellow flag, because full signaling has not been detected in these timeslots. You can now capture network traffic on the created links. Information ! ! ! ! All other Signaling Advisor functionality is frozen whilst Auto Configure is operating. Auto Configure cannot detect Fractional links (that is, a link spread across more than one timeslot). If alarms cannot be cleared, for example if the cable is damaged, Auto Configure skips the bearer. The first time you run Auto Configure you will be asked to select a Network Type. The Network Type sets up the appropriate data rate and protocol stack options that Auto Configure will check. These settings can be viewed and edited in the Auto Configure Options dialog.
How to Configure Automatically (Monitor Operation Only)

The first time you run Auto Configure you will be asked to select a Network Type. The Network Type sets the default Protocol Stack and Data Rate options. These options determine how Auto Configure works. It is recommended that you check them to ensure that they match the settings used by your network.
Auto Configure Options sheet.
Auto Configure ( ) is available in Real Time mode from any Configuration view.
Configuration's Auto Configure dialog box.
If Auto Configure returns unexpected results it may be because the default settings do not match your network configuration. You should check the setting in Auto Configure Options to ensure that Auto Configure is checking against the correct set of parameters.
Information ! The Network Type can only be selected the first time Auto Configure is run. Change the Auto Configure options if you need to edit the settings. All other Signaling Advisor functionality is frozen while Auto Configure is operating. If alarms cannot be cleared, for example if the cable is damaged, Auto Configure skips the Bearer. Auto Configure cannot detect Fractional links (that is, a link spread over more than one timeslot). Auto Configure will not configure emulation links.
! ! ! !
Auto Configure
1. 2. Connect the Signaling Advisor to your network. ), click In Monitor ( Real Time mode. to put the Signaling Advisor into
3. 4. 5.
Click to open Configuration and then Auto Configure dialog box.
to display the
Select the bearers you want to Auto Configure. By default all connected bearers are already selected. (OPTIONAL) Set up any Auto Configure options. Click Start.
Auto Configure running.
6.
Signaling Advisor will clear hardware alarms, create signaling links and assign protocol stacks for all the data it detects. Flags will appear in the timeslots where signaling has been detected. Auto Configure will stop automatically once all the selected bearers have been scanned.
Auto Configure complete.
7.
Click Close to close the Auto Configure dialog box. The detected links will be created. You can now capture data by clicking then to start capturing data. to open Monitor and
8.
Information ! ! All other Signaling Advisor functionality is frozen whilst Auto Configure is operating. If hardware alarms cannot be cleared, for example if the cable is damaged, Auto Configure skips the bearer.
Change Auto Configure Options

Select Options on the Auto Configure dialog box or Tools menu Options Auto Configure tab.
Auto Configure Options.
Allow Auto Configure to put bearer into Low Impedance mode To avoid Auto Configure disrupting a network by connecting with a low impedance, this option is disabled by default. Only select this if you know that you are connected to a protected monitor point. Caution
Selecting this option removes the Terminated Monitor Mode (High Impedance) protection. This option is automatically disabled when you shut down the Signaling Advisor. ! Data Rates Auto Configure checks for signaling at the selected data rates, in the order specified. A tick ( ) indicates the selected Data Rates. Reducing the number of data rates to check improves the speed of the Auto Configure process. Select the rates that match your network, then promote or the rates so that the most likely data rate is at the top demote of the list.
Signaling Advisor User's Manual Connecting and Configuring 15
Protocol Stacks This field defines the protocol stacks that Auto Configure will verify data against. Reducing the number of stacks to check improves the speed of the Auto Configure process. Select the protocol stack type (for example, SS7), then select the stack that Auto Configure should verify any captured data against. At least one stack needs to be selected for each stack type. If you know that the same stack is used on other timeslots then Auto Configure's performance can be improved further by selecting the appropriate 'Use same stack' option. Information
You can select multiple Protocol Stacks from each Stack type. ! Existing Signaling Links Defines what happens to existing signaling links when Auto Configure is running. The default is to leave the existing link settings unchanged, however you can delete all links or only replace the links where Auto Configure detects different settings.
Learn about Configuring Manually in Bearer View

Bearer view contains all the settings you need to configure the Signaling Advisor before capturing and analyzing your network traffic. The bearers on the Signaling Advisor must be configured to match your , will identify any network's configuration. The Alarm view, hardware alarms. These alarms indicate which hardware settings need to be changed in Bearer view. The Bearer view is displayed from Configuration by clicking selecting View menu Bearer View. or by
Configuration's T1 Bearer view.
The Signaling Advisor automatically knows what types of interface are fitted. The interface type is shown at the top left corner of the Bearer view. The Interface Module graphic shows the overall alarm status for the selected interface module. As you change the Bearer view parameters to the correct parameters the alarms will change to the 'No alarm' color (user selectable). The parameters displayed in Bearer view vary depending on the type of bearer. Each Bearer view contains identification, operating mode, hardware, clocks and timeslot parameters. Once you have connected to your network you must configure the instrument. There are two main steps to Manually Configuring the Signaling Advisor: 1. ) to Clearing Hardware Alarms Using Alarm View ( identify the hardware alarms, change the Bearer View ( ) settings until the alarms have cleared. The default color for detected alarms is red, the default color for no alarms is green. Creating Signaling Links Add ( ) a Signaling Link to the appropriate timeslot. Select the configuration options from the Signaling Link Properties dialog box. Repeat Step 2 for each link you want to create.
2.
Once a signaling link has been created you can capture data. Information You can click [F1] for more information on the current view.
Bearer Types
The available bearer types are: ! ! ! ! E1 T1 Datacom (V.35/RS-449/RS-232) DS0/DS0-A
The edit options available will change depending on settings you have already made - only valid options will be enabled.
Timeslot Grid
The Timeslot Grid represents the timeslots on the bearer. Timeslots for multiplexed interfaces, such as E1 and T1, are shown in a grid. Each cell represents a timeslot. DS0 and Datacom display a single cell.
A T1 timeslot grid.
Add signaling links to the appropriate timeslot to indicate where the signaling will be found on your network. Sub-rate and Fractional timeslots are set up by right-clicking the timeslot(s) in the Timeslot Grid. The settings for the link are displayed in the Link section of Bearer view when the signaling link is selected. Signaling links are represented by: Blue Flags represent SS7 signaling.
Green Flags represent Non-SS7 signaling (X.25/ISDN/V.5/NS GPRS/Frame Relay). represents GSM TRAU data. Double-clicking the left mouse button on a signaling link will display its properties. If you would prefer to display the Protocol Stack associated with the link when double-clicking, you can change the option in Tools menu Options General Setting tab Configuration panel.
Sub-rate Links
Sub-rate Links are configured in smaller timeslots within the standard timeslot. Sub-rate signaling links are shown in the appropriate sub-rate timeslot. The most significant bits start on the right hand side of the timeslot.
Configuration Bearer view's Sub-rate Timeslots.
Fractional Links
Fractional Links are configured across multiple timeslots on one bearer. When timeslots are contiguous the boundaries between each timeslot are changed to dotted lines. When one part of a fractional timeslot is selected the others are also selected.
Configuration Bearer view's Fractional Timeslots.
Filter Short and Retransmitted Messages

You can control what happens to short messages and retransmitted messages during a Real Time mode capture session. The default is to filter out short messages but allow retransmitted messages to be captured. Short and Retransmitted Message filtering is set when a signaling link is created. Short messages contain less than 4 bytes of user data (8 octets in total, including 1 flag and CRC bytes), for example, FISUs and LSSUs in SS7, S-Frames and R-Frames in ISDN and Alive and Alive-ACK messages in
GPRS networks. You set up this filtering in the Signaling Link Properties dialog box.
Configurations Signaling Link Properties dialog box showing SS7 link properties for a monitor link. Emulation options are disabled (grey).
Filter out Short Messages This is the default option. Short messages will not be captured. No Filtering or Collapsing No filtering or collapsing. All short messages will appear as individual messages in Monitor's Traffic Overview. To see these messages you must ensure that the Display Levels in Monitor are set to display all messages. Collapse Short Messages Consecutive short messages will be represented by a single message in Monitor's Traffic Overview. You can set the number of messages (maximum 65535) to be collapsed by entering the number in the box. The PCR Filter panel shows the option for controlling retransmitted messages. A tick ( ) indicates that retransmitted messages will not be captured.
20 Connecting and Configuring Signaling Advisor User's Manual
Caution If Short Message (e.g. FISU) and / or PCR filtering are not applied, the performance and longevity of the capture session will be reduced. It is therefore strongly recommended that these filters be applied.
Information When calculating the length of messages the Signaling Advisor includes 2 bytes for frame check sequence (FCS) and 1 byte for a flag.
How to Configure Manually

There are several steps involved in manually configuring your Signaling Advisor.
Step 1 Connecting
Ensure that the Interface Module(s) are inserted and locked into the side of the Signaling Advisor (this should ONLY be done when the instrument is switched off). Connect the Signaling Advisors Interface Modules to your network following the instructions for the Interface Module and the Operating Mode you want to use. See Help menu On-line Documentation and select the appropriate Interface Module Reference Manual for more information on cabling and connecting.
Step 2 Clearing Hardware Alarms

Hardware parameters, such as line-encoding, frame type and clocks, are ) Bearer view ( configured in Configurations ( links you must configure the bearer ). Before creating
The Interface Module graphic at the top of Bearer view indicates the hardware alarm status of all the bearers on the Interface Module. Red indicates that hardware alarms have been detected. Use Alarm view to identify the hardware alarms. Change the configuration settings in Bearer view to clear the hardware alarms.
Step 3 Creating Links

Create links on the timeslots you want to capture data from or send messages on. 1. Save a ConfigurationIn Configuration select File menu display the Export Configuration dialog box. Save As to
2. To save the file in a different folder, click a different drive in the Save in box, or double-click a different folder in the folder list. To save the file in a new folder, click Create New Folder.
3. 4.
In the File name box, type a name for the file. Click Save. Information
To use the saved configuration you must import it as part of an imported Measurement Setup file.
Configuring Bearer Physical Parameters for Monitoring

Before configuring bearers and creating links you must be connected to the network. You manually configure bearers by setting the individual parameters in Bearer view. Alternatively you can Auto Configure bearers that will be used for Monitoring.
Configuring an E1 Bearer for Monitoring

Read the E1 Balanced / E1 Unbalanced Interface Module Reference Manuals for more information on installing, connecting and verifying E1 Interface Modules.
Assumptions
! Either an E1 Balanced or E1 Unbalanced Interface Module is fitted in the Signaling Advisor.
Steps
1. 2. 3. 4. In Configuration, click to display Bearer view. In the Operating Mode panel select either Bridged Monitor, 20>30db Terminated Monitor or 0db Terminated Monitor. In the Multi-Frame Type panel select either No CRC4 or CRC4. In the Line Encoding panel select either HDB3 or AMI.
Information You can also configure the system to route any Monitor clock out on one of the two External Outputs using the View menu External Clocks dialogue within Configure.
What do you want to do next?

! Check hardware alarm status.
Configuring a T1 Bearer for Monitoring

Read the T1 Interface Module Reference Manual for more information on installing, connecting and verifying T1 Interface Modules.
Assumptions
!
A T1 Interface Module is fitted in the Signaling Advisor.

Steps
1. 2. 3. 4. 5. In Configuration, click to display Bearer view. In the Operating Mode panel select either Bridged Monitor, 20>30db Terminated Monitor or 0db Terminated Monitor. In the Multi-Frame Type panel select either SuperFrame
(D3/D4) or Extended Super Frame.
In the Line Encoding panel select either B8ZS or AMI. In the Data Rate panel select either 56K or 64K.

Configuring a Datacom Bearer for Monitoring

Read the Datacom Interface Module Reference Manual for more information on installing, connecting and verifying Datacom (V.35, RS232 or RS-449) Interface Modules.
Assumptions
! A Datacom Interface Module is fitted in the Signaling Advisor with either a V.35, RS-232 or RS-449 Monitor Cable connected.
Steps
1. 2. 3. In Configuration, click to display Bearer view. In the Operating Mode panel select Monitor. Select the Mark Polarity (Normal or Inverted) from the Mark Polarity panel.

Configuring a DS0 Bearer for Monitoring

Read the DS0 Interface Module Reference Manual for more information on installing, connecting and verifying DS0 Interface Modules.
Assumptions
! A DS0 Interface Module is fitted in the Signaling Advisor.
Steps
1. 2. 3. In Configuration, click to display Bearer view. In the Operating Mode panel select Monitor. Select the clock source from the Clock Source panel. This determines which clock will be used to receive the data from the Signaling Advisors Rx cables (RxA and RxB). The clock sources are:
Bit/Byte External
receives data using the external Bit/Byte clock fed into the 9-pin D-type connection on the front of the DS0 Interface Module. The external clock should be your network's System Wide Reference Clock.
Composite External receives data using the external Composite clock fed into the 9-pin D-Type on the front of the DS0 Interface Module (uses different pins from the Bit/Byte External clock above). The external clock should be your network's System Wide Reference Clock Internal receives data using the Interface Module's internal 64 kbit/s reference clock. (56k Data Rates still uses 64k clock - only seven of the eight bits are used). Other
receives data using the Bit/Byte clock fed in from another DS0 Interface Module or the Mainframe External Connector. The clock fed into the Mainframe External Connector must be Bit/Byte format.
4.
(OPTIONAL) Output the Clock Signal. If you selected 'Internal' or Other' clocks you can output the Bit/Byte clock signal. Click Output clock via interface in the Output Clock panel to output on the (Bit/Byte) clock pins of the 9-pin D-Type connector on the front of the Interface Module. Only the Bit/Byte clock output is supported.
5.
In the Data Rate panel select either 56K or 64K.
Caution Pins 3 and 4 on the 9-pin D-type connection are bi-directional. For
Bit/Byte and Composite clock sources they input the clock signal. For Internal or Other clock sources the same pins output the clock signal.
Information ! You can also configure the Signaling Advisor to route any Monitor clock out on the External Output using the View menu External Clocks dialog within Configure. You can only route the clock from one Interface Module to an external connector. When using a System Wide Clock you should only connect it to one DS0 bearer and route the signal to other DS0 bearers through the Signaling Advisor. Use the Other clock source setting to do this. DS0 bearers on one Interface Module must use the same clock source. Changing a clock source on Bearer1.1, for example, will automatically change the clock source for 1.2, 1.3 and 1.4.

!
Check hardware alarm status.

Configuring Physical Parameters for Emulating

Before configuring bearers and creating links you must be connected to the network. You must manually configure the bearers for EmuLite by setting the individual parameters in Bearer view. Information Auto configure cannot be used to configure bearers for emulation.
Configuring an E1 Bearer for Emulating

Read the E1 Balanced / E1 Unbalanced Interface Module Reference Manuals for more information on installing, connecting and verifying E1 Interface Modules.
Assumptions
! Either an E1 Balanced or E1 Unbalance Interface Module is fitted to the Signaling Advisor.
Steps
1. 2. 3. In Configuration, click to display Bearer view. In the Operating Mode panel select End Emulate. Select the clock source from the Emulate Clock panel. This determines which clock will be used to transmit the data from the Signaling Advisors Tx cable. The clock sources are:
! ! !
Internal transmits using the internal 2.048Mbit/s reference clock. Recovered Pair transmits using the clock recovered from the links Rx input. Other transmits using the clock fed in through one of the two External Clock inputs or the clock recovered from any other E1 Rx input in the system.
4. 5.
Select the Multi-Frame Type (CRC4 or No CRC4) from the Multi-Frame Type panel. Select the Line Encoding (HDB3 or AMI) from the Line Encoding panel.
Information You can also configure the system to route clocks out on the two External Outputs using the View menu External Clocks dialogue within Configure.

Configuring a T1 Bearer for Emulating

Read the T1 Interface Module Reference Manual for more information on installing, connecting and verifying T1 Interface Modules.
Assumptions
! A T1 Interface Module is fitted to the Signaling Advisor.
Steps
1. 2. 3. In Configuration, click to display Bearer view. In the Operating Mode panel select End Emulate. Select the clock source from the Emulate Clock panel. This determines which clock will be used to transmit the data from the Signaling Advisors Tx cable. The clock sources are: ! ! !
Internal transmits data using the internal 1.544Mbit/s reference clock. Recovered Pair transmits data using the clock recovered from the links Rx input. Other
transmits data using the clock fed in through one of the two External Clock inputs or the clock recovered from any other T1 Rx input in the system.
4. 5. 6.
Select the Multi-Frame Type (SuperFrame or Extended SuperFrame) from the Multi-Frame Type panel. Select the Line Encoding (B8ZS or AMI) from the Line Encoding panel. Select the Data Rate (56k or 64k) from the Data Rate panel.

Configuring a Datacom Bearer for Emulating

Read the Datacom Interface Module Reference Manual for more information on installing, connecting and verifying Datacom (V.35, RS232 or RS-449) Interface Modules.
Assumptions
! ! Either a V.35, RS-232 or RS-449 Interface Module is fitted to the Signaling Advisor. The cable supports emulation. (Check the Datacom Interface Module Reference Manual for details on cables that support emulation.).
Steps
1. 2.
In Configuration, click
to display Bearer view.
In the Operating Mode panel select Emulate.
3.
Decide whether you want to emulate either the DCE or the DTE end. Based on this selection the Signaling Advisor will automatically disable the irrelevant options on Bearer view. Only relevant options will be left enabled. Select the clock source from the Emulate Clock panel. This determines which clock will be used to transmit the data from the Signaling Advisors Tx cable. The clock sources are: !
Incoming TXC (only available when emulating DTE) transmits using the incoming clock received from the remote end (DCE). Internal transmits using the LIM's internal clock at the selected data rate (4.8kbit/s to 64kbit/s). Other
4.
! !
transmits using the clock either fed in through one of the two Mainframe External Clock inputs (D-Type on the side of the unit) or a clock recovered from any other Datacom Bearer in the system. The clocks displayed will depend on the Operating Mode and Terminal Type of the other bearers.
5.
Set up the TXD Timing Source from the TXD Timing Source panel. If you are emulating as DCE (Step 3) then you can set the TXD Timing Source to either option. If you are emulating as DTE then it is automatically set to DTE Sourced. Select the Mark Polarity (Normal or Inverted) from the Mark Polarity panel.
6.

Configuring a DS0 Bearer for Emulating

Read the DS0 Interface Module Reference Manual for more information on installing, connecting and verifying DS0 Interface Modules.
Assumptions
! A DS0 Interface Module is fitted to the Signaling Advisor.
Steps
1. 2. 3. In Configuration, click to display Bearer view. In the Operating Mode panel select Emulate. Select the clock source from the Clock Source panel. This determines which clock will be used to transmit the data from the Signaling Advisors Tx cable. The clock sources are: !
Bit/Byte External
transmits data using the external Bit/Byte clock fed into the 9-pin D-type connection on the front of the DS0 Interface Module.
Composite External transmits data using the external Composite clock fed into the 9-pin D-Type on the front of the DS0 Interface Module (uses different pins from the Bit/Byte External clock above). Internal transmits data using the internal 64 kbit/s reference clock. (56k Data Rates still use 64k clock only seven of the eight bits are used). Other
transmits data using the Bit/Byte clock fed in from either the Mainframe External Connector or the clock from another DS0 Interface Module. A clock fed into the Mainframe External Connector must be Bit/Byte.
4.
(OPTIONAL) Output the Clock Signal. If you selected 'Internal' or Other' clocks you can output the Bit/Byte clock signal. Click Output clock via interface in the Output Clock panel to output on the (Bit/Byte) clock pins of the 9-pin D-Type connector on the front of the Interface Module. Only the Bit/Byte clock output is supported.
5.
Select the Data Rate (56k or 64k) from the Data Rate panel.
Caution Pins 3 and 4 on the 9-pin D-type connection are bi-directional. For
Bit/Byte and Composite clock sources they input the clock signal. For Internal or Other clock sources the same pins output the clock signal.
Information ! You can also configure the Signaling Advisor to route any Monitor clock out on the External Output using the View menu External Clocks dialog within Configure. You can only route the clock from one Interface Module to an external connector. When using a System Wide Clock you should only connect it to one DS0 bearer and route the signal to other DS0 bearers through the Signaling Advisor. Use the Other clock source setting to do this. DS0 bearers on one Interface Module must use the same clock source. Changing a clock source on Bearer1.1, for example, will automatically change the clock source for 1.2, 1.3 and 1.4.

Create Links
Once you have configured the bearers hardware parameters you must create links. Create a link for each timeslot you expect to transmit and/or receive data on.
28 Connecting and Configuring Signaling Advisor User's Manual
Links are created in Configurations Bearer view (
).
Links are created in the same way for both monitoring and emulating. When creating a signaling link for a monitor bearer, any options specific to emulation will be disabled. Emulation SS7 Links Only The Automatically align link if it is out of service will ensure that the Signaling Advisor will automatically try to align the link when created and if it goes out of service. This option is enabled by default. You must disable this option if you want to align the link manually.
Create an SS7 Link Assumptions

! The bearer's physical parameters have been configured.
Steps
1. 2. In Configurations Bearer View ( ) select the bearer. Double-click the time-slot to display the Signaling Link Properties dialog box.
3. 4. 5. 6. 7.
Select SS7 to display the SS7 protocol stack list. Select the Protocol Stack from the list. Select the mode from the Mode panel. If emulating the mode is automatically set to Duplex. Select the Short Message filtering option. In the Short Messages panel select if you want short messages (for example FISUs, LSSUs) filtered or collapsed. If you want to filter out duplicate SS7 MSU messages tick ( ) the Filter out duplicate SS7 MSU messages option on the PCR Filter panel. (OPTIONAL) The Automatically align link if it is out of service option on the Link Alignment panel is selected by default. This option will align the link when it is created and realign it if it goes out of service. If you are emulating and want to align the link at a later time click the tick ( ) to remove it and deselect the automatic alignment option.
8.
9.
10. Click OK to create the link. The new link will appear in the timeslot. Blue Flags Information ! ! ! ! To edit - right-click on the link and select Properties or doubleclick the link. To delete - click the link and then click . represent SS7 signaling.
You can also set up Sub-Rate and Fractional links. Although traffic on a simplex bearer can be captured using a duplex bearer configuration, capture performance will be improved if the simplex bearer option is chosen when creating the link.

! ! ! View the status of the link. Bring the link into or out of service (both in Normal or Emergency mode of operation) (Emulation only). Modify the SS7 Automatic Level 2 Protocol Parameters (Link Alignment, Timers and Error Rate Monitor Thresholds) (Emulation Only). Use EmuLite (Emulation Only).
Modify SS7 Level 2 Parameters

The Level 2 dialog displays the default parameters as defined in the protocol specification. These values should not need changed.
Assumptions
! The SS7 link is configured.
Steps
1. In Configurations Bearer View ( ) right-click the link and select Level 2 Parameters to display the SS7 Level 2 Configurable Parameters dialog box. Change the Link Alignment Mode, the Timer Values or the Error Rate Thresholds. Alternatively you can Restore User Defaults or Restore System Defaults values. If you want to set these values as the default click Save As User Defaults.
2.
3.
Create an X.25/ISDN/V5 Link Assumptions

Steps
1. 2. 3. In Configurations Bearer View ( ) select the bearer. Double-click the time-slot to display the Signaling Link Properties dialog box. Select X.25/ISDN/V.5/NS GPRS/Frame Relay to display the GPRS NS, ISDN, V.5 and X.25 protocol stack list. Select the Protocol Stack from the list. (Only ISDN and GPRS NS (Network Service) available when emulating). Select the mode from the Mode panel. If emulating the mode is automatically set to Duplex. If emulating an ISDN link, select the end you want to emulate. Select User or Network from the ISDN EmuLite Options Side panel. If you select Network the link will automatically be established. !
User sets the Signaling Advisor to be a user of the network. The Signaling Advisor has a specific address on the bus - its Terminal Endpoint Identifier (TEI). If TEI is set to Automatic the Level 2 software will automatically request a TEI (64-126) from the Network during the alignment process. Alignment will fail if all possible TEIs are in use.
4. 5.
If TEI Negotiation is specified as Non-Automatic (Manual) then the link will use the TEI value (0 - 63)
specified by you when it tries to align. If the specified TEI value is already in use, alignment will fail. The failure reason will be displayed in Link Status view, for example 'TEI denied'. !
Network
sets the Signaling Advisor to assume the role of the network master. The Signaling Advisor will allocate TEIs to equipment and respond to Automatic Parameter Negotiation Requests. The Automatic Level 2 software keeps track of which TEIs are in use and allocates the next available TEI on request. When a link is stopped any allocated TEIs are freed and can be reused.
6.
If emulating, select how you want to setup Automatic Level 2 parameters.

! Automatic sets the Signaling Advisor to negotiate the level 2 parameter values directly with the opposite side of the link. Non-Automatic the Signaling Advisor uses the current Level 2 Parameter values.
! 7.
Click OK to create the link. The new link will appear in the timeslot. The link is represented by: represent Non-SS7 signaling Green Flags (X.25/ISDN/V.5/GPRS NS/Frame Relay).
Information ! ! ! ! To edit - right-click on the link and select Properties or doubleclick the link. To delete - click the link and then click .
You can also set up Sub-Rate and Fractional links. Although traffic on a simplex bearer can be captured using a duplex bearer configuration, capture performance will be improved if simplex bearer option is chosen when creating the link.
Modify ISDN Level 2 Parameters

The Level 2 dialog displays the default parameters as defined in the protocol specification. These values should not need to be changed.
Assumptions
! The ISDN link is configured.
Steps
1. In Configurations Bearer View ( ) right-click the link and select Level 2 Parameters to display the LAPD Level 2 Configurable Parameters dialog box. Change the Timer Values, the Maximum Outstanding Information Frames and other parameters. Alternatively you can Restore User Defaults or Restore System Defaults values. If you want to set these values as the default click Save As User Defaults.
2.
3.
Create a GPRS Network Service Link Assumptions

Steps
1. 2. 3. In Configurations Bearer View ( ) select the bearer. Double-click the time-slot to display the Signaling Link Properties dialog box. Select X.25/ISDN/V.5/GPRS NS/Frame Relay to display the GPRS, ISDN V.5 and X.25 protocol stack list. Select the Protocol Stack from the list. (Only GPRS Gb available when emulating). Select the mode from the Mode panel. If emulating the mode is automatically set to Duplex. Select the end you want to emulate. Select User or Network from the Network Service EmuLite Options Side panel. Selecting the emulation end controls which emulation parameters are displayed. !
User sets the Signaling Advisor to be a user of the network. The Signaling Advisor will emulate the BSS. Network
4. 5.
sets the Signaling Advisor to assume the role of the network master. The Signaling Advisor will emulate the SGN. The Automatic Level 2 software maintains the PVC management, Error Monitor and VC-Test procedures in the Network Service Layer.
6.
Click OK to create the link. The new link will appear in the timeslot. The link is represented by: represent Non-SS7 signaling Green Flags (X.25/V.5/ISDN/Frame Relay).
Information ! ! ! ! To edit - right-click on the link and select Properties or doubleclick the link. To delete - click the link and then click .
You can also set up Sub-Rate and Fractional links. Although traffic on a simplex bearer can be captured using a duplex bearer configuration, capture performance will be improved if simplex bearer option is chosen when creating the link.
Modify GPRS Network Service Level 2 Parameters

The Level 2 dialog displays the default parameters as defined in the protocol specification. These values should not need to be changed.
Assumptions
The following must be completed before progressing with this task. ! The Frame Relay or GPRS Gb link is configured.
Steps
1. In Configurations Bearer View ( ) right-click the link and select Level 2 Parameters to display the Network Service Level 2 Configurable Parameters dialog box. Change the Timer and Counters Values. Alternatively you can
Restore User Defaults or Restore System Defaults values.
2. 3.
If you want to set these values as the default click Save As User Defaults.
Create a TRAU Link Assumptions

! ! The bearer is configured for Monitoring. If using a T1 bearer, the Data Rate is set to 64K on T1.
Steps
1. In Configurations Bearer View ( ) right-click the timeslot to display the popup menu. Select Timeslot and then the data rate (16Kbits/s or 8Kbits/s) from the extended menu. The appropriate sub-rate timeslots will be created. Double-click the sub-rate time-slot to display the Signaling Link Properties dialog box. Select either TRAU 16K or TRAU 8K to display on the relevant TRAU protocol stack list. Select the Protocol Stack from the list.
2. 3.
4. 5.
Select Duplex, Simplex (Port A) or Simplex (Port B) from the Mode panel. Select whether you want to filter short messages from the Short Messages panel. Information
! ! ! !
Emulation on TRAU links is not available. To edit - right-click on the link and select Properties. To delete - click the link and then click .
Although traffic on a simplex bearer can be captured using a duplex bearer configuration, capture performance will be improved if simplex bearer option is chosen when creating the link.
Listen to Voice Traffic Assumptions

! ! E1 or T1 Bearers are in use. Only for 64k and 56k timeslots.
Steps
1. 2. 3. 4. Click to display Bearer view. Right-click on the timeslot and select the Connect to Handset option from the popup menu. Set up the options for the link. Click OK. Connect the handset to the handset port on the Signaling Advisor.
Emulating Voice Traffic (EmuLite Only) Assumptions

! ! ! E1 or T1 Bearers are in use. Only for 64k and 56k timeslots. End Emulate mode is selected.
Steps
1. 2. 3. 4. Click to display Bearer view. Right-click on the timeslot and select the Connect to Handset option from the popup menu. Set up the options for the link. Click OK. Connect the handset to the handset port on the Signaling Advisor.
Set up a Sub-Rate Link

1. 2. Click to display Bearer view. Right-click the timeslot you want to set up as a sub-rate timeslot. Select the Timeslot option and click on the sub-rate you want to use. Right-click on the timeslot and create a signaling link.
3.
Information ! ! On a T1 interface the Sub-Rate option is only available when the 64k Data Rate is selected. If you want to change the sub-rate setting you must return the timeslot to 64k and then set up the new sub-rate.
Set up a Fractional Link

1. 2. Click to display Bearer view. Select the timeslots to be included in the Fractional Timeslot. Select Adjacent Timeslots Click the first timeslot and then hold down [SHIFT] and click the last timeslot. Select Non-Adjacent Timeslots Click the first timeslot and then hold down [CTRL] and click each timeslot. 3. Right-click on any of the highlighted timeslots and create a signaling link.
Setting Short and Retransmitted Message Filtering Options

1. 2. 3. 4. Click to display Bearer view. Right-click on a signaling link and select Properties from the popup menu. Select the Short Messages filtering option you want to use. Select the PCR check box if you do not want to capture retransmitted messages. Click OK.
Caution If Short Message (e.g. FISU) and / or PCR filtering are not applied, the performance and longevity of the capture session will be reduced It is therefore strongly recommended that these filters be applied.
Learn about Alarms

The Alarm view shows whether hardware alarms have been detected on the bearers connected to your network. It identifies each alarm type so that you know which hardware setting to change to clear the alarm. Alternatively, you can let Auto Configure work out the settings and clear the alarms for you. There are two view styles: ! Simple Alarm view uses colored blocks to represent the alarm status for each fitted bearer. This small window does not obstruct the application view behind it. Full Alarm view expands the Simple Alarm view to show the operating mode and alarm status of each alarm type for the selected bearer. or from Tools menu
The Alarm view is displayed by clicking Alarm View. Information !
Click [F1] to display this help topic for Alarm view. In any Signaling Advisor view, click [F1] to display the current view's help topic. The Alarm view is only available when the Signaling Advisor is in Real Time mode.
How to Use Alarm View

Alarm view ( ) identifies any hardware alarms found on the selected bearers. It is useful to: ! ! Identify alarms and indicate which Bearer view settings need to be changed. Notify you that a new hardware alarm has been detected.
Identify and Clear Hardware Alarms

1. 2. Click to open the Alarm View. to display it. If the Full Alarm view is not displayed, click
Full Alarm View showing monitoring links. There are Loss of Signal alarms on all bearers except Bearer 1.2RxB. This indicates that only Bearer 1.2RxB is connected.
3.
If a hardware alarms have been detected on any of the bearers they will be shown in the alarm color (default red). Click the bearer on the left panel to select it and display its alarm details in the right panel. In the right panel the bearers are listed across the top and the alarms type down the left. The alarm color identifies the bearers where particular hardware alarms have been detected. Hover the mouse pointer over the alarm types to display a ToolTip of the complete alarm name. ) Bearer view ( ) and change the Open Configurations ( appropriate settings in Bearer view to clear alarms. The table below shows the Alarm type and the recommended settings to be changed.
4.
5.
Alarm Clearing Options.
Information When emulating, the transmit (Tx) side alarms will be greyed out.

! Create a signaling link.
Switch between Simple and Full Alarm View

To switch from Simple Alarm view to the Full Alarm view: ! ! ! ! Double-click the block Double-click the Alarm view title bar Click Click . .
To switch from the Full Alarm view to the Simple Alarm view: To minimize either Alarm view on to the Windows Task Bar:
Click
Stop Alarm View Popping Up

The default setting is for the Alarm view to popup when a new alarm is detected. 1. 2. Click to open the Alarm View.
On the Simple Alarm view right-click and select Alarm

Notification.
Simple Alarm View's right mouse button menu.
On the Full Alarm view: ! ! 1. 2. 3. Select View menu

Alarm Notification.
Right-click and select Alarm Notification. Select Tools menu

Options.
From any Signaling Advisor view: Click the Alarm View tab to select it. Click the Bring the Alarm View to the front when a new alarm occurs option to deselect it. Caution If Alarm view is not active when an alarm occurs, the Alarm view will NOT be brought to the front. Information A tick ( ) indicates that Alarm Notification is on.
Keep Alarm View on top

1. 2. Click
Top.
to open the Alarm View.
On the Simple Alarm view right-click and select Always on
On the Full Alarm view: ! Select View menu

Always on Top.
From any Signaling Advisor view: 1. 2. 3. Select Tools menu

Options.
Click the Alarm View tab to select it. Click the Keep alarm view on top option to select it.
Information A tick ( ) indicates that the Alarm view will remain on top of all other windows.
Alarm View Colors

The Error Color selected in the Alarm View tab will be used throughout the Signaling Advisor. When you change the Error Color setting in this tab the Error Color setting in the Color tab will automatically change. 1. 2. Select Tools menu
Options.
Click the Alarm View tab.
Tools Options tab for Alarm View settings.
3. 4.
Click the color and select the new color from the palette. Repeat Step 3 for each color you want to change. Click OK.
Information The selected Error Color will also be used by Traffic Overview and Configuration views.
Log Alarm Data to File

1. 2. 3. 4. Select Tools menu
Options.
Click the Alarm View tab. Click the Enable Alarm CSV Logging to enable alarm logging. Enter the filename or click Browse to select the file's location. Click OK.
Learn about the Status of Links

The Link Status view, , shows information about what has been detected on the links connected to the Signaling Advisor. The details shown on the Link Status view differ depending on the Protocol Stack being used by the link. The Link Status view is only available in Real Time mode. It shows the status of each link. Monitor Links: SS7 uses FISU/LSSU to determine the status of the link. Each side of a duplex link has its own state. X.25/ISDN/V5/TRAU initial status is Out of Service (red) and then changes to In Service (green) when the first good message has been received. Each side of a duplex link has its own state. Emulation Links: SS7/ISDN/GPRS NS use the state information obtained from the Automatic Level 2 software. If the link fails the failure reason will be displayed on the Link Status view. There are two view styles: ! ! Simple Link Status view uses colored blocks to represent the link status for each link. Full Link Status view expands the Simple Link Status view to show the statistics for the selected link.
Full Link Status view for Emulation , Duplex and Simplex Monitor links.
The Link Status view is displayed by clicking menu Link Status View. Information !
or by selecting Tools
Click [F1] to display this help topic for Link Status view. In any Signaling Advisor view, click [F1] to display the current view's help topic.
! ! !
Link Statistics are gathered even if data is not being captured from the link. The Link Status view is updated approximately once a second. Other link statistics can be gathered using Statistics link profiles.
How to Use Link Status View

The Link Status view displays status and statistics for each configured link. You can also start and stop link alignment for emulation links from Link Status view. You can quickly see the Erlang, FISU and other link statistics from this view. You can set the Link Status view to popup when the status changes. This means that you do not have to continually check the status of the links, the Signaling Advisor does it for you.
Bring a Link Into or Out of Alignment (EmuLite Only)

Before the Signaling Advisor starts to emulate on a link it checks that the to start link is aligned. This happens automatically when you click running EmuLite Sequences. If any link is out of service a message will be displayed informing you which links need to be aligned. 1. 2. Click to open the Link Status view.
If you are aligning an SS7 you should check the alignment mode. Right-click the link and select SS7 Alignment Normal or Emergency. Select the link(s) to be brought into alignment. Range of Adjacent Links Click the first link in the range, and then hold down [SHIFT] and click the last link in the range. Range of Non-Adjacent Links Click the first link in the range, and then hold down [CTRL] and click each link in the range.
3.
4.
Right-click the links and select Bring into Alignment from the popup menu.
Check the Status of a Link

1. 2. Click to open the Link Status view. If the link is aligned the link status color will be green. If the link status color is red the link is out of alignment.
Information ! Monitor Links: SS7 uses FISU/LSSU to determine the status of the link. X.25/ISDN/V5/TRAU initial status is Out of Service (red)
and then changes to In Service (green) when the first good message has been received. ! Emulation Links: SS7/ISDN/GPRS NS uses the state information obtained from the Automatic Level 2 software.
Bring Link Status View to the Front when Status Changes

1. 2. Click to open the Link Status view.
Link State Change Notification.
Select View menu
Caution If Link Status view is not active when a status change occurs the Link Status view will NOT be brought to the front.
Keep Link Status View on Top

1. 2. Click to open the Link Status view.
Always on Top.
In the Link Status view select View menu
Reset Link Statistics Counts

1. 2. Click to open the Link Status view. In the Link Status view select View menu Reset Statistics Counts. Either select Current Link to clear the statistics for the selected link or All Links.
Information ! ! You can also access the Reset Statistics Counts options by right-clicking the Full Link Status view. Error counts are set to zero when the link is created. Connecting and disconnecting cables will cause errors.
Link Status View Colors

1. 2. Select Tools menu
Options.
Click the Link Status View tab.
Tools Options tab for Link Status View settings.
3. 4.
Click the color and select the new color from the pallet. Repeat Step 3 for each color you want to change. Click OK.
Learn about Protocol Stacks and Protocols

The Protocol Stack view displays the protocol stacks used by the links in the current configuration file. Each stack shows the protocols used and their relationships with each other. The Protocol Stack defines how messages will be decoded and which Call Trace and Statistics profiles will be available. The Protocol Stack view is displayed from Configuration by clicking or by selecting View menu Protocol Stack View.
A typical Protocol Stack view (GPRS Gb).
Each Protocol Stack has a Point Code Format associated with it. This defines how the Point Codes will be displayed for links using this stack. You can edit the Protocol Stack and its protocols by right-clicking on the object you wish to edit. A popup menu will appear displaying the options available for the object you clicked. Protocol Stacks are automatically added to the Protocol Stack view when a link is created. Information Click [F1] to display this help topic for Protocol Stack view. In any Signaling Advisor view, click [F1] to display the current view's help topic.
Default Protocols
You can set up a protocol to be the default protocol. This is identified by 'Default' under the protocol. The Default Protocol will be used if no other protocol matches the selector value. If the selector value and default have not been defined messages will not decode. When there is only one available route 'Default' is not shown, keeping the display clear for other information. Protocol Stack Layer Select Code Clash Protocols on the same layer must use different selector values. If you modify the protocol stack, so that the same select code is used by two protocols on the same layer, a Select Code Clash message will be displayed.
How to Use Protocol Stacks

When you create a signaling link you select the Protocol Stack for the new link. This Protocol Stack will automatically be added to the Protocol Stack view. The Protocol Stack defines how messages will be decoded and which Call Trace and Statistics profiles will be available. If you find that the Protocol Stacks supplied with the Signaling Advisor do not match the details of your network then you can edit an existing Protocol Stack or create a new one.
Add a Protocol to the Stack

1. 2. 3. 4. Click to display the Protocol Stack view. If more than one Protocol Stack is displayed, select the stack you want to edit. Click the protocol you wish to add a higher level protocol to. to display the Add Protocol dialog box. Select the Click options from the dialog box.
Protocol Stack view's Add Protocol dialog box..
5. 6.
Click OK. The Protocol Properties dialog box will be displayed. Complete the properties for the protocol. Click OK to add the protocol to the Protocol Stack.
Information ! ! Protocols such as LAP, INAP, AIN, IS41 and so on, all include TCAP and can be added directly onto SCCP. To remove a protocol from the stack click the protocol to select it and then click deleted. . Any higher level protocols will also be
Edit a Protocol's Selector Value

1.
Click
to display the Protocol Stack view.

A typical Protocol Stack view (GPRS Gb).
2. 3. 4. 5.
If more than one Protocol Stack is displayed, select the stack you want to edit. Right-click the protocol you want to edit. Select Protocol Properties from the popup menu. Edit the Selector value. Click OK.
Information Click the Layer default protocol option to set this protocol as the default. Any value not already defined on this protocol layer will be decoded using the default protocol.
Edit a Protocol's Name

1. 2. 3. 4. 5. Click to display the Protocol Stack view. If more than one Protocol Stack is displayed, select the stack you want to edit. Right-click the protocol you want to edit. Select Protocol Properties from the popup menu. Edit protocol Name. Click OK.
Replace a Protocol in the Stack

1. 2. 3. 4. 5. 6.
Click
to display the Protocol Stack view.
If more than one Protocol Stack is displayed, select the stack you want to edit. Right-click the protocol you want to replace. Select Replace Protocol from the popup menu. Select the protocol. Click OK to display the Protocol Properties.
7.
Edit protocol properties as required. Click OK.
Information When you replace a protocol, higher level protocols connected to it are not deleted. This function is particularly useful when you wish to create a new protocol stack based on an existing one.
Edit Protocol Stack Name

1. 2. 3. 4. Click to display the Protocol Stack view. If more than one Protocol Stack is displayed, select the stack you want to edit. Right-click on the view to display the popup menu. Select Stack Properties. Make the changes. Click OK.
Save an existing Protocol Stack to a file

1. 2. 3. 4. Click to display the Protocol Stack view. If more than one Protocol Stack is displayed, select the stack you want to save. Select File menu box.
Save Protocol Stack As
to display the dialog
Enter the filename and click OK to save.
Information You must save the new Protocol Stack to the Configuration directory (this is the default directory). Only saved Protocol Stack files are available to be used with other configurations.
Create a Protocol Stack File

Creating a new Protocol Stack file lets you use the Protocol Stack in other configurations. 1. 2. 3. 4. In Post Capture mode, select Configuration's File menu Protocol Stack.
New
Select the Level 2 Protocol to be used to start the Protocol Stack. to add protocols to the stack. Continue adding Click protocols until the stack is complete. Select File menu Save As and enter the filename for this Protocol Stack file.
Apply a different Protocol Stack to a Link

A links Protocol Stack is selected when the link is created. The Protocol Stack is automatically added to the Protocol Stack view when the link is created. 1. 2. Click to display Bearer view. Right-click the link and select Properties to display the Signaling Link Properties dialog box.
3. 4.
Select the Protocol Stack to be used. Click OK. The new Protocol Stack will be added to the Protocol Stack view.
Change the Point Code Format used by a Protocol Stack

1. 2. Click to display the Protocol Stack view. Right-click on the Protocol Stack view to display the popup menu. Select the Stack Properties option.
3.
Select the Point Code Format from the drop-down list. Only Point Code Formats of the same size will be displayed, that is the same number of bits. Click OK.
4.
Information The Point Code Format defines how point code information will be displayed in Monitor's Traffic Overview, Call Trace and Statistics views.
How to Use Linksets

Bearers that share the same Protocol Stack can be grouped together in a linkset. Select the links to be grouped together in a linkset. You can use the linkset to associate a different Protocol Stack with all the links in the linkset or use the linkset to select the links in triggers or filters. The Linkset view can be displayed from Configuration by clicking by selecting View menu Linkset View. or
Configurations Linkset view.
The left side of the Linkset view displays the bearers included in the current linkset. The right side displays the links that are not included in any linkset. Links can only be in one linkset at a time. To move a link to another linkset you must remove it from its current linkset and add it to the new one. If you change a bearer's protocol stack it will automatically be removed from the linkset.
Create a Linkset
1. In Configuration, if the Linkset toolbar button ( ) is disabled select Insert menu Insert New Linkset from the list which appears. If the linkset button is enabled then click it to open the Linkset view.
2. 3.
From the Links available for Linkset panel click the link you want to add to the linkset. Click the <-Add button. The link will appear in the Links in Linkset panel.
Information ! If you add a link to the linkset which uses a different Protocol Stack a dialog box will appear asking you to change the Protocol Stack used by the link, or to change the Protocol Stack used by the Linkset or to not add the link to the linkset. Select and click Remove -> to remove a link from the linkset.
Learn about Point Code Mappings

Point Code Mappings are text descriptions associated with a Point Code. This makes it easy to associate messages with particular switches, for example '49-9-27' could be displayed as 'San Francisco'. The Point Code Mapping view displays the Point Code Mapping Tables available to the current configuration file. Each Table contains a list of Point Code Mappings that can be used to replace Point Code details in Monitor's Traffic Overview, Decode and Call Trace views. The Point Code Mapping view can be displayed from Configuration by clicking or by selecting View menu Point Code Mapping View.
Configuration's Point Code Mapping View.
Each Protocol Stack (that uses point codes) will automatically have a blank Point Code Mapping table.
How to Use Point Code Mappings

Point Code Mappings are text descriptions associated with a Point Code, for example, '49-9-27' could be displayed as 'San Francisco'. This makes it easy to associate messages with particular switch. They are added in
Configurations Point Code Mapping view but are displayed in Monitors Traffic Overview, Decode and Call Trace views. Each Protocol Stack (that uses point codes) will automatically have a blank Point Code Mapping table. Edit the Point Code Mapping Table and its Point Code Mappings by right-clicking on the mapping you wish to edit. A popup menu will appear displaying the options available for the object you clicked.
Create a Point Code Mapping File

1. In Post Capture mode, select Configuration's File menu Point Code Mapping. A file containing a Point Code Mapping view will be created. Click to display the Point Code Mapping dialog box. Enter the details for the Point Code Mapping. Click OK. Repeat from Step 2 for each mapping you want to add. Select File menu Save As and enter the filename you want to use for this Point Code Mapping file. The Point Code Mapping file can be imported into other configurations.
New
2. 3. 4. 5. 6.
Information You must save the new Point Code Mapping file to the Configuration directory (this is the default directory). Only saved Point Code Mapping files are available to be used with other configurations. Point Code Mappings embedded in Configuration files are not available to be used with other configurations.
Add a Point Code Mapping

1. 2. 3. 4. 5. 6. 7. Click to display the Point Code Mapping view. Click the Protocol Stack from the Protocol Stacks panel to display its Point Code Mapping table. Click to display the Point Code Mapping dialog box. Enter the Field Values. The number of values required depends on the Point Code Format being used. Enter the Mapping name (maximum 32 characters) at the bottom of the dialog box. Click OK. The new mapping is added to the Point Code Mapping view. If you want to add another mapping repeat from Step 4. If not, click Cancel.
Edit a Point Code Mapping

1.
Click
to display the Point Code Mapping view.

2. 3.
Click the Protocol Stack from the Protocol Stacks panel to display its Point Code Mapping table. Right-click on the Point Code Mapping you want to edit to display the popup menu. Select Properties from the popup menu. Enter the Field Values. The number of values required depends on the Point Code Format being used. Enter the Mapping name at the bottom of the dialog box. Click OK.
4. 5.
Insert Point Code Mapping Table

1. 2. 3. 4. Click to display Point Code Mapping view. Click the Protocol Stack from the Protocol Stacks panel to display its Point Code Mapping table. Click Insert from File button to display the Import File dialog box. Select Point Code Mappings (*.pcm) from the Files of Type drop-down list. (The Point Code Mappings supplied with the Signaling Advisor are located in the User Files\Configuration sub-directory.)
Export a Point Code Mapping Table

1. 2. 3. 4. 5. 6. Click Click to display Point Code Mapping view. to display the Point Code Mapping dialog box.
Enter the details for the Point Code Mapping. Click OK. Repeat from Step 2 for each mapping you want to add. Click the Save to File button to display the Save Point Code Mapping Table As dialog box. Enter the filename and click OK to save.
Information You must save the new Point Code Mapping file to the Configuration directory (this is the default directory). Only saved Point Code Mapping files are available to be used with other configurations. Point Code Mappings embedded in Configuration files are not available to be used with other configurations.
Learn about Point Code Formats

Point Code Formats define how the Point Code bit structure will be decoded. The Point Code Formats defines how many fields, how many bits in each field and the display order.
The Point Code Format view displays the Point Code Formats that are available to the current configuration. The Point Code Format to be used in the current configuration is defined in the Protocols Stack properties. The Protocol Stacks supplied with the Signaling Advisor are already set up with the appropriate Point Code Formats. When you create a link, and select the Protocol Stack to be used by the link the appropriate Point Code Format is allocated automatically. The Point Code Format view displays the standard Point Code Formats defined in the relevant specifications. The default Point Code Formats included in the Signaling Advisor are: ! ! ! ! ! ! ! 14 bit CCITT 14 bit CCITT (Q.708 Int) 14 bit CCITT (Q.708 SANC) 14 bit German 14 bit Korean 16 bit Japanese 24 bit ANSI
These default Point Code Formats cannot be changed or deleted. You can add other Point Code Formats. The Point Code Format view is or by selecting View menu displayed from Configuration by clicking Point Code Format View.
Configuration's Point Code Format view.
This view configures the Point Code Formats to be used. It defines how the Point Code is split into its component fields - how many fields, how many bits in each field and the display order. You can edit additional Point Code Formats by right-clicking on the field you wish to edit. A popup menu will appear displaying the available options. You can define your own Point Code Formats that can be associated with a Protocol Stack.
How to Use Point Code Formats

Point Code Formats define how the Point Code bit structure will be decoded in Monitor's Traffic Overview, Call Trace and Statistics views.
Setting the correct Point Code Format ensures that the Point Code information is displayed in the format used by your network.
Add a Point Code Format

1. 2. 3. Click Click to display the Point Code Format view. to display the Point Code Format dialog box.
Enter the Point Code Format Name, the Field Name and Bits and the Separator character.
A partially complete Point Code Format dialog box..
2. 3. 4. 5.
Click OK. Click to display the Protocol Stack view. Right-click on the Protocol Stack view to display the popup menu. Select the Stack Properties option. Select the Point Code Format from the drop-down list. Click OK.
Information You can only change a Protocol Stack's Point Code Format to another format of the same length (max length 32 bits). You make this change in Protocol Stack view.
Edit a Point Code Format

1. 2. 3. Click to display the Point Code Format view. Right-click on the Point Code you want to edit to display the popup menu. Select Properties from the popup menu. Enter the Point Code Format Name, the Field Name and Bits and the Separator character. Click OK.
Information Default Point Code Formats cannot be edited.
Capturing Traffic
Learn about Capturing

Once the Signaling Advisor is connected to your network and configured you only have to click the record button in Monitor to capture the signaling traffic on your network. When Monitoring The Signaling Advisor will capture everything from connected links unless you set up restrictions. The Signaling Advisor can start and stop capturing automatically based on the Trigger settings you set. You can also restrict which events and messages are captured by setting logging filters. Triggers and Logging Filters are set up in Measurement Setup view. Each setup is stored in the log file (*.tol) along with the captured network traffic. The Measurement Setup information can also be exported and used again for future captures. Call Trace and Statistics Filters are treated as logging filters when set up for a Real Time mode capture. They are 'OR'ed with any logging filter to ensure that all the data for the Call Trace or Statistics Filter is captured, regardless of the logging filter settings. The filters are reapplied in Post Capture mode to process the messages for the Call Trace and Statistics views. When Emulating If you have purchased EmuLite, any suites and sequences selected in the Test Manager or Conformance Test Manager will be run when clicked. is
Triggers and Log Filters will be disabled when EmuLite is running.
How to Capture Traffic

You can quickly capture all the signaling traffic on the configured links by following the Quick Capture instructions. You can add and save Filters, Call Traces and Statistics views in Post Capture mode.
Capturing Traffic 59
To restrict which messages are captured go to Monitor's Measurement Setup view ( ) where you can define Triggers, Logging Filters, Call Trace Filters and Statistics Filters.
Quick Capture
1. 2. 3. After connecting and configuring click Click to go to Monitor.
to start capturing using the default settings.
when you want to stop capturing from your network. Click Then click to save.
Caution ! Do not pause for too long whilst capturing at high data rates as you may lose data. The green area of the Free Buffers indicator at the bottom right of the windows ( ) will reduce as the buffer space is used. When buffer space is almost full the green band will change to red ( ). You must resume the capture to avoid loosing data. A band will indicate ). if data has been lost ( If you have purchased EmuLite, any suites and sequences selected in the Test Manager will be run when Information ! ! To pause traffic press or [Spacebar]. Messages will continue to be recorded, only the views are paused. To resume processing captured messages after pausing press ! ! . is clicked.
is disabled when the Signaling Advisor is in Post Capture mode. The default configuration settings do not capture short messages.
Learn about Measurements

Measurement Setup view graphically represents all the applications and views being used in Real Time mode ( Post Capture mode ( ).
Measurement Setup View.
), or by the selected log file in
The Measurement Setup view is displayed from Monitor by clicking or by selecting View menu
Measurement Setup view shows the flow of messages:

60 Capturing Traffic Signaling Advisor User's Manual
! !
Black Path shows messages and events that have been saved into the log file and are available to be analyzed. Blue Path represents the processing performed on the signaling traffic. This drives the Call Trace and Statistics views.
Real Time Measurement Setup

In Real Time mode, the Measurement Setup view shows the elements that have been set up for capturing from your network. To put the in Monitor. To add Signaling Advisor into Real Time mode click Call Trace, Statistics and additional Traffic Overviews and set up any associated filters, click the button and select the relevant options.
Monitor's Measurement Setup view in Real Time mode showing Call Trace and Statistics view. If emulating an additional EmuLite route shows that all emulation traffic is displayed in the EmuLite view.
In Real Time Measurement Setup you can: ! ! ! ! ! Go to Configuration and edit the settings. Define which messages and events should be captured. Define how the data should be analyzed and viewed. Copy and paste Trigger and Filter settings. Import an existing measurement file (containing configuration and measurement settings).
Measurement Setup view is the only view where you can define which messages and events should be captured. Triggers and all the filters to the left of the Log File icon define which messages are captured. In Post Capture mode, Call Trace and Statistics Filters are reapplied to process the views.
Information To improve capture performance close unnecessary views, especially Traffic Overviews. These can be added later during Post Capture analysis.
Post Capture Measurement Setup

In Post Capture mode, the settings used during the file's capture are shown in the Capture Details box. These settings cannot be changed in Post Capture. To put the Signaling Advisor into Post Capture mode click in Monitor.
Monitor's Measurement Setup view in Post Capture mode.
In Post Capture Measurement Setup you can: ! ! ! ! ! ! View the Configuration settings used during the capture. Edit part of the Configuration (you cannot add links or edit hardware settings). View any triggers and logging filters. Add new Call Trace, Statistics and Traffic Overviews. Edit any Call Trace and Statistics configurations and filters. Add view filters to the Traffic Overviews.
How to Use Measurement Files

Measurements contain all the information used to capture your network traffic. You can export to *.msf files. Once exported, you can import the file and reuse, or edit, the settings (filters, triggers, call traces, tabular statistics and statistics) in a new Real Time measurement. Measurement details can also be imported from a log file (*.tol). When you import measurements the triggers and filter (logging and view, and so on) are imported into the current Real Time setup. You
62 Capturing Traffic Signaling Advisor User's Manual
then choose whether to use your current Real Time hardware configuration setting or use the settings from an existing configuration file.
Export a measurement
1. 2. Select File menu
Export Setup.
Enter the filename you want to use and click OK. You can use this measurement in another Real Time capture by importing it.
Import a measurement
1. If the Signaling Advisor is not in Real Time mode, click Monitor's ( 2. 3. ) Real Time button ( ). Select File menu Import Setup to display the Select Setup to Import dialog box. Select the measurement setup file (*.msf) you want to use for the current Real Time capture and click Open. The Setup Import dialog box will be displayed. You must choose whether to use the existing Real Time configuration or to use an existing configuration file. Select Yes to use the current Real Time configuration, OR No to select another configuration. The Select configuration for dialog will be displayed. Select the configuration file from the list and click Open.
4.
The current Measurement Setup and Configuration, where applicable, will be replaced. Information You cannot import measurements in Post Capture mode.
Import a measurement from a log file

1. If the Signaling Advisor is not in Real Time mode, click Monitor's ( 2. 3. 4. 5. ) Real Time button ( ). Select File menu Import Setup to display the Select Setup to Import dialog box. to display the higher level directories and double-click Click the Capture Data directory. Change the File type to Tol Files (*.tol) to display the log files. Select the file you want to import the measurement setup from and click Open. The Setup Import dialog box will be displayed.
6.
You must choose whether to use the existing Real Time configuration or to use an existing configuration file. Select Yes to use the current Real Time configuration, OR No to select another configuration. The Select configuration for dialog will be displayed. Select the configuration file from the list and click Open.
The current Measurement Setup and Configuration, where applicable, will be replaced. Information You cannot import measurements in Post Capture mode.
Learn about Triggers and Filters

Triggers and Filters are used to control which events and messages are captured and displayed. You can have any mixture of triggers and filters. The defaults are set to capture and display everything when clicked. There are two parts to triggers and filters: is
Criteria define what happens when the conditions are met. Criteria
are set in the upper half of the dialog box. Multiple triggers or filters are 'OR'ed, that is, ALL CONDITIONS in ALL TABS for ANY ONE (trigger or filter) will activate the trigger or pass through the filter.
Conditions define the event or message that will activate the trigger or pass through the filter. Conditions are set up in the lower half of the dialog box.
In a single trigger or filter the conditions are 'AND'ed, that is, ALL CONDITIONS in ALL TABS must be met to activate the trigger or pass through the filter.
Criteria
Trigger and Filter Criteria are defined in the top half of Trigger and Filter Editors. They define what action is to be taken when the Trigger or Filter Conditions are met. Start Triggers automatically starts capturing when the Signaling Advisor detects an event or message that meets the conditions. Using Criteria, you can capture before the event or message that activates the trigger. You can capture a number of messages or for a period of time before the Start Trigger. Stop Triggers automatically stops capturing when the Signaling Advisor detects an event or message that meets the conditions. Using Criteria, you can capture after the event or message that activates the
64 Capturing Traffic
trigger. You can capture a number of messages or for a period of time after the Stop Trigger. Logging Filters restricts which links, events and messages are captured. Call Trace Filters filters for the messages required by Call Trace. In Real Time the Call Trace Filters will be 'OR'ed with the Logging Filter. In Post Capture mode, the filter will be reapplied to process the messages for the Call Trace view. Statistics Filters filters for the messages required by Statistics. In Real Time the Statistics Filters will be 'OR'ed with the Logging Filter. In Post Capture mode, the filter will be reapplied to process the messages for the Statistics view. View Filters restricts which captured events and messages are displayed in Traffic Overview. Find finds events and messages in Traffic Overview. Once the filter conditions are defined you can Find Next and Find Previous to highlight the next event or message that meets the conditions.
Conditions
Trigger and Filter Conditions are defined in the lower half of Trigger and Filter Editors. They define the events and messages that will activate the Trigger or Filter. There are several types of Trigger and Filter Conditions: Event defines Received Messages with good or bad CRCs (Cyclic Redundancy Checks), transmitted messages or truncated data, and so on. Message Match defines messages based on Protocol Stacks and Protocols, for example, Message Types, Calling Party Number, Destination Point Codes, and so on. Time defines messages based on the Time they were received. Linksets defines messages based on individual links and linksets. Message Validity (Post Capture mode only) defines messages based on the associated Protocol Stack. You can use this filter to highlight where changes may be required in the Protocol Stack. Trigger Counts (Real Time Triggers only) defines the occurrence of the trigger conditions that will activate the trigger, for example, if you set the trigger to be activated on the fourth occurrence, the first three times will be ignored.
Event Types
Event Types are displayed in the Event tab. The events are: Buffer Management event Message dropped indicates that the capture buffer was unable to store all the available messages and that some messages were lost.
Received Message (abort) indicates that an Rx Abort (seven consecutive 1s) message was received. Received Message (bad CRC) indicates that a message was received that had a bad CRC. Received Message (good CRC) indicates that a message was received that had a good CRC. Received Message (raw data) reserved for future Signaling Advisor use. Received Message (receive overflow) indicates the Signaling Advisor was unable to capture all the available messages and that some messages were lost. Received Message (truncated data with bad CRC) indicates that a message was received with a bad CRC where the last byte did not contain a full 8 bits of user data. Received Message (truncated data with good CRC) indicates that a message was received with a good CRC where the last byte did not contain a full 8 bits of user data. Transmitted Message indicates messages transmitted by the Signaling Advisor.
How to Use Triggers and Filters

Triggers and Filters restrict which events and messages are processed. In Monitor's Measurement Setup view: ! ! Set up Triggers to automatically start and stop capturing Real Time events and messages from your network. Set up Logging Filters to restricts which events and messages are captured. Set up View Filters to restrict which events and messages are displayed in the current Traffic Overview. Set up Find Filters to highlight defined events and messages.
In Monitor's Traffic Overview; ! !
Create a Start or Stop Trigger (Monitor ONLY)

Triggers automatically start or stop the capture of network traffic when an event which meets the trigger is detected. You can have no triggers, a start trigger, a stop trigger or both start and stop triggers. Trigger Criteria 1. If the Signaling Advisor is not in Real Time mode, click ) Real Time button ( Monitor's ( Monitors Measurement Setup view. ). Click to open
2.
Double-click
to display the Trigger Editor.
Monitor Measurement Setup view's Trigger Editor.
3. 4.
Click either the Start or Stop Trigger panel to select it and then click New button to create a new trigger. (OPTIONAL) Set up options in the Criteria panel. If you do not set criteria the capture session will start and /or stop at the message that activates the trigger(s).
(OPTIONAL) Start Criteria You can capture for a specified time, or specific number of messages before the event or message that activates the Start Trigger. You can also set the maximum capture duration if there is no Stop Trigger or its conditions have not been met by the defined duration. (OPTIONAL) Stop Criteria You can capture for a specified time or specific number of messages after the event or message that activates the Stop Trigger. 5. 6. Set up the Trigger Conditions in the tabs in the lower half of the Trigger Editor. Click OK to apply the trigger(s).
Information ! Disable a trigger, without losing the settings, by clicking on the tick ( ). Only triggers which are ticked will be used during the capture. Triggers are only available when monitoring in Real Time mode. Triggers are disabled on emulation links. Message conditions (in the lower half of the Trigger and Filter Editors) are set up the same way in Start Triggers, Stop Triggers, Logging Filters, View Filters and Find Message.
! !
Create a Logging Filter

Logging Filters restrict which events and messages are captured. Only events and messages which pass through the logging filter are captured. Event and Messages on emulation links will not be filtered. 1. If the Signaling Advisor is not in Real Time mode, click ) Real Time button ( Monitor's ( Monitors Measurement Setup view. ). Click to open
2.
Double-click
to display the Filter Editor.
Monitor Measurement Setup view's Logging Filter Editor.
3. 4. 5.
Click New to create a new filter. Set up the Filter Conditions in the tabs in the lower half of the Filter Editor. Click OK to apply the filter.
Information ! ! Logging Filters are disabled on emulation links. Call Trace or Statistics Filters will be treated as logging filters when capturing (in Real Time mode) and are reapplied in Post Capture mode to process the Call Trace or Statistics view. Logging Filter criteria cannot be changed in Post Capture mode.
Event Filter Set up

1. 2. 3. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Event tab. Click on the events to select (or deselect) those you want to include.
Monitor's View Filter on Events.
4.
Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Information A tick ( ) indicates that messages containing the event will pass through the filter.
Message Match Filter Set up

1. 2. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab.
3.
Double-click the Protocol. The list will update to show the fields in the selected protocol.
Monitor's View Filter on Message Match.
4. 5. 6.
Click on the Field. The Value criteria will be displayed opposite the field list. Select the value from the list. Or, click Add Value to display a dialog box, enter the new value in the dialog box and click OK. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Information A tick ( ) indicates that messages containing the event will pass through the filter.
Remove a Protocol's Filter Settings from the Filter

Right-click on the Protocol and select Deselect Presence of Protocol from the popup menu.
Trigger and Filter Editor Deselect Protocol Option.
Invalid Fields Filter Set up

1. 2. 3. 4. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Protocol. The list will update to show the fields in the selected protocol. Click the field you want to filter on. The Value criteria will be displayed opposite the field list. Click Select All and the Not Match option. This will filter for messages containing this field with any value other than a valid one.
Invalid Field filter setting.
5.
Protocol Presence Filter Set up

1. 2. 3. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Right-click the Protocol to display the popup menu and select the Select Presence of Protocol option. This will filter for any message using the selected Protocol. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
4.
Field Presence Filter Set up

1. 2. 3. 4. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Protocol to display the Fields. This will filter for any message containing the selected Field. Right-click the Field to display the popup menu and select the Select Presence of Field option. Or, select Any Value on the opposite panel.
5.
Message Type Filter Set up

1. 2. 3. 4. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Protocol. The list will update to show the fields in the selected protocol. Click the MT field. The Value criteria will be displayed opposite the panel. Note - not all protocols contain the Message Type field. Select the value from the list. Or, click Add Value to display a dialog box, enter the new value in the dialog box and click OK.
5.
Monitor's View Filter on Message Type.
6.
Not Match Filter Set up

1. 2. 3. 4. 5. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Protocol. The list will update to show the fields in the selected protocol. Click the Field. The Value criteria will be displayed opposite the field list. Select the value from the list. Or, click Add Value to display a dialog box, enter the new value in the dialog box and click OK.
6. 7.
Click Not Match. This will filter for any value other than those entered. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Point Code Filter Set up

1. 2. 3. 4. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Level 3 Protocol and select the field, for example, OPC or DPC. If Point Code Mappings have been set up they will be listed in the opposite field list. Select each mapping you want to filter on. If no Point Code Mappings are in use, or if the required Point Code is not listed, you must enter Point Code values. Click Add Value to display the dialog box, enter the values and click OK. A tick ( ) indicates that the Point Code is included in the filter. 5. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Bit Mask Filter Set up

1. 2. 3. 4. 5. 6. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Match tab. Double-click the Protocol. The list will update to show the fields in the selected protocol. Click the Field. The Value criteria will be displayed opposite the field list. Click Add Value. Enter the Bit Value (5), '&' and the Bit Mask (7) in decimal, for example, 5&7. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Time Filter Set up

1. 2. 3. 4. 5. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Time tab. Click on the time filter type you want to apply. Enter the date and time details required. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Information The Time Filter set up options change depending on the timestamp format being used in Monitor.
Linkset Filter Set up

1. 2. 3. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Linksets tab. Click on the links and linksets to select (and deselect) those you want to include in your filter. A tick ( ) indicates that messages in that link/linkset will pass through the filter. Selecting a linkset will select all the links in the linkset. Similarly deselecting a linkset will deselect all the links in the linkset. 4. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Trigger Counts Set up

You can set up the trigger to be ignored until the conditions have been met a defined number of times. Set the occurrence you want to activate the trigger. The default is to activate the trigger on the first occurrence. 1. 2. 3. 4. Click New to create a new trigger. Or edit an existing trigger by adding 'AND' criteria to it. Click the Trigger Counts tab. Enter the number of the start trigger occurrence that you want to actually start capturing messages. Either click another tab to add 'AND' criteria to the trigger or click OK to apply the trigger.
Information ! ! Available only in Trigger Editor. Triggers available only in Real Time mode.
Message Validity Filter Set up

1. 2. 3. 4. Click New to create a new filter. Or edit an existing filter by adding 'AND' criteria to it. Click the Message Validity tab. Click on the filter option you want to use. Either click another tab to add 'AND' criteria to the filter or click OK to apply the filter.
Information Available only in Post Capture mode ( )
Copy a Filter or Trigger

1. 2. From Monitor click to open Measurement Setup view.
Right-click the icon for the trigger or filter you want to copy and select Copy.
Monitor Measurement Setup's Copy Filter option.
3.
Right-click the trigger or filter you want to overwrite and select Paste.
Monitor Measurement Setup's Paste Filter option.
Information Triggers can be copied only to triggers and filters can be copied only to filters.
Export a Trigger or Filter

1. 2. From either the Trigger or Filter Editor click Export to open the Export dialog box. If more than one trigger of filter exists select the filters or triggers to be exported. Click OK. If only one exists go to Step 3. Type the filename. Click Save.
3.
Import a Trigger or Filter

1. 2. From either the Trigger or Filter Editor click Import to open the Import dialog box. Select the file you want to import and click OK.
Only Filter files can be imported to the Filter Editor. Similarly, Trigger files can only be imported into the Trigger Editor.
Disable a Trigger or Filter

From either the Trigger or Filter Editor click the tick box next to the trigger or filter. A tick ( ) indicates that the trigger or filter is enabled. Click the tick box to remove the tick and disable the trigger or filter.
Remove a Trigger or Filter

1. 2. Click the trigger or filter to be deleted. Click Remove.
Information ! ! Disable triggers or filters if you want to remove them temporarily. Export a trigger or filter if you want to save it.
Rename a Trigger or Filter

1. 2. Double-click the trigger or filter to display the dialog box. Type the new name. Click OK.
Isolating Calls
Learn About Isolating Calls

Call Trace correlates calls by associating a message with the others in the call. Each Call Trace profile supplied with the Signaling Advisor contains a configuration for a particular Call Trace. You select a profile and then define the calls you want to isolate. Use the Call Warnings and Call Phase Colors tabs to define what colors are used to indicate particular circumstances. Once a Call Trace view has been created you can jump from a message in Traffic Overview directly to the associated call in Call Trace view by right-clicking the message and selecting Select Call.
Monitor's Call Trace View.
Call Traces are created and displayed in Monitor. Clicking will display the Call Trace Configuration dialog box. Select a profile and then click OK to create a Call Trace view using the profile's default settings. You can configure the call trace and select logging parameters from the other tabs. Calls As the call progresses colored blocks are added to the Phase Graphics column to the right of the view. The blocks are added from left to right so the furthest right block indicates the current phase of the call. Columns The columns available in Call Trace view vary depending on the Call Trace Profile selected. Right-clicking on the Call Trace view will display a popup menu. You can select the columns you want to display by clicking on them.
Signaling Advisor User's Manual Isolating Calls 77
You can add other columns to the list by selecting Column Setup from the popup menu. A tick ( ) indicates that the column is displayed. Some of the commonly used columns are described below: Call ID Each call is represented by a row in the Call Trace view and is given a sequential identification number. The details about the call are shown across the columns. Duration Shows the duration of the call (once the call is set up). If you define Call Warnings the background to this column will change to indicate the warning status (call duration longer or shorter than defined). The criteria for calculating duration depends on the protocol being used. The duration format is hh:mm:ss. Call Status Indicates whether the call is Active or Terminated. If Release Cause Warnings have been set up, the warning color will be displayed in the Status column for the terminated calls that meet the Release Cause criteria. Phase Graphics Call Phases let you track the progress of each call from beginning to end. As messages are received (or transmitted) the relevant colored block is added to the Call Trace view. Hovering the mouse pointer on the phase graphics displays a ToolTip that lists the messages received (or transmitted) and their direction. The phase being hovered over is shown in bold text. You can set the colors used to define each phase of a call. The available phases depend on the profile selected. Some significant phases are identified by icons on top of the configured phase color. Call Counts The total number of calls and how many are Active or Terminated is shown in the Summary View. You can display the call counts by rightclicking on the Call Trace view and selecting Summary View. Call Warnings You can set the colors used to indicate particular circumstances. The Status columns background color changes when calls are Active or Terminated. If a call is terminated for one of the selected Release Causes then the Release Cause background color is used in the Status column. Grouping the Messages for a Call Double-clicking a call uses Group to display all the messages that make up that call. These messages are displayed in Traffic Overview. Information ! Click [F1] to display this help topic for Call Trace view. In any Signaling Advisor view, click [F1] to display the current view's help topic. Click on a Call Trace view to show the Call Trace menu on Monitor's menu bar.
78 Isolating Calls
Call Sequence Information is stored in a log file. You can remove this information by Resetting the Sequence Information. The next time a Call Trace is run on the log file the Call Sequence Information will be recreated. You can trace GPRS sessions on the Gb interface (SGSN BSS) using the Call Trace functionality. Session Trace profiles are available when the GPRS Gb protocol stack is in use. When grouping the messages for a call the most recently used Traffic Overview is used when multiple Traffic Overviews of the same log file are being displayed. If some messages have been filtered out of the Traffic Overview you may wish to disable any filters which have been applied or change the Display Level Settings. When running Call Trace Configurations during Real Time captures you can close the Traffic Overview. This will improve the performance of the Signaling Advisor. All messages are still captured and the Traffic Overview (and other views) can be added in Post Capture mode.
How to Isolate Calls

Call Trace lets you quickly isolate a wide variety of calls based on the criteria you define, for example unsuccessful calls, particular telephone number(s), release causes and so on. Once the calls are isolated you can use the 'Group' function to display the messages associated with the call and then decode them to get to the route of a problem. You can also jump from a message in Traffic Overview directly to the associated call in Call Trace view by rightclicking the message and selecting Select Call. Information You can trace GPRS sessions on the Gb interface (SGSN - BSS) using the Call Trace functionality. Session Trace profiles are available when the GPRS Gb protocol stack is in use.
Create a Call Trace View

Call Trace links messages into calls and then displays the calls that contain the criteria you define. 1. 2. Click to open the Call Trace Configuration dialog box.
Select the Profile from the drop-down list.
Isolating Calls 79
Monitor's Call Trace Configuration dialog box.
3. 4.
In the Select Call Type panel define the type of calls. (OPTIONAL) In the Select Criterion panel select the options you want to use. (OPTIONAL) The Select Values panel will update to show the values for the selected criterion. The Select Values panel will differ depending on the type of value required. Select each option you want to include. You can click Add Value to add your own values.
5. 6.
Repeat Step 4 to add AND criteria to the Call Trace criteria. (OPTIONAL) Click OK to complete the Call Trace setup.
Information ! You can set Call Warnings, the Call Phase colors and whether the Call Trace data should be logged to a Comma Separated Value file. You cannot choose another profile once you have selected a profile and clicked OK. To use a different profile you must create a new Call Trace view.
Trace Unsuccessful Calls

1. 2. Click to open the Call Trace Configuration dialog box. Select the Profile from the drop-down list. The Select Criterion panel will update to show the options for the selected profile.
80 Isolating Calls
3. 4.
In the Call Selection tab select Unsuccessful from the Select Call Type panel. In the Select Criterion panel select the options. (OPTIONAL) The Select Values panel will update to show the values for the selected criterion. The Select Values panel will differ depending on the type of value required. Click to select a listed option or click Add Value to add a value. A tick ( ) indicates each selected option.
5.
Repeat Step 4 to add AND criteria to the Call Trace criteria. (OPTIONAL) Click OK.
Trace a Particular Telephone Number

1. 2. Click to open the Call Trace Configuration dialog box. Select the Profile from the drop-down list. The Select Criterion panel will update to show the options for the selected profile. In the Call Selection tab select Called Party Number (for example) from the Select Criterion panel. The Select Values panel will update to show the values for the selected criterion. Click Add Value to add the telephone number.
3. 4.
Call Trace's Telephone Number entry.
5.
Click OK.
Information You can use wildcards to indicate any number of number completion. Wildcard definitions are given in Add Value dialog boxes.
Edit a Call Trace Configuration

1. In Monitor, right-click on the Call Trace view and select Configure to display the Call Trace Configuration dialog box.
Isolating Calls 81
2.
Make the changes to the configuration. Click OK.
Information ! ! To edit a Real Time mode Call Trace configuration click stop the capture before you edit the configuration. You cannot choose another profile once you have selected a profile and clicked OK. To use a different profile you must create a new Call Trace view. You can also edit the Call Trace Configuration from Measurement Setup view by double-clicking the Call Trace box. to
Display the Messages in a Traced Call

Double-click the call in the Call Trace view. The messages for that call will be grouped and displayed in the Traffic Overview. Information Once grouped you can copy all the messages in Traffic Overview and paste them into EmuLite.
Change Call Trace View Colors

1. 2. Right-click on the Call Trace view to display the popup menu. Select Configure. Select either Call Warnings or Call Phase Color tabs.
Monitor's Call Trace Call Warning tab.
3. 4.
Click the color and select the new color from the palette. Repeat from Step 2 for each color you want to change. Click
OK.
82 Isolating Calls
Set Call Warnings

1. In Monitor, right-click on the Call Trace view to display the popup menu and select Configure to display the Call Trace Configuration dialog box. Select the Call Warnings tab. You can set up all or some of the options. Call Status Colors Select the colors to indicate Active or Terminated calls. These colors are used by the Status column. Call Duration Colors Click the Under and/or Over Duration boxes to activate Call Duration Warnings. Select the color to be used for each and enter the duration. When a call is shorter than the Under Duration time the Duration column background in Call Trace view will display the selected color. The same applies for the Over Duration settings. Release Cause Colors Click the Release Cause box to activate the Release Cause Warnings. Select the color and Release Causes. The selected color will be used as the background color for the Status column when the call's Release Cause matches one of those selected. 4. Click OK.
2. 3.
Display Call Trace Summary

Right-click on the Call Trace view and select Summary View from the popup menu.
Log Call Trace Data to a File

1. 2. 3. 4. 5. 6. 7. In Monitor, right-click on the Call Trace view and select Configure to display the Call Trace Configuration dialog box. Click the Logging tab. Click Enable Call Trace CSV Logging to select it and enable the logging options. Click Browse, and either select or enter the filename. Click the Output Summary Information to log the details displayed in the Call Trace Summary view. Select how columns should be logged. Select how call phase descriptions should be logged.
Isolating Calls 83
Monitor's Call Trace Logging tab.
8.
Click OK.
Remove a Call Trace

! ! From Monitor click the remove it. on the CALL TRACE window to
From Measurement Setup right-click the Call Trace button
and select Delete from the popup menu.
84 Isolating Calls
Gathering Statistics
Learn about Graphical Statistics

You can analyze your network traffic to highlight important trends and information. You can display the statistical information graphically ( ) or in a tabular format ( )
Time Series Statistics view. In this example the Bar Labels have been switched off.
Each Statistics Profile supplied with the Signaling Advisor contains a configuration for a particular statistics calculation. The available profiles are listed in the Profiles tab when a protocol is selected. You select a profile and define how the data is to be displayed. You can also display the values in a tabular view and log the statistics data to a file. Statistics are gathered and displayed within Monitor. Clicking or selecting View menu New Statistics View will display the Statistics Configuration dialog box. If you select the profile and then click OK the profile's default graph settings will be used. Any changes you make to the profile will be retained as its default settings. You can configure the graph in detail and select logging parameters from the other tabs. Statistics on messages You can collect statistics based on messages (received and transmitted). Message-based profiles are indicated by the message icon ( ). Statistics on calls You can collect statistics based on calls. Call-based profiles are indicated by the call icon ( ). These statistics profiles use the Call Trace function to correlate the messages into calls. The relevant Call Trace tabs are automatically added to the Statistics Configuration dialog box allowing you to set up all the parameters from the one dialog box.
Signaling Advisor User's Manual Gathering Statistics 85
Statistics on GSM Base Station Optimization You can display the statistics for GSM Base Station Optimization. GSM Base Station Optimization statistics are indicated by the aerial icon ( ). Statistics Options The selected profile for an existing Statistics view cannot be changed. When creating a statistics view the settings are stored and will be the default settings the next time the profile is used. These default settings are not changed when the view is edited.
How to Gather Graphical Statistics

Statistics show trends and the number of instances criteria have been detected. You use Statistics to display trends in messages or calls, highlight traffic peaks, and so on, over time or over links.
Create a Statistics View

1. Click to open the Statistics Configuration dialog box.
Monitor's Statistics Configuration dialog box Profiles tab.
2.
Select the required protocol from the drop-down list. The Protocol Stack view defines which protocols are listed. The selected protocol defines which profiles are listed in the Available Profiles panel. Select the profile you wish to use. The profile types are: Statistics on messages. Statistics on calls. Statistics on GSM Base Station Optimistation A tick ( ) will appear next to the profile name you select. If you want to use the default settings for the profile click OK to complete the configuration.
3.
86 Gathering Statistics
4. 5.
Configure the graph and logging options in their appropriate tabs (OPTIONAL). Click OK to close the Statistics Configuration dialog box.
Information ! The default settings are saved when a new Statistics view is created. The default settings will not be changed when the Statistics Configuration is edited. In Monitors Measurement Setup view you can create a Logging Filter for Statistics.
Edit a Statistics Configuration

1. 2. In Monitor right-click the Statistics view and select Configure to display the Statistics Configuration dialog box. Make the changes to the Statistics Options and click OK to close the Statistics Configuration dialog box.
Monitor's Statistics Configuration dialog box Graph tab.
Information ! To edit a Statistics configuration click to stop the capture (Real Time mode). Some options can be changed without clicking Stop. Right-click on the Statistics view to display and select these options. You cannot change the profile used by a Statistics Configuration. To use a different profile you must create a new Statistics view.
Gathering Statistics 87
Open the Statistics Configuration dialog box from
Measurement Set up view by double-clicking
Statistics Options
In Monitor right-click the Statistics view or in Measurement Setup view
double-click
to display the Statistics Configuration dialog box.
If a call-based profile is selected the Call Trace tabs will be displayed in addition to the Statistics tabs listed below.
Profile Tab
Lists the available profiles based on the selected protocol. There are several statistics profile types available; message, call and link. The profile cannot be changed once the Statistics View has been created.
Graph Tab
Graph Layout ! ! Graph Type shows the available graph types. Click the graph type to select it. Graph Title is shown at the top of the graph. The title in the text box opposite is displayed when the Graph Title box is ticked ( ). Value Title displays the title for the y-axis. The title in the text box below is displayed when the Value Title box is ticked ( ). Bar Labels displays a label on each bar on the graph. Data labels will not be displayed if there is not enough graph space. Threshold Colors shows the colors used to indicate when threshold values have been reached. The left column color indicates that the lower threshold has not been exceeded, the middle column color indicates the upper threshold has not been exceeded and the right column color indicates the upper threshold has been exceeded. When using radar graphs the entire graph changes color when a threshold is exceeded. Upper Threshold checks each field's value against the upper threshold value and changes the graph color to indicate that a threshold value has been exceeded. Threshold values are shown and edited in the Thresholds panel. Lower Threshold checks each field's value against the lower threshold value and changes the graph color to indicate that a
! !
threshold value has been exceeded. Threshold values are shown and edited in the Thresholds panel. ! ! Axis Labels displays a label for each bar on the x-axis. Data Title displays the title for the x-axis. The title in the text box opposite is displayed when the Data Title box is ticked ( ). Threshold List sets the threshold values for each field. Values can be edited by clicking and typing the new value. If the lower threshold is greater than or equal to the upper threshold the field will be highlighted in yellow. Hide Zero Values hides fields that have a value of zero. Selecting this options improves the readability of the graph. Show as % displays the graph values as a percentage of the sum of all fields. Show Tabular View displays a table of results beside the graph. View Refresh Period sets how often the view is updated with the latest information. In Real Time mode, this refresh may be less frequent if a large amount of data is being captured. Timeseries enables the Timeseries options listed below. Time Series Update Period sets the time period covered by each graph. Number of Visible Graphs sets how many graphs are displayed at once. Display Date with the Timestamp shows the date together with the timestamp on the graph. The time is always shown.
Threshold List !
Data Display ! ! ! !
Timeseries ! ! ! !
Logging Tab
! Enable Statistics CSV Logging activates the logging of statistics data to a comma separated value file. This lets you import the data into spreadsheets and databases. Statistics Log File displays the filename being used for the statistics data. Click the Browse button to edit or select the filename. Log to file every sets how often data should be logged to the CSV file. If using a Time Series the Timeseries Update Period will be used as the Logging Period.
Information You must stop ( Series. Click ) a Real Time capture to change to (or from) Time to start capturing again.
Measure Statistics over Time Periods

Timeseries can be used to identify trends over time periods on your network. For example, you could gather the statistics for the number of calls over 5 minute periods. The Statistics graph will display a new set of bars for each 5 minute period and you can easily see when the busiest periods occurred. 1. 2. Click to create a new Statistics view.
Select the required protocol from the drop-down list. The protocols displayed in the Protocol Stack view define which profiles are listed. Select the profile you wish to use. A tick ( ) will appear next to the profile name you select. If you want to use the default settings for the profile click OK to complete the configuration. Click the Graph tab to display the graph options. Click the Timeseries check box to enable the Timeseries options. Enter the values to configure the Timeseries graph display. Click OK to close the Statistics Configuration dialog box.
3.
4. 5.
6.
Information
Configure
To edit an existing Statistics view right-click the view and select to display the Statistics Configuration dialog box.
Set up Graph Thresholds

1. 2. 3. 4. In Monitor right-click the Statistics view and select Configure. Click the Upper Threshold and/or Lower Threshold check box. A tick ( ) indicates that the threshold settings will be used. Select the threshold colors. On the threshold value list change the threshold values. Select each value and type the new threshold. Click OK.
Information ! If any threshold value is illegal (for example, the upper threshold value is less than the lower threshold value) the threshold field will be highlighted in the list.
The default settings are saved when a new Statistics view is created. The default settings will not be changed when the Statistics Configuration is edited. To edit a Real Time Statistics configuration click capture before you edit the configuration. to stop the
! !
You cannot change the profile used by a Statistics view. To use a different profile you must create a new Statistics view.
Show the Last Message Counted

Double-click the statistics bar and the last message which updated that bar will be highlighted in the Traffic Overview. If a call-based profile has been used the messages for the last call will be grouped and shown in Traffic Overview. Information When highlighting the last message to be counted in a bar (or in a section) the most recently selected Traffic Overview is used when multiple Traffic Overviews of the same log file are being displayed. If that message is filtered out of the Traffic Overview you should disable any filters which have been applied or change the Display Level Settings.
Show the Graph Values

Right-click the Statistics view and select Tabular View from the popup menu. Information Hovering the mouse pointer over a graph field will display its details.
Log Statistics Data to a File

1. 2. 3. 4. 5. In Monitor right-click the Statistics view and select Configure. Click the Logging tab. Click Enable Statistics CSV Logging to select it and enable the logging options. Click Browse and either select or enter the filename. Enter the logging rate. Click OK.
Information When logging Time Series graphs the Time Series Update Period is used as the logging rate.
Print Statistics
1. Right-click the Statistics view and select Print from the popup menu.
2.
Click OK to print.
Information Right-click on the Tabular view to print the detailed statistics.
Remove a Statistics View

! ! From Monitor click the remove it. on the STATISTICS window to
From Measurement Setup right-click on the Statistics button
Learn about Tabular Statistics

You can analyze your network traffic to highlight important trends and information. You can display the statistical information graphically ( ) or in a tabular format ( ).
The Tabular Statistics view displays the counts of the parameters relating to the Tabular Statistics configuration. For example for ISUP calls the first level of statistics counts the number of calls between each OPC and DPC. Once the statistics have been gathered you can see the next level statistics. So in the example above, you could then look at the breakdown of CICs between your chosen OPC and DPC.
How to Gather Tabular Statistics

Call statistics are gathered and displayed by Tabular Statistics. Tabular Statistics displays the statistics of the calls (or GPRS sessions), for example, the number of calls between the point codes on the network. You could then look at the statistics for the traffic between two particular point codes by right-clicking the window and selecting Next Level.
Create a Tabular Statistics View

1. 2. Click to open the Tabular Statistics Configuration dialog box. Select the Profile from the drop-down list.
Monitor's Tabular Statistics Configuration dialog box.
3.
In the Select Criterion panel select the options you want to use. (OPTIONAL) The Select Values panel will update to show the values for the selected criterion. The Select Values panel will differ depending on the type of value required. Select each option you want to include. You can click Add Value to add your own values.
4. 5.
Repeat Step 4 to add AND criteria to the Tabular Statistics criteria. (OPTIONAL) Click OK to complete the Tabular Statistics setup.
Information You cannot choose another profile once you have selected a profile and clicked OK. To use a different profile you must create a new Tabular Statistics view.
Edit a Tabular Statistics Configuration

1. In Monitor, right-click on the Tabular Statistics view and select Configure to display the Tabular Statistics Configuration dialog box. Make the changes to the configuration. Click OK.
2.
Information ! To edit a Real Time mode Tabular Statistics configuration click to stop the capture before you edit the configuration.
You cannot choose another profile once you have selected a profile and clicked OK. To use a different profile you must create a new Tabular Statistics view. You can also edit the Tabular Statistics Configuration from Measurement Setup view by double-clicking the Tabular Statistics box.
Trace Calls from Tabular Statistics View

1. 2. Right-click the row on the Tabular Statistics view that shows the calls you want to trace. This will display a popup menu. Select Call Trace or Call Trace Unsuccessful from the popup menu.
Display More Statistics Information

1. 2. Right-click the row on the Tabular Statistics view that you want to display more details for. This will display a popup menu. If enabled, select Next Level from the popup menu. A new Tabular Statistics view will appear displaying a breakdown from the calls on the selected row.
Information You can also double-click a row to display the next level.
Log Tabular Statistics Data to a File

1. 2. 3. In Monitor, right-click on the Tabular Statistics view and Save to CSV Logging File. Select the directory and enter the filename. Click OK.
Remove a Tabular Statistics

! ! From Monitor click the window to remove it. on the TABULAR STATISTICS
From Measurement Setup right-click the Tabular Statistics
button
Analyzing Captured Data
Learn about Analyzing Messages

The basic view used to display signaling is the Traffic Overview window. The Traffic Overview window can be split into two. The upper pane displays the Traffic Overview and the lower pane displays the detailed Decode view.
Monitor's Traffic Overview (top half) and Decode View (lower half).
Traffic Overview In this example, for each message Traffic Overview displays the link, direction, timestamp and description. The details for the selected message appear in the Status Bar. As messages are captured they scroll up the Traffic Overview. The detail level and color can be changed to display messages in different ways. Traffic Overviews are added by clicking New Traffic Overview. Decode View The Decode view is displayed in the bottom half of the Traffic Overview. It shows the decoded information for the message highlighted in the Traffic Overview. The decodes are automatically determined from the protocol associated with that link. The Decode view shows each protocol layer in a different color. or by selecting View menu
Analyzing Captured Data 95
The current message is decoded by clicking , by selecting Traffic menu Decode View or by double-clicking the message. You can add Call Traces, Statistics and View Filters to the data you capture. You can set up these applications before beginning a Real Time capture or you can add them to an existing log file. Information Capturing from many links and analyzing the data through many views may affect the performance. Here are some tips: ! ! ! ! Run Call Trace, Statistics and View Filters in Post Capture mode ( ). Minimize Traffic Overviews. Use Logging Filters to restrict the data captured. Or all three above.
How to Analyze Captured Data

From Monitor you can define what and how messages are displayed. You can also: ! ! ! ! Add Call Trace views to isolate particular calls. Add Statistics views to highlight important trends and information. Apply view filters to display only the desired messages. Group the messages that make up a particular call.
From setting filters to changing the layout and level of details displayed, you have a variety of display tools.
Opening Log Files

From the Start Up Screen 1. 2. Click Post Capture to display the Open dialog box. Select the file you want to open. Click OK.
From Monitor 1. From Monitor (click if Monitor view is not displayed) click
to display the Open dialog box. 2. Select the file you want to open. Click OK. You can now analyze the data using Call Trace, Statistics or Filters.
96 Analyzing Captured Data
Information ! In Real Time mode ( ), only a single Real Time file is ), multiple log files can
available. In Post Capture mode ( be open simultaneously. !
Log files containing emulation traffic cannot be opened on instruments where EmuLite is not enabled.
Decode Messages
There are three ways to decode a message: ! ! ! Click view. . Clicking the button again will hide the Decode
Select Traffic menu Decode view. (Or in EmuLite view select EmuLite menu Decode view.) Double-click the message you want to decode. The decode will appear in the lower half of the Traffic Overview window.
To decode another message simply select it in the Traffic Overview. The Decode view always shows the decode for the highlighted message.
Group Messages for One Call

1. 2. 3. Click the message you want to group on. Click . All the messages associated with the call will be displayed. Select Group again to return to the full Traffic Overview.
Information If the call sequence information is not available you can generate it by using Call Trace. Create a Call Trace view and the call sequence information will be generated automatically as the data is processed. The Group function can now be used.
Find the Call Associated with a Message

1. 2. Run Call Trace if a Call Trace view does not exist. Right-click the message and select Select Call from the popup menu. The call the message was part of will be highlighted in the Call Trace view.
Create a View Filter

View Filters restrict which events and messages are displayed. Only captured events and messages which pass through a view filter will be displayed. 1.
In Monitor select Traffic menu
View Filter. Analyzing Captured Data 97
View Filter from Monitor's Traffic Overview.
2. 3. 4.
Click New to create a new filter. Set up the Filter Conditions in the tabs in the lower half dialog. Click OK to apply the filter.
Find an Event or Message

Find Filters highlight particular events or messages. 1. 2. 3. 4. In Monitor select Traffic menu Click New to create a new filter. Set up the Filter Conditions in the tabs in the lower half dialog. Click OK to apply the find filter and locate the first message. Select Traffic menu Find Next or [F3] to select the next event or message that meets the conditions. Or, select Traffic menu Find Previous or [Shift]+[F3] to select the previous event or message that meets the conditions.
Find.
Traffic Overview and Decode View Colors

The Error Color selected in the Color tab will be used throughout the Signaling Advisor. When you change the Error Color setting in this tab the Error Color setting in the Alarm View tab will automatically change. 1. 2. 3. Select Tools menu Click the Color tab. Click the color and select the new color from the palette.
Options.
Color Palette from the Color Selection tab.
4.
Repeat Step 3 for each color you want to change. Click OK.
Saving data
The changes to log files can be saved either by: ! ! Clicking to overwrite the existing file.
Saving the data displayed in Traffic Overview to a different file. Select File menu dialog box.
Save data to new log file
Saving to a different file 1. 2. 3. to display the
There will be a tab for each Traffic Overview window. Select the settings for the data you want to save from each view. Click Save to save data.
Save Decodes to a Text File

1. 2. Click to display the decode for the selected message in Traffic Overview. (OPTIONAL) Select multiple messages. Range of Adjacent Messages Click the first message in the range (as in Step 1 above), and then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range (as in Step 1 above), and then hold down [CTRL] and click each message in the range. You can scroll to make the last message visible.
Signaling Advisor User's Manual Analyzing Captured Data 99
3. 4.
Right-click the Decode view and select Save to Text File from the popup menu. Select the directory and enter the filename for the text file.
Opening Other File Formats

You can import text and capture files from other instruments directly into the Signaling Advisor.
Assumptions
! Text format for the messages are in the appropriate format defined below.
Steps
1. Select File menu Open Log File to display the Open Log File dialog box. Select the appropriate file type and file. Click OK to open the file. You will be prompted to select an appropriate configuration file (*.cfg). The file will be opened in Traffic Overview.
2.
Format Text Messages to be Imported into Monitor

You can import messages into Monitor from text/hex files using the File menu Open Log File and selecting the appropriate file type.
Assumptions
! The messages are in a text file in the format defined below.
Format
"Comment" [Link Number in range 1..128] (Timestamp in dd/mm/yyyy hh:mm:ss.uuuuuu format) Hex Octet1 (00..FF) HexOctet2 (00..FF) .... Hex octetN (00..FF);
Example Message
"Msg 1 - Call 1 Msg 1 IAM" [128] (24/07/2000 12:00:00.000000) f5 ff 3f 15 01 01 01 10 10 10 0a 01 01 01 00 00 00 0a 03 06 0a 03 80 90 a2 04 01 10 00 01 0a 07 73 13 10 00 00 00 00 c3 07 01 05 00 36 00 36 65 ef 1b 09 19 00 01 10 2a 31 23 2a 31 39 2a 50 23 2a 35 30 2a 32 34 30 38 23 35 30 39 34 00 ;
Notes
! Anything in quotes or preceded by a "#" is a comment and is ignored.
! ! ! ! ! !
Link Number is optional. If it exists it will be used when displaying messages in Traffic Overview. 128=Link1 RxA, 127=Link1 RxB, etc. Timestamp information is optional. If it exists it will be used when displaying messages in Traffic Overview. The data octets range is 00..FF. ";" is used to terminated each message.
Copying
You can copy messages and decodes and paste them into other applications. Messages can also be copied into EmuLite. The copying methods available from Traffic Overview, Decode and EmuLite views are:
Copy Messages
5. 6. Click the message to select it. (OPTIONAL) Select multiple messages. Range of Adjacent Messages Click the first message in the range (as in Step 1 above), and then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range (as in Step 1 above), and then hold down [CTRL] and click each message in the range. You can scroll to make the last message visible. 7. 8. Right-click the selection and select Copy from the popup menu. Follow the Paste instructions for the application you want to paste into.
Information ! You can copy a maximum of 100 messages from Traffic Overview into EmuLite and use them in sequences. and then You can copy the messages for a call by clicking copying all the messages displayed in Traffic Overview (as described above). In EmuLite view's Sequence pane you can copy messages and paste them into new sequences. If you run a sequence and receive an unexpected message you can copy it back into the sequence and then re-run it. You can paste messages into other applications, such as MS Notepad.
Copy Decodes
1. 2. 3. Click to display the Decode view.
Click the message in Traffic Overview to select it. (OPTIONAL) Select multiple messages. Range of Adjacent Messages Click the first message in the range (as in Step 2 above), and then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range (as in Step 2 above), and then hold down [CTRL] and click each message in the range. You can scroll to make the last message visible.
4. 5.
Right-click the Decode view and select Copy from the popup menu. Follow the Paste instructions for the application you want to paste into. Information
and then copying You can copy the decodes for a call by clicking all the decodes for the messages displayed in Traffic Overview.
Printing
You can print messages and decodes. Printing methods available from Traffic Overview and Decode view are:
Print Messages
1. 2. 3. 4. Click the Traffic Overview you want to print. Select File menu Click OK to print.
Print
to display the Print dialog box.
(OPTIONAL) Change the print settings.
Print a Range of Messages

1. 2. Click the Traffic Overview containing the messages you want to print. Select the messages. Range of Adjacent Messages Click the first message in the range, and then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range, and then hold down [CTRL]
102 Analyzing Captured Data Signaling Advisor User's Manual
and click each message in the range. You can scroll to make the last message visible. 3. 4. 5. Select File menu Click OK to print. Information You can print the messages for a call by clicking all the messages displayed in Traffic Overview. and then selecting
Print
to display the Print dialog box.
(OPTIONAL) Change the print settings.
Print Decodes
1. 2. 3. Click to display the Decode view.
Click the message in Traffic Overview to select it. (OPTIONAL) Select multiple messages. Range of Adjacent Messages Click the first message in the range (as in Step 2 above), and then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range (as in Step 2 above), and then hold down [CTRL] and click each message in the range. You can scroll to make the last message visible.
4.
Right-click the Decode view and select Print from the popup menu. Information
and then printing You can print the decodes for a call by clicking all the decodes for the messages displayed in Traffic Overview.
Print from an EmuLite pane

1. 2. Right-click the EmuLite pane to select it and select Print from the popup menu. Click OK. Information Only the individual EmuLite pane will be printed. You can print other panes by right-clicking the other pane and selecting Print.
Display Settings
You can use a variety of display settings to customize the way events and messages are displayed. Detail settings, colors and columns can all be used to customize the way information is displayed.
Validate Messages
The Signaling Advisor can validate messages against the associated Protocol Stack. Check Message Validation 1. 2. 3. 4. 5. Select Tools menu panel.
Options General Settings tab Monitor
Click Display invalid messages in Traffic Overview using error color. Click OK. Scroll through messages to check if any are displayed in the error color (default red). No messages in the error color indicates that the correct Protocol Stack is being used. If messages are displayed in the error color continue to Step 6. Double-click an error colored message to decode it. Scroll through the decode to identify where the message stopped being decoded correctly. Click view. then to display Configuration's Protocol Stack
Identify the Problem 6. 7.
8. 9.
Hover the mouse pointer over the protocols to display the ToolTips.
10. Check that the protocol details match those being used on your network. 11. If appropriate edit the Protocol Stack and/or Protocols. Repeat Step 4 to check if message has been validated.
Change Timestamp Format

1. 2. 3. Right-click the Traffic Overview or EmuLite's Sequence pane to display the popup menu. Select Timestamp Format. Select the format you require from the list shown. A tick ( ) to the left of a timestamp format indicates the format that is in use.
Display Point Codes in Messages

The default setting is to display Point Code Mappings. You can create your own and edit Point Code Mappings. 1. 2. Click the Traffic overview to select it. Select Traffic menu
Point Code Mapping.
Information ! Point Code Mappings are created in Configurations Point Code Mapping view but are displayed in Monitors Traffic Overview, Decode and Call Trace views. A tick ( ) indicates that if Point Code Mappings exist they will be displayed instead of Point Codes. Clicking removes the tick and the Point Codes will be displayed.
Compare Two Different Messages in the Same File

1. From the Traffic menu check that there is no tick ( ) to the left of the Synchronize Views option. If there is a tick ( ), indicating that synchronization is on, click the option to turn it off. Click to open a second Traffic Overview.
2.
You can now decode a message from each window.
Display the Same Message in Different Views

1. From the Traffic menu check that there is a tick ( ) to the left of the Synchronize Views option. If there is no tick ( ), indicating that synchronization is off, click the option to turn it on. Click to open a second Traffic Overview. Click a message in one view and the same message will be highlighted in the other Traffic Overview.
2. 3.
Information If the message has been filtered out of the other Traffic Overview the nearest message will be highlighted.
Hide Sensitive Information

Sensitive information, such as telephone numbers and credit card numbers can be hidden. 1. 2. 3. Select Tools menu
Options.
Click the General Settings tab. Click Show sensitive fields in the Security panel. A tick ( ) indicates that sensitive fields will be displayed. No tick indicates sensitive fields will not be shown. Click OK to close the Option sheets.
4.
Change Decode Display Format

The fields in the Decode view can be displayed either as one Field Per Line or one Octet Per Line. 1. Right-click on the Decode view to display the popup menu.
Monitor's Decode View Settings.
2.
Select Field Per Line. A tick ( ) indicates that the display is using the Field Per Line format. No tick indicates that the Octet Per Line format is being used.
Rearrange Windows
Select Window menu Tile Horizontally to display the windows so that they do not overlap on the screen. Alternatively you can select Cascade to display the Windows in an overlapped fashion. Information In Monitor windows are tiled automatically when a new view/window is created.
Displaying Columns
You can customize which columns are displayed, their order and widths. You can restrict the displayed information to the details you need to see.
Show/Hide Columns
You can change the columns in Traffic Overview, Decode view, Call Trace view or EmuLite views. 1.
Right-click on the view to display the popup menu.
2. 3.
Select Columns from the popup menu. Click the column you want to show/hide. Displayed columns have a tick ( ) to the left of them. Hidden columns have no tick. Clicking on the ticked options will hide the column. Clicking options with no tick will show them.
If you wish to display other Protocol Field columns in Traffic Overview or Call Trace view: 1. 2. 3. Right-click on the view to display the popup menu. Select Column Setup from the popup menu. Select the fields to be displayed.
Move Columns
You can move the columns in Traffic Overview, Decode view, Call Trace view, Tabular Statistics view or EmuLite views. 1. 2. Select the column heading of the column you want to move. Hold the mouse button down on the heading and drag the heading to its new location.
Resize Columns
You can change the column widths in Traffic Overview, Decode view, Call Trace view, Tabular Statistics view, Statistics Tabular view or EmuLite views. 1. 2. Select the column whose width you want to adjust. Drag the border at the right of the column heading until the column is the width you want.
Information Double-click the border to the right of the column heading to make the width fit the contents of the column.
Using Emulation (EmuLite and Conformance Tests) (Option)
Learn about Emulation (Option)

Emulation is the ability to send messages into your network and react to the responses received. Traditionally this has meant programming the sequences and messages to be emulated. EmuLite lets you perform the emulation activities in a graphical environment without the need for any programming. EmuLite is the Signaling Advisors graphical interface where you can construct sequences and messages. Emulation sequences are configured, run and displayed within Monitor. or selecting View menu Clicking EmuLite dialog box.
EmuLite
will display the
Specific emulation sequences are supplied so that you can run Conformance Tests on your network. Conformance tests check your network behaves as defined in the relevant conformance test specifications. Selecting View menu Conformance Tests will display the Conformance Test dialog box. You can emulate simple or complex sequences. Complex sequences can include; timers, user input requests, optional commands that depend on which message is received, jumps to other blocks of the sequence, and so on. The result for each sequence (pass or fail) is displayed in Monitors EmuLite views. The number of passes or failures is shown in the EmuLite view title bar. There are three panes in EmuLite view: Status pane displays the summary information about the sequence. It shows the run status, the result and the suite the sequence belongs to. Sequence pane displays the events and messages for the sequence selected in the Status pane or the sequence that is currently running. Decode pane displays the decode of the message selected in the Sequence pane.
Using Emulation (EmuLite and Conformance Tests) (Option) 109
Status Pane
The Status pane is displayed in the top left of the EmuLite view. It displays the status of each sequence as it is run. The Status pane is always shown when EmuLite view is displayed. The possible sequence statuses are: ! ! ! ! ! ! ! Not Run when a sequence is waiting to be run. Loading when a sequence is being loaded, prior to being run. Running when the sequence has started running. User Stopped when the user stopped the sequence. Pass when the sequence has stopped running and passed. Fail when the sequence has stopped running and failed. Aborted when the running of the sequence has been stopped before completion.
A Status pane showing completed emulation sequences.
Log files (*.tol) that contain EmuLite data will only show final results, that is Pass, Fail, Aborted or User Stopped. Not Run can appear if a sequence was configured to run but did not. Running only appears when the sequence is being executed. The details of the events in the selected sequence is shown in the Sequence pane.
Sequence Pane
The Sequence pane is displayed in the top right of the EmuLite view. When sequences are being run the Sequence pane displays the currently running sequence, adding each event and message to the display as it occurs. When a log file (*.tol) is open the Sequence pane displays the events and messages for the sequence selected in the Status pane.
Sequence pane. In the above, the IAM message was transmitted on Link1. The message received after the ACM message did not match the message expected in the sequence. The reason for the mismatch will displayed in EmuLite's Decode view. 110 Using Emulation (EmuLite and Conformance Tests) (Option) Signaling Advisor User's Manual
The decode of the selected message is shown in the Decode pane (the Decode view will be blank if a message is not selected). The events and messages shown in the Event column and represented by the following: Received Message Transmitted Message Timer Set Timer Cancelled Timer Expired Waited for Key Press Wait for the Set Time Manual Stop Link Failure Sequence Passed Sequence Failed
Decode Pane
The Decode pane is displayed at the bottom of the EmuLite view. It shows the decode of the message selected in the Sequence pane. This view is very similar to Traffic Overview's Decode view in that the message details are shown on the top row of the view and the protocol stack layers are identified in the relevant color. However in EmuLite the Decode pane also displays detailed information when a match fails. There are three types of Message Mismatch: Key Field mismatch is identified by red text at the top of the Decode pane. Fixed Location Field mismatch is identified by red text at the top of the Decode pane. In addition the Expected Binary column will automatically be displayed. The expected binary digits that did not match will be displayed in red. Link mismatch is identified by the red text at the top of the Decode pane. If more than one branch was present in the sequence you can compare a field mismatch against the messages in other branches.
EmuLite's Decode pane showing a Fixed Location Field Mismatch. The binary digits that did not match are shown in red in the Expected Binary column.
How to Use EmuLite and Conformance Tests (Option)

EmuLites graphical interface lets you test new services, maintain existing services and troubleshoot problems by allowing you to write test sequences that transmit messages and react to the responding messages. EmuLite provides a set of easy-to-use graphical tools, which help to quickly solve emulation-based acceptance and maintenance problems. You can: ! ! ! ! Quickly create message sequences using EmuLites powerful graphical Sequence Editor. Correctly build complex signaling messages using EmuLites protocol field based Message Editor. Easily manage the execution of tests using EmuLites built in Test Manager. Instantly identify failed tests and use the Signaling Advisors graphical analysis tools to identify the problem.
Step 1 - Connecting and Configuring

Ensure that the Interface Module(s) are inserted and locked into the side of the Signaling Advisor (this should ONLY be done when the instrument is switched off). Connect the Signaling Advisors Interface Modules to your network following the instructions for the Interface Module and the Operating Mode you want to use. See Help menu On-line Documentation and select the appropriate Interface Module Reference Manual for more information on cabling and connecting. Hardware parameters, such as line-encoding, frame type and clocks, are ) Bearer view ( ). Follow the configured in Configurations ( instructions for the Interface Module you want to configure. The Interface Module graphic at the top of Bearer view indicates whether hardware alarms have been detected on the receive side of the bearers. Use Alarm view to identify and clear any hardware alarms.
112 Using Emulation (EmuLite and Conformance Tests) (Option)
Step 2 - Creating Links

Create links on the timeslots you want to transmit and receive messages on. In EmuLite, you must specify which link you want a message to be transmitted on. However, you can set up EmuLite to receive messages on a specific link or any emulate link. You can now run a Conformance Test or continue to create and run your own sequences.
Step 3 - Creating and Editing Test Sequences

Once configured you can create and edit test sequences and messages from the EmuLite Configuration dialog ( ! ! ):
Create and edit sequences and messages in the Sequence Editor. Edit message fields in the Message Editor.
Step 4 - Align Links

You must align links before running sequences. SS7 links can be aligned automatically (when creating the link). All other links are aligned manually in Link Status view ( ).
Step 5 - Running Test Sequences

Select the sequences to be run in the Test Manager. You can define the order the sequences will be run and how often. Once the tests have been selected you must close the EmuLite dialog (click OK) and click start sequentially running your selected sequences. to
How to Check that EmuLite is Enabled

If you have purchased the EmuLite option the EmuLite button on Monitors toolbar will be colored button will not be displayed. Information You can enable the EmuLite option by purchasing the appropriate Software Option Controller Key. . If EmuLite is not enabled the
Run a Conformance Test

Assumptions
! The links have been created and aligned (in service).
Steps
1. In Monitor ( ) select View menu Conformance Tests to display the Conformance dialog box.
2.
On the Test Manager tab select the sequence from the Available Sequences panel and click to add it to the Selected Sequences panel. Only one sequence can be run at a time. Choose the action to be taken by the Signaling Advisor if one of the selected sequences fails when it is run. Select either Stop on Failure or Continue on Failure from the Error Handling panel.
Run Once, Run Continuous
3.
4.
Select how often the selected sequences should be run. Select or Run a number of Times from the Repetitions panel.
5.
(OPTIONAL) If you want the Signaling Advisor to automatically stop capturing when the last sequence has been run select Stop Capture on Test Completion. A tick ( ) indicates that the capture will be stopped automatically. (OPTIONAL) If you want to log the emulation results to a file click the Write Results to CSV File to enable CSV logging. A tick ( ) indicates that results will be logged to CSV file. Enter the filename in the text box below the Write Results to CSV File option
6.
7. 8. 9. 10. 11. 12. Click
Select the Parameter Editor tab and choose the links from the Select link(s) to be used panel. (OPTIONAL) Edit the timer values. The default values are those specifies in the conformance test specification. Select the Test Manager tab again. Click OK to close the EmuLite dialog box and return to Monitor. to run the selected sequences and to capture the Click messages transmitted and received. (OPTIONAL) Stop continuous repetitions (if automatic stop has not been set in Step 6). at any time to stop running the sequence. Information
You can see the description of the selected conformance test by selecting the Test Description tab on the Conformance test dialog box
Basic Emulate Sequences

You must create the message sequence you want to emulate. The basic steps are:
Steps
1. 2. 3. 4. 5. 6. 7. In Monitor ( ) click to display the EmuLite dialog box.
Create a New Suite, if required. Create a New Sequence. Add messages and commands to the sequence. Select the sequence to be run and define the test parameters. Run the sequence. Analyze results in EmuLite view.
Create EmuLite Sequences

Test sequences are displayed in the Sequence Editor. They represent the message sequence to be tested and contain both the messages to be transmitted by the Signaling Advisor and the messages it expects to receive. The test sequence defines the order in which the messages are expected. Test sequences are stored within Test Suites. You can use Test Suites to group sequences together, for example you may want to group sequences used to test a new service. You can run all the sequences in a Test Suite by selecting the suite in Test Manager. There are three pre-defined Test Suite Folders. They are: ! Example Sequences this Test Suite folder contains the example sequences supplied with the Signaling Advisor. You can copy these sequences and edit them to suit the sequence you are creating. These are read-only and cannot be edited. User Sequences this Test Suite folder contains sequences you create. You can copy and paste sequences and messages from any test suite folder. From Call Trace this Test Suite folder is automatically created when you create a sequence from a Call Trace view. This is where any auto-generated sequence from Call Trace is stored.
When transmitting a message you select the link it is to be transmitted on. A message can be received on a particular link or any emulate link. For information on configuring links see Configuration's Bearer view.
EmuLites Sequence Editor. The Sequence List is shown on the left and the Sequence Diagram shown on the right. Only one sequence can be loaded (edited) at time. The Loaded Sequence is indicated by bold underlined text in the Sequence List and is also shown at the top of the Sequence Diagram. The Selected Sequence is highlighted in the Sequence List and will be loaded into the Sequence Diagram when Edit is clicked.
Create a Test Suite

Sequences are organized in Test Suites. When you create a sequence you must select the suite where the new sequence will be stored.
Assumptions
! EmuLites Test Manager tab is displayed.
Steps
1. Click New Suite to add a suite to the Available Sequence panel. A new suite called User Sequences n will be added to the list. (OPTIONAL) To rename the Test Suite, right-click the new suite and select Rename from the popup menu. Type the new name, and then press [Enter]. Information ! ! You can also create a Test Suite by right-clicking the sequence list in the Sequence Editor tab and selecting New Suite. To remove a suite and all its sequences click the suite and then click Remove Suite. This will completely remove the suite and its sequences from the Sequence Editor and the Test Manager. You can remove a suite by right-clicking the sequence list in Test Manager tab or the Sequence Editor tab and selecting Remove Suite.
2.
You can rename a Test Suite, Sequence, Message or Link by selecting it, pressing [F2] and typing the new name.
Rename a Test Suite Assumptions

! EmuLites Test Manager or Sequence Editor tab is displayed.
Steps
1. 2. Right-click the Test Suite Folder to select it and display the popup menu. Select Rename Suite and enter the new name. Information You can rename a Test Suite, Sequence, Message or Link by selecting it, pressing [F2] and typing the new name.
Copy a Sequence from One Test Suite to Another Assumptions

! EmuLites Sequence Editor tab is displayed.
Step
Drag the sequence you want to copy to the destination Test Suite Folder. A copy of the sequence will be added to the destination suite.
Create a New Sequence Assumptions

! ! The appropriate Test Suite exists. EmuLites Sequence Editor tab is displayed.
Steps
1. 2. Click the appropriate test suite from the Sequence List. Click New from the Sequence panel. The new sequence will be added to the selected test suite and loaded into the Sequence Diagram. Information ! ! You can create a new sequence by right-clicking the Sequence List and selecting New Sequence from the popup message. To remove a suite and all its sequences right-click the suite, in the Sequence Editor, and then select Remove Suite. This will completely remove the suite and its sequences from the Sequence Editor and the Test Manager.
Rename a Sequence Assumptions

! ! EmuLites Test Manager or Sequence Editor tab is displayed. A User Sequence is selected.
Steps
1. 2. Right-click the Sequence Folder to select it and display the popup menu. Select Rename and enter the new name. Information ! ! You can rename a Test Suite, Sequence, Message or Link by selecting it, pressing [F2] and typing the new name. Example Sequences cannot be renamed.
Rename a Link Assumptions

! ! EmuLites Test Manager or Sequence Editor tab is displayed. A User Sequence is selected.
Steps
1. 2. Right-click the link to select it and display the popup menu. Select Rename and enter the new name. Information ! You can rename a Test Suite, Sequence, Message or Link by selecting it, pressing [F2] and typing the new name.
Copy an Existing Sequence Assumptions

Steps
1. 2. Select the sequence you wish to copy. Drag the sequence to the destination Test Suite. Information You can also copy and paste sequences using MS Windows Explorer. Sequences are stored in the Example Sequences and User Sequences directories within C:\Program Files\Agilent Signaling Advisor\User Files\Suites.
Automatically Create a Sequence from Monitor's Call Trace View Assumptions

! Call Trace has already been run in Monitor.
Steps
1. 2. In Monitor's ( ) Call Trace view right-click the call you want to automatically create to display the popup menu. Click Create Sequence to extend the menu and then select either As Originating End or As Terminating End. If you select As Originating End the Signaling Advisor will assume that you want to send the first message. If you select As Terminating End the Signaling Advisor will assume you expect to receive the first message. EmuLite will open at the Sequence Editor tab. The sequence will automatically be added to the From Call Trace Sequence List. Information Pasting messages captured from your network is the easiest way to set up sequences. This is because the parameters within the captured messages will be set correctly from your monitored messages.
Edit a Sequence
Before you can add messages or commands to a sequence is must be loaded. The loaded sequence is displayed in the Sequence Diagram to the right of the Sequence Editor tab.
Assumptions
Step
1. 2. Click the sequence you want to edit in the Sequence Diagram. Click Edit in the Sequence panel.
Print a Sequence Assumptions

! ! EmuLites Sequence Editor tab is displayed. The sequence must be loaded.
Steps
1.
Right-click the Sequence Diagram to select it and display the popup menu.
2.
Select Print to display the Print dialog box. Click OK to print.
Add Messages and Commands to a Sequence

Messages and commands are added to a sequence in the Sequence Editor. The Sequence List is shown on the left and the Sequence Diagram shown on the right. Messages are displayed in the Sequence List. From the Sequence List messages are inserted into the Sequence Diagram as transmit or receive events. Sequences may also include timer and wait events.
Sequence Editor.
The Example Sequences supplied with your Signaling Advisor cover most of the common protocols. Messages can be added to the loaded sequence in the following ways: ! ! ! ! Inserted from the list of example messages supplied with the Signaling Advisor. Copied and Pasted from another sequence. Copy messages pasted from Monitors Traffic Overview (maximum of 100 messages at a time). Imported as text files, binary files from the Hewlett Packard 37900D and 3rd Party Instruments.
Example Sequences shown in the Sequence List cannot be edited. They can be copied to a different suite by: ! ! ! Using the Copy and Paste buttons in the Message panel. Dragging directly to the loaded sequence. A copy of the message is automatically added to the sequence list. Inserting into the loaded User Sequence using (transmit) or (receive) button commands. A copy of the message is automatically added to the sequence list.
Commands are added directly into the Sequence Diagram using the command buttons shown at the bottom of the Sequence Diagram. Messages and commands are added below the current cursor position in the Sequence Diagram. You can save your own messages as a User Message. These saved messages will be listed in the User Messages folder when you add a New Message.
Add a New Message Assumptions

! The User Sequence is loaded in EmuLites Sequence Editor.
Steps
1. 2. 3. Click New in the Message panel to display the Add Message dialog box. Select a Protocol Stack from the Protocol Stack drop-down list. Select the message from the list of protocols in the Messages Available panel. Click Add > to add the message to the Message(s) to Add panel. Or, drag the new message to the Message(s) to Add panel. Repeat for each message. Click OK to add all the messages listed in the Message(s) to Add panel. Information ! Both supplied Example Messages and saved User Messages are displayed in the New Message dialog box. Messages listed under User Messages are those that you have previously saved. When you add a new message its direction will not be assigned ). When you add the message to the Sequence Diagram, ( using (transmit) or (receive) button commands, the direction is assigned. If you decide to transmit a receive message (or receive a transmit message) you will be prompted to create a copy. You can rename a Test Suite, Sequence, Message or Link by selecting it, pressing [F2] and typing the new name. The Signaling Advisor will set up certain fields within received messages to match automatically. These can be edited in Message Editor. The fields of Example Messages are set to '0'. You will need to edit these values before the message is used.
4.
! ! !
Delete a Message
The message will be removed from both the Sequence List and the Sequence Diagram
Assumptions
Steps
1. 2. Select the Message. Click Remove from the Message panel. Information To remove a message from the Sequence Diagram and NOT from the Sequence list select the messaged in the Sequence Diagram and click .
Import Messages
You can import messages from a text file, Hewlett Packard 37900D Emulate Message Catalogs (*.mg), Access7 files and files from 3rd Party Instruments.
Assumptions
! ! ! The User Sequence is loaded in EmuLites Sequence Editor. The messages to be imported are available from Windows Explorer. The messages are in the correct format.
Steps
1. 2. 3. 4. 5. Right-click the sequence in the Sequence list to display the popup menu. Select Import Message(s) from the popup menu to display the Import Messages dialog. Select the message file to be imported. Select the appropriate Protocol Stack(s). Click OK.
Format Text Messages to be Imported into EmuLite

You can import messages into EmuLite from text/hex files.
Assumptions
! The messages are in a text file in the format defined below.
Format
"Message Name" Hex Octet1 (00..FF) HexOctet2 (00..FF) .... Hex octetN (00..FF);
Example Message
"Initial Address Message" f5 ff 3f 15 01 01 01 10 10 10 0a 01 01 01 00 00 00 0a 03 06 0a 03 80 90 a2 04 01 10 00 01 0a 07 73 13 10 00 00 00 00 c3 07 01 05 00 36 00 36 65 ef 1b 09 19 00 01 10 2a 31 23 2a 31 39 2a 50 23 2a 35 30 2a 32 34 30 38 23 35 30 39 34 00;
Notes
Anything in quotes or preceded by a "#" is a comment and is ignored. ";" is used to terminated each message. Information ! You can import text files that are in the Monitor format. The Monitor format contains extra parameters (timestamp and link) that are ignored by EmuLite. If no Message Name exists a default name (Message1, Message2, and so on) will be given.
Import HP 37900D Emulation Catalogs

1. 2. If you do not have a LIF formatted floppy disk, create one using the HP 37900D's Filer. Copy the Emulate Message Catalog files (*.MG) onto the LIF formatted floppy disk using the 900D Filer. Insert the LIF floppy disk into your Signaling Advisor. Run the LIFUTIL.exe program from Start (Windows taskbar)
Programs Signaling Advisor Tools HP LIF Utilities HP LIF Utilities. Select LIF to DOS to copy the HP37900D
Emulate Message Catalog files from the LIF floppy disk to the PC's hard disk. Select the following options: LIF drive name: A: (assuming this to be the floppy drive). LIF file name: <enter desired filename>. (LIFUTIL may not accept the .MG part of the name. If this happens use the wildcard '*' instead of the file extension. e.g. If your file is called 'IAMMSG.MG' use the filename 'IAMMSG.*'. DOS directory name: <enter the DOS directory were the file should be saved>. Copy as: Same as source file. File name conversion: Truncate. Duplicate filename: Make unique name. File format conversion: Binary image: no format change (all file types). When all the selections have been made press the function key labelled START. The result of the conversion is a binary file.
Signaling Advisor User's Manual Using Emulation (EmuLite and Conformance Tests) (Option) 123
The binary file created by LIFUTIL may not have a'.mg' extension. Rename the file so it has a '.mg' extension. 3. If not already running, start up the Signaling Advisor and click to display the EmuLite dialog box. 4. 5. 6. Select or create a User Sequence. Right-click the sequence and select Import Messages from the popup menu. Select the 900D Emulate Message Catalog file and choose the Protocol Stacks for each personality. (The HP37900D personalities are similar to the Signaling Advisor's Protocol Stacks). Press Open to import your messages.
7.
Information ! HP LIF Utilities software only works on Windows 95 and Windows 98. It does not work on Windows NT.
Copy and Paste a Message from Another Sequence Assumptions

! ! EmuLites Sequence Editor tab is displayed. The destination sequence has been selected for editing.
Steps
1. 2. 3. Click the message you want to copy. Click Copy from the Message panel.
Edit
If not already loaded, click the destination sequence and click from the Sequence panel to load it and display it in the Sequence Diagram. Click Paste from the Message panel.
4.
Copy and Paste Messages from Traffic Overview Assumptions

! Monitors Traffic Overview is displayed.
Steps
1. 2. Click a message in Traffic Overview to select it. (OPTIONAL) Select multiple messages (maximum 100 messages). Range of Adjacent Messages Click the first message in the range (as in Step 1 above), and
then hold down [SHIFT] and click the last message in the range. You can scroll to make the last message visible. Range of Non-Adjacent Messages Click the first message in the range (as in Step 1 above), and then hold down [CTRL] and click each message in the range. You can scroll to make the last message visible. 3. 4. 5. Right-click the selection and select Copy from the popup menu. to display the EmuLite dialog box and select the Click Sequence Editor tab.
Edit
If not already loaded, click the destination sequence and click from the Sequence panel to load it and display it in the Sequence Diagram. Click Paste in the Message panel.
6.
Information ! Pasting messages captured from your network is the simplest and fastest way to set up sequences. This is because most parameters will be set correctly from you monitored messages. Messages are automatically given a default name which is usually the Message Type or Operation Code.
Add a Transmit Message Command Assumptions

! ! The User Sequence is loaded in EmuLites Sequence Editor. The message exists. The message can be inserted into the Sequence Diagram from any sequence (not only from the loaded sequence).
Steps
1. 2. Click the message in the Sequence List to select it. Select where the message is to be inserted into sequence diagram. The new transmit message will be copied below the selected message. to add the 'Transmit' message. The message will be Click displayed in the Sequence Diagram
3.
Result
Information ! Messages can only be sent/received in one direction. Messages . that currently have no direction assigned are indicated by
Once the message has been added to the Sequence Diagram the assigned direction will be shown. ! If you choose to transmit a message that is currently marked as ) EmuLite a receive message in the Sequence List ( will make a copy and append 'Tx' after the name. Variables can be restored into transmit messages prior to running the sequence. If you create EmuLite sequences off-line they are automatically set up to use an Undefined link. When you use Real Time mode on the instrument, you must change the undefined link to a proper signaling link. You can type the name of the signaling link you will be using. When the link is created EmuLite will use the link (assuming the link names match). You can also add a transmit message by dragging it from the Sequence List to the right hand side of the Sequence Diagram. To remove a message from the Sequence Diagram and NOT from the Sequence List select the messaged in the Sequence Diagram and click .
! !
! !
Add a Receive Message Command Assumptions

! ! The User Sequence is loaded in EmuLites Sequence Editor. The message exists. The message can be inserted into the Sequence Diagram from any sequence (not only from the loaded sequence).
Steps
1. 2. Click the message in the Sequence List to select it. Select where the message is to be inserted into sequence diagram. The new receive message will be added below the selected message. to add the 'Receive' message. The message will be Click displayed in the Sequence Diagram.
3.
Result
Information ! ! If you have a receive command and a different message is received the sequence will fail. Messages can only be sent/received in one direction. Messages that currently have no direction assigned are indicated by .
Once the message has been added to the Sequence Diagram the assigned direction will be shown. ! You can save fields off from received messages into variables. The variable can then be used to update subsequent transmit messages. If you create EmuLite sequences off-line they are automatically set up to use an Undefined link. When you use Real Time mode on the instrument, you must change the undefined link to a proper signaling link. You can type the name of the signaling link you will be using. When the link is created EmuLite will use the link, assuming the link names match. If you choose to receive a message that is currently marked as ) EmuLite will make a transmit in the Sequence List ( copy and append 'Rx' after the name. You can also add a receive message by dragging it from the Sequence List to the left hand side of the Sequence Diagram. You can add branches to a Receive Message command. These allow decisions to be made depending upon the message received. To remove a message from the Sequence Diagram and NOT from the Sequence List select the messaged in the Sequence Diagram and click .
! !
Add a Receive Any Message Command Assumptions

Steps
1. 2. Click the <Any Message> in the Sequence List to select it. Click the position in the sequence you want the message to be added to. The message will be copied below the selected message. to add the Receive Any Message command. The Click message will be displayed in the Sequence Diagram.
3.
Result
Information ! The <Any Message> command can only be used on receive messages. You must define the message and a specific link for transmit events.
The <Any Message> command is automatically added to the Sequence List of each new sequence.
Add a Receive Multiple Messages Branch Command

Multiple Message Branches are used to define the different messages that could be received. You can add a branch for each message that could be received.
Assumptions
! ! The User Sequence is loaded in EmuLites Sequence Editor. The messages exist.
Steps
1. 2. Add the first possible receive message to the sequence. With the first message still selected in the Sequence Diagram to click the next message that may be received and click add it to the Sequence Diagram.
Result
In the above, two possible messages could be received, either ACM or REL2. In this example a 'Jump to Block' command has also been added. If an ACM is received the sequence will expect the next received message to be an ANM. If REL2 is received the sequence will jump to Block1 and continue from there, sending the RLC2.
Select Links for Sequences Developed Offline

You must select the link a message will be transmitted on. You can select: ! ! ! the link you expect to receive messages on. the link used by the last received message. any emulate link.
If you create EmuLite sequences off-line they are automatically set up to use an Undefined link. When you use Real Time mode on the
128 Using Emulation (EmuLite and Conformance Tests) (Option) Signaling Advisor User's Manual
instrument, you must change the undefined link to a proper signaling link. You can type the name of the signaling link you will be using. When the link is created EmuLite will use the link, assuming the link names match.
Assumptions
! ! The User Sequence is loaded in EmuLites Sequence Editor The link exists.
Steps
1. 2. Click the message to select it. A drop-down list will be available for the message and the link selections. Select the link from the drop-down list.
Add a Jump to Block Command

Jumps to a different block of commands when the defined message is received.
Assumptions
Steps
1. 2. 3. Select the message in the Sequence Diagram. (This message will be used to jump to a new block when it is received). to insert the Jump to Block command. The new Click block will be added to the bottom of the Sequence Diagram. Add messages and commands to the new block (Block1).
Result
In the above, if an ACM message is received the sequence will continue to the ANM message.
In this example a 'Receive Multiple Messages Branch' command has also been added. If a REL2 message is received the sequence will jump to Block1 and transmit a RLC2 message. The sequence will fail.
Information ! ! You can toggle Pass/Fail by double-clicking. Click again to remove the Jump to Block command.
Add a Start Timer Command

Timers are used to stop a sequence waiting forever on a message to be received. Typically a timer is started after a transmit message and is cancelled after a response is received. A maximum of 20 Timers are available. They can also be used to ensure overall sequence execution is within a specified time.
Assumptions
Steps
1. Click the position in the sequence you want the Start Timer command to be added to. The timer will be added below the selected message. Click to insert the timer below the selected message. A Timer expiry block will be added to the bottom of the Sequence Diagram. If the timer expires Sequence Execution will jump to the timer Expiry Block, where further message can then be sent (OPTIONAL). Select the timer and edit the timer value (mm:ss.d). Timers have a resolution of 100 ms and a range from 00:00.1 (100ms) to 59:59.9 (59 minutes, 59.9 seconds). (OPTIONAL) Add messages and commands to the timer expiry block.
2.
3.
4.
Result
In the above, if the ACM message is not received within 10 seconds of the IAM being sent, Timer1 will expire and the sequence will jump to the Timer1 block and the sequence will fail. If the ACM is received within 10 seconds the timer will be cancelled and the sequence will pass.
Information You can add commands and messages to the Timer1 block.
Add a Cancel Timer Command

Timers are used to stop a sequence waiting forever on a message to be received. Typically a timer is started after a transmit message and is cancelled after a response is received.
Assumptions
! ! The User Sequence is loaded in EmuLites Sequence Editor. The timer exists.
Steps
1. Click the position in the sequence you want the Cancel Timer command to be added to. The timer cancellation will be added below the selected message. Click to insert the cancel timer below the selected message. Select the timer to be cancelled from the drop-down list.
2. 3.
Result
In the above, if the ACM message is not received within 10 seconds of the IAM being sent, Timer1 will expire and the sequence will jump to the Timer1 block and the sequence will fail. If the ACM is received within 10 seconds the timer will be cancelled and the sequence will pass.
Information ! ! If you start a timer and then branch to a different block you have to cancel the timer in each block. You can add commands and messages to the Timer1 block.
Add a Wait for Time Command

This command adds a delay. The range, formatted mm:ss.d, 00:00.1 (100 ms)to 59:59.9 (59 minutes, 59.9 seconds) is available.
Assumptions
! !
The User Sequence is loaded in EmuLites Sequence Editor. A transmit message will follow the Wait command.
Steps
1. Click the position in the sequence you want the Wait for Time command to be added to. The command will be added below the selected message. Click to insert the Wait for Time command. Enter the time period you want to wait in the format mm:ss.d. Add the transmit message to be sent when the time period has passed.
2. 3. 4.
Result
The example above waits for 10 seconds.
Add a Wait for Key Press Command

This command pauses the running of the sequence until you click OK. When the sequence is running, a dialog box will be displayed in EmuLite view when the Wait for Key Press command has been reached. When you click OK the transmit message will be sent and the sequence will continue.
Assumptions
! ! The User Sequence is loaded in EmuLites Sequence Editor. A transmit message will follow the Wait for Key Press command.
Steps
1. 2. 3. Click the message in the sequence that will be before the Wait for Key command. Click to insert the Wait for Key below the selected message. Add the transmit message to be sent when the key has been pressed.
Result
Delete a Command or Block Assumptions

Steps
1. 2. Select the message or command to be deleted. Click to delete the selected message or command.
Change the Expected Result of a Test

The sequence ends when the Pass/Fail command is reached. You should select the test result to be displayed in EmuLite view when the sequence has been run.
Assumptions
Step
Click either or to toggle the result you want to be displayed in EmuLite views Status pane.
Edit Message Fields

Messages are edited in the Message Editor.
Message Editor tab. Some columns are only displayed when a transmit message is selected, other columns are only displayed when a receive message is selected.
Edit the fields in the selected message by: ! ! ! Double-clicking the value in the description column and typing a new value or selecting a value from the list. Double-clicking the hex or decimal column and typing the new value. Clicking the field and selecting one of the function buttons at the bottom of the dialog box. Key Field the field variable (for example, OPC, DPC, Message Type, CIC) is used for matching and restoring field values. Key Field variables are shown in blue and can appear anywhere in the message.
For matching, saving and restoring there are two criteria: !
Fixed Location Field the fixed location variable is used for matching and restoring the value at the selected location. Fixed Location variables are shown in yellow.
Dynamic Fields Certain fields within messages are dynamic and either need to be managed during the execution of a test sequence or modified using values from received messages. Examples of these types of fields are OPC/DPC, Source Local Reference Numbers/Destination Local Reference Number, Originating Transaction ID/Destination Transaction ID. Depending on whether the Signaling Advisor is acting as the originating or terminating end of the sequence, these fields will either have to be supplied by the sequence or extracted from received messages for inclusion in subsequent transmit messages. When creating the sequence and its messages you must manage these fields by configuring appropriate save/restore variables for use within the sequence.
Select a Message to be Edited Assumptions

! EmuLites Message Editor tab is displayed.
Steps
1. Select the message you want to edit from the drop down list. Only the messages in the sequence currently loaded in the Sequence Editor are displayed. Make the changes. You can select other messages from that sequence from dropdown Message list in the Message Editor. Information You can also select the message to be edited by, double-clicking it in the Sequence Editor's Sequence List or Sequence Diagram, or by rightclicking the Sequence List and selecting Edit Message from the popup menu.
2. 3.
Change a Field in a Message Assumptions

! The message is displayed in Message Editor.
Steps
1. 2. Double-click the field in the description column to a dropdown list of the available fields. Click the field you want from the list.
Information ! If the Auto lengths & pointers option is ticked ( ) EmuLite will automatically update the length and pointer details to reflect the new value. Click Undo to undo the change and revert back to the previous value.
Edit an Octet Value in a Message Assumptions

Steps
1. 2. Double-click the hex or decimal column or the description column value of the field you want to edit. Type the new value. Information ! If the Auto lengths & pointers option is ticked ( ) EmuLite will automatically update the length and pointer details to reflect the new value. Click Undo to undo the change and revert back to the previous value.
Insert an Information Element

An Information Element is a series of octets that make up message parameters, rather than individual fields (for example Called Party Number in ISUP).
Essential
! ! The message is displayed in Message Editor. The Information Element exists.
Steps
1. 2. Click the field above the point where the Information Element is to be inserted. Click to display the Insert Information Element dialog box. The dialog box will only show Information Elements for the current Protocol Stack. Select the Information Element from the list. Click OK.
3. 4.
Information ! ! The fields of Example Messages are set to '0'. You will need to edit these values before the message is used. Insert Information Elements at the beginning of a field tag to avoid invalidating the rest of the message.
Insert an Octet Essential

Steps
1. 2. Right-click the field above the point where the octet is to be inserted. This will display a popup menu. Click Insert Octet. Information ! ! ! You can insert an octet by selecting the field where the octet is to be inserted and pressing [Ins]. Insert multiple octets by highlighting multiple fields instead of a single field. Delete octet(s) by highlighting the octets and choosing Delete Octets from the right-click menu or by pressing [Del].
Match on a Value
'Match' is used to specify the values that need to be present in a received message. You can match fields and fixed position and octet values. When you add a receive message to a sequence, EmuLite will automatically add relevant matches. These matches will identify the message when it is received.
Assumptions
! The receive message is displayed in Message Editor.
Steps
1. 2. Select the field you want to match on. Click .
Result
A Received IAM Message showing match criteria for Message Type (MT). When the IAM is received its DPC, OPC, SLS and CIC values will be saved into variables. These values can be restored into fields in transmit messages. Key Field variables are highlighted in blue and Fixed Location Field variables are highlighted in yellow.
Information ! To remove the match setting click the field and click . If you remove all matches and saves the receive message will be invalid (displayed red in Sequence Editor). The Match column header indicates the number of variables that must match, for example Match (1) when one variable must match. When creating an octet match, right-click the field and select Match on receive Octet Match from the popup menu. Add the new octet value and click OK. The number of octet matches is shown in the column header, for example Match (3) [1] when three variables and one octet must match. You can add wildcards to matched variable length fields, for example Calling Party Number. '=' completes the number, ? accepts any digit. Double-click Fixed Location match bits (highlighted yellow) in the MSB Bin LSB column to deselect that bit from the match criteria.
Save a Message Field into a Variable

You can save field and fixed position values from a messages into variables. Variables can then be restored into subsequent transmit messages.
Assumptions
!
The message is displayed in Message Editor.

Steps
1. 2. Select the field you want to save. Click .
Result
A Receive Message showing match criteria for an IAM message type. When the IAM is received its DPC, OPC and CIC values will be saved to variables. Key Field variables are highlighted in blue and Fixed Location Field variables are highlighted in yellow.
Information ! To remove the save variable setting select the field and click . If you remove all matches and saves the receive message will be invalid (displayed red in Sequence Editor). The Save column header indicates the number of fields that have been saved from that message, for example Save (4) is shown when four fields have been saved. You can edit the name of a saved variable in the Message Editor. Right-click to display the popup menu and select Edit Variables.
Restore a Variable
You can restore a fixed position variable into a fixed position in a transmit message.
Assumptions
Steps
1. Select the field you want to restore.
2.
Click to display the Restore from variable dialog box. Only variables of the appropriate type and size will be listed. Select the variable you want to be restored. If there is no variable click New and define the new variable with its initial value. Click OK.
3.
4.
Result
A Transmit Message showing match criteria for an ACM message type. When the ACM is sent its DPC, OPC and CIC values will be restored from variables. In this example, the variables have been restored from the 'Save a Message Field into a Variable' example. The restored DPC value is taken from the saved OPC, the restored OPC from the saved DPC and the restored CIC from the saved CIC. Fields can only be stored into Fixed Location.
Information ! ! To remove the restore variable setting click the field and click . The Restore column header indicates the number of variables that have been restored, for example Restore (4) when four variables have been restored. The variable name and values can be edited in the Restore from Variable dialog box.
Insert the Next Logical Field

When building up from a blank message you can use display on the fields that could logically be inserted at the current position. If red fields are displayed in the Message Editor, you can use to replace the red fields with valid fields. to
Assumptions
! ! The message is displayed in Message Editor. Ensure Calculate lengths & pointers is ticked ( ) if you want EmuLite to automatically recalculate the lengths and pointers for the message.
Steps
1. 2. 3. 4. 5. Click the field above the point where the next field is to be inserted. Click to display the Next Field(s) dialog box. Select the field from the list of fields which could logically appear at that point in the message. Select Insert to insert after the selected field or Overwrite to overwrite the next field. Click OK. Information When editing TCAP messages use the Next Fields instead of Insert Information Elements. This will ensure parameter IDs are set up correctly.
Automatically Set Lengths and Pointers

When the fields within a message are edited the lengths, pointers and odd/even indicator information can be updated automatically to ensure that the message is valid. If you may wish to create a message with an invalid length, for example to confirm how your network would handle these messages, you can disable this option.
Assumptions
Steps
1. 2. The Calculate lengths & pointers option is selected ( ) by default. If the tick is not displayed, click to select the option. Edit the message fields. The lengths and pointers will be updated.
Set Invalid Lengths and Pointers Assumptions

Steps
1. Click Calculate lengths & pointers to remove the tick ( ). The tick indicates that EmuLite will automatically recalculate the lengths and pointers information when changes are made. Edit the message fields. The lengths and pointers will not be updated and will be invalid.
2.
Edit Variables
You can edit variable names and initial values.
Assumptions
Steps
1. 2. 3. Right-click and select Edit variables. Select the name or value you want to change and type the new name or value. Click OK.
Get Help on a Field

You can get Protocol Help on a particular field in a message.
Assumptions
Steps
1. 2. Right-click the field to display the popup menu. Select Protocol Help.
Change the Protocol Stack Used by a Message Assumptions

Step
Select the Protocol Stack from the Protocol Stack drop-down list.
Save a Message Assumptions

Steps
1. 2. Right-click the message to display the popup menu. Select Other Save As User Message. The message will be saved as a User Message.
Information ! ! The saved message can be inserted as a new message in other User Sequences. They will appear under User Sequences. Remove a User Message by repeating steps 1 and 2, select the User Message to be deleted and press [Del].
Create an Information Element

An Information Element is a series of octets that make up message parameters, rather than fields (for example Called Party Number in ISUP). You can select a series of octets and save them as an Information Element. They can then be inserted into other messages using .
Assumptions
Steps
1. 2. 3. Right-click the field to select it and display the popup menu. Select Other
Save as User Information Element.
Enter the name and click OK. Information
Remove an Information Element by repeating steps 1 and 2, select the Information Element to be deleted and press [Del].
Print a Message Assumptions

Steps
1. 2. Right-click the message to display the popup menu. Select Other Print to display the Print dialog box. Click OK to print the message.
Copy a Message Assumptions

Steps
1. 2. Right-click the message to display the popup menu. Select Other
Copy.
3.
Follow the Paste instructions for the application you want to paste into.
Running Test Sequences

EmuLite sequentially runs the selected test sequences that are specified in the Selected Sequences list one at a time. A sequence will only be run if it appears in the Selected Sequences list and is ticked ( ).
Test Manager tab.
Run Sequences Assumptions

! ! ! The sequence is complete. The links have been created and aligned (in service). All messages are assigned to signaling links.
Steps
1. In EmuLites Test Manager tab select the sequence from the Available Sequences panel and click to add it to the Selected Sequences panel. (OPTIONAL) Add multiple sequences. Range of Adjacent Sequences Click the first sequence and then hold down [SHIFT] and click the last sequence in the range. You can scroll to make the last sequence visible. Click to add them to the Selected Sequences panel. Range of Non-Adjacent Messages Click the first sequence and then hold down [CTRL] and click
Signaling Advisor User's Manual Using Emulation (EmuLite and Conformance Tests) (Option) 143
2.
each sequence in the range. You can scroll to make the last sequence visible. Click to add them to the Selected Sequences panel. 3. (OPTIONAL) Change the order the selected sequences will be run. Click 4. or to move the sequence up or down the order. Select the action to be taken by the Signaling Advisor if one of the selected sequences fails when it is run. Select either Stop on Failure or Continue on Failure from the Error Handling panel.
Run Once, Run Continuous
5.
Select how often the selected sequences should be run. Select or Run a number of Times from the Repetitions panel.
6.
(OPTIONAL) If you want the Signaling Advisor to automatically stop capturing when the last sequence has been run select Stop Capture on Test Completion. A tick ( ) indicates that the capture will be stopped automatically. (OPTIONAL) If you want to log the emulation results to a file click the Write Results to CSV File to enable CSV logging. A tick ( ) indicates that results will be logged to CSV file. Enter the filename in the text box below the Write Results to CSV File option
7.
8. 9. 10.
Click OK to close the EmuLite dialog box and return to Monitor. Click to run the selected sequences and to capture the messages transmitted and received. (OPTIONAL) Stop continuous repetitions (if automatic stop has not been set in Step 6). Click at any time to stop running the selected sequences.
Information ! You can also add sequences to the Selected Sequence panel by double-clicking or dragging the sequence from the Available Sequences panel. Deselect sequences from the Selected Sequences panel by double-clicking or clicking the tick ( ) next to the selected sequence. The tick will be removed and the sequence will not be run. Select all the sequences in the Selected Sequence panel by clicking Select All. All sequences will be ticked ( ) and will be run when is clicked.
Deselect all the sequences in the Selected Sequence panel by clicking Select None. All sequences will be deselected and will not be run when is clicked. Add whole test suites by selecting the suite and clicking <-Add Completely remove the sequence from the Selected Sequence . panel by clicking the sequence and then The CSV file is updated each time a sequence is completed. Change the order the selected sequences will be run by dragging a sequence up or down the list. Repetitions will stop automatically when the hard disk is full.
! ! ! ! !
Log EmuLite Results to a file Assumptions

! The Test Manager tab is displayed.
Steps
1. In EmuLites Test Manager tab click the Write Results to CSV File to enable CSV logging. A tick ( ) indicates that results will be logged to CSV file. Enter the filename in the text box below the Write Results to CSV File option.
2.
Analyze Results
The results of the emulation are displayed in Monitors EmuLite view. This view is created automatically when is clicked and the selected Test Sequences are run. When an existing log file (*.tol) that contains emulation data is opened it will be shown in the EmuLite view. Once all the sequences have run (or you have stopped running sequences) you can display more detailed information to find out why a sequence failed.
EmuLite View.
Identify and Analyze Mismatch Errors Assumptions

! ! The test(s) have been run. Monitor's EmuLite view is displayed.
Steps
1. Check the type of mismatch in the Decode pane. The mismatch type will be shown in red on the second row of the pane. Link Mismatches occur when the message was not received on the expected link. If there was either a Key Field or a Fixed Location Field Mismatch go to Step 2. 2. If a branch was used in the sequence you can check the mismatch against the other expected messages in the branch. Right-click the Decode pane and select Compare with from the popup menu. Select the message from the list.
3.
Display next failed sequence Assumptions

! ! The test(s) have been run. Monitor's EmuLite view is displayed.
Steps
1. 2. Right-click the Suite pane to display the popup menu. Select either Find Next Fail or Find Prev Fail to display the next or previous failed sequence.
Display the EmuLite Message in Traffic Overview

If you have been emulating and monitoring at the same time you can see the position of the emulated messages relative to the rest of the network traffic.
Assumptions
! ! ! The test(s) have been run. Monitor's EmuLite view is displayed. A Traffic Overview is open. Click to open view.
Steps
1. 2. Right-click the message in the Sequence pane to display the popup menu. Select Traffic Link. Information Call Trace, Statistics and Filtering tools are available from Monitor's Traffic Overview.
Application Programming Interface

The Signaling Advisor contains an Application Programming Interface (API). It lets you write programs, using your own C/C++ software, that will send and receive messages using the Signaling Advisor software and interfaces. The API can be used when the Signaling Advisor software is running in Post Capture mode or from the Startup dialog (before the operation mode has been selected). The three files you need can be found in C:\Program Files\Agilent Signaling Advisor\Api. They are: API,h which describes the functionality. Client.lib your application will need to link to this file. APIdefines.h contains # defines. You will also need to use a Win32 compiler so that your applications can send/receive messages and start/stop links.
Other Tasks and Self Tests
Other Tasks
Only in particular circumstances will the tasks that follow will only need to be carried out, for example, when controlling the Signaling Advisor remotely from another PC or when upgrading the software or hardware.
Remote Operation
You can use a PC and a third party application such as Carbon Copy to remotely control your Signaling Advisor. Carbon Copy allows you to use the Signaling Advisor user interface from a PC that is located at a remote site. The Signaling Advisor is shipped to you with Carbon Copy (host and client versions) ready for installation, (see Registration & Initial Set up Manual). The Carbon Copy User manual (as well as all other manuals) is available from Help menu On-line Documentation. A Product Note explaining remote control operations is also available from the On-line Documentation suite.
Remote Control Connection diagram.
Other Tasks and Self Tests 149
Information Carbon Copy 32 is a registered trademark of Microcom System Inc.
Re-install/Upgrade the Signaling Advisor

The installation process will detect any previous versions of the Signaling Advisor. The previous version will automatically be uninstalled before the new version is installed. 1. 2. Insert the CD in your CD-ROM drive. If your instrument/PC is setup to run when a CD is inserted you should accept the default options shown during the installation process. If your instrument does not auto-run when it detects a CD you should run the Setup.exe file on the CD from Windows Explorer. Accept the default options suggested by the installation process. 3. 4. Once installed the Signaling Advisor icon will appear on your desktop. Reboot the instrument. Double-click the icon to launch the Signaling Advisor. If a previous version was installed the current Serial Number and Software Option Controller Keys will be used.
Information A message will be displayed if the Serial Number or Key Information is not retained. You should re-enter the details in the Software Option Controller.
Activating Software Options

The Software Option Controller manages the software for your instrument. Each Software Option can be enabled to allow access to particular Signaling Advisor features. Different options are accessed by different 'Keys'. Many features are available with the basic Signaling Advisor. Others, such as extra protocol support, can be bought separately for your instrument. The Software Option Controller is accessed from the Windows Start Menu. Click ! Start Programs Agilent Signaling Advisor
Software Option Controller.
Backup Your Files

1. 2. Double-click the My Computer icon on the Windows Desktop. Locate the files. If you are using the default directory for the Signaling Advisor this should be C:\Program Files\Agilent Signaling Advisor\User Files Each sub-directory contains specific types of files.
150 Other Tasks and Self Tests
3.
Copy all the files in the User Files directory and its subdirectories to your backup destination.
Information After you have backed up your files you can delete them from the hard disk to free up space.
Copying Hardware Version to another application

If you contact your supplier you may be asked to confirm the software versions on the Signaling Advisor hardware. You can copy the hardware version details to Microsoft applications such as Notepad or into an email. 1. 2. 3. 4. Click to open Configuration.
Hardware Versions.
Select View menu
Click the Copy To Clipboard button. Follow the paste instructions for the other MS Windows application.
Install an Interface Module

1. 2. If the Signaling Advisor is running, select File menu from Monitor, to exit the Signaling Advisor.
Exit,
Click Start on the Windows taskbar (at the bottom left of your screen) and select Shut Down to display the Shut Down Windows dialog. Select Shut down from the list of options. Windows will display a message when the Signaling Advisor's power can be switched off.
3. 4.
Switch off your instrument. If necessary, remove the existing Interface Module from the slot. Push in the latch above the Interface Module and slide to unlock the Interface Module. The Interface Module is now disconnected from the Signaling Advisor. Pull the Interface Module to remove it from its slot.
5. 6. 7.
Push the Interface Module into either opening at the side of the Signaling Advisor. Slide the latch (above the Interface Module) into the locked position to lock the Interface Module in place. You can now switch on the instrument and run the Signaling Advisor.
Caution " When connecting or disconnecting Interface Modules, ensure that you are grounded. Make contact with the metal surface of the mainframe with your free hand to bring you, the module and the mainframe to the same static potential. Modules remain susceptible to ESD damage while installed in the mainframe. Never insert or remove an Interface Module when the Signaling Advisor power is on. Always shut down and power off the Signaling Advisor before inserting or removing an Interface Module. Always lock the Interface Module in place to prevent damage to the Signaling Advisor and the Interface Module.
"
"
Remove an Interface Module

1. 2. If the Signaling Advisor is running, select File menu from Monitor, to exit the Signaling Advisor.
Exit,
3. 4.
Switch off your instrument. Push in the latch above the Interface Module and slide to unlock the Interface Module. The Interface Module is now disconnected from the Signaling Advisor. Pull the Interface Module to remove it from its slot.
5.
Caution " When connecting or disconnecting Interface Modules, ensure that you are grounded. Make contact with the metal surface of the mainframe with your free hand to bring you, the module and the mainframe to the same static potential. Modules remain susceptible to ESD damage while installed in the mainframe. Never insert or remove an Interface Module when the Signaling Advisor power is on. Always shut down and power off the Signaling Advisor before inserting or removing an Interface Module.
"
Reprogram an Interface Module

The Signaling Advisor will display the dialog box below when any of the fitted Interface Modules needs to be reprogrammed. This dialog will appear during the Signaling Advisor Start-Up.
Information " " ONLY reprogram the Interface Module when the Signaling Advisor informs you that it is necessary. If the Interface in Slot 1 needs to be reprogrammed go to Step 5. (Slot 1 is on the right hand side of the instrument when you face the display.) If the Signaling Advisor is running, select File menu from Monitor, to exit the Signaling Advisor.
Exit,
1. 2.
3. 4. 5. 6.
Switch off your instrument. Remove the Interface Module to be reprogrammed. Remove the Interface Module from Slot 1 and replace with the Interface Module to be reprogrammed. Switch on the instrument and open the Signaling Advisor. A message will appear saying that the Interface Module in Slot 1 requires reprogramming.
7. 8. 9.
Select OK. At the Start Up Screen click Post Capture button. When prompted to select the log file to be opened click the Cancel button.
Update Interface Module
10. In Monitor select Tools menu Software.
11. The Serial Number for the Interface Module will be displayed. Select Start Update to start reprogramming. 12. The Interface Module will be reprogrammed. A box will popup when reprogramming is complete. Click the OK button. 13. Exit the Signaling Advisor, shut down and switch off your instrument.
If you swapped two different types of Interface Module then you will probably want to swap them back. Once the Interfaces have been returned to their previous slots continue with Step 12. 14. Switch on the instrument and open the Signaling Advisor.
Reset Call Sequence Information

The Call Sequence Information is correlated from the defined Call Trace calls. If you change Call Trace settings you may have to clear the existing Call Sequence Information. The new Call Sequence Information will be correlated the next time Call Trace is run. 1. 2. In Monitor select Tools menu
Reset Sequence Information.
Select the protocol layers you want to reset the sequence information for. Click OK.
Self Tests
Correct operation of your instrument can be verified by running the extensive Self Tests which are integrated in the Signaling Advisor. If you think that there may be a problem with the instrument you should run the appropriate self tests. If you find a problem contact your local Agilent Service Office. Caution Ensure that the Signaling Advisor is in Post Capture mode and disconnected from your network. Running Self Tests may cause some network disruption.
All Tests Essential

The following items are required when running all Self Tests: " " " Loopback cables (E1, T1 and DS0) or connector (Datacom) for all Interface Modules. 15-pin D-type cable to connect the external clock ports on either side of the Signaling Advisor. Handset.
Steps
1. 2. If the Signaling Advisor is not already in Post Capture mode click .
Self Tests.
In Monitor select Tools menu
Self Tests dialog box showing an Interface Module test on bearers 1.1 and 1.2.
3. 4.
Click the All Tests button in the Test Selection panel. All applicable tests will be selected. Click the Run Tests button in the Test Control panel. You will be prompted to connect various cables, and so on, during the tests.
Single Test
Some of the following items are required when running Self Tests. The panel below the Test Selection will indicate which, if any, of the following are required for the highlighted test:
Essential
" " " Loopback cables (E1, T1 and DS0) or connector (Datacom) for all Interface Modules. 15-pin D-type cable to connect the external clock ports on either side of the Signaling Advisor. Handset if the Codec test is selected.
Steps
1. 2. 3. If the Signaling Advisor is not already in Post Capture mode click .
Self Tests.
Click the box next to the test you want to run. This will select the test. A tick ( ) will appear showing the test has been selected and the description of the test will appear in the box below. If you have chosen a LIM test select the LIMs and the bearers you wish to test. If you have chosen a LIM test or a test which
4.
requires you to attach a cable, a configuration panel will appear next to the list of tests. Select the options you require. 5. 6. Set up the Repetitions, Error Handling and File Handling for the test. Click the Run Tests button in the Test Control panel.
Combination of Tests
Some of the following items are required when running Self Tests. The panel below the Test Selection will indicate which, if any, of the following are required for the highlighted test:
Essential
" " " Loopback cables (E1, T1 and DS0) or connector (Datacom) for all Interface Modules. 15-pin D-type cable to connect the external clock ports on either side of the Signaling Advisor. Handset if the Codec test is selected.
Steps
1. 2. 3. If the Signaling Advisor is not already in Post Capture mode click .
Self Tests.
Click the box next to the first test you want to run. This will select the test. A tick ( ) will appear showing the test has been selected and the description of the test will appear in the box below. If you have chosen a LIM test select the LIMs and the bearers you wish to test. If you have chosen a LIM test or a test which requires you to attach a cable, a configuration panel will appear next to the list of tests. Select the options you require. Repeat Steps 3 (and 4 if applicable) for each test you want to run. Setup the Repetitions, Error Handling and File Handling for these tests. Click Run Tests in the Test Control panel.
4.
5. 6. 7.
Information If you wish to run many tests click the All Tests button and click the boxes of the tests you do not want to run. Clicking a ticked ( ) test will deselect the test.
Glossary of Terms
3rd Party Instruments

Files from some other Protocol Analyzers (for example, INET Spectra) are supported.
Contents tab
Shows the hierarchy of the Help Topics.
DCE
Data Communications Equipment. (Datacom Emulation Only).
Glossary of Terms 157
Dongle
A hardware license verification security device attached to the parallel (printer) port.
DTE
Data Terminating Equipment. (Datacom Emulation Only).
Events
Receive Abort, Start and Stop Triggers being activated are some examples of events. Events are treated as messages but they are not Signaling Traffic from the links.
Find tab
A search feature which lists every topic that contains the given word or phrase.
Fixed Location Field

Fixed Location Fields are used in EmuLite. They are fields that can only be matched against their position in the message.
158 Glossary of Terms
Fractional
Fractional Links are configured across multiple timeslots on one bearer. When a fractional link is selected in Bearer View all the timeslots used by the fractional link are highlighted. You cannot auto configure fractional links.
Index tab
A list of topic titles and keywords.
Key Field
Key Fields are used in EmuLite. They are fields that can be matched against regardless of their position in the message.
Logical Bearer
Logical Bearers link the individual parts of your network.
Messages
Messages are Signaling Traffic.
Microsoft Windows
The Off-line version of the Signaling Advisor is designed to operate on PCs which use: ! Microsoft Windows 95 OSR2 version 4.00.95B. ! Microsoft Windows 95 OSR2 version 4.00.95C. ! Microsoft Windows 98 SE version 4.10.2222A. ! Microsoft Windows NT 4 SP3/4/5. The Signaling Advisor may operate satisfactorily on other versions of Microsoft Windows released after 95. Microsoft ,Windows NT and Windows are U.S. registered trademarks of Microsoft Corp.
National Bits Generated Bit Pattern

The pattern that is inserted into the Framing Timeslot of the E1 Frame. Specific to E1.
Physical Bearer
The Physical Bearers are located in the Interface Modules fitted to your Signaling Advisor.
Shut down
The Signaling Advisor operates on Microsoft Windows. You must always shutdown Windows before switching off the power to the instrument. If you do not shutdown correctly Windows will automatically perform a check the next time the instrument is switched on. To shutdown correctly: 1. 2. 3. Click Start on the Windows taskbar (at the bottom left of your screen. Select Shut down from the dialog box. Select Shut down from the list of options. Windows will display a message when the Signaling Advisor's power can be switched off.
Sub-rate
Sub-rate Links are a lower bandwidth than a standard 64k timeslot, and typically used in wireless networks. For example, 16k or 8k.
TXC
Transmit Clock (Datacom).
TXD
Transmit Data (Datacom).
XTC
External Transmit Clock (Datacom).
V.35 16 View 6, 16, 18, 35
Index
C
Call Trace 79, 82, 83 Adding 59, 77, 79, 80, 81 Colors 77, 82 Columns 77, 106, 107 Editing 77, 80, 81, 83 Summary view 83 Tabular Statistics 94 View 77, 83, 106, 107, 154 Calls Call Trace view 77 Grouping Messages 82, 97 Tabular Statistics view 92 Tracing Calls 69, 77, 80, 81, 154 Capturing 59, 60 Chart Statistics view 88 Types 88 Clearing Hardware Alarms 10, 13, 16, 17 Color Alarm view 37, 41 Call Trace view 77, 82 Decode view 95, 98 Link Status view 44 Statistics view 88, 90 Traffic Overview 95, 98 Configuring Auto Configure Signaling Links 9, 13, 14 Call Trace 77, 81, 83 Manually Configure Signaling Links 16, 19, 55 Statistics 82, 83, 85, 87, 90, 91 Tabular Statistics 92, 93 Conformance Tests 109, 112, 113 Copying 61, 101, 124, 151 Decodes 102 Filter Settings 61, 75 Hardware Versions 151 Messages 101, 142 Trigger Settings 61, 75
A
Adding Call Trace views 61, 77, 80, 81 Decode views 95 Logging Filters 61, 69, 70, 71, 72, 73, 74 Point Code Formats 55, 56 Point Code Mappings 53, 54 Protocol Stacks 46, 49 Protocols 46, 47, 49 Signaling Links 18 Statistics views 61, 85 Tabular Statistics views 92, 93 Traffic Overviews 61, 95 Triggers 61, 69, 70, 71, 72, 73, 74 View Filters 61, 69, 70, 71, 72, 73, 74 Alarms 37, 39, 40, 41 Clearing Hardware Alarms 10, 13, 16, 17 Color 41 Notification 40 View 16, 39, 40 Analyze 98, 100 Application Programming Interface (API) 147 Auto Configure 9, 11, 13, 14, 37 Auto Configuring Bearers 13, 14 Signaling Links 13, 14
B
Bearer Settings Datacom 16 DS0 16 E1 16 Manual Configuration 16, 18, 36, 37, 50 RS232 16 RS449 16 T1 16
D
Datacom Bearer Settings 18 Datacom Interface 23, 26 Decode Messages 97, 102, 104, 105 Printing 103
Index 163
View 95, 98, 101, 102, 103, 104, 105, 106, 107 Decode View 95 Delete Call Trace 84 Filters 76 Statistics 92 Tabular Statistics 94 Triggers 76 Disable Triggers or Filters 68, 76 Display 104, 105, 106 Level of Detail 20, 104 Point Code Mappings in Traffic Overview 52, 105 DS0/DS-0A Interface 23, 27 Duplicated MSU Filtering 19
Triggers 76
F
Filtering 59, 61, 64, 69, 7071, 72, 73, 74, 79, 96 Conditions 64 Copying 75 Criteria 64 Disable 76 Duplicated MSUs 19 Exporting 76 Find 98 Find a Message or Event 98 Importing 76 Logging Filters 59, 64, 68 Logically 'AND'ing Filters 59, 64 Logically 'OR'ing Filters 59, 64 PCR Filtering 19 Removing 76 Short Messages (FSSUs, LSSUs, S-Frames and R-Frames) 19 View Filter 64, 97 Find a Message or Event 98 FISU Filtering 19 Fractional Links 19, 36
E
E1 Interface 22, 25 Editing 30, 32, 34, 35 Call Trace Configurations 81 Point Code Formats 55, 57 Point Code Mappings 53 Protocol Stacks 46, 49 Protocols 46, 47, 48 Statistics Configurations 85, 87, 89 Tabular Statistics Configurations 93 Emulating Voice 35 Emulation 25, 26, 27 Printing 103 EmuLite Analyze Results 145, 146, 147 Application Programming Interface (API) 147 Basic Steps 112 Copy 142 Messages 133, 134, 135, 136, 137, 138, 139, 140, 141, 142 Print 142 Running Sequences 143, 145 Sequences 114, 115, 116, 117, 118, 119, 120, 121, 122, 124, 125, 126, 127, 128, 129, 130, 131, 132 Test Suites 116, 117 Variables 136, 137, 138, 141 Views 109, 110, 111, 145 Exporting Filters 76 Measurement Setups 62, 63
164 Index
G
GPRS 33, 34 Graph Adding 85, 87, 88 Editing 88 Statistics view 85 Statistics View 88 Tabular view 85, 91 Tabular View 88 Types 88, 90 Grouping Messages into Calls 82, 97
H
Handset 35 Hardware Alarms 10, 13, 16, 17, 37
I
Import Point Code Mappings into Mapping Table 54 Importing Filters 76 Measurement Setups 61, 63 Triggers 76
Interface Modules Connecting 9 Upgrading 152 Introduction Analyzing 95, 96 Auto Configure 9 Call Trace 77 Capturing 59 Connecting 9 Copying 101 Decode Views 95 EmuLite 109 Hardware Alarms 37 Link Status 42 Linksets 51 Manual Configure 16 Measurement Setup 60 Monitor 95, 96 Point Code Formats 54 Point Code Mappings 52 Printing 102 Protocol Stack 45 Remote Operation 149 Self Tests 154 Signaling Advisor 1, 2, 151, 152 Statistics 85 Tabular Statistics 92 Traffic Overview 95 Triggers and Filters 64 ISDN 31, 32
M
Manual Configuration 16, 17 Manuals Online 9 Measurement Setup 60, 61, 62 Creating Logging Filters 68 Creating Triggers 66 Exporting 63 Importing Files 63 Importing from a Log File 63 Message Capturing 59, 60 Color 95 Copying 101 Decoding 97 Display Point Code Mappings 95, 105 Emulating 112, 120, 133 Filtering Retransmitted Messages 19 Filtering Short Messages 19 Grouping for a Single Call 97 Level of Detail 95, 104 Printing 102 Timestamp Format 95 Monitor 96 Monitoring 22, 23 MSU Filtering 19
O
On-line Manuals 9 Options Auto Configure 13, 14 Call Trace 80, 81, 83 Configuraiton 18, 35 Display 41, 44, 98, 105, 107 Statistics 85, 87, 88, 91 Tabular Statistics 93 Updating Software 150
L
Link 10, 13, 18, 19, 35, 95 Fractional 36 Link Status View 44 Linksets 74 Sub-Rate 36 Link Status 43, 44 Checking a Link 44 Colors 44 View 44 Links 28 GPRS 33, 34 ISDN 31, 32 SS7 29, 31 TRAU 34 V5 31 Voice 35 X.25 31 Linksets 51 Logging Filters 59, 64, 68 LSSU Filtering 19
P
Paste Filters 75 Messages 101, 102 Triggers 75 PCR Filtering 19 Point Code Format Adding 54, 56 View 54 Point Code Formats 55 Point Code Mapping Adding 52, 53, 54
Index 165
Creating a New File 53 Editing 53 Hiding in Traffic Overview 105 View 52 Point Code Mappings 52 Post Capture Analysis 59, 61, 65, 69, 77, 85, 92, 96 Measurement Setup 69 Print 142 Decodes 103 EmuLite 103 Statistics 91 Traffic Overviews 102 Printing 102, 103 Protocol Stack 6, 16, 45, 47, 104 Create New File 49 Editing 47, 48, 49, 50 Tooltips 6 View 45 Protocols Adding to Protocol Stack 47 104 Editing 46, 47, 48 Replacing 48
Sensitive Data 105 S-Frame Filtering 19 Short Message Filtering 19 Signaling Link Creating Automatically 9, 13, 15 Creating Manually 16, 18 SS7 29, 31 Statistics 85, 86, 90, 91, 92 Adding 86, 96 Editing 87, 91 Graph Types 90, 91 Options 88 Printing 91 Tabular view 91 ToolTips 6 Status Alarm 17, 37 Hardware Alarm 17, 37 Link Status 44 Sub-rate Links 19 Sub-Rate Links 36
T
T1 Interface 22, 26 Tabular Statistics 92, 94 Adding 92 Columns 92 Editing 92, 93, 94 View 92 Telephone Handset 35 Time and Date Format 95, 104 Timestamp Format 104 Tracing Calls 69, 77, 80, 81, 154 Traffic Overview 82, 95, 97, 98, 104, 105, 106, 107 TRAU 34 Triggering 61, 64 Conditions 64, 66 Copying 66, 75 Critieria 64, 66, 74 Disable 76 Exporting 76 Importing 76 Removing 76 Start Triggers 61, 64, 66 Stop Triggers 61, 64, 66 Trigger Editor 64 Triggers and Filters 64, 65, 66, 76
R
Real Time Analyzing 59, 65, 68, 69, 77, 87, 92, 96, 97 Measurement Setup 59, 60, 63, 65, 68, 69 Remote Operation 149 Remove Cables 9 Call Trace 79, 84 Filters 76 Link from a Linkset 51 Protocol from a Protocol Stack 47 Statistics 92 Tabular Statistics 94 Triggers 76 Reprogramming an Interface Module 152 Retransmitted Message Filtering 19 R-Frame Filtering 19 RS232 Interface 23, 26 RS449 Interface 23, 26
S
Save 99 Saving 49, 53, 61, 99 Self Tests 154, 155, 156
166 Index
U
Updating Software Options 150
V
V.35 Interface 23, 26 V5 31 Verification Tests 154, 155, 156 View Filters 59, 64, 96, 97 Views Alarm view 37, 39, 40, 41 Bearer view 16, 18, 20, 35, 36, 50 Call Trace view 77, 79, 81, 82, 83 Decode view 97, 98, 106 Link Status view 44 Linkset view 51 Measurement Setup view 60 Point Code Format view 55, 56, 57 Point Code Mapping view 52, 53, 54 Protocol Stack view 45, 47, 48, 49, 50, 54, 56 Statistics view 85, 86, 87, 88, 90, 91, 92 Tabular Statistics view 92, 93, 94 Traffic Overview 98, 104, 105 Voice 35
X
X.25 31
Index 167
In this book
You will learn about the Signaling Advisor user interface.
Printed in UK 07/01 37907-90229

Agilent Signaling Advisor: User's Manual

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Agilent Signaling Advisor: User's Manual

Transféré par

Droits d'auteur :

Formats disponibles

Agilent Signaling Advisor

Learn about Using Help ............................................................................................................ 5 How to Use On-line Documentation......................................................................................... 7

Connecting and Configuring

Learn About Isolating Calls ....................................................................................................77 How to Isolate Calls ................................................................................................................79

Analyzing Captured Data

Using Emulation (EmuLite and Conformance Tests) (Option)

Other Tasks and Self Tests

Other Tasks ...........................................................................................................................149 Self Tests...............................................................................................................................154

Glossary of Terms Index

Signaling Advisor User's Manual

Using Signaling Advisor

The Basic Steps

Step 1 - Connecting and Configuring

2 Using Signaling Advisor

Signaling Advisor User's Manual

Step 3 - Analyzing Data

and shut down Windows

Signaling Advisor User's Manual

Using Signaling Advisor 3

Signaling Advisor User's Manual

Learn about Using Help

Fonts and Symbols ! ! ! !

Signaling Advisor User's Manual

In Dialog Boxes ! ! Tips !

Signaling Advisor User's Manual

How to Use On-line Documentation

Signaling Advisor User's Manual

Signaling Advisor User's Manual

Connecting and Configuring

How to Connect Cables

Learn about Configuring Automatically (Monitor Operation Only)

Signaling Advisor User's Manual

Connecting and Configuring 9

Auto Configure's dialog box..

10 Connecting and Configuring

Signaling Advisor User's Manual

How to Configure Automatically (Monitor Operation Only)

Signaling Advisor User's Manual

Connecting and Configuring 11

Auto Configure Options sheet.

Configuration's Auto Configure dialog box.

12 Connecting and Configuring

Signaling Advisor User's Manual

Click to open Configuration and then Auto Configure dialog box.

Auto Configure running.

Signaling Advisor User's Manual

Connecting and Configuring 13

Auto Configure complete.

Change Auto Configure Options

14 Connecting and Configuring

Signaling Advisor User's Manual

Auto Configure Options.

Learn about Configuring Manually in Bearer View

16 Connecting and Configuring

Signaling Advisor User's Manual

Configuration's T1 Bearer view.

Signaling Advisor User's Manual

Connecting and Configuring 17

18 Connecting and Configuring

Signaling Advisor User's Manual

Configuration Bearer view's Sub-rate Timeslots.

Configuration Bearer view's Fractional Timeslots.