Svi 9220 User Guide

Squire Technologies 2007
This document is the property of Squire Technologies. Information contained herein is confidential. This document, either in whole or
in part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied, without
Squire Technologies prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly
authorised under that contract.

SVI 9220
SS7 to SS7 Protocol Converter
User Guide

27 September 20076

Document STPD0038-0018

Version 2
SVI 9220 Product Series
User Guide
Squire Technologies, 64 High West Street,
Dorchester, Dorset, DT1 1XA

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 2/103

Change History

Date Version Description Author
09.01.04 1.0
Initial Release
AC
15.01.04 1.1
Release after full review
AC
18.03.04 1.2
Added redundancy
J E
07.10.04 1.3
Updated for MMI version 2
AC
09.01.05 1.4
Updated with M3UA
AC
11.02.05 1.5
Added Add Routes (replaces
primary/secondary/tertiary on hunt group/
routing criteria)
AC
29.04.2005 1.6
Add Routes, AddCircuits, have changed to
Add Route, Add Circuits.
Added Routing Criteria Stats, updated Hunt
Group Stats
J E
10.05.2005 1.7
Updated to include Radius section
AC
07.06.2005 1.8
Update to include time of day resource
AC
15.06.05 1.9
Added ANSIISUPSigLink behaviour
J E
2/08/05 1.10
First Draft of next version just Type 2 CDR
at the moment. Please update this comment
b4 release
J E
17/10/05 1.11
Fixed Various Errors
J E
8/12/05 1.12
Revised Registration Functionality
J E
14/12/05 1.13
Updated radius and RC resources
J E
19/01/06 1.14
Added Multiple Customer Configuration via
Loadfile
J W
15/2/06 1.15
Added E1 LED status
J E
21/2/06 1.16
Added SCCP connection-oriented
J E
21/02/06 2
Added SNMP resource separated out from
SoftSwitch
AC
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 3/103

Table of Contents
1 INTRODUCTION......................................................................................8
2 OVERVIEW..............................................................................................9
2.1 SS7 Interconnect....................................................................................................................... 9
2.1.1 Protocol Support....................................................................................................................9
2.1.2 Terminating and Non Terminating Voice Support..............................................................10
2.2 Call Control functionality...................................................................................................... 10
2.3 MTP Layer 3 Routing Functionality .................................................................................... 10
2.4 SSCP Routing functionality................................................................................................... 10
2.5 OA&M functionality.............................................................................................................. 11
3 INSTALLATION .....................................................................................12
3.1 Pre-configuration ................................................................................................................... 12
3.2 Pre Installation....................................................................................................................... 12
3.3 Chassis Overview ................................................................................................................... 12
3.4 Power....................................................................................................................................... 13
3.5 Power On self Tests. ............................................................................................................... 13
3.6 Earthing .................................................................................................................................. 13
3.7 Connecting Ethernet Cable ................................................................................................... 13
3.8 Monitor, Keyboard and Mouse Access................................................................................. 13
3.9 Signalling Interface Cards..................................................................................................... 14
4 SYSTEM OPERATION...........................................................................16
4.1 Operating System................................................................................................................... 16
4.2 Directory/File Structure ........................................................................................................ 16
4.3 Accessing Linux Terminal Command Line. ........................................................................ 16
4.3.1 Connecting Locally.............................................................................................................16
4.3.2 Connecting Remotely..........................................................................................................17
4.3.3 Basic Linux Terminal Commands.......................................................................................17
4.4 Startup..................................................................................................................................... 18
4.4.1 Controlling Automatic Startup............................................................................................18
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 4/103

4.5 Manually Controlling The system......................................................................................... 19
4.5.1 Manually Starting the System.............................................................................................19
4.5.2 Manually Stopping the System............................................................................................19
4.6 Powering Down System......................................................................................................... 19
4.7 Changing Ethernet Properties .............................................................................................. 19
4.8 Changing System Password................................................................................................... 20
5 SYSTEM RESOURCES .........................................................................21
6 CONFIGURATION .................................................................................23
6.1 Configuration File Syntax .....................................................................................................23
6.1.1 Resource..............................................................................................................................23
6.1.2 Instance Range....................................................................................................................23
6.1.3 Attribute..............................................................................................................................23
6.1.4 Value...................................................................................................................................23
6.1.5 Comment.............................................................................................................................23
6.2 Common Configuration......................................................................................................... 24
6.2.1 System Configuration..........................................................................................................24
7 SS7 CONFIGURATION..........................................................................25
7.1 Introduction............................................................................................................................ 25
7.1.1 PCM Interconnect................................................................................................................25
7.1.2 SIGTRAN Interconnect.......................................................................................................25
7.2 Configuring TDM Interconnect ............................................................................................ 26
7.2.1 Configuring the SS7 Interface card.....................................................................................26
7.2.2 Setting up the SS7 system Timing.......................................................................................29
7.2.3 Timing Fail over..................................................................................................................31
7.2.4 Handling Voice Circuits on Signalling PCMS, TSMap Resource......................................31
7.2.5 Configuring the SS7 Interconnect.......................................................................................34
7.2.6 Configuration Examples......................................................................................................37
7.3 Setting Up A SIGTRAN Interconnect .................................................................................. 42
7.3.1 Setting Up SCTP Connection..............................................................................................42
7.3.2 Configuring M3UA Interconnect........................................................................................45
7.3.3 ISUP IP resource Syntax.....................................................................................................47
7.3.4 Example Configuration.......................................................................................................47
7.3.5 Configuring M2UA Interconnect........................................................................................49
7.3.6 Configuring M2PA Interconnect.........................................................................................50
7.4 SS7 Stack................................................................................................................................. 50
7.4.1 Attributes.............................................................................................................................50
7.5 SS7 Voice Circuit Resource Syntax ...................................................................................... 51
7.5.1 Attributes.............................................................................................................................51
7.6 Configuration examples......................................................................................................... 52
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 5/103

7.6.1 Single Media Gateway Connected to 4 TDM PCMS..........................................................52
8 MTP ROUTING.......................................................................................54
8.1 MTP Routing Resource Syntax............................................................................................. 54
8.1.1 Attributes.............................................................................................................................54
9 SCCP ROUTING....................................................................................56
9.1 SCCP Routing Resource Syntax ........................................................................................... 56
9.1.1 Attributes.............................................................................................................................56
10 SETTING UP CALL ROUTING...........................................................59
10.1 How the SVI makes a routing Decision................................................................................ 59
10.2 Configuring Hunt Groups ..................................................................................................... 60
10.2.1 Hunt Group Syntax.........................................................................................................60
10.3 Hunt Group Configuration Examples.................................................................................. 61
10.3.1 TDM Hunt Group...........................................................................................................61
10.3.2 SCCP Hunt Group..........................................................................................................61
10.4 Setting Up Routing Criteria .................................................................................................. 61
Routing Criteria Syntax.....................................................................................................................63
10.5 Setting Up The Parameter Database .................................................................................... 64
10.5.1 Matching against Called Party Number..........................................................................65
10.6 Configuring Parameter Database ......................................................................................... 66
10.6.1 Parameter Database Syntax............................................................................................66
10.7 Routing Configuration Examples ......................................................................................... 70
10.7.1 Example 1.......................................................................................................................70
10.8 Time Of Day Routing............................................................................................................. 70
10.8.1 Time of Day Routing Syntax..........................................................................................70
10.8.2 Date and Time Format....................................................................................................71
10.8.3 SCCP Routing Configuration.........................................................................................72
11 CDR RECORDS .................................................................................74
11.1 CDR Formats.......................................................................................................................... 74
11.1.1 Type 1.............................................................................................................................74
11.1.2 Type 2.............................................................................................................................75
11.2 Interrogating Current Live Calls.......................................................................................... 76
11.3 Unauthorised Call Access ...................................................................................................... 76
12 RADIUS ..............................................................................................77
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 6/103

12.1 Radius Accounting ................................................................................................................. 77
12.2 Routing Criteria ..................................................................................................................... 77
12.3 Radius Resource..................................................................................................................... 78
12.3.1 IP resource for Radius Sockets.......................................................................................79
13 OPERATION ADMINISTRATION AND MAINTENANCE...................80
13.1 Telnet Sessions........................................................................................................................ 80
13.1.1 Trap Port.........................................................................................................................80
13.1.2 OA&M Port....................................................................................................................80
13.2 Connecting a Telnet Session.................................................................................................. 80
13.3 Traps ....................................................................................................................................... 81
13.3.1 Trap Format....................................................................................................................81
13.4 Using the OA&M Port ........................................................................................................... 82
13.4.1 Checking the Syntax of a Resource................................................................................83
13.4.2 Interrogating A Resources Contents Using The Show Command.................................84
13.4.3 Manually Taking Resources In And Out Of Service......................................................85
13.5 Configuration Of Resources.................................................................................................. 86
13.5.1 Configuring Resources...................................................................................................86
13.6 Information Command.......................................................................................................... 86
13.6.1 Hunt Group Call Statistics..............................................................................................86
13.6.2 Routing Criteria Call Statistics.......................................................................................87
14 DEBUG LOGGING.............................................................................88
14.1 Debug Overview..................................................................................................................... 88
14.1.1 Message Decode.............................................................................................................88
14.1.2 Errors..............................................................................................................................89
14.1.3 Information.....................................................................................................................89
14.2 Debug Resource Syntax ......................................................................................................... 90
15 DUAL PLANE REDUNDANCY...........................................................91
15.1 Interconnect Considerations ................................................................................................. 92
15.1.1 SS7 Interconnect Considerations....................................................................................92
15.2 Configuring the System for Dual Redundancy.................................................................... 92
15.2.1 Plane Configuration Syntax............................................................................................92
15.3 Configuration Example.......................................................................................................... 93
16 SPECIFICATIONS..............................................................................94
16.1 PCI Chassis............................................................................................................................. 94
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 7/103

16.2 CPCI Chassis .......................................................................................................................... 94
16.3 MTBF figures ......................................................................................................................... 95
16.4 Environmental ........................................................................................................................ 95
16.5 Safety....................................................................................................................................... 95
16.6 System Environment.............................................................................................................. 95
16.7 Interconnect............................................................................................................................ 96
17 APPENDIX A - RADIUS ACCOUNTING TRACE...............................97
17.1 Accounting Request Start...................................................................................................... 97
17.2 Accounting Request Stop....................................................................................................... 97
18 APPENDIX B - SS7 NETWORK OVERVIEW.....................................99
18.1 F Link Interconnect ............................................................................................................. 101
18.2 A Link Interconnect............................................................................................................. 102
19 APPENDIX C - THE CALLCONTROL RESOURCE ........................103
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 8/103

1 INTRODUCTION
The SVI 9220 User Guide covers the configuration and operation of the Squire
Technologies SS7 to SS7 protocol converter.

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 9/103

2 OVERVIEW
The SVI 9220 SS7 to SS7 protocol converter provides interconnect between different
SS7 networks running disparate SS7 protocols. It can also provide MTP L3 and SCCP
routing functionalities as well as allowing for transport of SS7 between NGN IP
networks and traditional TDM networks.
2.1 SS7 INTERCONNECT
The SVI 9220 product series terminate the SS7 signalling directly on the unit via the
SS7 signalling interface boards over TDM or can provide SS7 over IP connectivity
via SIGTRAN. When connecting direct over TDM via the interface boards the low
layer SS7 protocols are terminated directly on the unit. When interfacing using
SIGTRAN the system uses the M3UA/M2UA or M2PA adaptation layer to provide
SS7 interconnect.
2.1.1 PROTOCOL SUPPORT
The SVI soft switch can support many different protocol variants. The following table
provides a list of protocols that the SVI can support. A full list is maintained on the
Squire web site.

Protocols
ETSI ISUP V1, V2, V3
ITUT ISUP Blue Book, White Book
SSUTR2
BTNUP (IUP)
UK ISUP
TUP Blue Book
ANSI ISUP
SCCP
Country Variants Swiss, Mexican, Pakistan, Chinese, contact
Account manager for full list
Capacity
Total Originating Points 32
Total Destination Points 256 per originating point
Total linksets 16 per originating point
Total signalling links 64 per originating point
Link Support A,F
Circuit support 16834 per originating point
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 10/103

2.1.2 TERMINATING AND NON TERMINATING VOICE SUPPORT
The SVI allows when inter working between two distinct protocols the ability to act
as a signalling engine only for circuit based protocols. This reduces the requirement
for the number of E1/T1 trunks to be terminated on the unit. A direct relationship is
formed between the two interconnecting circuits of two different networks. This
arrangement is especially useful for injecting additional traffic into a network without
the need to allocate a separate point code for the interconnect.

2.2 CALL CONTROL FUNCTIONALITY
The SVI switch adds a number of call control routing options enabling the user to
control the flow of calls and the call information across the system. The following
provides an overview of some of these functions

Routing on called party number
Routing on calling party number
Routing on incoming network circuit.
Called and Calling party digits and associated information
manipulation.
White List, Black List functionality.
Protocol information manipulation.
Reattempt on failure
2.3 MTP LAYER 3 ROUTING FUNCTIONALITY
The SVI 9220 provides the ability to route SS7 messages at MTP Layer 3 depending
on the SS7 routing label. The outgoing routing label can then be changed allowing for
translation of the routing label and expansion of an incoming linkset to multiple
outgoing linksets. The matching and routing functionality includes

Match on OPC, DPC, NI, CIC, SIO and Originating linkset
Over writing on OPC, DPC,NI and CIC
Specifying outgoing primary and secondary linksets.
2.4 SSCP ROUTING FUNCTIONALITY
The SVI 9220 provides the ability to route SS7 messages at the SCCP layer
depending on the SCCP routing label. The outgoing SCCP routing label can then be
Network
B
TDM
Network
A
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 11/103

changed allowing for translation of the routing label. The matching and routing
functionality includes.

Matching on full called and calling party address parameters
Translation of routing between Global Title and Pointcode routing
Translation on full called and calling party address parameters
ANSI and ETSI support and translation between both variants
Specifying outgoing SCCP destination.

2.5 OA&M FUNCTIONALITY
The SVI provides full remote configuration and management control via standard
TCP/IP. This allows for full remote management and installation of the device.

Trap reporting both locally and remotely.
Host protocol system log file capturing.
Remote Configuration
Comprehensive Real time configuration
Remote system resource interrogation
Fully automated maintenance system.
Statistic reporting

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 12/103

3 INSTALLATION
3.1 PRE-CONFIGURATION
If a pre-installation checklist had been provided to Squire Technologies before
shipment the unit will have be configured to the pre-installation checklist. As long as
the pre-installation list was correct the unit can be plugged and played into the
network without any configuration requirements.

If the pre-configuration checklist was not provided or the checklist was not complete
or incorrect the unit will need to be configured before the system will operate
correctly.
3.2 PRE INSTALLATION
On delivery of the SVIS, the system needs to be checked to ensure that all cards are
seated correctly in the PCI chassis. The SVIS contains components that can be
damaged by electrostatic discharge. Anti-static procedures should be followed at all
times, when handling components of the SVIS.

1U Chassis

3.3 CHASSIS OVERVIEW
The following diagram shows an overview of the rear of the SVI chassis.

Signalling Interface Card
PCM Layer 1 indicators
Monitor Keyboard
Mouse
3 2 1 0
RJ45 PCM Interface Ports
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 13/103

3.4 POWER
The chassis is supplied with either single or dual hot swap power supplies. The power
supplies are rated at either 110/240 Volts AC or 48 Volts DC. Check that the correct
power supply has been provided. The Power Supply will auto-sense the power
connected and adjust accordingly.

There are two power switches on the 1U chassis, the main power supply switch is at
the rear of the unit above the power cord, and a toggle switch on the front panel of the
unit. On activation of the rear power switch if power is connected correctly the power
switch will illuminate and the system will start up.

If the system does not power up hold down the toggle button on the front of the unit
for 1-2 seconds. The unit should now power up. If after this the unit still does not
power up check the power lead and power supply, otherwise contact Squire support.
3.5 POWER ON SELF TESTS.
When the system powers up it performs a number of self tests, these tests take up to 1
minute from power up. The system becomes available after these tests.
3.6 EARTHING
It is important the power supply is correctly earthed. Failure to do this may result in
system failure. There is an additional earth point provided on the rear of the chassis
which Squire Technologies recommend is used.
3.7 CONNECTING ETHERNET CABLE
If the system is connected to a standard network hub then a straight through network
cable should be used. If the cable is connected directly to an IP device then a cross
over network cable should be used.

If the network cable is connected correctly a green light will activate on the Ethernet
socket on the chassis. If this does not activate then check that both ends of the
Ethernet cable is connected and also check that the cable is correctly wired and
working.

The unit is shipped with an IP address of 192.168.2.100 with a net mask of
255.255.255.0. To check that the IP is functioning OK run a ping test to the machines
IP address on a (windows DOS session type ping 192.168.2.100 at the command
prompt).
3.8 MONITOR, KEYBOARD AND MOUSE ACCESS
The system does not generally require a monitor, keyboard and mouse but standard
monitors, keyboards and mice can be connected to the system if required.
Ethernet Connector
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 14/103

3.9 SIGNALLING INTERFACE CARDS
The signalling interface cards provide standard RJ 45 connectivity.
The following diagram shows the pin out of the RJ 45 connectors used.

Pin 1 Pin 8

Pin Designation Description
1 RX - Receive signal into interface card
2 RX + Receive signal into interface card
3 NC Not connected
4 TX - Transmit signal out of interface card
5 TX + Transmit signal out of interface card
6 NC Not connected
7 NC Not connected
8 NC Not connected

The SVI signalling interface card provides a programmable E1, T1 and J 1 physical
interfaces. The E1 interconnect is rated at 120 Ohms and the T1 is rated at 100 Ohms.
If any other connection is required, i.e. 75 Ohm BNC, please contact your account
manager who can arrange for the supply of interface converter baluns.

Dominant
Colour
Flashing
Colour
Description
Red None Port initialised, no signal received
Blank Red Receiving AIS from far end
Red Green Synchronisation is lost
Yellow None Receiving remote alarm signal
from remote end
Yellow Blank Receiving remote alarm signal
from remote end and CRC
checking is failing
Green Red Synchronisation achieved but with
framing errors
Green None Aligned
Green Yellow Losing alignment with far end
Blank Blank Not initialised
Multi Multi downloading
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 15/103

When the system powers up the interface cards will go through an initialisation
process before activating the PCMS. This can take up to 2 minutes after the POST
tests. The interface indicators will go through a process of cycling through the LEDS
before activating the PCMS.

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 16/103

4 SYSTEM OPERATION
The SVIS systems have a fully onboard automated maintenance system that
automatically brings the system into service on power up. The system continuously
monitors the status of the connecting network interfaces and reacts appropriately to
loss of signalling and bearer interfaces, maintaining system bandwidth and operation
even under failure conditions.

This section describes how to gain access to the unit if required for general
maintenance operations.
4.1 OPERATING SYSTEM
The SVIS runs on PC technology using Red Hat Linux as the core operating system.
4.2 DIRECTORY/FILE STRUCTURE
The following major files are located on the systems hard drive.
File Location Description
sswitch /home/squire Main switch program
Dbase.cfg /home/squire System configuration file
gw /etc/init.d Switch start up script
Gateway_DD-MM-YY /home/squire Debug file

4.3 ACCESSING LINUX TERMINAL COMMAND LINE.
All system commands described within this document use the terminal command line
interface. This allows for commonality across different versions of Linux and also
allows for remote access of the unit through a telnet session.
4.3.1 CONNECTING LOCALLY
The SVIS is provided with standard PC monitor, mouse and keyboard inputs allowing
for local connection and control of the system. The monitor must be capable of
supporting a display resolution of at least 1024*768.
When the system has booted the user will be asked to enter a username and password.
The system is supplied with the root (administrator) account setup with the following
user name and password and a user account called squire.

Username Password
root squire
squire squire

Enter the user name and password at the prompt and the main Red Hat GUI will start
up.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 17/103

To start a terminal session double click the terminal emulation program icon in the
panel at the bottom left hand side of the screen. When started a terminal screen will be
displayed as shown below.
[ r oot @l ocal host / r oot ]

4.3.2 CONNECTING REMOTELY
The SVI can be connected remotely over an IP connection using a standard telnet
program. Unless requested otherwise, the SVI is delivered with the following default
configuration

TCP-IP Attribute Value
IP Address 192.168.2.100
Netmask 255.255.255.0
Broadcast Address 192.168.2.255

From either a DOS or Terminal command line to telnet into the system enter at the
command line telnet 192.168.2.100. This will open a telnet session on the SVI.
The user will be prompted for a user name and password, use the squire account user
name and password as shown in the previous section. The user needs to now login as
root or administrator. This is done by using the su command. When entered the user
will be prompted for the root password.
4.3.3 BASIC LINUX TERMINAL COMMANDS.
The following provides a brief overview of useful linux commands that allow the user
to navigate and maintain the system.

Command Description
pwd Displays the current working directory
cd Change directory
ls List contents of directory
Ls al Display time date information
mkdir Make new directory
rm Remove file
cp Copy file
mv Move file

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 18/103

4.3.3.1 Manual Pages
To display more information about the above commands and their options use the
man command followed by the command for which more information is required,
man pwd
4.4 STARTUP
When the system is powered up the switch will automatically attempt to bring into
service the switch. The switch is run as a daemon at power up using the standard
Linux init process, which runs the gw start-up script.
4.4.1 CONTROLLING AUTOMATIC STARTUP
To check the status of the gw script, use the chkconfig command. On the
command line, type the following

[ r oot @l ocal host / r oot ] / sbi n/ chkconf i g - - l i st

This will display all current scripts controlled by the init process. If the gw script is
present and started at power up, then the following line will be included in the output
from the chkconfig command.

[ r oot @l ocal host / r oot ] / sbi n/ chkconf i g l i st
gw 0: of f 1: of f 2: of f 3: on 4: on 5: on 6: of f

If the script is present but not started at power up the following will be displayed

[ r oot @l ocal host / r oot ] / sbi n/ chkconf i g l i st
gw 0: of f 1: of f 2: of f 3: of f 4: of f 5: of f 6: of f

4.4.1.1 Stopping Automatic Startup
To stop automatic startup the following is typed at the command line

[ r oot @l ocal host / r oot ] / sbi n/ chkconf i g gw of f

4.4.1.2 Starting Automatic Startup
To start automatic startup the following is typed at the command line

[ r oot @l ocal host / r oot ] / sbi n/ chkconf i g gw on

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 19/103

4.5 MANUALLY CONTROLLING THE SYSTEM
If the user wants to manually start and stop the system the startup script gw can be
controlled from the terminal command line
4.5.1 MANUALLY STARTING THE SYSTEM
To manually start the system, enter the following command.

[ r oot @l ocal host / r oot ] ser vi ce gw st ar t

4.5.2 MANUALLY STOPPING THE SYSTEM
To manually stop the system, enter the following command.

[ r oot @l ocal host / r oot ] ser vi ce gw st op

4.6 POWERING DOWN SYSTEM
The system must be powered down using the command line. The system should not
be powered down by turning off the unit before a controlled shutdown has taken
place. The user can either instruct the system to restart or power down.

To restart the system type at the command line

[ r oot @l ocal host / r oot ] / sbi n/ shut down r now

To halt the system allowing for the unit to be powered off type at the command line

[ r oot @l ocal host / r oot ] / sbi n/ shut down h now

4.7 CHANGING ETHERNET PROPERTIES
To change the Ethernet properties on the system use the netconfig utility.
To run the netconfig utility type the following at the command line.

[ r oot @l ocal host / r oot ] / user / sbi n/ net conf i g

To apply the new configuration either restart the system or at a command prompt type
the command

[ r oot @l ocal host / r oot ] ser vi ce net wor k r est ar t

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 20/103

4.8 CHANGING SYSTEM PASSWORD
To change a username password make sure you are logged in as root. At the
command prompt type the following

[ r oot @l ocal host / r oot ] / usr / bi n/ passwd

The user will be prompted to enter in a new password twice. If the error
BAD PASSWORD: it is based on a dictionary word is displayed ignore and
continue to confirm your password.

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 21/103

5 SYSTEM RESOURCES
The SVIS controls all aspects of the system by abstracting the system down to a
number of resources. These resources are further divided into sub resource types that
describe the operation of a given resource. There are a number of instances of a given
resource and each resource has a number of configurable attributes.
These resources are used to allow the administrator to configure and maintain the
system.
The following table shows the list of resources used within the system.

Resource Types Description
System Entire System
Driver NS700 Driver Driver instance describes and controls
the SS7 signalling cards.
Card NS700 Card The SS7 signalling interface card
Interface SS7 Interface

Defines a PCM physically terminated
on the SS7 signalling card
Originating Point SS7 Originating Point Defines the originating point of the SS7
interconnect
Signalling Link SS7 Signalling Link Defines an SS7 signalling link of an
SS7 interconnect
Linkset SS7 Linkset Defines the Linkset or Adjacent point
of the SS7 interconnect
Destination Point SS7 Destination Point Defines the destination points of an SS7
signalling interconnect
SS7 Stack SS7 Stack Defines the layer 4 protocol
Circuit SS7 Circuit Specifies the SS7 circuits for the SS7
interconnect
Remote Block SS7 Remote Block Indicates the remote block status of a
circuit.
Local Block SS7 Local Block Specifies and controls the local block
status of a circuit.
ASP ASP Defines the characteristics of the
M3UA/M2UA interconnect.
SCTP SCTP Defines an SCTP connection
TS Map TSMAP Controls the PCM timeslot cross
connect
Propagate Propagate Controls the Resource Maintenance
Propagation functionality

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 22/103

All of these resources are arranged into a parent-child hierarchical arrangement. The
following diagram shows the relationship between the main resources within the
system.

The maintenance module within the system uses these associations to determine the
behaviour of a resource. The SVI maintenance system starts from the top of the tree
and works its way down the hierarchical tree starting each resource one by one. A
resource can only be started to be brought into service when its parent is in service
(for example a signalling link is only attempted to be started when its Interface cable
is in service).
If when running a system a given resource does not come into service the user can
look back at the resources parents to see which resources are not in service providing
a speedy way of debugging a system.
System
Driver

Card

Interface
(SS7 Interface)
Signalling Link
(SS7 Signalling
Link)
TSMap Destination
(SS7
Destination)
Local Block Remote Block
Cct
&
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 23/103

6 CONFIGURATION
The configuration of the system is read on start up from an ASCII flat file called
Dbase.cfg, located in directory /home/squire. This configuration file populates the
systems database which is held in volatile RAM. When the system is running the
configuration of the system can be changed by using the OA&M telnet connection
provided into the system.
This section describes the configuration which can be applied for both the ASCII flat
file and through the OA&M Telnet port.
6.1 CONFIGURATION FILE SYNTAX
The syntax for the configuration file is shown below

<Resource><Instance Range><Attribute><Value>
6.1.1 RESOURCE
The resource field contains the name of the resource that is to be configured. See
section System Resources for full resource definition.
6.1.2 INSTANCE RANGE
The instance range contains the instance of the resource that is to be configured. This
field can take a range of instance i.e. 1-3.
6.1.3 ATTRIBUTE
The attribute field is the attribute of the resource that is to be configured. These are
described for each resource within this section.
6.1.4 VALUE
This field contains the value of the attribute. This may be a text string, number or
range of numbers.
If the value is a number the H prefix can be used to describe the number in a
hexadecimal number, i.e. H10
6.1.5 COMMENT
To comment out a line in the ASCII text file the * character is used.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 24/103

6.2 COMMON CONFIGURATION
The following configuration options are common to all systems of the SVIS.
6.2.1 SYSTEM CONFIGURATION
The top level resource is the system resource.
6.2.1.1 Attributes
Attribute Description Values
Status Describes the status of system OSF: Start System
Name Name of the system ASCII String
Type Describes the behaviour of the
system
SS7 Signalling Gateway
Address Local IP Address of the system IP Address string
Partner IP Address of redundant plane IP Address string
Stats Window size Size of wrap around statistics
window for calculating QoS.
16 bit number
Redundant mode Specifying if system is in a
redundant architecture or
standalone
Single (Default)
Redundant
OID Prefix SNMP O.I.D. ASCII String
Username Username for access to MMI
session
ASCII String
Password Password for access to MMI
session
ASCII String

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 25/103

7 SS7 CONFIGURATION
7.1 INTRODUCTION
If you are new to SS7 it may be helpful to read Appendix B SS7 Network
Overview.
The SVI can terminate SS7 signalling using various methods.

Using an onboard signalling-only card
Using a third-party Signalling Gateway.

The type of SS7 termination will determine the SS7 configuration required.
7.1.1 PCM INTERCONNECT
The SS7 board handles the SS7 signalling. The SVI must be configured for the full
SS7 interconnect from MTPL2 upwards. Any bearer channels that are associated on
the terminating PCMs are drop and inserted across to the corresponding E1 on the
other SS7 switch.
7.1.2 SIGTRAN INTERCONNECT
On a SIGTRAN interconnect the signalling PCMS are terminated on a third party SS7
signalling gateway and the SS7 information is backhauled over IP using the SCTP
protocol to the SVI. The SVI currently supports M3UA, M2UA and M2PA adaptation
layers.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 26/103

7.2 CONFIGURING TDM INTERCONNECT
7.2.1 CONFIGURING THE SS7 INTERFACE CARD
The 4 port SS7 interface card provides the signalling and PCM termination for
connection into the SS7 network. The system will be supplied with a minimum of 1
SS7 card, however it may be necessary to deploy additional cards for additional
signalling links or PCM termination.

To set up the card the following resources need to be configured

Driver
Card
Interface
Timing Priority

The following diagram shows the physical association between the three main
resources driver, card and interface.

From this diagram it can be easily seen how quickly additional cards can be added to
the system to enable additional signalling or PCM bandwidth.
Driver 0
NS700 Driver

Card 0
NS700 Card

Card N
NS700 Card

Interface
(N*4)
SS7
Interface
Interface
(N*4)+1
SS7
Interface Interface
(N*4)+2
SS7
Interface Interface
(N*4)+3
SS7
Interface
Interface
0
SS7 Inte

Interface
1
SS7
Interface Interface
2
SS7
Interface Interface
3
SS7
Interface
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 27/103

7.2.1.1 Driver Configuration Syntax
7.2.1.1.1 Attributes
Status Describes the status of system Start: Start Driver
NIU: Driver not present
Type Describes which type of card
this driver is controlling
NS700 Driver
7.2.1.2 Card Configuration Syntax
Status Describes the status of system Start: Start Card
NIU: Card not present
Type Describes the type of card NS700
Driver Indicates the Driver resource
instance that the card is
associated with
0
Download Indicates the Download file
required by the card
NS700
SS7 vxwpcdld002089029.01.s
FPGA NS700 only. Indicates the FPGA
file required by the card
indepdld001134102.mcs
Role This indicates the timing role of
the card with in the system, see
section on configuring timing
A Primary Master
A Slave
Source This indicates the timing source
for a master role clock. It refers
directly to the number of the
port on the card
Port 0
Port 1
Port 2
Port 3
Internal
None
BusType This indicates the type of
Telephony bus used in the
system
MVIP
H100
H110

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 28/103

7.2.1.3 Interface Configuration
7.2.1.3.1 Interface Attributes
Start Start Interface Status Describes the status of system
NIU Resource not
present
Type Describes the type of interface SS7 Interface
SS7 Drop Insert
Card Indicates the Card instance that
this interface is associated to
0-MAX_CARDS
CRC ON CRC Controls CRC
CRC OFF
Electrical Defines the electrical interface E1 75 HDB3
E1 120 HDB3
T1 100 SF B8ZS
T1 100 SF AMI
T1 100 ESF B8ZS
T1 100 ESF AMI
E1 75 AMI
E1 120 AMI
LineLength (T1 Only)
Defines the T1 line build-out
1 =0dB
2 =-7.5dB
3 =-15dB
4 =-22.5 dB
7.2.1.4 Timing Priority Configuration
7.2.1.4.1 Interface Attributes
Start Start Interface Status Describes the status of system
NIU Driver not present
Interface Defines the interface within the
timing priority list
0-MAX_INTERFACES

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 29/103

7.2.2 SETTING UP THE SS7 SYSTEM TIMING
7.2.2.1 System Synchronisation
All circuit switched digital telephony networks need to be fully synchronised against a
common clock. This synchronisation is also referred to as timing. When a systems
timing is synchronised all PCMS will be running at the same frequency and with in
the same phase. To achieve this a system derives its clock from a single timing
source. This source is either from the clock provided on a given PCM or from an
internal clock running on a particular interface card. This source clocks timing is then
distributed to all other PCMs on the system. This method ensures system
synchronisation with the network.
If the system is not synchronised to the network then PCM alignment and speech
problems will occur.

In nearly all cases the SoftSwitch will be synchronising its timing off the SS7
network.
7.2.2.2 Multiple Card Synchronisation
If multiple SS7 cards are within a system one card will be responsible for sourcing the
synchronisation clock. The remaining cards will synchronise their interfaces form the
Telephony bus that connects all of the interface cards together. In a multiple card
arrangement the card that derives the timing is called the Primary Master Clock and
the remaining cards that drive their PCMS from this clock are called Slaves.

The following examples show possible timing scenarios and provides examples of the
configuration file syntax.

Example 1
Single Card
Network Synchronisation
Timing Source Port 1

Dr i ver 0 St at us St ar t
Dr i ver 0 Type NS700

Car d 0 St at us St ar t
Car d 0 Type NS700
Car d 0 Dr i ver 0
Car d 0 Downl oad vxwpcdl d002089029. 01. s
Car d 0 FPGA i ndepdl d001134102. mcs
Card 0 Role A Primary Master
Card 0 Source Port 1

I nt er f ace 0- 3 St at us St ar t
I nt er f ace 0- 3 Car d 0
I nt er f ace 0- 3 CRC CRC Of f
I nt er f ace 0- 3 El ect r i cal E1 120 HDB3
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 30/103

To achieve this timing card 0s role is set to A Primary Master indicating that this
interface board is sourcing the synchronisation clock, and the source attribute is set to
Port 1.

If the system needed to be set up to provide the synchronisation clock from the
internal on board oscillator the configuration file would read

Dr i ver 0 Type NS700 Dr i ver

Car d 0 St at us St ar t
Car d 0 Type NS700
Car d 0 Dr i ver 0
Car d 0 Downl oad vxwpcdl d002089029. 01. s
Car d 0 FPGA i ndepdl d001134102. mcs
Card 0 Role Internal
Card 0 Source none


Example 2
Two Cards
Network Synchronisation on card 1
Timing Source Card 1 Port 2

Dr i ver 0 Type NS700 Dr i ver

Car d 0- 1 St at us St ar t
Car d 0- 1 Type NS700
Car d 0- 1 Dr i ver 0
Car d 0- 1 Downl oad vxwpcdl d002089029. 01. s
Car d 0- 1 FPGA i ndepdl d001134102. mcs

Card 0 Role A Slave
Card 0 Source none

Card 1 Role A Primary Master
Card 1 Source Port 2


In this example card 0 is the slave card and card 1 is the Master card as indicated
above.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 31/103

7.2.3 TIMING FAIL OVER
If the synchronisation source port on the Master card fails for any reason, the whole
system will become unstable because there is no timing source. To prevent this the
system can set up a list of alternative timing source PCMs which the system on failure
of the main timing source, will switch to and source the synchronisation clock from.
These alternative timing sources can be located on either a Master or Slave Card. The
following shows how to achieve a configuration of two clock sources, one on
interface 0 which is on card 0 port 0 and one on interface 4 which is card 1 port 0.

Ti mi ng Pr i or i t y 0 St at us St ar t
Ti mi ng Pr i or i t y 0 I nt er f ace 0

Ti mi ng Pr i or i t y 1 St at us St ar t
Ti mi ng Pr i or i t y 1 I nt er f ace 4

On start up the system will always try to attempt to source the synchronisation clock
from the Card resource configuration, however if one of the alternative timing sources
comes into service first the system will source the timing off this interface.
7.2.4 HANDLING VOICE CIRCUITS ON SIGNALLING PCMS, TSMAP RESOURCE
SS7 allows for the signalling PCM to also carry bearer (voice) channels as well. Any
bearer traffic that is present on the terminating PCMS on the system need to be hard
wired between the two SS7 networks. This is achieved by setting up a number of
timeslot cross connects on the signalling board. This enables PCM timeslots on
network A to be connected directly to the associated PCM timeslot on network B.

The TSMap resource is used to setup these cross connects on the system

SS7
Network
A
30 Bearers +signalling
Switching
Matrix HDLC
30 Bearers +signalling
SS7
Network
B
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 32/103

7.2.4.1 Attributes
Start Bring in service Status Describes the status of the resource
NIU

Resource not present
Type Describes the type of the driver for
which the originating switch request
should be made
NS700 TsMap
Card Specifies the originating card for
which the 64Kbit timeslot is
originating on
0 to MAX CARDS
On Duplex Duplex Specifies whether the switch connect
is a duplex or simplex connection
(i.e. both way or one way connection)
Off Simplex
SrcType Defines the type of the source of the
64Kbit timeslot
H100
E1Interface
HDLCController
H100 Stream of the
H100 bus
SrcStream Value depends on the SrcType
E1Interface Resource
interface
instance
H100 0-127 SrcTimeslot Defines the source timeslot
dependant on the SrcType
E1Interface 0-31
DestType Defines the type of the destination of
the 64Kbit timeslot
H100
E1Interface
H100 Stream of the
H100 bus
DestStream Value depends on the DestType
E1Interface Resource
interface
instance
H100 0-127
E1Interface 0-31

DestTimeslot Defines the destination timeslot
dependant on the DestType

Each interface card has on board a switching matrix that enables any timeslot on any
stream (TDM, HDLC Controllers and Telephony buses) to be connected to any other
timeslot on any other stream.

The following diagram shows how the streams are connected to a central Switching
Matrix allowing for cross connect of 64Kbit channels between the different resources.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 33/103

The resources are therefore set up to instruct a cards switching matrix to connect an
incoming timeslot/stream to an outgoing timeslot/stream.

Example

Form Cross Connect between Port 0 bearer timeslots to Port 2 bearer timeslots.

TsMap 1- 31 St at us St ar t
* do not connect si gnal l i ng t i mesl ot
TsMap 16 St at us Ni u
TsMap 1- 31 NS700 TsMap
TsMap 1- 31 Car d 0
TsMap 1- 31 Dupl ex 1
TsMap 1- 31 sr ct ype E1I nt er f ace
* E1 i nt er f ace por t 0
TsMap 1- 31 sr cst r eam 0
TsMap 1- 31 sr ct i mesl ot 1- 31
TsMap 1- 31 dest t ype E1I nt er f ace
*E1 i nt er f ace por t 2
TsMap 1- 31 dest st r eam 2
TsMap 1- 31 dest t i mesl ot 1- 31

TDM Interfaces
H100/MVIP Telephony Bus
Switching
Matrix
HDLC
Controller
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 34/103

7.2.5 CONFIGURING THE SS7 INTERCONNECT
The SVI uses the concepts of SS7 blocks as described in Appendix A to match with
the SVIs resources to provide a simple way of configuring the SS7 interconnect. The
following sections list the available resources and their attributes.
7.2.5.1 Originating Point Resource syntax
The originating point resource contains the configuration of the originating points on
the unit. The system can handle multiple originating points.
7.2.5.2 Attributes
Status Describes the status of
originating point
OSC: Start Resource
NIU: Resource not present
Type Describes the type of resource SS7 Originating Point
Pointcode Contains the originating
pointcode
32 bit number
Ni Network Indicator of the route 2 bit number
0 International
1 Spare (for International Use
only)
2 National
3 Reserved for National Use
Protocol Contains the MTPL3 protocol
variant
ETSI (default)
ANSI
Chinese
STPMode Activates the partial MTP mode None (default)
Partial
Setdebug Sets the debug level of the STP 32 bit, bit mask allowing for
display of MTP FSM levels
0x0000 TLAC
0x0001 TCOC
0x0002 TCBC
0x0004 SLTC
0x0008 LSAC
0x0010 HMRT
0x0020 HMDT
0x0040 SQAPI

7.2.5.3 Signalling Link Resource Syntax
The signalling link carries the 64Kbit/s signalling channel.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 35/103

7.2.5.4 Attributes
OSC Start Signalling Link Status Describes the status of the
signalling link
NIU

Signalling link not
Present
Type Describes the type of signalling link SS7 Signalling Link
ANSIISUP Signalling Link
Interface Specifies the instance of the
interface resource that the signalling
link will be located on
8 bit number
Timeslot Specifies the signalling timeslot 0-31
Slc Specifies the signalling link code of
the signalling link
0-15
Linkset Indicates the instance of the linkset
resource for which this linkset is
associated to
8 bit number
Originating Specifies the instance of the
originating point resource to which
the signalling link is associated to
8 bit number
Transmission Rate (T1 Links only)
Specifies the Signalling Link
Transmission rate
64K (default)
56K
Interface ID For SIGTRAN interconnects this
specifies the M2UA Interface ID
16 bit number
Stream For M2UA specifies the SCP
stream the M2UA uses
8 bit number default 1
SLT Type For ANSI interconnects specifies
the type of SLTM to be sent at layer
3
Regular
Special
Protocol For SIGTRAN interconnects
specifies the adaptation layer used
M2PA
M2UA
M3UA
7.2.5.5 Linkset Resource Syntax
The linkset resource specifies the adjacent point of the SS7 interconnect
7.2.5.6 Attributes
OSF Linkset Present Status Describes the status of the linkset
NIU

Signalling link not
Present
Type Describes the type of signalling link SS7 Linkset
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 36/103

Originating Specifies the instance of the originating
point resource that the linkset is
associated to
8 bit number
Pointcode Pointcode of the adjacent point 32 bit number
Ni Network indicator of the adjacent point 2 bit number
0 International
1 Spare (for International
Use only)
2 National
3 Reserved for National
Use
Combined If the linkset is part of a combined
linkset this value is set to the resource
instance of the combined linkset, else it
is set to the value of this linksets
instance
8 bit number
Add Transfer
Report
Specifies the destination points that
need to be reported available via the
TFP/TFA message to the adjacent
linkset
List of destination points
TFx Required If this is set to True the destinations
route that is accessible from this linkset
will require reception of a TFA before
it will come into service
True
False
7.2.5.7 Destination Point Resource Syntax
The Destination Point resource identifies the termination point of the voice circuits.
This may be the same as the adjacent points for SP and SSP interconnects or for STP
interconnect this may be different from the adjacent point.
7.2.5.8 Attributes
OSFD Bring in destination Status Describes the status of the
signalling link
NIU

Destination point not
present
Type Describes the type of
destination point
SS7 Destination Point
Pointcode Contains the pointcode of the
destination point
32 bit number
Ni Contains the Network Indicator
of the destination point
2 bit number
0 International
1 Spare (for International Use
only)
2 National
3 Reserved for National Use
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 37/103

Primary This indicates the primary
linkset that the destination is
connected to
8 bit number
Secondary If a linkset is connected to a
secondary linkset this attribute
contains the linkset resource
instance which is the secondary
route
8 bit number
originating point that the
destination is associated to
8 bit number
Loadshare Specifies if the destination has a
combined linkset if it should
loadshare across the combined
linkset.
True
False
7.2.6 CONFIGURATION EXAMPLES
The following sections provide an explanation of how to configure the system.
Note that these examples are for ITU ISUP. Please refer to the Type field reference
of each Resource to adjust each resource for ANSI ISUP.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 38/103

7.2.6.1 Interconnect to single SSP
Two signalling links F link interconnect
o SLC 0 on interface 0, timeslot 16
o SLC 1 on interface 1, timeslot 16
SoftSwitch originating point code 1111
SS7 Switch destination point code 2222

Because this is a F link interconnect the above configuration can be represented in
the following diagram.

In this type of configuration the voice circuits are resident on the same equipment as
the adjacent point, therefore that adjacent point has the same point code as the
destination point. To configure this arrangement the following configuration syntax is
used.

* Set up or i gi nat i ng poi nt of t he SVI Sof t Swi t ch
Or i gi nat i ng Poi nt 0 St at us St ar t
Or i gi nat i ng Poi nt 0 St ack 0
Or i gi nat i ng Poi nt 0 Dr i ver 0
Or i gi nat i ng Poi nt 0 Type I SUP Or i gi nat i ng Poi nt
Or i gi nat i ng Poi nt 0 Poi nt Code 1111
Or i gi nat i ng Poi nt 0 NI 2

Si gnal l i ng Li nk 0- 1 St at us St ar t
Si gnal l i ng Li nk 0- 1 Type I SUP si gnal l i ng Li nk
Si gnal l i ng Li nk 0- 1 I nt er f ace 0- 1
Si gnal l i ng Li nk 0- 1 t i mesl ot 16
Si gnal l i ng Li nk 0- 1 sl c 0- 1
Si gnal l i ng Li nk 0- 1 Or i gi nat i ng 0
Si gnal l i ng Li nk 0- 1 Li nkset 0
Si gnal l i ng Li nk 0- 1 map 0- 1

*Set up up t he adj acent poi nt / l i nkset
Li nkset 0 St at us St ar t
Li nkset 0 Or i gi nat i ng 0
Li nkset 0 Poi nt Code 2222
Li nkset 0 NI 2

Dest i nat i on Poi nt 0 St at us St ar t
Dest i nat i on Poi nt 0 Type I SUP Dest i nat i on Poi nt
Dest i nat i on Poi nt 0 Poi nt Code 2222
Dest i nat i on Poi nt 0 NI 2

Adjacent
Point 0
Originating
Point 0
Destination
Point 0
SLC 0
SLC 1
OPC 1111 DPC 2222

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 39/103

7.2.6.2 Interconnect to 2 SSPs
SSP 0
o Point code 2222
o Two signalling links
SLC 0, interface 0 timeslot 16
SSP 1
o Point code 3333
o Two signalling links
SLC 1, interface 2, timeslot 1

To change the original configuration to add a new SSP interconnect the following
would be added to the configuration file for the second SSP.
Si gnal l i ng Li nk 2- 3 St at us St ar t
Si gnal l i ng Li nk 2- 3 Type I SUP si gnal l i ng Li nk
Si gnal l i ng Li nk 2- 3 Or i gi nat i ng 0
Si gnal l i ng Li nk 2- 3 Li nkset 1
Si gnal l i ng Li nk 2- 3 I nt er f ace 2- 3
Si gnal l i ng Li nk 2- 3 t i mesl ot 1
Si gnal l i ng Li nk 2- 3 sl c 1- 2
Si gnal l i ng Li nk 2- 3 map 2- 3

*Set up up t he adj acent poi nt / l i nkset
*show t hat l i nkset i s not combi ned wi t h anot her l i nkset by set t i ng
*t he combi ned at t r i but e t o t he same val ue as t hi s r esour ces i nst ance
Li nkset 1 combi ned 1
Li nkset 1 NI 2

Dest i nat i on Poi nt 1 Type SS7 Dest i nat i on Poi nt
*i ndi cat e whi ch i nst ance of t he l i nkset r esour ce
* t he dest i nat i on i s associ at ed wi t h
Dest i nat i on Poi nt 1 Pr i mar y 1

Adjacent
Point 0
Originating
Point 0
Destination
Point 0
SLC 0
SLC 1
OPC 1111 DPC 2222

Adjacent
Point 1
Destination
Point 1
SLC 0
SLC 1
DPC 3333
TDM
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 40/103

7.2.6.3 Interconnect to two STPs
STP 0
o Point code 2222
o One Linkset with Two signalling links
STP 1
o Point code 3333
o One Linkset with Two signalling links
SSP 0
o Point Code 4444
o Terminates the bearer circuits for the SVIs provisioned Cics

Or i gi nat i ng Poi nt 0 St ack 0
Or i gi nat i ng Poi nt 0 Dr i ver 0
Or i gi nat i ng Poi nt 0 Type I SUP Or i gi nat i ng Poi nt
Or i gi nat i ng Poi nt 0 Poi nt Code 1111
Or i gi nat i ng Poi nt 0 NI 2

Si gnal l i ng Li nk 0 St at us St ar t
Si gnal l i ng Li nk 0 Type I SUP si gnal l i ng Li nk
Si gnal l i ng Li nk 0 I nt er f ace 0
Si gnal l i ng Li nk 0 t i mesl ot 16
Si gnal l i ng Li nk 0 sl c 0
Si gnal l i ng Li nk 0 Or i gi nat i ng 0
Si gnal l i ng Li nk 0 Li nkset 0
Si gnal l i ng Li nk 0 map 0

Si gnal l i ng Li nk 1 St at us St ar t
Si gnal l i ng Li nk 1 Type I SUP si gnal l i ng Li nk
Si gnal l i ng Li nk 1 Or i gi nat i ng 0
Si gnal l i ng Li nk 1 Li nkset 1
Si gnal l i ng Li nk 1 I nt er f ace 1
Adjacent
Point 0
DPC 2222
Originating
Point 0
SSP 0
DPC 4444
SLC 0
OPC 1111
Adjacent
Point 1
DPC 3333
SLC 0
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 41/103

Si gnal l i ng Li nk 1 t i mesl ot 16
Si gnal l i ng Li nk 1 sl c 0
Si gnal l i ng Li nk 1 map 1

*Set up up t he f i r st adj acent poi nt / l i nkset
*i ndi cat e t hat l i nkset i s combi ned wi t h
*anot her l i nkset by set t i ng t he combi ned at t r i but e t o t he
*ot her r esour ce' s i nst ance
Li nkset 0 NI 2

Dest i nat i on Poi nt 0 Type I SUP Dest i nat i on Poi nt
Dest i nat i on Poi nt 0 Secondar y 1

*Set up up t he second adj acent poi nt / l i nkset
*i ndi cat e t hat l i nkset i s combi ned wi t h
*anot her l i nkset by set t i ng t he combi ned at t r i but e t o t he
*ot her r esour ce' s i nst ance
Li nkset 1 NI 2

Dest i nat i on Poi nt 1 St at us st ar t

** Add dest i nat i on poi nt of t he swi t ch car r yi ng t he ci cs.

** Not e t hat Ci r cui t Resour ces must have t hei r opc and dpc val ues set
** t o t he cor r ect DPC ( i e t he DPC of t he swi t ch wher e t hei r bear er
** ci r cui t s t er mi nat e)

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 42/103

7.3 SETTING UP A SIGTRAN INTERCONNECT
In this scenario, the SS7 is backhauled from the carrier interconnect over IP using the
SIGTRAN range of protocols. The SVI supports different adaptation layers including
M2UA, M2PA and M3UA. Depending on the interconnect required will depend on
the adaptation layer used.

For a SIGTAN interconnect common resources are used for each of the adaptation
layers, these are specified below.
7.3.1 SETTING UP SCTP CONNECTION
7.3.1.1 SCTP Resource Syntax
The SCTP resource syntax sets up the SCTP connection between two end points.
Start Bring resource into service Status The Status of SCTP at SVI
startup
NIU Resource not present
ASP Contains the instance of the
ASP resource for which the
SCTP connection is associated
to.
0 to MAX_ASP
Local port Contains the local port of the
SCTP socket
16 bit number, default 2905
Local address Contains the local address of the
SCTP socket (i.e. address of the
SVI)
ASCII string
Remote port Contains the remote port of the
SCTP socket
Remote address Contains the remote address of
the SCTP socket (ie the Media
Gateways address)
ASCII string
Incoming Streams The number of incoming
streams used on the ASP
connection
SS7
Network
SVI 9220
SS7 over IP SIGTRAN
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 43/103

Outgoing Streams The number of outgoing
streams used on the ASP
connection
End Specifies if the SCTP is a client
or server end
Server
Client
Protocol Adaptation layer used on SCTP
connection
M2PA
M2UA
M3UA
Multihomed local
Address
For multi-homed systems this
specifies the IP address of the
SVI
IP Address
Multihomed
remote Address
For multi-homed systems this
specifies the IP address of the
car end
IP Address
7.3.1.2 ASP Resource Syntax
This resource defines the ASP over the SCTP socket.
Start Bring resource into service Status The Status of the ASP at SVI
startup
Type Describes the type of this
resource
M3UA ASP
IsupIP The instance of the ISUP IP
resource associated with this
ASP
0-MAX_IP
SCTP The instance of the SCTP
resource associated with this
SCTP
0-MAX_SCTP
Protocol The Adaptation layer running
on the ASP
M2PA
M2UA
M3UA
End Indicates if the ASP is a client
or server end
Server
Client
AS Specifies the ASs that are
associated with this ASP
0 MAX_AS
7.3.1.3 AS Resource Syntax
This specifies the AS part of the SIGTRAN interconnect.
Status The Status of the AS at SVI Start Start AS
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 44/103

startup NIU Resource not present
Type Describes the type of this
resource
M3UA AS
Originating Point Defines which originating point
this AS is associated to (M3UA)
8 bit number
Destination Point Defines which destination point
this AS is associated to (M3UA)
8 bit number
IP Resource The instance of the ISUP IP
resource associated with this AS
(M3UA)

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 45/103

7.3.2 CONFIGURING M3UA INTERCONNECT
Setup of an M3UA interconnect on the system is very simple. The resources that are
used to configure an M3UA interconnect are:-

SCTP
ASP
AS
Originating point
Destination point

The SS7 circuits on this interconnect are configured as described in the next section.
The following diagram shows the association between these resources

7.3.2.1 Originating Point Resource syntax
The originating point resource contains the configuration of the originating points of
the unit. The system can handle multiple originating points.
originating point at startup
INS: Start Resource
Driver The NS700 Driver Instance 0
Type Describes the type of resource SIGTRAN Originating Point
Pointcode Contains the originating
pointcode
32 bit number
NI Network Indicator of the route 2 bit number
Originating Point
Destination
Point
Driver
ASP
AS
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 46/103

7.3.2.2 Destination Point Resource Syntax
The Destination Point resource identifies the termination point of the voice circuits.
This may be the same as the adjacent points (for SP and SSP interconnects), or for
STP interconnect this may be different from the adjacent point.
OSFD Bring in destination Status Describes the status of the
destination point at startup
NIU

Destination point not
present
destination point
ISUP Destination Point
Pointcode Contains the pointcode of the
destination point
32 bit number
Ni Contains the Network Indicator
of the destination point
2 bit number
Primary This indicates the primary
linkset that the destination is
connected to
8 bit number
Secondary If a linkset is connected to a
secondary linkset this attribute
contains the linkset resource
instance which is the secondary
route
8 bit number
originating point that the
destination is associated to
8 bit number
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 47/103

7.3.3 ISUP IP RESOURCE SYNTAX
The IP Resource is a local connection to an ISUP Stack process running on the SVI.

originating point at startup
OSC: Start Resource
Name A Unique Name ISUP Skt
Type Describes the type of resource Telnet IP
SocketType IP Socket Type Server
PacketOwner The owner task M3UA
MntOwner The task that maintains the
socket
Maintenance
Packaged Fixed
Port The IP Port to listen on 3020
7.3.4 EXAMPLE CONFIGURATION
The following example sets up the SVI to communicate with a SIGTRAN M3UA
Media Gateway with the following requirements.

One M3UA connection to 192.168.2.229
SVI IP address 192.168.2.235
2 incoming and outgoing streams
Originating point code 1000
Destination point code 2000

*Set up M3UA i nt er connect
Dr i ver 0 st at us St ar t
Dr i ver 0 t ype ns700 dr i ver

Or i gi nat i ng Poi nt 0 Type SI GTRAN Or i gi nat i ng Poi nt
Or i gi nat i ng Poi nt 0 poi nt code 1000
Or i gi nat i ng Poi nt 0 ni 2
Or i gi nat i ng Poi nt 0 dr i ver 0

Dest i nat i on Poi nt 0 st at us St ar t
Dest i nat i on Poi nt 0 t ype i sup dest i nat i on poi nt
Dest i nat i on Poi nt 0 poi nt code 2000
Dest i nat i on Poi nt 0 ni 2
Dest i nat i on Poi nt 0 or i gi nat i ng 0

SCTP 0 St at us St ar t
SCTP 0 l ocal addr ess 192. 168. 2. 235
SCTP 0 r emot e addr ess 192. 168. 2. 229
SCTP 0 l ocal por t 2905
SCTP 0 r emot e por t 2905
SCTP 0 ASP 0

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 48/103

ASP 0 St at us St ar t
ASP 0 Or i gi nat i ng Poi nt 0
ASP 0 I supI P 4
ASP 0 SCTP 0

AS 0 St at us St ar t
AS 0 Or i gi nat i ng Poi nt 0
AS 0 Dest i nat i on Poi nt 0
AS 0 I P Resour ce 4

I P 4 St at us St ar t
I P 4 name I SUP skt
I P 4 t ype t el net i p
I P 4 Socket Type Ser ver
I P 4 Packet Owner SCTP
I P 4 Mnt Owner Mai nt enance
I P 4 packaged Fi xed
I P 4 Por t 3020

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 49/103

7.3.5 CONFIGURING M2UA INTERCONNECT
Setup of an M2UA interconnect on the system requires the addition of setting up the
MTPL2 and MTPL3 resources. The relevant resources that are used to configure an
M2UA interconnect are:-

SCTP
ASP
AS
Originating point
Signalling Link
Linkset
Destination point

The SS7 circuits on this interconnect are configured as described in the next section.
The following diagram shows the association between these resources

To configure the SCTP refer to the SCTP section of this document to configure the
MTPL2 and MTP L3 refer to the Configuring SS7 Interconnect Section.

Originating Point
Linkset
Driver
ASP
AS
Signalling
Links
SCTP
Destination
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 50/103

7.3.6 CONFIGURING M2PA INTERCONNECT
Setup of an M2PA interconnect on the system is the same as the M2UA interconnect
apart from setting up the protocols on the SCTP and ASP to be M2PA instead of
M2UA
7.4 SS7 STACK
The SS7 Stack resource specifies the SS7 layer 4 protocol stack that is used for an
interconnect. A stack instance specifies a routeset between an originating point and a
destination point.
7.4.1 ATTRIBUTES
OSC Bring in service Status Describes the status of the
resource
NIU

resource
SS7 Stack
Originating Point Contains Originating point
resource instance
8 bit number
Destination Point Contains Destination point
resource instance
8 bit number
Protocol Indicates layer 4 protocol ITUT_ISUP
ETSI_ISUP
ANSI_ISUP
BTNUP
UKISUP
CHINA_TUP
TUP
Variant Indicates layer 4 variant ITUT_BLUE (Default TUP)
ITUT_WHITE (Default ITUT_ISUP)
ETSI_V1
ETSI_V2
ETSI_V3 (Default ETSI_ISUP)
SWISS
MEXACO
MALTESE
PAKISTAN
RUSSIA

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 51/103

7.5 SS7 VOICE CIRCUIT RESOURCE SYNTAX
The voice circuits are the bearer channels that are located on the PCMs terminating on
the SVI, or direct between the two SS7 interconnects.
7.5.1 ATTRIBUTES
OSC Bring in service Status Describes the status of the
resource
NIU

Type Describes the type of resource ISUP Circuit
Interface Only needs to be set if the circuit
terminates on an interface
located on the SVI
8 bit number
CIC Contains the Circuit Identifier
Code for this circuit
16 bit number
End Indicates if the circuit controls,
owns or has priority of this
circuit. For odd/even, the
individual circuit will be set
according to whether it is odd or
even.
Controlling
Non Controlling
Even Controlling
Odd Controlling
Stack For multiple stack systems this
indicates the originating point
that the circuit is associated with
8 bit number
Map Index of circuit into protocol
stack
16 bit number
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 52/103

7.6 CONFIGURATION EXAMPLES
The following section describes using examples how to construct configuration of the
media gateways.
7.6.1 SINGLE MEDIA GATEWAY CONNECTED TO 4 TDM PCMS
4 E1 Interconnect
o 2 E1s with signalling, timeslot 16 used SLC 0 and SLC 1
o CIC range 1-127
o Network A
ETSI ISUP V2
o Network B
ANSI ISUP

* SS7 St ack Net wor k A
SS7 St ack 0 St at us St ar t
SS7 St ack 0 t ype SS7 St ack
SS7 St ack 0 pr ot ocol ETSI _I SUP
SS7 St ack 0 var i ant ETSI _V2
SS7 St ack 0 or i gi nat i ng poi nt 0
SS7 St ack 0 dest i nat i on poi nt 0

* Set up SS7 ci r cui t s Net wor k A
ci r cui t 1- 127 St at us St ar t
ci r cui t 1- 127 t ype I SUP Ci r cui t
ci r cui t 1- 127 CI C 1- 127
ci r cui t 1- 31 I nt er f ace 0
ci r cui t 1- 127 st ack 0

*r emove ci r cui t s t hat ar e associ at ed wi t h t i mesl ot 0 and
*t i mesl ot 16 on t he PCM i nt er f aces.
Ci r cui t 0 st at e Ni u

SS7
Network
B

SS7
Network
A
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 53/103

* SS7 St ack Net wor k B
SS7 St ack 1 St at us St ar t
SS7 St ack 1 t ype SS7 St ack
SS7 St ack 1 pr ot ocol ANSI _I SUP
SS7 St ack 1 or i gi nat i ng poi nt 1
SS7 St ack 1 dest i nat i on poi nt 1

* Set up SS7 ci r cui t s Net wor k A
ci r cui t 1001- 1127 St at us St ar t
ci r cui t 1001- 1127 t ype I SUP Ci r cui t
ci r cui t 1001- 1127 CI C 1- 127
ci r cui t 1001- 1127 Map 1- 127
ci r cui t 1001- 1127 st ack 1

*r emove ci r cui t s t hat ar e associ at ed wi t h t i mesl ot 0 and
*t i mesl ot 16 on t he PCM i nt er f aces.

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 54/103

8 MTP ROUTING
MTP Routing can be setup on the SVI to route at the MTP L3 layer between different
networks and different protocols depending on originating of the SS7 messages and
the information contained within the SS7 routing label. The routing label can then be
translated if required and the SS7 messages re-routed out onto another destination.

8.1 MTP ROUTING RESOURCE SYNTAX
To provide MTP routing the following attributes of the MTP Route resource can be
setup to control the routing. Multiple routing tables are setup to capture a unique
combination of routing label to determine the actions upon the message which
matches the routing table instance.
8.1.1 ATTRIBUTES
Start Bring in service Status Describes the status of the
resource
NIU


OPC Specifies the originating point
code of the incoming routing
label
32 bit number
Set to Not Present if not used
DPC Specifies the destination point
code of the incoming routing
label
32 bit number
Set to Not Present if not used
SS7
Network
OPC B
SS7
Network
OPC C
SS7
Network
OPC D
SS7
Network
OPC A

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 55/103

NI Specifies the network indicator
of the incoming routing label
8 bit number
Set to 255 if not used
SIO Specifies the SIO of the
incoming routing label
8 bit number
Set to 255 if not used
Linkset Specifies the incoming linkset
that the message arrives in on
0 (MAX_LINKSETS-1)

Set OPC If required this will over write
the incoming OPC of the out
going SS7 routing label.
32 bit number
Set DPC If required this will over write
the incoming DPC of the out
going SS7 routing label.
32 bit number
Set NI If required this will over write
the incoming NI of the out going
SS7 routing label.
8 bit number
Route This specifies the primary
linkset that the SS7 message will
be routed to
0 MAX_LINKSETS-1
Secondary This specifies the secondary
linkset that the SS7 message will
be routed to
0 MAX_LINKSETS-1
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 56/103

9 SCCP ROUTING
SCCP Routing can be setup on the SVI to route at the SCCP layer between different
networks and different SCCP protocols depending on originating of the SS7 messages
and the information contained within the SCCP routing label. The routing label can
then be translated if required and the SCCP messages re-routed out onto another
destination.
9.1 SCCP ROUTING RESOURCE SYNTAX
To provide SSCP routing the following attributes of the SSCP DB resource can be
setup to control the routing. Multiple routing tables are setup to capture a unique
combination of routing label to determine the actions upon the message which
matches the routing table instance.
9.1.1 ATTRIBUTES
Start Bring in service Status Describes the status of the resource
NIU

Cdpn Defines the called party number NULL Terminated ASCII
string
Cdpnnoa Defines the called party nature of
address

Subscriber
National
International
Unknown
National specific
CdpnRoutingInd
Matches the Called Party Routing
Indication
Route on SSN
Route on Global Title
CdpnPointCode
Matches the Called Party Signalling
Point Code.
If present just checks that a PC is
present, not the value
Present /
32-bit number
CdpnSSN
Matches the Called Party Sub-System
Number
8 bit number
CdpnGTI
Matches the Called Party Global Title
Indicator
8 bit number.
This is in ITU GTI format.
CdpnEncodingSch
eme

Matches the Called Party encoding
scheme
Unknown
BCD
National
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 57/103

CdpnNational
Matches the National flag
National
International
CdpnNumberingPl
an

Matches the Called Party Numbering
Plan
Unknown
ISDN
Generic
Data
Telex
Maritime
Mobile
Land Mobile
ISDN/mobile
CdpnTranslationT
ype

Matches the Called Party Translation
Type
8 bit number
Cgpn Defines the calling party number NULL Terminated ASCII
string
Cgpnnoa Defines the calling party nature of
address

Subscriber
National
International
Unknown
National specific
CgpnRoutingInd Matches the Calling Party Routing
Indication
Route on SSN
CgpnPointCode Matches the Calling Party Signalling
Point Code.
If present just checks that a PC is
present, not the value
Present /
32-bit number
CgpnSSN Matches the Calling Party Sub-System
Number
8 bit number
CgpnGTI Matches the Calling Party Global Title
Indicator
8 bit number.
CgpnEncodingSch
eme
Matches the Calling Party encoding
scheme
Unknown
BCD
National
CgpnNational Matches the National flag National
International
CgpnNumberingPl
an
Matches the Calling Party Numbering
Plan
Unknown
ISDN
Generic
Data
Telex
Maritime
Mobile
Land Mobile
ISDN/mobile
CgpnTranslationT
ype
Matches the Calling Party Translation
Type
8 bit number

Action Criteria
CDPNstrip Strips n digits of the prefix
of a called party number
Integer
CDPNprefix Adds defined digits to end
of called party number
ASCII String
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 58/103

SetCDPNnoa Sets the called party
number nature of address
Subscriber
National
International
Unknown
National specific
CGPNstrip Strips n digits of the prefix
of a calling party number
Integer
CGPNprefix Adds defined digits to start
of calling party number
ASCII String, or range value see
section 11.6.2
ASCII String
SetCGPNnoa Sets the calling party
Subscriber
National
International
Unknown
National specific
Route Specifies the MTP L3
destination the outgoing
SCCP message needs to be
routed to
0-MAX_DESTINATIONS-1
SetCdpnRoutingInd Sets the Called Party
Routing Indication
Route on SSN
SetCdpnPointCode Sets the Called Party
Signalling Point Code.
If present just checks that
a PC is present, not the
value
Present /
32-bit number
SetCdpnSSN Sets the Called Party Sub-
System Number
8 bit number
SetCdpnGTI Sets the Called Party
Global Title Indicator
8 bit number.
SetCdpnEncodingScheme Sets the Called Party
encoding scheme
Unknown
BCD
National
SetCdpnNational Sets the National flag
ANSI only
National
International
SetCdpnNumberingPlan Sets the Called Party
Numbering Plan
Unknown
ISDN
Generic
Data
Telex
Maritime
Mobile
Land Mobile
ISDN/mobile
SetCdpnTranslationType Sets the Called Party
Translation Type
8 bit number
Cdpnnoa Specifies the incoming
Called Party Number NOA
Spare
Subscriber
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 59/103

10 SETTING UP CALL ROUTING
Once the SVI SoftSwitch has all of the hardware and protocol configuration done the
system requires routing configuration to be added to the system to allow for the
routing of calls and SCCP messages from one destination to another.

To achieve routing the TDM circuits are grouped in hunt groups. Routing Criteria
plans are then configured which determine on how an incoming call is to be routed.

This criteria can be on the called or calling party digits, originating hunt group, time
of day, type of call or a combination of these criterias. Once a criteria has been
matched an outgoing call to the required hunt group can be made or the call rejected.
Both digit and protocol parameter manipulation can be done on both the incoming and
outgoing leg of the call.

10.1 HOW THE SVI MAKES A ROUTING DECISION
The SVI will first look through the list of configured Routing Criteria. For each one, it
tries to match the incoming call against each DB Parameter resource set in the
Routing Criteria matchDB attribute. When it finds the best match it will either use
the route set in the Db Parameters Add Route attribute, or if that is not set, it will
use the route set in the Routing Criterias Add Route attribute.
The SVI now has an outgoing hunt group to use. Before it makes the call to the
Circuits in that hunt group, it will apply the settings in the Hunt Groups MatchDB
attribute. It then makes the call.

Find Routing
Criteria/ Db
Parameter
using match
DB attribute
Call / SCCP message
Reject Call / message
Apply settings of
best match Db
Parameter and set
outgoing hunt group
Apply settings of
Db Parameter from
Hunt Groups Match
Db attribute
Make call using
outgoing Hunt
Group
Call / SCCP message
Reject Call Due to congestion
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 60/103

10.2 CONFIGURING HUNT GROUPS
To allocate a number of circuits to a hunt group the following resource needs to be
configured.

Hunt Group
10.2.1 HUNT GROUP SYNTAX
This resource groups a number of outgoing routes into a group to specify the outgoing
route.
Add Circuit Adds a range of circuits to the hunt
group. Circuits listed in the hunt group
in order.
(previous syntax AddCircuit will still be accepted)
NULL ASCII string
defining instance of
circuit resource
Algorithm Defines hunting algorithm for circuit
based hunt group.
DropInsert
OddEven Allows the hunting algorithm to run
over odd or even entries in the hunt
group
Odd
Even
Normal (Default)
MatchDB Specifies the instance range of the
Parameter Database resource that is to
be applied to this hunt group for digit
and protocol manipulation
Character string
containing numerical
range
CongestionTimer If set this allows for a call to be held for
n seconds within the hunt group to wait
for an outgoing circuit to become free
before rejecting the call
8 bit number seconds
MaximumCalls This defines the maximum number of
calls that can be made on this hunt
group.
16 bit number

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 61/103

10.3 HUNT GROUP CONFIGURATION EXAMPLES
10.3.1 TDM HUNT GROUP
The following shows a TDM hunt group with the following criteria
Add circuit resource 1-127
Using the drop and insert algorithm

*Set up TDM Hunt Gr oup
Hunt Gr oup 0 St at us I ns
Hunt Gr oup 0 Add Ci r cui t 1- 127
Hunt Gr oup 0 Al gor i t hm Dr opI nser t
Hunt Gr oup 0 OddEven Nor mal

Hunt Gr oup 1 Add Ci r cui t 1001- 1127
Hunt Gr oup 1 Al gor i t hm Dr opI nser t
Hunt Gr oup 1 OddEven Nor mal

10.3.2 SCCP HUNT GROUP
The SCCP routing function routes on MTP label, but it will automatically modify
called/calling party pointcodes, and can be set to change any of the parameters in the
called/calling party SCCP parameters.
SCCP Hunt Groups are set up by adding defined SS7 Destination Resources to a hunt
group
*Set up SCCP Hunt Gr oup
Hunt Gr oup 1 Add SCCPDest i nat i on 7

10.4 SETTING UP ROUTING CRITERIA
The routing criteria determines, for a given set of matching criteria, what the action
criteria should be for an individual call. The routing criteria uses the parameter
database resource to determine if an incoming call matches this criteria. The
parameter database allows for the setup of the following matching criteria

Called Party Number
Calling Party Number
Hunt Group
Type of Call

A match can be made against single or multiple matching criterias. Once a match has
been made against a particular parameter database entry actions can be carried out on
the call information, these include

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 62/103

Stripping Digits
Prefixing Digits
Overwriting digits
Changing protocol parameters.

Once the routing criteria has been selected either the call can be rejected with a
specified reject reason or the call is routed out on a TDM based hunt group. Up to two
alternative hunt groups can be defined in the case of call rejection or congestion.

Options for Authentication of callers, Authorisation of calls and Accounting for calls
can also be set in the Routing Criteria.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 63/103

ROUTING CRITERIA SYNTAX
MatchDb Specifies the parameter control resources
instance range over which the routing
criteria needs to be matched
ASCII String
Add Route Adds outgoing route to routing criteria
(previous syntax Add Routes will still be accepted)
0-MAX Hunt Groups
Reject Cause If this is set the call will be rejected with
the cause set in the value of this attribute
Integer
CDR Specifies the CDR format type. CDROff
Type 1
Type 2
Type 3
SUITIUS
CDRName Specifies the name of the CDR file to be
added to.
ASCII String
CDRInterval Interval between writing a new CDR file Daily
Hourly
Local Congestion
Cause
The Cause for calls to be cleared with if
local congestion (no routing criteria) is
encountered
Q850 cause value
Remote Congestion
Cause
The Cause for calls to be cleared with if
remote congestion (all routes busy or no
routes available) is encountered
Q850 cause value
Maximum Calls The maximum number of simultaneous
incoming calls allowed on this Routing
Criteria
Integer
Authentication/
Authorisation Settings

Radius AA The Authentication Method. Internal
relies on a list of subscribers entered into
the Dbase.cfg file.
External authenticates the caller using the
RADIUS server specified in the AA
Server attribute.
Internal
External
AA Server The Radius Server Resource to be used for
Authentication and Authorisation (see
Radius AA, above)
Integer
Authenticate/Authorise The circumstances under which
Authentication and Authorisation is
performed.
Never
Registration
Calls
Always
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 64/103

Authenticate Method How a caller is Authenticated
Cisco sip-hdr uses the Cisco VSA
Draft Sterman01 uses the method
outlined in the IETF draft draft-sterman-
aaa-sip-01.txt (this is the default)
Calling Number uses the calling Party
Number to authenticate.
Cisco sip-hdr
Draft Sterman-01
Draft Digest-06
Calling Number
Authorise Method How a call is Authorised.
If none, no authorisation is performed. If
Called Party, the Called Party number is
included in the Radius Access Request.
None
Called Number
Accounting Settings
Radius Accounting Specifies if Radius Accounting is to be
used on this criteria and if the accounting is
raised on the incoming or outgoing leg
None
Outgoing
Incoming
Accounting Server Specifies the Radius resource which is to
be used for this criteria
Integer
Radius Identity Configures the use of the radius User-
Name attribute. Setting this field overrides
any setting in the radius resource
Identity setting
Called
Calling

h323-call-origin The value used in the Cisco Radius VSA
h323-call-originfield
Free-form text.
Default answer
h323-call-type The value used in the Cisco Radius VSA
h323-call-typefield
Free-form text
Default VoIP
10.5 SETTING UP THE PARAMETER DATABASE
The parameter database is used to match a calls details against a predefined set of
criteria and once matched perform actions on this calls information.

The parameter databases attributes are divided into match attributes and action
attributes. The match attributes are: -

Hunt Group
Called Party Number
Calling Party Number
Bearer
Time of Day

The action attributes are: -

Strip Called Party Number
Strip Calling Party Number
Prefix Called Party Number
Prefix Calling Party Number
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 65/103

Change Called Party Nature of address
Change Calling Party Number of address

10.5.1 MATCHING AGAINST CALLED PARTY NUMBER
When searching for a called party number match the SVI will search between the two
defined resource instances for the longest match or exact match for this number.
Numbers can be defined as individual numbers or as ranges.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 66/103

10.6 CONFIGURING PARAMETER DATABASE
10.6.1 PARAMETER DATABASE SYNTAX
Match Criteria
Hunt Specifies the Incoming
hunt group
0-MAX_HUNT_GROUPS
Cdpn Defines the called party
number
NULL Terminated ASCII string
Cgpn Defines the calling party
number
NULL Terminated ASCII string
Cdpnnoa Defines the called party
nature of address
(Can also be used to match
to match the SCCP Called
Party NOA ITU Only)
Subscriber
National
International
Unknown
National specific
Cgpnnoa Defines the calling party
nature of address
(Can also be used to match
to match the SCCP Calling
Party NOA ITU Only)
Subscriber
National
International
Unknown
National specific
Bearer Bearer Capability of call Speech
3.1 KHz
64K restricted
64K unrestricted
Unknown
Network Specifies which network
the call originated from
SS7 Circuit
ITU SCCP Stack
ANSI SCCP Stack
TOD low

Contains the lowest
instance of the range of
time of day resources
which the routing table
will apply
0-MAX_TODS
TOD high

Contains the highest
instance of the range of
time of day resource which
the routing table will
apply. If only one instance
if the time of day resource
is used, this field is set to
be equal to TOD low
0-MAX_TODS
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 67/103

CdpnRoutingInd (SCCP Only)
Matches the Called Party
Routing Indication
Route on SSN
CdpnPointCode (SCCP Only)
value
Present /
32-bit number
CdpnSSN (SCCP Only)
Sub-System Number
8 bit number
CdpnGTI (SCCP Only)
8 bit number.
CdpnEncodingScheme (SCCP Only)
encoding scheme
Unknown
BCD
National
CdpnNational (ANSI SCCP Only)
Matches the National
flag
National
International
CdpnNumberingPlan (SCCP Only)
Numbering Plan
Unknown
ISDN
Generic
Data
Telex
Maritime Mobile
Land Mobile
ISDN/mobile
CdpnTranslationType (SCCP Only)
Translation Type
8 bit number
Note : The SCCP Only fields are also available for the Calling Party parameter by
changing the parameter prefix to Cgpn
Action Criteria
CDPNstrip Strips n digits of the prefix
of a called party number
Integer
CDPNprefix Adds defined digits to end
of called party number
ASCII String
SetCDPNnoa Sets the called party
Subscriber
National
International
Unknown
National specific
CGPNstrip Strips n digits of the prefix
of a calling party number
Integer
ASCII String
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 68/103

SetCGPNnoa Sets the calling party
Subscriber
National
International
Unknown
National specific
Setbearer Sets the outgoing calls
bearer capability
Speech
3.1KHz
7Khz
64K restricted
64K unrestricted
Unknown
Add Route Add outgoing hunt group
to parameter database
0-MAX Hunt Groups
SetCSI ANSI Sets Carrier
Selection Information
As T1.113
SetCIPNiType ANSI Sets Carrier
Identification Parameter
Network ID Type
As T1.113
SetCIPNiPlan ANSI Sets Carrier
Network ID Plan
As T1.113
SetCIPDigits ANSI Sets Carrier
Digits
As T1.113 - 3-4 Ascii Digits
SetCdpnRoutingInd (SCCP Only)
Sets the Called Party
Routing Indication
Route on SSN
SetCdpnPointCode (SCCP Only)
value
Present /
32-bit number
SetCdpnSSN (SCCP Only)
Sets the Called Party Sub-
System Number
8 bit number
SetCdpnGTI (SCCP Only)
8 bit number.
SetCdpnEncodingScheme (SCCP Only)
encoding scheme
Unknown
BCD
National
SetCdpnNational (ANSI SCCP Only)
Sets the National flag
National
International
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 69/103

SetCdpnNumberingPlan (SCCP Only)
Numbering Plan
Unknown
ISDN
Generic
Data
Telex
Maritime Mobile
Land Mobile
ISDN/mobile
SetCdpnTranslationType (SCCP Only)
Translation Type
8 bit number
Note : The SCCP Only fields are also available for the Calling Party parameter by
changing the parameter prefix to SetCgpn
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 70/103

10.7 ROUTING CONFIGURATION EXAMPLES
These following examples show a number of different routing requirements and how
to configure the SoftSwitch to handle these criterias
10.7.1 EXAMPLE 1
Setup route for circuits between two SS7 interconnects

*Set up Par amet er Dat abase t o be used by r out i ng cr i t er i a
DB Par amet er 0 St at us I ns
DB Par amet er 0 Hunt Gr oup 0
Db Par amet er 0 add r out e 1

DB Par amet er 1 St at us I ns
DB Par amet er 1 Hunt Gr oup 1
Db Par amet er 0 add r out e 0

*Set up Rout i ng Cr i t er i a
Rout i ng Cr i t er i a 0 St at us I ns
Rout i ng Cr i t er i a 0 Mat chDb 0

10.8 TIME OF DAY ROUTING
The SVI allows for start and stop time of day criterias set against a parameter
database allowing for a routing criteria to only be active during a specific time period.
10.8.1 TIME OF DAY ROUTING SYNTAX
OSF Bring resource into
service
Status Describes the status of the resource
NIU Resource not in use
Start Specifies the start period when the time of
day routing instance is active
Date and time format
Stop Specifies the end period of the time of day
routing instance.
Date and time format
TOD Low Allows for nesting of additional time of day
resources within a time of day resource.
This specifies the low instance of the nested
time of day resource
0-MAX_TOD
TOD High Allows for nesting of additional time of day
resources within a time of day resource.
This specifies the high instance of the
nested time of day resource
0-MAX_TOD

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 71/103

10.8.2 DATE AND TIME FORMAT
The syntax for the date and time format of the start and stop attributes of the time of
day resource is:-

[dd/mm/yyyy][hh:mm:ss] or [hh:mm:ss]

Where dd =day of week (1-31), mm =month of year (1-12), yyyy =4 digit year (i.e.
2005), hh =24 clock hour of day (0-23) , mm =minute of day (0-59), ss =second of
day (0-59)

This allows for the setting of the start or stop attributes against just a time or a date
and time.

The following table shows the allowable syntaxes that can be used for the start and
stop attributes.

Start Stop Description
[dd/mm/yyyy][hh:mm:ss] [dd/mm/yyyy][hh:mm:ss] The criteria will be active between
the date and times specified in the
start and stop fields
[dd/mm/yyyy][hh:mm:ss] The criteria will be active
continuously from the date and time
specified in the start field
[hh:mm:ss] [hh:mm:ss] The criteria will be available daily
between the times specified in the
start and stop attributes.

*Set up t i me of day t o be act i ve bet ween t he hour s of 22: 30 p. mand
*7: 00 a. m
Ti me of day 0 st at us I ns
Ti me of day 0 st ar t [ 22: 30: 00]
Ti me of day 0 st op [ 07: 00: 00]

* Set up up same as r esour ce 0 but onl y al l ow t hi s t o be i n ef f ect
*f r omt he 10
t h
Oct ober 2004

Ti me of day 1 st at us I ns
Ti me of day 1 st ar t [ 10/ 10/ 2004] [ 00: 00: 00]
Ti me of day 1 TOD Low 0
Ti me of day 1 TOD Hi gh 0

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 72/103

10.8.3 SCCP ROUTING CONFIGURATION
This configuration assumes that SS7 Destination Points 1-7 have already been set up
and configured with Alternate PointCodes (see section )
This configuration will route from destination point 0 (hg 100) to destination point 7
(hg 102) and destination point 1 (hg 103) and one of destination points 2-6 (hg 102),
whichever destination matches the alternate pointcode in the received message.
** Configuration for SCCP Routing

** ITU National SCCP Hunt Group
Hunt Group 100 Status Ins
Hunt Group 100 Add SCCPDestination 7

** ITU National Spare SCCP Hunt Group
Hunt Group 101 Add SCCPDestination 2-6

** ANSI National SCCP Hunt Group

** ANSI National Spare SCCP Hunt Group

** Routing Parameters
** ITU->ANSI national
DB Parameter 100 status ins
DB Parameter 100 network ITU SCCP Stack
DB Parameter 100 hunt 100
DB Parameter 100 Add Route 102

** ITU->ANSI national-spare
DB Parameter 101 network ITU SCCP Stack

** ANSI->ITU national
DB Parameter 102 network ANSI SCCP Stack

** ANSI->ITU national-spare
DB Parameter 103 network ANSI SCCP Stack
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 73/103


Routing Criteria 100 Status Ins
Routing Criteria 100 MatchDB 100-103

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 74/103

11 CDR RECORDS
The SVI allows for the capture of CDR (Call Data Records) information to disk
providing full call capture of calls through the switch allowing for call analysis and
billing information.

The CDR records are all stored on the hard disk in the /home/squire/cdr directory and
have a file name syntax of <prefix>CDR_DD-MM-YY.

It is important if using the CDR Record option to maintain the number of CDRs on
the system. If these are not managed this can cause the hard drive to become full and
result in a lose of CDR and debug information.

The determination of whether a call is logged to CDR file is determined by the
routing criteria record. The user can define if CDRs are logged, to what CDR format
they are logged and the prefix name of the file the CDRs are to be added to.
11.1 CDR FORMATS
11.1.1 TYPE 1
The Type 1 CDR format is a comma separated file with the following fields.

Field Format Description
Call clearing stare ASCII String Setup
Routing
Ringing
Answered
Start date and time Date and time format Start date and time of call
Ringing date and time Date and time format Time call moves to ringing state. If call
does not go to ringing , ringing field
contains -------------------
Answer date and time Date and time format Time call is answered. If call is not
answered field contains -------------------
Clear date and time Date and time format Time and date of when call is cleared
Incoming Network ASCII String SS7 Network
H323 Stack
SIP Stack
Incoming identity ASCII String SS7 is circuit
H323 is destination address and call
reference
SIP is SIP call identity
Incoming called party
number
ASCII String Decoded called party number
Incoming calling party
number
ASCII String Decoded calling party number
Outgoing Network ASCII String SS7 Network
H323 Stack
SIP Stack
Outgoing identity ASCII String SS7 is circuit
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 75/103

reference
Outgoing called party
number
Outgoing calling party
number
Clearing party ASCII String Incoming
Outgoing
Internal
Reason 8 bit Number Release reason as a decimal number
Text Reason ASCII String Release reason as descriptive text
Duration Duration number Duration of call in seconds
11.1.2 TYPE 2
Field Format Description
Call clearing stare ASCII String Setup
Routing
Ringing
Answered
Start date and time Date and time format Start date and time of call
Ringing date and time Date and time format Time call moves to ringing state. If call
does not go to ringing , ringing field
contains -------------------
Answer date and time Date and time format Time call is answered. If call is not
answered field contains -------------------
Clear date and time Date and time format Time and date of when call is cleared
Incoming Network ASCII String SS7 Network
H323 Stack
SIP Stack
ISUP Circuit
Incoming IP Address ASCII String For VoIP destinations, the IP Address
Incoming identity ASCII String SS7 is circuit
reference
Incoming called party
number
Incoming calling party
number
Outgoing Network ASCII String SS7 Network
H323 Stack
SIP Stack
ISUP Circuit
Outgoing IP Address ASCII String For VoIP Destinations, the IP Address
Outgoing identity ASCII String SS7 is circuit
reference
Outgoing called party
number
Outgoing calling party
number
Codec ASCII String The last codec used in the call
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 76/103

G711 ALAW
G711 ULAW
G722
G723.1 LOW RATE
G723.1 HIGH RATE
G723.1 LOW RATE SS
G723.1 HIGH RATE SS
G728
G729
G729A
G729B
G729AB
GSM FULL RATE
GSM HALF RATE
t38
speex
Clearing party ASCII String Incoming
Outgoing
Internal
Reason 8 bit Number Release reason as a decimal number
Text Reason ASCII String Release reason as descriptive text
Duration Duration number Duration of call in seconds

11.2 INTERROGATING CURRENT LIVE CALLS
The SVI MMI provides the ability to inspect the status of the current live calls going
through the system. The CDR resource can be interrogated using the show command
with a resource name of CDR, as described in the following section. Calls are
dynamically added to the lowest free CDR instance and contains the same information
as produced in the standard CDR records.

11.3 UNAUTHORISED CALL ACCESS
Any calls that access the unit and can not be routed to a hunt group because a routing
criteria is not matched will be automatically added to the unauthorised CDR record.
This record is located in the /home/squire directory and is in the format

unathCDR_DD_MM_YYYY

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 77/103

12 RADIUS
The SVI provides a RADIUS interface allowing for real time accounting with a
Radius server. The SVI can be upgraded to support different Radius dictionaries,
Appendix A shows a standard trace of the output from the SVI Radius Accounting
Interface. If a different variant is required please contact your account manager.

12.1 RADIUS ACCOUNTING
Routing criterias are setup to access a given Radius server allowing for different
routing criterias to access different Radius servers if required. The following show
the resources that are required to setup the system to perform Radius Accounting

12.2 ROUTING CRITERIA
Each Routing Criteria resource should indicate if Radius Accounting is required by
setting the Radius Accounting attribute to either Incoming or Outgoing. These two
options allow for the system to determine if the Radius start and stop accounting will
happen for the dialled information on the incoming leg or for the dialled information
on the outgoing leg which may be different from the incoming leg due to database
manipulation of the dialled information.
The Accounting Server field should also be setup to indicate which Radius resource
this routing criteria is to use. Multiple routing criterias can use the same Radius
resource.

SVI SoftSwitch

Radius Server
IP Cloud
Routing Criteria
Radius
IP
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 78/103

12.3 RADIUS RESOURCE
The Radius resource contains information allowing for a Radius service to be
deployed point to point between the SVI and a Radius Server. The configuration
options are described below.

INS Bring resource into
service
Status Describes the status of the resource
NIU Resource not in
use
Resource IP Contains the instance of the IP
resource that will provide the UDP
transport layer
0-MAX_IP
IP Contains the IP address of the
Radius Server
ASCII String
Port Contains the Port of the Radius
server for this service
Integer
Identity Contains the identity to be used for
the user name to access the Radius
account. (radius User-Name
attribute). This setting will be over-
ridden by the Radius Identity
setting on the Routing Criteria
resource, if set.
Called
Calling
NAS
Name If the identity status is set to NAS
the name attribute will be used for
the User Name in a Radius
Accounting Request.
ASCII String
Secret Contains the RADIUS shared secret
for authenticating responses
ASCII String
Authentication The Type of authentication that the
RADIUS server supports
Cisco sip-hdr
Draft Sherman01
Draft Digest06
(see note)

Notes on Authentication Attribute
Cisco sip-hdr Conforms to Cisco sip-hdr specification
Draft Sherman01 Conforms to IETF draft - draft-sterman-
aaa-sip-01.txt - 6/2/04
Draft Digest06 Conforms to IETF draft - draft-ietf-
radext-digest-auth-06.txt - 14/10/05

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 79/103

12.3.1 IP RESOURCE FOR RADIUS SOCKETS
An IP resource is required to be setup to handle the incoming and outgoing UDP layer
which acts as a transport layer for the Radius protocol.

OSC Start Resource Status Describes the status of this
resource NIU Resource not present
Type Defines the behaviour of the IP
Stack
Radius IP
Name Specifies the internal name of
the socket for debugging and
reporting purposes
ASCII String
Socket Type Specifies the protocol type
running above IP
UDP Peer
PacketOwner Indicates the internal task that
handles any received packets
Radtrans
MntOwner Indicates the internal task that
handles the maintenance of the
socket
Maintenance
Port Specifies the listening port of the
socket
16 bit number

Example

The following shows a configuration example of setting up radius accounting.

*Set up Rout i ng Cr i t er i a
Rout i ng Cr i t er i a 0 St at us I ns
Rout i ng Cr i t er i a 0 Mat chDb 0
Rout i ng Cr i t er i a 0 Add Rout e 10
Rout i ng Cr i t er i a 0 Add Codec G729
Rout i ng Cr i t er i a 0 Add Codec G723. 1
Rout i ng Cr i t er i a 0 Radi us Account i ng I ncomi ng
Rout i ng Cr i t er i a 0 Account i ng Ser ver 1

Radi us 1 St at us I ns
Radi us 1 r esour ce i p 10
Radi us 1 i p 88. 123. 45. 123
Radi us 1 por t 1813
Radi us 1 i dent i t y NAS
Radi us 1 name gat eway1

I P 10 st at us Osc
I P 10 name r adi us I P
I P 10 t ype r adi us I P
I P 10 socket t ype UDP Peer
I P 10 packet owner r adt r ans
I P 10 mnt owner mai nt enance
I P 10 por t 1813
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 80/103

13 OPERATION ADMINISTRATION AND MAINTENANCE
The system provides a number of facilities enabling the administrator to manage the
system to provide resource status information, real time configuration and protocol
flow information.
13.1 TELNET SESSIONS
The system provides a number of MMI telnet interfaces to allow for OA&M
operations and collection of statistical information.
Two different types of telnet port are available a Trap port, and a OA&M port.
13.1.1 TRAP PORT
The trap port provides asynchronous reports of resource information. When a resource
on the system changes state a trap will automatically be raised by the system on this
TCP-IP port. All OA&M actions can also be performed on this port.
13.1.2 OA&M PORT
The OA&M port allows the user to perform the following actions

Interrogate Current Resource Status
Take Resources out of service (Circuits, signalling links, etc)
Return resources back to service
Configure resources
Inspect resource configuration
View real time statistical information including
o ASR
o Average Answer length
o Number of calls
13.2 CONNECTING A TELNET SESSION
To connect to the systems telnet port a standard telnet program should be used. The
Telnet program must send all line information in one TCP-IP packet and not as
separate characters. The system does not support single character transmission.

Each Telnet session has an IP resource associated with it to allow for configuration of
the Telnet IP address. To inspect the Telnet settings look in the SVI Soft Switch
configuration file and within the IP resources will be the following resource types,
Trap Port, OA&M Port and Statistic Port. Against these resources will be the
configuration for the appropriate Telnet port.

The factory defaults for these ports are as follows

OA&M Port 15001
Trap Port 15002
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 81/103

To connect to one of the Telnet ports, on a Unix terminal type

t el net <I P addr ess> 15001

For example if the IP address of the unit is 192.168.2.100 the command to connect to
the systems telnet port will be

t el net 192. 168. 2. 100 15001

The user will need to enter a username and password to gain access to the telnet
session. The username and password are configured in the configuration file against
the System resource.

On successful connection the user will be greeted by the following welcome
*** Wel come System Name Ver si on x. x Tr ap Cont r ol ****
>
13.3 TRAPS
When a resource changes state moving from an in service to an out of service and visa
versa state an asynchronous trap report is sent to all connect Trap Telnet ports. This
enables remote administrators to monitor the status of all of the resources on the
system.
13.3.1 TRAP FORMAT
The format of the trap enables the user to quickly identify which resource has failed.
The syntax of the traps is as follows

<Ti me><Dat e> <Syst emName> Tr ap: <Type> <Name> <I nst ance> <St at e>
13.3.1.1 System Name
The system name is the system resource name attribute as defined in the configuration
file.
13.3.1.2 Type
This field contains the resource type of the resource. These are defined in Section
System Resources
13.3.1.3 Name
This field contains the name of the resource. These are defined in Section System
Resources
13.3.1.4 Instance
This field contains the instance of the resource. A range of instances can be applied
using the - character as a range indicator i.e. 1-100
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 82/103

13.3.1.5 State
The state field contains the status of the resource. The following table describes the
different states

Abbreviation State Description
NIU Not In Use This resource is not present in the
system
OSC Out Service Configure This resource is waiting to be
configured
OSCP Out Service Configure
Pending
This resource is being configured
OSF Out Service Faulty This resources is not in service and is
waiting for its parent to come into
service before attempting to bring the
resource into service
OSFP Out Service Faulty
Pending
This resource is attempting to return to
service
OSD Out Service Dependant This resources parent is not in service
OOS Out Of Service This resource has been manually taken
out of service.
OSFD Out of Service Faulty
Dependant
This resource has been taken out of
service by a remote system.
INS In Service This resource is in service.

13.4 USING THE OA&M PORT
The OA&M port has a wide range of operations available to the user. The following
provides an overview off the commands that are available on the OA&M Port

Command Description
Configure Configures a given resource
Show Shows details of a resource
Syntax Shows the possible contents of a resourceq
Take OOS Takes a resource out of service
Bring INS Brings a resource in service
Help Displays a simple help screen
Parent Shows the hierarchical parent of a resource
Children Shows the hierarchical children of a resource
Exit Exits from the telnet session
Info Shows specific information for a resource

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 83/103

13.4.1 CHECKING THE SYNTAX OF A RESOURCE
To configure and inspect a resource the user needs to identify the correct name,
number of instance and names of the attributes of a resource. The user also needs to
know what is the correct syntax to use to load a value into a given resource.

This is achieved by using the syntax command which has the following format

Syntax <resource name><instance range><attribute name>
13.4.1.1 Checking valid resource names
To check the available resources on the unit and the correct name of these resources
the following syntax is used

>Synt ax

A full list of resources will then be displayed
13.4.1.2 Checking resources instance range
To check the total number of instances of a given resource the following entry is
entered at the command line

Syntax <resource name>

>Synt ax Car d

13.4.1.3 Check a resources valid attributes
To see a list of attributes for a given resource the following is entered on the
command line

Syntax <resource name><instance range>

>Synt ax Car d 0

13.4.1.4 Check an attributes valid values
To check a given attributes values the following is entered at the command line

Syntax <resource name><instance range><attribute name>

>Synt ax Car d 0 st at us

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 84/103

13.4.2 INTERROGATING A RESOURCES CONTENTS USING THE SHOW COMMAND
The show command allows the user to interrogate the contents of a resource. The
syntax for interrogating the a resources contents is

show <resource name><instance range><attribute><status>

Different fields can be used to show different levels of a resources contents. To show
all attributes of all active instances of a resource only the resource name is defined as
show below

>Show car d

To show all attributes of a range of instance of a resource, the instance range is also
defined as follows

>Show Car d 0- 2

To show the value for a given range of resources of a particular attribute the attribute
filed is entered and the following is entered on the command line

>Show Car d 0- 2 st at us

If it is required to show only attributes in a range with a given value the value field is
entered using the following syntax

>Show Car d 0- 2 st at us i ns

The user can also show a range of resources attributes that do not have the value
specified, to perform this action the following syntax is entered.

>Show Car d 0- 2 st at us ! i ns

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 85/103

13.4.3 MANUALLY TAKING RESOURCES IN AND OUT OF SERVICE
An administrator can manually take certain resources out of service and return them
back to service. This command will only affect the following resources.

Resource Take Out Of service Bring In Service
Interface Will take Layer 1 out of
service
Will Bring Layer 1 back
into service
Signalling Link Will take signalling link out of
service
Will return signalling link
back into service
Local block Will locally block circuit Will locally unblock
circuit

13.4.3.1 Taking a resource out of service
To take a resource out of service the following syntax is used.

Take Oos <Resource Name><Instance Range>
Example

>Take Oos si gnal l i ng l i nk 0

13.4.3.2 Bringing a resource into service
To bring a resource into service the following syntax is used.

Bring Ins <Resource Name><Instance Range>
Example

>Br i ng I ns si gnal l i ng l i nk 0

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 86/103

13.5 CONFIGURATION OF RESOURCES
The Squire SVI Switch provides comprehensive real time configuration of the system.
This feature enables the user to add, remove and reconfigure resources on the system
without stopping the system and therefore effecting existing customers.
13.5.1 CONFIGURING RESOURCES
To configure a resource the OA&M port is used. New configurations can be added by
the command line.
13.5.1.1 Command Line Configuration
To change any exiting resources attribute the user only needs to enter the
configuration syntax as defined in the configuration sections of this manual and
prefixing this syntax with the configure command.

For example to change the routing criteria resource instance 2 to make calls on hunt
group 3, the following would be entered

>Conf i gur e Rout i ng Cr i t er i a 2 Add Rout es 3

13.6 INFORMATION COMMAND
The info command is used to display a reduced set of a resources attributes. The
syntax for the info command is

Info <Resource Name><instance range>

This command is valid on the following resources
13.6.1 HUNT GROUP CALL STATISTICS
The hunt group resource contains a number of call statistics that enable the user to
investigate the number and quality of outgoing calls from a particular hunt group.
The following fields are available

Attribute Description
Setup Total This is the total number of outgoing calls from this
hunt group
Ringing Total This is the total number of outgoing calls from this
hunt group that achieved ringing
Answer Total This is the total number of outgoing calls from this
hunt group that achieved answer
Congestion Total This is the total number of outgoing calls from this
hunt group that were rejected due to congestion
Minutes This is the total number of whole seconds that calls
have been in answer for outgoing calls on this hunt
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 87/103

group
Active This is the average length of time in seconds that
outgoing calls from this hunt group were in answer
ASR This is the percentage of outgoing calls from this hunt
group that went to ringing.
ACD This is the Average Call Duration
PDD This is the average post dial delay

13.6.2 ROUTING CRITERIA CALL STATISTICS
Attribute Description
Setup This is the total number of incoming calls from this
routing criteria
Ringing This is the total number of incoming calls from this
routing criteria that achieved ringing
Answer This is the total number of incoming calls from this
routing criteria that achieved answer
Congestion Total This is the total number of incoming calls from this
routing criteria that were rejected due to congestion
Rejected By
Criteria
Total Number of calls that were explicitly rejected by
this criteria
Minutes This is the total number of whole seconds that calls
have been in answer for incoming calls on this routing
criteria
Active This is the average length of time in seconds that
incoming calls from this routing criteria were in answer
ASR This is the percentage of incoming calls from this
routing criteria that went to ringing.

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 88/103

14 DEBUG LOGGING
The system provides different levels of debugging to enable full protocol and system
analysis.
14.1 DEBUG OVERVIEW
The system consists of several tasks, and messages flowing between them. The
messages are split into sub-groups, known as discriminators

Debug can be output to file or screen (stdout). In normal operation, the system runs as
a daemon (hidden process), and so any screen output goes to a system file. For this
reason, screen output should not be used.

The system produces a new log file at midnight and uses the file syntax
Gateway_DD-MM-YY and stores these locally in directory /home/squire

The system produces three different levels of debug which can be categorised into
three types :
14.1.1 MESSAGE DECODE
The SoftSwitch uses an internal message passing mechanism to route signalling,
media control and internal messages between individual tasks. These messages
passing between different functional tasks can be captured to log file. The system can
also be set to display a complete message hex break down allowing for the
determination of protocol or message contents. The Filtering of these messages can be
determined by the following criteria
14.1.1.1 Task
The filtering of messages can be narrowed down to messages being received to and
from a particular task. These tasks are listed below

Task Description
CallControl The call control task provides the common routing functionality
for the system.
Maintenance The maintenance task controls all resources within the system.
DRVNS700 Interface to the SS7 interface stack
Timer Timer task
MGCP MGCP Task
MEGACO Megaco Task
H323Stack H.323 messages
SIPStack SIP Stack

The system allows for either all tasks to be filtered in or allows for the selection of
specific tasks to be selected.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 89/103

14.1.1.2 Discriminators
All internal messages within the system are grouped into discriminator groups. The
system can filter on these discriminator groups to focus on a particular aspect of the
systems operation.

Discriminator Description
DIS_MNT Maintenance messages that control configuration and bringing
resources in and out of service.
DIS_CC_RX Call control protocol messages that are received from the network
by the system.
DIS_CC_TX Call control protocol messages that are transmitted to the network
from the system.
DIS_TIMER Timer messages
DIS_SWITCH Media Gateway switching messages

The system allows for either all discriminators to be filtered in or allows for the
selection of specific discriminators to be selected.
14.1.2 ERRORS
If an error occurs within the system relating to call control or system behaviour an
error message will be produced. These errors may not be service affecting but any
errors that are produced should be verified by a Squire Technologies support engineer
to confirm if interconnect problems are occurring.
14.1.3 INFORMATION
Individual tasks that control an aspect of the SoftSwitch can individually turned on to
obtain system information that can assist with the diagnostics of the behaviour of the
system. This information will be generally used by Squire Technologies support staff
to assist with support issues.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 90/103

14.2 DEBUG RESOURCE SYNTAX
14.2.1.1 Attributes
INS Debug available Status Describes the status of the resource
NIU No debug available
Off Display to screen (stdout) Screen Indicates if the debug output is to be
displayed in real time to the terminal
screen. ONLY to be used when the
system is not being run as a daemon.
On Do not display to screen
Off Capture debug from all tasks Tasks Global switch for tasks
On Capture debug only from tasks
set on
On Capture Debug to file File Indicates if the debug output should
go to file Off Do not capture Debug to file
On Display detailed breakdown Detailed Indicates if all of the message should
be displayed
Off Do not display detailed break
down
On Messages with all discriminators
will be displayed
Discriminators Global switch for message
discriminators
Off Only messages with
discriminators set on will be
displayed
File Capture traps to file Traps If set to on all maintenance traps will
be written to file, highly
recommended
Screen Traps got to terminal screen.
ONLY to be used when the
system is not being run as a
daemon.

To inspect the current status of the debug resource use the resource info command to
check the current settings

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 91/103

15 DUAL PLANE REDUNDANCY
The SVI SoftSwitch can be deployed in a dual plane architecture to provide a high
availability redundant system into the network. With a dual plane architecture if one
of the planes fails due to hardware or software failure the second plane will continue
to process active calls without the loss of any calls in answer.

The dual plane system works in a active/warm standby arrangement. This means that
processing of both IP and MTP L2 traffic is terminated on both planes, however only
the Active plane processes this information to control the calls, the warm standby
plane acts as a router to pass this traffic information to the Active plane. The warm
standby is continually updated in real time of call state changes and configuration
changes so in the case of a failure on the Active Plane the warm standby plane can
immediately become the new Active plane with a complete snapshot of the current
call states and configuration data.

The dual redundant architecture is shown below

Physical Interconnect

Redundant System Overview

Ethernet
Configuration
Database
Call Control
and protocol
Stack FSM
MTP L2 Signalling Ethernet
Configuration
Database
MTP L2 Signalling
Security
router
Security
router
Call Control
and protocol
Stack FSM
Warm Standby Active
SS7
Network
Plane 0
Plane 1

IP Cloud

DNS Server
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 92/103

15.1 INTERCONNECT CONSIDERATIONS
15.1.1 SS7 INTERCONNECT CONSIDERATIONS
To achieve redundancy in the SS7 network, if using the dual plane mode, the
signalling links from the SS7 interconnect should be equally divided across the two
units. The system will use general load sharing and change over SS7 procedures to
ensure no loss of SS7 messaging during a fail over.
15.2 CONFIGURING THE SYSTEM FOR DUAL REDUNDANCY
To deploy a dual redundant system a new resource is used to define the behaviour of
each plane. The System type behaviour is also changed to be set to SoftSwitch Dual.

The plane resource defines each of the dual planes in the system.
15.2.1 PLANE CONFIGURATION SYNTAX
OSF Bring resource in service State Describes the start up state
of the resource
Behaviour Describes the behaviour of
the plane.
Local Plane
Remote Plane
IP Address IP Address of plane NULL terminated string
Preferred Specifies if both planes start
up at the same time which
plane should start first as
Active
Preferred Active
Non Preferred Active
Current This specifies the status of
the plane
Active
Standby
Going Active

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 93/103

15.3 CONFIGURATION EXAMPLE

To add a dual plane architecture into the system the following configuration should be
added.

System 0 Status Osf
System 0 name Plane 0
System 0 type SoftSwitch Dual

*define local plane 0
Plane 0 status Osf
Plane 0 behaviour local plane
Plane 0 Address 127.0.0.1
Plane 0 Preferred Preferred Active

*define other remote plane 1
Plane 1 status Osf
Plane 1 behaviour remote plane
Plane 1 Address 10.2.2.1
Plane 1 Preferred Non Preferred Active

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 94/103

16 SPECIFICATIONS
16.1 PCI CHASSIS
Plane
Chassis 4U 19 industrial rack mounted chassis
Capacity
PCMS per card 4
Signalling Links per card Up to 16 per board
Total Boards per system Up to 8 boards
Total PCMS per system Up to 32
Total Signalling Links per plane Up to 32
Chassis
Size Height 196mm
Width 435mm
Depth 435mm
PSU Dual 240/110 Volt AC, -48 Volt DC
Processor 1.2 GHz Intel CPU
RAM 512 MB
Hard disk Standard 8 GB
Upgrade Mirrored Raid disk 146 GB
Ethernet 10/100 Base T RJ 45
16.2 CPCI CHASSIS
Plane
Chassis 4U 19 industrial rack mounted chassis
Capacity
PCMS per card 8
Signalling Links per card Up to 16 per board
Total Boards per system Up to 7 boards
Total PCMS per system Up to 56
Total Signalling Links per plane Up to 32
Chassis
Size Height 225mm
Width 485mm
Depth 300mm
PSU Dual 240/110 Volt AC, -48 Volt DC
Processor 850 GHz Intel CPU
RAM 512 MB
Hard disk Standard 8 GB
Upgrade Mirrored Raid disk 146 GB
Ethernet 10/100 Base T RJ 45

User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 95/103

16.3 MTBF FIGURES

Signalling Cards 19.2711 Years
System 10 years (FDD 5 years, CPU battery 5 years)
16.4 ENVIRONMENTAL
Interface Hardware
EN55022: 1998 Class A Radiated Electric Field Emissions
EN55022: 1998 Class A Power Line Conducted Emissions
EN55022: 1998 Class A Telecom Port Conducted Emissions
EN55024: 1998 (IEC 61000-4-2) Electro Static Discharge Immunity
EN55024: 1998 (IEC 61000-4-3) Radiated Electric field Immunity
EN55024: 1998 (IEC 61000-4-4) Burst Transient Immunity
EN55024: 1998 (IEC 61000-4-5) Surge Immunity
EN55024: 1998 (IEC 61000-4-6) Conducted Disturbance Immunity
EN55024: 1998 (IEC 61000-4-11) Power Line Voltage Dips & Interruptions Immunity
CISPR 22: 1997 Class A Radiated Electric Field Immunity
CISPR 22: 1997 Class A Power Line Conducted Emissions
CISPR 22: 1997 Class A Telecom Line Conducted Emissions
47 CFR 15:1999 (ANSI C63.4: 1992)
Class A
Radiated Electric Field Immunity
47 CFR 15:1999 (ANSI C63.4: 1992)
Class A
Power Line conducted Emissions
System
EN55022:1998 Class B, FCC Class B EMC Emissions
EN55024:1998 Class B Immunity

16.5 SAFETY
Interface Hardware
BSEN 60950: 1992 (Up to A5: 1998) Safety of Information Technology Equipment, including
Electrical Business Equipment
EN41003: 1998 Particular Requirements for Equipment to be connected
to Telecommunications Networks
IEC CB Scheme Certificate No GB4800Z
UL 1950 Third Edition Safety of Information Technology Equipment, Including
Electrical Business Equipment, CSA C22.2 No 950
System
EN60950 Safety

16.6 SYSTEM ENVIRONMENT
Operating Temperature 0-60 Degrees Centigrade
Storage -20 to 80 Degrees Centigrade
Relative Humidity 10-90% Non condensing
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 96/103

16.7 INTERCONNECT
Interconnect
Impedance 75, 110, 120 Ohm
Connection RJ 45
Interconnect T1, E1 or J1
Erlang Support per link 1 erlang
Compliance
FCC Part 68 Subpart D Certification of Telephone and Data Terminal Equipment
IC CS-03 Issue 8 Part II & VI Industry Canada Terminal Equipment Certification
J ATE Green Book J apanese ISDN
ITU-T G.703 E1/T1 Physical/Electrical Interface
ITU-T G.704 E1/T1 Frame Structures
ITU-T G.705 E1/T1 Digital Termination Characteristics
ITU-T G.706 E1/T1 CRC Procedures
ITU-T G.821 Error Performance on Digital Links
ITU-T G.822 Controlled Slip Objectives
ITUT-T G.823/G.824 Control of J itter and Wander
J T G.703 J 1 Physical/Electrical Interface
J T G.704 J 1 Frame Structures
ITU-T Q.703 Signalling System Number 7- Signalling Link
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 97/103

17 APPENDIX A - RADIUS ACCOUNTING TRACE
17.1 ACCOUNTING REQUEST START
Account i ng Request ( 4) ( i d=0, l =112)

User Dat agr amPr ot ocol , Sr c Por t : r adacct ( 1813) , Dst Por t : r adacct
( 1813)
Sour ce por t : r adacct ( 1813)
Dest i nat i on por t : r adacct ( 1813)
Lengt h: 120
Checksum: 0x776b ( cor r ect )
Radi us Pr ot ocol
Code: Account i ng Request ( 4)
Packet i dent i f i er : 0x0 ( 0)
Lengt h: 112
Aut hent i cat or : 0x36323535353865633261653839343461
At t r i but e val ue pai r s
t : NAS I P Addr ess( 4) l : 6, Val ue: 192. 168. 2. 215
Nas I P Addr ess: 192. 168. 2. 215 ( 192. 168. 2. 215)
t : User Name( 1) l : 10, Val ue: " 98765432"
User - Name: 98765432
t : Cal l ed St at i on I d( 30) l : 6, Val ue: " 6000"
Cal l ed- St at i on- I d: 6000
t : Cal l i ng St at i on I d( 31) l : 10, Val ue: " 98765432"
Cal l i ng- St at i on- I d: 98765432
t : Acct St at us Type( 40) l : 6, Val ue: St ar t ( 1)
Account i ng St at us Type: St ar t ( 1)
t : Ser vi ce Type( 6) l : 6, Val ue: Voi ce( 12)
Ser vi ce- Type: Voi ce ( 12)
t : Acct Sessi on I d( 44) l : 48,
Val ue: " 192. 168. 2. 213/ 7a1477c63f 1cb2119cf f 00308487de39"
Account i ng Sessi on I d:
192. 168. 2. 213/ 7a1477c63f 1cb2119cf f 00308487de39
17.2 ACCOUNTING REQUEST STOP
Account i ng Request ( 4) ( i d=0, l =118)

User Dat agr amPr ot ocol , Sr c Por t : r adacct ( 1813) , Dst Por t : r adacct
( 1813)
Sour ce por t : r adacct ( 1813)
Dest i nat i on por t : r adacct ( 1813)
Lengt h: 126
Checksum: 0x8f e5 ( cor r ect )
Radi us Pr ot ocol
Code: Account i ng Request ( 4)
Packet i dent i f i er : 0x0 ( 0)
Lengt h: 118
Aut hent i cat or : 0x37346230646335313636333334383733
At t r i but e val ue pai r s
t : NAS I P Addr ess( 4) l : 6, Val ue: 192. 168. 2. 215
Nas I P Addr ess: 192. 168. 2. 215 ( 192. 168. 2. 215)
t : User Name( 1) l : 10, Val ue: " 98765432"
User - Name: 98765432
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 98/103

t : Cal l ed St at i on I d( 30) l : 6, Val ue: " 6000"
Cal l ed- St at i on- I d: 6000
t : Cal l i ng St at i on I d( 31) l : 10, Val ue: " 98765432"
Cal l i ng- St at i on- I d: 98765432
t : Acct St at us Type( 40) l : 6, Val ue: St op( 2)
Account i ng St at us Type: St op ( 2)
t : Ser vi ce Type( 6) l : 6, Val ue: Voi ce( 12)
Ser vi ce- Type: Voi ce ( 12)
t : Acct Sessi on I d( 44) l : 48,
Val ue: " 192. 168. 2. 213/ a29f 544d3f 1cb211856700308487de39"
Account i ng Sessi on I d:
192. 168. 2. 213/ a29f 544d3f 1cb211856700308487de39
t : Sessi on Ti meout ( 27) l : 6, Val ue: 0
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 99/103

18 APPENDIX B - SS7 NETWORK OVERVIEW
The SS7 network can be represented in an easy to understand topology as shown
below which can describe any SS7 interconnect. Some interconnects only require a
minimal understanding of this topology whilst more complex interconnects require a
greater in depth understanding, however Squire Technologies have designed the
configuration parameters of the SVI SoftSwitch to enable a simple configuration
interface that provides an intuitive configuration syntax for simple configurations but
powerful enough for complex interconnects. Squire Technologies under any systems
general warranty will provide support to enable the client to achieve interconnect
configuration within minutes.

The following shows the general representation of an SS7 interconnect. Table 1
defines the terms used with in the diagram. This diagram is only a configuration
overview of the network with relationship to a point of interconnect.

Item Name Description
Originating Point The Originating Point describes the equipment that is
interconnecting into the SS7 network. The originating
point will be provided with a unique pointcode by the
network provider allowing for identification of this
point with in the SS7 network. The originating point
can be assumed to be the SVI SoftSwitch
1 Signalling Link The SS7 network uses the signalling links to transport
the call information for a particular interconnect. In
SS7 the signalling links are not on every TDM
interface. A single SS7 signalling link can control the
calls across multiple TDM interfaces allowing for a
distributed architecture.

Adjacent
Point 0
Adjacent
Point 1
Adjacent
Point m
Originating
Point 0
Destination
Point 0
Destination
Point 1
Destination
Point n
1
1
3
3
2
4
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 100/103

2 Linkset A number of links can be grouped into a linkset that
connects to an adjacent point. Each signalling link is
provided with a unique code called a signalling link
code (SLC). Traffic is load-shared across this linkset.
The signaling links within a linkset also provide a
redundant transport mechanism. Therefore the more
links there are to a linkset the higher the transport
bandwidth is and the higher the redundancy.
Adjacent Point The Adjacent point is the SS7 equipment which the
signaling links terminate on. This equipment will also
have a unique point code. This equipment may be
either STP equipment or SSP equipment depending on
type of interconnect
Destination Point The Destination Point of the SS7 network defines the
switching equipment within the PSTN network which
terminates the TDM interfaces of this interconnect.
This point is also allocated a unique pointcode within
the SS7 network. If the adjacent point is a SSP or MSC
interconnect the destination point will be the same as
the adjacent point.
3 Route The route defines which adjacent point the destination
point can receive and transmit signalling traffic to. A
particular destination point may have a number of
routes to different adjacent points.
4 Routeset A routeset is made up of a number of routes. This
allows for redundancy with in the SS7 network
allowing for communication from the originating point
to the destination point even if a particular adjacent
point fails.

These modules and terms will be understood by all SS7 interconnect providers. In
General these configurations can be broken down into two main interconnects A and
F link configurations. These two configurations are described in the following
sections.
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 101/103

18.1 F LINK INTERCONNECT
An F link interconnect provides an SS7 connection where the signalling and all TDM
traffic is terminated on the same equipment. TDM interfaces [1] will usually carry
both voice and signalling links. The signalling links will be terminated on the SVI
9220 with the remaining voice channels on these cables being switched (drop and
insert) onto a separate TDM interface and feed out onto the other network. The
remaining TDM interfaces are connected directly between the two networks

Figure 2 shows a SSP interconnect.

Figure 2 only showed the SVI9220 interconnecting to one SS7 switch. The SVI 9220
has the capability of connecting up to sixteen adjacent points which equates to sixteen
SS7 switches connecting to the same SVI 9220 via F links.
SS7 Network
SS7
Switch
SVI
1
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 102/103

18.2 A LINK INTERCONNECT
An A link interconnect provides connections directly into the SS7 network generally
via redundant STP pairs. STPs or signalling transfer points provide a secure and fully
redundant signalling only network. The SVI 9220 connects directly to the two STPS
(or adjacent points) and terminates directly the signalling links. In general no voice
circuits are present on the TDM interfaces that are carrying the signalling links so no
drop and insert TDM interfaces are required. The STPs direct the signalling
information generated at the originating point [1] through the redundant network to
the appropriate SSP. The SSP terminates the voice circuits associated with the call
and presents them to the media gateways via the voice only TDM interface [2]. The
SSP interconnects can be many miles from the STP SS7 interconnect allowing for
centralised routing of traffic over many different territories.

The SVI 9220 has the capability of providing interconnect up to 256 destination SSPs
providing a comprehensive interconnect solution for all sizes of networks.
SVI

STP
SS7
Network
B
STP STP
STP
SSP
SSP
1
2
User Guide

Squire Technologies
Confidential

Part Number:
Version / Date: 1.8,/ 09/11/03
Author: squire
Page: 103/103

19 APPENDIX C - THE CALLCONTROL RESOURCE
The Call Control resource can be used by TDM Circuits to specify various parameters
that affect the way a call progresses.
Most of these parameters are fine-tuning mechanisms, and do not normally need
to be set by the user.

Ci r cui t 1- 31 Cal l Cont r ol 0

INS In use Status Describes the status of the
resource
NIU Resource not in use
Tid The inter-digit timer value. On
overlap calls, the time between
the last digit being received and
the call being considered ready
to route.
Seconds. Default 5
Tcf The channel-free timer. If a call
does not clear successfully, after
this time, the call will be forced
to clear
Seconds. Default 120
Tsus The suspend timer. (ISUP only)
when a SUSPEND is received,
after this period of time the call
will be cleared if a RESUME is
not received
Seconds. Default 60
COTHandling If True, COT calls are accepted.
If false, COT calls and COT
tests are rejected
Default True
Overlap Whether this circuit/supports
Overlap.
True/False
Tacm If set, this timer causes an ACM
to be sent to the incoming party
after this time, even if no ACM
has been received on the
outgoing side
Seconds. Off by default.
ISUP ISUP Circuits only the ISUP
resource for this circuit

Svi 9220 User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Svi 9220 User Guide

Uploaded by

Copyright:

Available Formats

Squire Technologies 2007

You might also like