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 JE

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

JE

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 JE

2/08/05 1.10 First Draft of next version just Type 2 CDR at the moment. Please update this comment b4 release

JE

17/10/05 1.11 Fixed Various Errors JE

8/12/05 1.12 Revised Registration Functionality JE

14/12/05 1.13 Updated radius and RC resources JE

19/01/06 1.14 Added Multiple Customer Configuration via Loadfile

JW

15/2/06 1.15 Added E1 LED status JE

21/2/06 1.16 Added SCCP connection-oriented JE

21/02/06 2 Added SNMP resource separated out from SoftSwitch

AC





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





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





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





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





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





1 INTRODUCTION

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





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





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





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





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





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





3.9 SIGNALLING INTERFACE CARDS The signalling interface cards provide standard RJ45 connectivity. The following diagram shows the pin out of the RJ45 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 J1 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

FlashingColour

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





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.





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.





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. [root@localhost/root]

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





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 [root@localhost/root]/sbin/chkconfig --list 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. [root@localhost/root]/sbin/chkconfig list gw 0:off 1:off 2:off 3:on 4:on 5:on 6:off [root@localhost/root] If the script is present but not started at power up the following will be displayed [root@localhost/root]/sbin/chkconfig list gw 0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@localhost/root]

4.4.1.1 Stopping Automatic Startup To stop automatic startup the following is typed at the command line [root@localhost/root]/sbin/chkconfig gw off

4.4.1.2 Starting Automatic Startup To start automatic startup the following is typed at the command line [root@localhost/root]/sbin/chkconfig gw on





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. [root@localhost/root]service gw start

4.5.2 MANUALLY STOPPING THE SYSTEM

To manually stop the system, enter the following command. [root@localhost/root]service gw stop

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 [root@localhost/root]/sbin/shutdown r now To halt the system allowing for the unit to be powered off type at the command line [root@localhost/root]/sbin/shutdown 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. [root@localhost/root]/user/sbin/netconfig To apply the new configuration either restart the system or at a command prompt type the command [root@localhost/root] service network restart





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 [root@localhost/root]/usr/bin/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.





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





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

&





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

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.





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





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.





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





7.2.1.1 Driver Configuration Syntax

7.2.1.1.1 Attributes Attribute Description Values

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





7.2.1.3 Interface Configuration

7.2.1.3.1 Interface Attributes Attribute Description Values

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 Attribute Description Values

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





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

Driver 0 Status Start Driver 0 Type NS700 Card 0 Status Start Card 0 Type NS700 Card 0 Driver 0 Card 0 Download vxwpcdld002089029.01.s Card 0 FPGA indepdld001134102.mcs Card 0 Role A Primary Master Card 0 Source Port 1 Interface 0-3 Status Start Interface 0-3 Card 0 Interface 0-3 CRC CRC Off Interface 0-3 Electrical E1 120 HDB3





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 Driver 0 Status Start Driver 0 Type NS700 Driver Card 0 Status Start Card 0 Type NS700 Card 0 Driver 0 Card 0 Download vxwpcdld002089029.01.s Card 0 FPGA indepdld001134102.mcs Card 0 Role Internal Card 0 Source none Interface 0-3 Status Start Interface 0-3 Card 0 Interface 0-3 CRC CRC Off Interface 0-3 Electrical E1 120 HDB3 Example 2

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

Driver 0 Status Start Driver 0 Type NS700 Driver Card 0-1 Status Start Card 0-1 Type NS700 Card 0-1 Driver 0 Card 0-1 Download vxwpcdld002089029.01.s Card 0-1 FPGA indepdld001134102.mcs Card 0 Role A Slave Card 0 Source none Card 1 Role A Primary Master Card 1 Source Port 2 Interface 0-7 Status Start Interface 0-3 Card 0 Interface 4-7 Card 1 Interface 0-7 CRC CRC Off Interface 0-7 Electrical E1 120 HDB3 In this example card 0 is the slave card and card 1 is the Master card as indicated above.





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. Timing Priority 0 Status Start Timing Priority 0 Interface 0 Timing Priority 1 Status Start Timing Priority 1 Interface 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






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.





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 Status Start * do not connect signalling timeslot TsMap 16 Status Niu TsMap 1-31 NS700 TsMap TsMap 1-31 Card 0 TsMap 1-31 Duplex 1 TsMap 1-31 srctype E1Interface * E1 interface port 0 TsMap 1-31 srcstream 0 TsMap 1-31 srctimeslot 1-31 TsMap 1-31 desttype E1Interface *E1 interface port 2 TsMap 1-31 deststream 2 TsMap 1-31 desttimeslot 1-31

TDM Interfaces

H100/MVIP Telephony Bus

Switching Matrix

HDLC Controller





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.


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.






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


OSF Linkset Present Status Describes the status of the linkset NIU

Signalling link not Present

Type Describes the type of signalling link SS7 Linkset





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.


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





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 Specifies the instance of the 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.





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. * Setup originating point of the SVI SoftSwitch Originating Point 0 Status Start Originating Point 0 Stack 0 Originating Point 0 Driver 0 Originating Point 0 Type ISUP Originating Point Originating Point 0 PointCode 1111 Originating Point 0 NI 2 Signalling Link 0-1 Status Start Signalling Link 0-1 Type ISUP signalling Link Signalling Link 0-1 Interface 0-1 Signalling Link 0-1 timeslot 16 Signalling Link 0-1 slc 0-1 Signalling Link 0-1 Originating 0 Signalling Link 0-1 Linkset 0 Signalling Link 0-1 map 0-1 *Setup up the adjacent point/linkset Linkset 0 Status Start Linkset 0 Originating 0 Linkset 0 PointCode 2222 Linkset 0 NI 2 Destination Point 0 Status Start Destination Point 0 Type ISUP Destination Point Destination Point 0 PointCode 2222 Destination Point 0 NI 2

Adjacent Point 0

Originating Point 0

Destination Point 0

SLC 0 SLC 1

OPC 1111 DPC 2222





7.2.6.2 Interconnect to 2 SSPs SoftSwitch originating point code 1111 SSP 0

o Point code 2222 o Two signalling links

SLC 0, interface 0 timeslot 16 SLC 1, interface 1 timeslot 16

SSP 1 o Point code 3333 o Two signalling links

SLC 1, interface 2, timeslot 1 SLC 2, interface 3, 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. * Setup originating point of the SVI SoftSwitch Signalling Link 2-3 Status Start Signalling Link 2-3 Type ISUP signalling Link Signalling Link 2-3 Originating 0 Signalling Link 2-3 Linkset 1 Signalling Link 2-3 Interface 2-3 Signalling Link 2-3 timeslot 1 Signalling Link 2-3 slc 1-2 Signalling Link 2-3 map 2-3 *Setup up the adjacent point/linkset Linkset 1 Status Start Linkset 1 Originating 0 Linkset 1 PointCode 3333 *show that linkset is not combined with another linkset by setting *the combined attribute to the same value as this resources instance Linkset 1 combined 1 Linkset 1 NI 2 Destination Point 1 Status Start Destination Point 1 Type SS7 Destination Point Destination Point 1 PointCode 3333 Destination Point 1 NI 2 *indicate which instance of the linkset resource * the destination is associated with Destination Point 1 Primary 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





7.2.6.3 Interconnect to two STPs SoftSwitch originating point code 1111 STP 0

o Point code 2222 o One Linkset with Two signalling links

SLC 0, interface 0 timeslot 16 STP 1

o Point code 3333 o One Linkset with Two signalling links

SLC 0, interface 1, timeslot 16 SSP 0

o Point Code 4444 o Terminates the bearer circuits for the SVIs provisioned Cics

* Setup originating point of the SVI SoftSwitch Originating Point 0 Status Start Originating Point 0 Stack 0 Originating Point 0 Driver 0 Originating Point 0 Type ISUP Originating Point Originating Point 0 PointCode 1111 Originating Point 0 NI 2 Signalling Link 0 Status Start Signalling Link 0 Type ISUP signalling Link Signalling Link 0 Interface 0 Signalling Link 0 timeslot 16 Signalling Link 0 slc 0 Signalling Link 0 Originating 0 Signalling Link 0 Linkset 0 Signalling Link 0 map 0 Signalling Link 1 Status Start Signalling Link 1 Type ISUP signalling Link Signalling Link 1 Originating 0 Signalling Link 1 Linkset 1 Signalling Link 1 Interface 1

Adjacent Point 0 DPC 2222

Originating Point 0

SSP 0 DPC 4444

SLC 0 OPC 1111

Adjacent Point 1 DPC 3333

SLC 0





Signalling Link 1 timeslot 16 Signalling Link 1 slc 0 Signalling Link 1 map 1 *Setup up the first adjacent point/linkset Linkset 0 Status Start Linkset 0 Originating 0 Linkset 0 PointCode 2222 *indicate that linkset is combined with *another linkset by setting the combined attribute to the *other resource's instance Linkset 0 combined 1 Linkset 0 NI 2 Destination Point 0 Status Start Destination Point 0 Type ISUP Destination Point Destination Point 0 PointCode 2222 Destination Point 0 NI 2 *indicate which instance of the linkset resource * the destination is associated with Destination Point 0 Primary 0 Destination Point 0 Secondary 1 *Setup up the second adjacent point/linkset Linkset 1 Status Start Linkset 1 Originating 0 Linkset 1 PointCode 3333 *indicate that linkset is combined with *another linkset by setting the combined attribute to the *other resource's instance Linkset 1 combined 0 Linkset 1 NI 2 Destination Point 1 Status start Destination Point 1 Type SS7 Destination Point Destination Point 1 PointCode 3333 Destination Point 1 NI 2 *indicate which instance of the linkset resource * the destination is associated with Destination Point 1 Primary 1 Destination Point 1 Secondary 0 ** Add destination point of the switch carrying the cics. Destination Point 2 Status Start Destination Point 2 Type SS7 Destination Point Destination Point 2 PointCode 4444 Destination Point 2 NI 2 *indicate which instance of the linkset resource * the destination is associated with Destination Point 2 Primary 0 Destination Point 2 Secondary 1 ** Note that Circuit Resources must have their opc and dpc values set ** to the correct DPC (ie the DPC of the switch where their bearer ** circuits terminate)





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





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 NIU Resource not present

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





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)






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.


Status Describes the status of originating point at startup

INS: Start Resource NIU: Resource not present

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





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

Type Describes the type of 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 Specifies the instance of the originating point that the destination is associated to

8 bit number





7.3.3 ISUP IP RESOURCE SYNTAX

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

Attribute Description Values Status Describes the status of

originating point at startup OSC: Start Resource NIU: Resource not present

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

*Setup M3UA interconnect Driver 0 status Start Driver 0 type ns700 driver Originating Point 0 Status Start Originating Point 0 Type SIGTRAN Originating Point Originating Point 0 pointcode 1000 Originating Point 0 ni 2 Originating Point 0 driver 0 Destination Point 0 status Start Destination Point 0 type isup destination point Destination Point 0 pointcode 2000 Destination Point 0 ni 2 Destination Point 0 originating 0 SCTP 0 Status Start SCTP 0 local address 192.168.2.235 SCTP 0 remote address 192.168.2.229 SCTP 0 local port 2905 SCTP 0 remote port 2905 SCTP 0 ASP 0





ASP 0 Status Start ASP 0 Originating Point 0 ASP 0 IsupIP 4 ASP 0 SCTP 0 AS 0 Status Start AS 0 Originating Point 0 AS 0 Destination Point 0 AS 0 IP Resource 4 IP 4 Status Start IP 4 name ISUP skt IP 4 type telnet ip IP 4 SocketType Server IP 4 PacketOwner SCTP IP 4 MntOwner Maintenance IP 4 packaged Fixed IP 4 Port 3020





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





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

Attribute Description Values OSC Bring in service Status Describes the status of the

resource NIU


Type Describes the type of 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





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

Attribute Description Values 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 o

svi 9220 user guide

Documents