Specifications

ManualsBrandsDialogic ManualsNetwork CardTX4000 PCI SS7

100 Crossing Boulevard

Framingham, MA 01702-5406 US

www.nmscommunications.com

NMS SS7 Configuration Manual

9000-6464-26

Summary of content (147 pages)

PAGE 1
NMS SS7 Configuration Manual 9000-6464-26 100 Crossing Boulevard Framingham, MA 01702-5406 USA www.nmscommunications.
PAGE 2
NMS SS7 Configuration Manual No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of NMS Communications Corporation. © 2006 NMS Communications Corporation. All Rights Reserved. Alliance Generation is a registered trademark of NMS Communications Corporation or its subsidiaries.
PAGE 3
Table Of Contents Chapter 1: Introduction .................................................................................7 Chapter 2: Configuration overview ................................................................9 Sample SS7 configurations ........................................................................... 9 Configuration summary ...............................................................................11 Chapter 3: Configuring TDM (TX 4000/C) ........................................
PAGE 4
Introduction NMS SS7 Configuration Manual Configuring multiple OPC emulation ..............................................................59 Configuring multiple OPC emulation for a single network ...............................59 Emulating different point codes to directly connected signaling points .............62 Configuring multiple OPC emulation for multiple networks .............................64 Configuring MTP for the Japan-NTT variant ....................................................
PAGE 5
NMS SS7 Configuration Manual Introduction Chapter 8: Configuring TCAP......................................................................119 TCAP configuration overview ...................................................................... 119 Creating the TCAP configuration ................................................................. 120 Sample TCAP configuration file ................................................................ 120 TCAP configuration reference .................................
PAGE 6
PAGE 7
1 Introduction The NMS SS7 Configuration Manual explains how to configure NMS SS7 and bring the links into service.
PAGE 8
PAGE 9
2 Configuration overview Sample SS7 configurations Depending on the physical hardware configuration of your TX boards, the SS7 link interface between the boards can be one of the following: • A single timeslot on one of the T1/E1 trunks. TX 3220/C boards require a dual-T1 or dual-E1 daughterboard or a rear transition board. TX 4000/C boards include an on-board quad T1/E1 interface. • All of the timeslots on a T1/E1 trunk. High speed links (HSL) meet the ANSI T1.111-1996 and Q.703/Annex A standards.
PAGE 10
Configuration overview NMS SS7 Configuration Manual The following illustration shows the ANSI standalone sample configuration: PC bus Host TX board 1 txalarm Point code 1.1.1 utility TX device driver SS7 link (T1/E1 crossover cable) TX board 2 Point code 1.1.
PAGE 11
NMS SS7 Configuration Manual Configuration overview Configuration summary Before starting the NMS SS7 configuration, complete the following installations: Step Description For details, refer to... 1 Install the TX board The appropriate board installation manual. 2 Install the Natural Access development environment under Windows or UNIX. The Natural Access Installation booklet and the Natural Access Developer's Reference Manual. 3 Install the NMS SS7 software The NMS SS7 Installation booklet.
PAGE 12
PAGE 13
3 Configuring TDM (TX 4000/C) TDM configuration overview (TX 4000/C) Before T1/E1 trunks or H.100/H.110 bus channels (also known as TDM channels) can be used for physical SS7 links, you must download a TDM configuration to the TX board. To configure a TX 4000/C board, create a TDM configuration file (txcfgn.txt) that defines TDM clocking control, configures all T1/E1 trunks, and defines all dedicated data channels. Each TX board in a system requires a separate TDM configuration file.
PAGE 14
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual The following example shows a txcfg.txt for a TX 4000 board operating in T1 mode: # T1 Example # Timing Configurations: # # use clock recovered from trunk 1 as board’s clock and drive H.100/H.
PAGE 15
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) • The sample configuration files contain commented out sections that define other types of TDM connections, such as E1 for files that default to T1 or H.100/H.110. To change from T1 to E1 or from T1 to H.100 for example, comment out the original configuration lines and paste a copy of the desired example lines, removing the comment character to activate the pasted lines. • Modify clocking control based on the specific environment.
PAGE 16
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual H.100 and H.110 bus clocking overview If the boards in a system are connected to each other on the CT bus, you must set up a bus clock to synchronize communications between the boards connected to the bus. To provide redundant and fault-tolerant clocking on the bus, configure alternative (fallback) clock sources to provide the clock signal if the primary source fails.
PAGE 17
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) Two CT bus clocks can run simultaneously on the bus. They are called A_CLOCK and B_CLOCK. The clock master can drive either one. When you set up CT bus clocking, choose one of these clocks for your master and slaves. The other one is a redundant signal that can be used by a secondary clock master (described in Secondary clock master fallback on page 22).
PAGE 18
Configuring TDM (TX 4000/C) In a system with no digital telephone network interfaces, an on-board oscillator can be used as the timing reference to drive the clock signals. This is called an OSC timing reference and is shown in the following illustration. Use OSC only if there is no external clock source available.
PAGE 19
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) The channel over which the timing reference signal is carried to the clock master is called NETREF, as shown in the following illustration: Timing reference channel CT bus clocks CT bus A_CLOCK B_CLOCK NETREF Primary clock master Driving A_CLOCK based on timing reference signal from NETREF Clock slave Clock slave Driving timing reference signal on NETREF based on external timing reference Clock slave Timing reference (digital trunk) On the H.
PAGE 20
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Fallback timing references Boards can optionally be assigned a backup (fallback) timing reference that it can use if its primary timing reference fails. For a clock master, the source for the fallback timing reference must be a different source than the one currently used by the clock master for its primary timing reference.
PAGE 21
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) The following table summarizes the timing references that a clock master can use: Timing reference Details NETWORK The timing signal from a digital trunk attached to the clock master board. Within the digital trunk interface, an 8 kHz reference is derived from the frequency of the incoming signal. The clock master is frequency-locked to this 8 kHz reference so that the long-term timing of the system matches that of the public telephone network.
PAGE 22
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Secondary clock master fallback You can set up a second device to be used as a backup or a secondary clock master if the primary clock master stops driving its CT bus clock (because both of its timing references failed, or it was hot-swapped out). Clock fallback for a secondary clock master works as follows: 1. As long as the primary clock master is driving its CT bus clock, the secondary clock master acts as a slave to the primary clock master.
PAGE 23
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) The following illustration shows a sample clock fallback configuration: Driving clock Clock source Fallback clock source H.110 Bus A_CLOCK A_CLOCK B_CLOCK B_CLOCK NETREF NETREF NETREF2 NETREF2 Board A Primary clock master (Network board) Drives A_CLOCK. Uses NETREF as timing reference. Falls back to network signal. Network (trunk connection) Board B Secondary clock master (Network board) Drives B_CLOCK. Uses A_CLOCK as timing reference.
PAGE 24
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Configuring clocking (TX 4000/C) The txcfg.txt clock command defines the clocking configuration of the TX 4000/C board main clock source. This clock is used as the internal clock for TX 4000/C boards. The clock signal can also be routed to other clocking signals. The clock source can be a clock signal of the H.100/H.110 bus, the TX board internal oscillator, or an oscillator or trunk connected to another device in the system (see H.100 and H.
PAGE 25
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) where netref speed optionally specifies the NETREF speed and is one of the following values: Value Description 8k 8 kHz NETREF clock signal. 15m 1.544 MHz NETREF clock signal. 20m 2.048 MHz NETREF clock signal. - Speed of NETREF clock signal not provided. where fallback source optionally specifies the clock signal to fall back to and is one of the following values: Value Description a H.100/H.110 bus A_CLOCK. b H.100/H.
PAGE 26
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Secondary clock master Follow these guidelines when configuring a TX 4000/C board as the secondary clock master: • It must receive its primary timing reference from the CT bus clock driven by the primary clock master (either A_CLOCK or B_CLOCK). • It must drive the CT bus clock not driven by the primary master. For example, if the primary clock master is driving A_CLOCK, the secondary clock master must drive B_CLOCK.
PAGE 27
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) where netref speed optionally specifies the NETREF speed and is one of the following values: Value Description 8k 8 kHz NETREF clock signal. 15m 1.544 MHz NETREF clock signal. 20m 2.048 MHz NETREF clock signal. - Speed of NETREF clock signal not provided. Configuring T1/E1 trunks (TX 4000/C) The txcfg.txt T1/E1 configuration command determines whether a TX 4000/C board's trunk is configured as E1 (e1cfg), T1 (t1cfg), or J1 (j1cfg) mode.
PAGE 28
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual where encoding is one of the following values: Value Description nozcs AMI encoding with no zero code suppression. hdb3 High density bipolar order 3. where master is one of the following values: Value Description true Local side of connection acts as timing source for this circuit. false Remote side of connection acts as timing source.
PAGE 29
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) Flag name Description XCRCI Transmission of CRC (4|6) bit inversion. DCOXC Center function of transmission circuitry enabled. ALMF Automatic loss of multiframe alignment when excessive CRC errors. Default is SET. AXS Automatic transmission of submultiframe status. Default is SET. EBP In asynchronous state, E-bit is set (valid only if AXS is set). Default is SET. DAIS Automatic AIS insertion disabled.
PAGE 30
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual E1 option values Option name Default Valid range Description XP0 0x14 0x00 through 0x1F Transmission of pulse shape mask (for 1st level). XP1 0x13 0x00 through 0x1F Transmission of pulse shape mask (for 2nd level). XP2 0x00 0x00 through 0x1F Transmission of pulse shape mask (for 3rd level). XP3 0x00 0x00 through 0x1F Transmission of pulse shape mask (for 4th level). RIL 0x02 0x00 through 0x07 Receive input threshold.
PAGE 31
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) where encoding is one of the following values: Value Description nozsc AMI encoding with no zero code suppression. b7zs Bit 7 stuffing with zero code suppression. b8zs Bipolar eight zero substitution. where build_out is one of the following values: Value Transmitter attenuation 0 0 dB 1 -7.5 dB 2 -15 dB 3 -22.
PAGE 32
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual T1 and J1 option flags The following table lists the T1 and J1 option flags. If the default of the option flag is SET, use ! flag name to clear. Flag name Description EXZE Extended code violation or excessive zero detection. SRAF F12: FS-bit of frame 12; ESF: bit 2 = 0. CRC CRC6 check or generation (ESF format only) enabled. Default is SET. AIS3 AIS detection only in asynchronous state.
PAGE 33
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) T1 and J1 option values Option name Default Valid range Description XP0 T1_XPM_0 (0xFF) 0x00 through 0x1F Transmission of pulse shape mask (for 1st level). See Line buildout values. XP1 T1_XPM_1 (0xFF) 0x00 through 0x1F Transmission of pulse shape mask (for 2nd level). See Line buildout values. XP2 T1_XPM_2 (0xFF) 0x00 through 0x1F Transmission of pulse shape mask (for 3rd level). See Line buildout values.
PAGE 34
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Configuring ports (TX 4000/C) The txcfg.txt port command defines a full-duplex connection between the TX 4000/C board communication controller and a remote SS7 connection over either the H.100/H.110 bus or over one of the board’s T1/E1 trunks. Port numbers are specified in the MTP configuration file as Tn where n is the port number. The port command abstracts the TX board’s internal local stream mapping scheme.
PAGE 35
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) The following table presents the local stream mapping scheme: Trunk connections (T1 or J1 trunks) Trunk connections (E1 trunks) SS7 communication controller Trunk Trunk Trunk Trunk 13, Trunk 17, Trunk 21, Trunk 25, Trunk 29, 1: 2: 3: 4: Trunk Trunk Trunk Trunk 13, Trunk 17, Trunk 21, Trunk 25, Trunk 29, 1: 2: 3: 4: Streams Streams Streams Streams 0 and 1, 4 and 5, 8 and 9, 12 and 5: Streams 16 and 6: Streams 20 and 7: Streams 24 and 8: Stre
PAGE 36
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual where outstream is interpreted based on the value of bus: If bus is... Then outstream (and implied instream) is... h100 Outbound H.100/H.110 stream number. The range is 0 through 31. If outstream is even, instream = outstream + 1. If outstream is odd, instream = outstream - 1. local Outbound local stream number. The range is based on the specific TX board type. See Local stream mapping scheme on page 34. instream = outstream.
PAGE 37
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) where inbus specifies the input source and is one of the following values: Value Description h100 Input source is the stream and timeslot from the H.100/H.110 bus. local Input source is the stream and timeslot from one of the TX board’s local streams (either a T1/E1 interface or an SS7 communication controller). where instream is the inbound stream number: 0 through 31 (Hbus); 0 through n (local).
PAGE 38
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual H.100/H.110 example This command: port 9 h100 2 7 creates the following TDM connections: • Local stream 72 timeslot 8 transmitting to H.100 stream 2 timeslot 7 • H.100 stream 3 timeslot 7 transmitting to local stream 72 timeslot 8 This command creates a full-duplex connection used by the MTP link defined as T9. Local stream 72 connects to and from the SS7 communication controller with timeslot 8 (port number 9 - 1). H.
PAGE 39
NMS SS7 Configuration Manual Configuring TDM (TX 4000/C) Example mapping of all non-signaling T1 channels (trunk 2) to trunk 3 This example shows the port and connect commands required to fully access the channels on T1 trunk 2. The example creates a single SS7 port on T1 channel 23 (trunk 2) and maps all other channels of trunk 2 to trunk 3. Command Description port 1 t1 2 23 Port 1 maps to T1 trunk 2 channel 23.
PAGE 40
Configuring TDM (TX 4000/C) NMS SS7 Configuration Manual Example mapping of all non-signaling E1 channels (trunk 1) to H.100/H.110 This example shows the port and connect commands required to fully access the channels on E1 trunk 1. The example creates a single SS7 port on E1 channel 1 (trunk 1) and maps all other channels of trunk 1 to the H.100/H.110 bus (transmitting to stream 30 and receiving from stream 31). Command Description port 1 e1 1 1 Port 1 maps to E1 trunk 1 channel 1.
PAGE 41
4 Configuring TDM (TX 3220/C) TDM configuration overview (TX 3220/C) Before T1/E1 trunks or H.100/H.110 bus channels (also known as TDM channels) can be used for physical SS7 links, you must download a TDM configuration to the TX board. To configure a TX 3220/C board, create a TDM configuration file (tdmcpn.txt under Windows and TDMcpn.txt under UNIX) that defines TDM clocking control, configures all T1/E1 trunks, and defines all dedicated data channels.
PAGE 42
Configuring TDM (TX 3220/C) NMS SS7 Configuration Manual The following example shows a tdmcp.
PAGE 43
NMS SS7 Configuration Manual Configuring TDM (TX 3220/C) Configuring clocking (TX 3220/C) A TX communications processor can either provide an H.100 or an H.110 TDM bus interface. The clocking entry describes the clocking configuration for the H.100/H.110 bus clock signals and secondary 8K clock signals. The clocking configuration statement syntax is: CLOCK clockmode SEC8K sec8kmode where clockmode is one of the following values: Value Description BUS Interface gets its timing signals from the H.100/H.
PAGE 44
Configuring TDM (TX 3220/C) NMS SS7 Configuration Manual Configuring T1/E1 trunks (TX 3220/C) The T1/E1 configuration entry for TX 3220/C boards consists of an identifier for the circuit (A or B) being configured and parameters specifying the circuit framing, line encoding, line buildout, robbed bit signaling, and loop master configuration: This parameter... Determines... Framing Framing format to be used for this T1/E1 circuit.
PAGE 45
NMS SS7 Configuration Manual Configuring TDM (TX 3220/C) Configuring ports (TX 3220/C) The port definition entry defines the characteristics of each dedicated data channel. Channels are always defined as full-duplex connections. For the H.100/H.110 bus, stream n is always paired with stream n+1. The following table describes the port configuration parameters: This parameter... Identifies...
PAGE 46
Configuring TDM (TX 3220/C) NMS SS7 Configuration Manual Generating the binary file Generate the binary TDM configuration file by running the tdmcfg utility on the text file according to the following syntax: tdmcfg -i filename where filename is the name of the TDM configuration text file (for example, tdmcp1.txt). The configuration utility generates the following files: File Description filename.bin Binary configuration file. filename.dbg Text representation of the binary file.
PAGE 47
5 Configuring MTP MTP configuration overview MTP 3 (Message Transfer Part 3) has two primary functions: Function Description Message routing and distribution Routes outgoing messages to specified destinations and distributes incoming messages to the appropriate user part or application. MTP uses a flexible configuration capable of supporting a wide variety of network routing and addressing requirements.
PAGE 48
Configuring MTP NMS SS7 Configuration Manual The following illustration shows the relationship between links, linksets, and routes: Combined linkset SS7 STP 1.1.0 TX MTP 1.1.100 Link 0 Link 1 Linkset 1 Link 2 Link 3 Linkset 2 Destination SP 1.1.200 Destination SP 1.1.201 SS7 STP 1.1.1 Route 1, DPC 1.1.0 Route 2, DPC 1.1.1 Route 3, DPC 1.1.200 Route4, DPC 1.1.201 Linkset 1 Adj DPC 1.1.0 Route 1,0 Route 2,1 Route 3 Route 4 End Linkset 2 Adj DPC 1.1.
PAGE 49
NMS SS7 Configuration Manual Configuring MTP MTP configuration considerations Configure MTP 3 as either a signal transfer point (STP) or as a signaling end point (SP). The primary difference between STP operation and SP operation is the handling of messages that MTP 3 receives from signaling links that are addressed to other destinations. When configured as an STP, MTP 3 searches for an outbound route to the message destination and, if found, routes the message over an outbound link.
PAGE 50
Configuring MTP NMS SS7 Configuration Manual Sample MTP 3 configuration file The following example is the ANSI configuration file for board 1 in the two-board sample configuration: #-----------------------------------------------# Overall MTP3 Parameters #-----------------------------------------------NODE_TYPE STP # choose STP [routing] or SP [non-routing] PC_FORMAT DFLT # Point code format: DFLT (8.8.8) / INTL (3.8.3) / # JNTT (7.4.5) POINT_CODE 1.1.
PAGE 51
NMS SS7 Configuration Manual Configuring MTP DIRECTION UP # default is DOWN ADJACENT_ROUTE FALSE END # # Route to board 2 # ROUTE 1 DPC 1.1.2 # board 2's point code LINK_TYPE ANSI # ANSI / ITU / JNTT / JTTC END # # #-----------------------------------------------# Linkset Parameters #-----------------------------------------------LINK_SET_DESCRIPTOR 1 ADJACENT_DPC 1.1.
PAGE 52
Configuring MTP NMS SS7 Configuration Manual Links configuration section The links configuration section defines the physical signaling links between the TX board and the adjacent signaling points. It contains a link configuration block for each SS7 link. The MTP 3 and MTP 2 configuration utilities scan the links section. The links section is the only section scanned by the MTP 2 configuration utility.
PAGE 53
NMS SS7 Configuration Manual Configuring MTP Route definition section Routes specify the destination signaling points (sub-networks or clusters when route masks are employed) that are accessible from the node being configured. Each route is assigned an up or down direction. Up routes are used to identify incoming messages that are to be routed up to the applications or user parts. One down route is required for each remote signaling point, network, or cluster accessible from the SP being configured.
PAGE 54
Configuring MTP NMS SS7 Configuration Manual Since the non-adjacent SP in the illustration (point code 1.1.200) is accessible from both STPs, the route entry for 1.1.200 is added to the linkset definitions for both linksets 1 and 2. Since the STPs are cross connected, the route to each STP is also added to both linksets 1 and 2 since STP 1.1.1 can be reached directly through linkset 2 or indirectly through linkset 1 with STP 1.1.0.
PAGE 55
NMS SS7 Configuration Manual Configuring MTP Using priorities Priority levels range from 0 (highest) to 15 (lowest). To use priorities, start with zero for the highest priority linkset for a given route and increment by one for lower priority linksets for that route. There can be no gaps in the priority assigned for a given route, although equal priorities are allowed. Use linkset priorities to ensure that the shortest path is taken by a message, when available.
PAGE 56
Configuring MTP NMS SS7 Configuration Manual The following configuration sample shows how to specify linkset priorities for the illustrated example: # # Routing Parameters # ROUTE 0 DPC 1.1.100 DIRECTION UP END # ROUTE 1 DPC 1.1.0 END # ROUTE 2 DPC 1.1.1 END # ROUTE 3 DPC 1.1.200 ADJACENT_ROUTE FALSE END # ROUTE 4 DPC 1.1.201 ADJACENT_ROUTE FALSE END # # Link Set Parameters # LINK_SET_DESCRIPTOR 1 ADJACENT_DPC 1.1.
PAGE 57
NMS SS7 Configuration Manual Configuring MTP Using routing masks Use routing masks to help decrease the size of the routing tables that must be configured. Routing masks are bit masks that specify a subset of a destination point code to be matched against the routing table when searching for a route for either an inbound or outbound message. Use routing masks to implement network and cluster routing in ANSI networks.
PAGE 58
Configuring MTP NMS SS7 Configuration Manual The following partial MTP configuration file configures routing masks: MAX_ROUTE_MASKS ROUTE_MASK ROUTE_MASK ROUTE_MASK #Routing Parameters ROUTE DPC DIRECTION END # ROUTE DPC END # ROUTE DPC END # ROUTE DPC END # ROUTE DPC ADJACENT_ROUTE END # ROUTE DPC ADJACENT_ROUTE END # ROUTE DPC ADJACENT_ROUTE END # Link set Parameters LINK_SET_DESCRIPTOR ADJACENT_DPC ROUTE_NUMBER ROUTE_NUMBER END # LINK_SET_DESCRIPTOR ADJACENT_DPC ROUTE_NUMBER ROUTE_NUM
PAGE 59
NMS SS7 Configuration Manual Configuring MTP Configuring multiple OPC emulation You can configure MTP to act as multiple point codes to the network and receive and send inbound traffic destined to a number of point codes.
PAGE 60
Configuring MTP NMS SS7 Configuration Manual NODE_TYPE STP POINT_CODE 1.1.100 # This node’s point code # #Link Parameters # LINK T1 # Link 0 to STP 1.1.0 LINK_SET 1 ADJACENT_DPC 1.1.0 END # LINK T2 # Link 1 to STP 1.1.1 LINK_SET 2 ADJACENT_DPC 1.1.1 END # #Routing Parameters # # Route UP from network to applications on this node # ROUTE 0 DPC 1.1.100 # this node DIRECTION UP END # ROUTE 1 DPC 1.1.0 # STP 1.1.0 END # ROUTE 2 DPC 1.1.1 # STP 1.1.1 END # ROUTE 3 DPC 1.1.
PAGE 61
NMS SS7 Configuration Manual Configuring MTP While the previous configuration allows upper layers to receive messages directed to 1.2.200 and 1.3.300, this is not sufficient for all upper layers to operate properly (for example, NMS ISUP). ISUP requires that a RESUME indication be returned for each OPC/DPC combination for which it has circuits defined, so it can activate those circuits and respond to incoming IAM messages.
PAGE 62
Configuring MTP ROUTE OPC DPC END # ROUTE OPC DPC END # # # Link set Parameters # LINK_SET_DESCRIPTOR ADJACENT_DPC ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER END # LINK_SET_DESCRIPTOR ADJACENT_DPC ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER END NMS SS7 Configuration Manual 6 1.2.200 1.1.200 # emulated point code # Route to non-adjacent 1.1.200 7 1.3.300 1.1.200 # emulated point code # Route to non-adjacent 1.1.200 1 1.1.0 1 2 3 6 7 2 1.1.
PAGE 63
NMS SS7 Configuration Manual LINK LINK_SET ADJACENT_DPC T1 2 1.1.1 Configuring MTP # Link 1 to STP 1.1.1 OPC 1.2.200 END # #Routing Parameters # # Route UP from network to applications on this node # ROUTE 0 DPC 1.1.100 # this node DIRECTION UP END # ROUTE 1 DPC 1.1.0 # STP 1.1.0 END # ROUTE 2 DPC 1.1.1 # STP 1.1.1 END # ROUTE 3 DPC 1.1.200 # Route to non-adjacent 1.1.200 END # ROUTE 4 DPC 1.2.200 # emulated point code DIRECTION UP END # ROUTE 5 DPC 1.3.
PAGE 64
Configuring MTP NMS SS7 Configuration Manual To avoid confusion when emulating different point codes to directly connected signaling points, NMS recommends that you specify the OPCs in each link and linkset and make sure they match between the linkset and the links. Configuring multiple OPC emulation for multiple networks In the previous configurations, outbound traffic is routed by destination point code (DPC) and signaling link selector (SLS) only.
PAGE 65
NMS SS7 Configuration Manual ROUTE DPC 4 1.1.200 OPC END # ROUTE DPC DIRECTION END # ROUTE DPC DIRECTION END # # # Link set Parameters # LINK_SET_DESCRIPTOR ADJACENT_DPC OPC 1.1.100 ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER END # LINK_SET_DESCRIPTOR ADJACENT_DPC OPC 1.2.200 ROUTE_NUMBER ROUTE_NUMBER ROUTE_NUMBER END 1.2.200 Configuring MTP # Route to non-adjacent 1.1.200 5 1.2.200 UP # emulated point code 6 1.3.300 UP # emulated point code 1 1.1.0 # link set to STP 1.1.0 1 2 3 2 1.1.
PAGE 66
Configuring MTP NMS SS7 Configuration Manual For example: PC_FORMAT ... LINK LINK_TYPE ADJACENT_DPC ... JNTT S1 JNTT 1.1.2 is equivalent to: ... LINK LINK_TYPE ADJACENT_DPC ... S1 JNTT 0x421 Sample MTP configuration file for the Japan-NTT protocol variant The following sample MTP 3 configuration file configures two V.
PAGE 67
NMS SS7 Configuration Manual Configuring MTP NSAP 0 # isup LINK_TYPE JNTT END # NSAP 1 # spare LINK_TYPE JNTT END # # #Routing Parameters #-----------------# # Route UP from network to applications on this node # ROUTE 0 LINK_TYPE JNTT DPC 1.1.1 # this node DIRECTION UP # default is DOWN ADJACENT_ROUTE FALSE END # # Route to Adjacent node # ROUTE 1 LINK_TYPE JNTT DPC 1.1.2 END # # # Linkset Parameters #------------------LINK_SET_DESCRIPTOR 1 ADJACENT_DPC 1.1.
PAGE 68
Configuring MTP NMS SS7 Configuration Manual For example: PC_FORMAT ... LINK LINK_TYPE ADJACENT_DPC ... JNTT T1 JTTC 1.1.2 is equivalent to: ... LINK LINK_TYPE ADJACENT_DPC ... • • T1 JTTC 0x421 Set the following general parameters: • RESTART_REQUIRED to FALSE. • DISABLE_UPU to TRUE. Set the following parameters for each link definition: • LSSU_LEN to 1. • IDLE_FREQ to 24. • RT_FREQ to 24.
PAGE 69
NMS SS7 Configuration Manual Configuring MTP # Link 1 # LINK T2 # TDM port 2 LINK_SET 1 LINK_TYPE JTTC ADJACENT_DPC 1.1.2 LINK_SLC 1 LSSU_LEN 1 RT_FREQ 24 IDLE_FREQ 24 END # #User Parameters (NSAP definition) #--------------------------------# NSAP 0 # isup LINK_TYPE JTTC END # NSAP 1 # spare LINK_TYPE JTTC END # # #Routing Parameters #-----------------# # Route UP from network to applications on this node # ROUTE 0 LINK_TYPE JTTC DPC 1.1.
PAGE 70
Configuring MTP NMS SS7 Configuration Manual Configuring high speed links (HSL) High speed links (HSL) meet the ANSI T1.111-1996 and Q.703/Annex A standards. Each HSL occupies a full (unchannelized) T1/E1 line and transfers data at the rate of 2.0 (1.544) Mbps. Parameters Configuring high speed links in MTP uses two parameters, HS_LINK and HS_EXT_SEQ, which are contained in the Link section of the configuration file.
PAGE 71
NMS SS7 Configuration Manual Configuring MTP MTP configuration reference This topic presents the MTP configuration file parameters: • General parameters • Link parameters • NSAP parameters • Routing parameters • Linkset parameters General parameters The following table lists the configurable parameters in the MTP 3 general configuration section. The default values for all timers at the MTP 3 level are shown below in tenths of a second.
PAGE 72
Configuring MTP Parameter Default VALIDATE_SSF NMS SS7 Configuration Manual Valid values Description TRUE TRUE/YES FALSE/NO If TRUE, MTP 3 validates incoming MTP 3 signaling network management (SNM) and test (SLTM/SLTA) messages. Messages with an SSF that does not match the value configured for the link on which the message was received are rejected. If FALSE, the SSF is not checked on incoming MTP 3 management or test messages (any SSF value is accepted).
PAGE 73
NMS SS7 Configuration Manual Parameter Default Configuring MTP Valid values Description TIMER_T23_ANSI 300 1 through 65535 ANSI restart timer at restarting SP waiting for TRA messages. TIMER_T26_ANSI 130 1 through 65535 ANSI restart timer at restarting SP waiting to repeat TRW message. TIMER_T27_ANSI 30 1 through 65535 Minimum duration of unavailability for full restart. TIMER_TRTEINST 18000 0 through 65535 Internal route instance timer (how long a route instance is valid).
PAGE 74
Configuring MTP NMS SS7 Configuration Manual Link parameters The following tables list the MTP 3 and MTP 2 configuration parameters applicable to each link: MTP 3 link parameters Parameter Default Valid values Description PORT None S1 through 4 (serial) T1 through 16|32 (TDM) R (remote) Sn for serial (V.35) (TX 3220 or TX 3220C only). Tn for T1, E1, H.100, and H.110. R for remote links (links on the other board in a redundant system). LINK None 0 through 15|31 Zero-based link number.
PAGE 75
NMS SS7 Configuration Manual Configuring MTP Parameter Default Valid values Description USE_PRIORITY TRUE TRUE FALSE If TRUE, message priorities generated by user parts are inserted into the SIO octet (spare bits) of outgoing messages. If FALSE, the SIO spare bits are set to zero. Usually set to TRUE in ANSI networks and FALSE in ITU-T networks. MGNT_MSG_PRIORITY 3 0 through 3 Priority to use for MTP3 management messages.
PAGE 76
Configuring MTP NMS SS7 Configuration Manual Parameter Default Valid values Description P2QUE_LENGTH 64 (p1Qlen + 2) through 1024 Transmit queue length threshold at which the congestion priority is raised to level 2. P3QUE_LENGTH 128 (p2Qlen + 2) through 1024 Transmit queue length threshold at which the congestion priority is raised to level 3.
PAGE 77
NMS SS7 Configuration Manual Configuring MTP Parameter Default Valid values Description TIMER_T31 50 0 through 65535 Internal BSN requested timer (not ANSI T31). TIMER_T32 100 0 through 65535 Time to wait for response to SLTM timer (ANSI T1.111.7 timer T1, not ANSI T32). TIMER_T33 200 0 through 65535 Signaling link connection timer (not ANSI T33). TIMER_T34 600 0 through 65535 Periodic signaling link test timer (ANSI T1.111.7 timer T2, not ANSI T34).
PAGE 78
Configuring MTP NMS SS7 Configuration Manual MTP 2 link parameters All layer 2 timer values are specified in tenths of a second (60 = 6 seconds). Parameter Default Valid values Description ERR_TYPE NORMAL NORMAL PCR Error correction method. TRUE FALSE Setting this parameter to TRUE, notifies MTP that high speed links are in effect and automatically sets HS_EXT_SEQ to TRUE.
PAGE 79
NMS SS7 Configuration Manual Configuring MTP Parameter Default Valid values Description L2_T7 20 1 through 65535 Timer excessive delay of acknowledgement. L2_T10 30 1 through 65535 Amount of time MTP 2 can be isolated from a remote MTP 3 before sending processor outage (SIPO). L2_T11 20 1 through 65535 Time to wait for a flow control acknowledgement from MTP 3 before sending another flow control indication.
PAGE 80
Configuring MTP NMS SS7 Configuration Manual Parameter Default Valid values Description USE_FLAGS TRUE TRUE FALSE If TRUE, use flags between frames. If FALSE, idle between frames. MIN_FLAGS 0 0 through 15 Minimum number of additional flags between frames (in addition to shared flag). ISO_THRESH 1000 1 through 65535 Number of messages queued to MTP 3 while isolated that cause MTP 2 to begin processor outage (SIPOs).
PAGE 81
NMS SS7 Configuration Manual Configuring MTP Network service access point (NSAP) parameters The following table lists the parameters used for defining an NSAP: Parameter Default Valid values Description NSAP None 0 through MAX_USERS - 1 NSAP number. This parameter is required. LINK_TYPE ANSI ANSI ITU JNTT JTTC MTP 3 protocol variant used by this MTP 3 user part. P0QUE_LENGTH 0 2 through 1024 Receive queue length threshold at which the congestion priority is raised to level 0.
PAGE 82
Configuring MTP NMS SS7 Configuration Manual Parameter Default Valid values Description SUB_SERVICE 2 0 through 3 Overrides SSF parameter. Use either SUB_SERVICE or the SSF parameter. DIRECTION DOWN UP DOWN Route direction. Up routes result in messages being routed to user parts or applications on this node; Down routes are routes to remote signaling points.
PAGE 83
NMS SS7 Configuration Manual Configuring MTP Linkset parameters The following table lists the parameters for defining a linkset: Parameter Default Valid values Description LINK_SET_DESCRIPTOR None 1 through MAX_LINKSETS Linkset identifier number; referenced in LINK_SET parameter of each individual link. ADJACENT_DPC None N/A Point code of the adjacent SP that terminates this linkset. Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101).
PAGE 84
PAGE 85
6 Configuring ISUP ISUP configuration overview The ISUP (ISDN User Part) layer provides the interface for applications to establish, maintain, and clear circuit switched connections through the SS7 network in accordance with the following recommendations: • CCITT Q.761 - Q.764 (Blue Book, White Book, and 1997) • ANSI T1.113 (1988, 1992, and 1995) • ETSI Version 2 • ETSI Version 3 • Q.767 • NTT Q.
PAGE 86
Configuring ISUP NMS SS7 Configuration Manual The following illustration shows the concept of user SAPs and network SAPs: ISUP application User SAP User SAP ISUP layer SCCP layer ISUP NSAP SCCP NSAP NSAP 0 SIO x85 MTP 3 NSAPs NSAP 1 SIO x83 MTP 3 layer Creating the ISUP configuration NMS SS7 provides sample files for ANSI standalone and redundant configurations and ITU standalone and redundant configurations that you can modify for your specifications.
PAGE 87
NMS SS7 Configuration Manual Configuring ISUP Sample ISUP configuration file The following example is the configuration file for board 1 in the two-board ANSI sample configuration: # General configuration parameters MAX_SAPS 2 MAX_NSAPS 2 MAX_CIRCUITS 96 MAX_GROUPS 5 MAX_CALLREFS 96 MAX_ROUTES 10 OPC 1.1.1 CLLINAME NMSsfwB2.
PAGE 88
Configuring ISUP NMS SS7 Configuration Manual Configuring ISUP for the Japan-NTT variant Follow these guidelines when configuring the ISUP layer for Japan-NTT network operation: • Set the SWITCH_TYPE attribute for all USAP, NSAP, and CIRCUIT entries to JNTT. • Specify 16-bit point codes in either hexadecimal or x.y.
PAGE 89
NMS SS7 Configuration Manual Configuring ISUP ISUP configuration reference This topic presents the ISUP configuration file parameters: • General parameters • SAP parameters • NSAP parameters • Circuit group parameters General parameters The general parameters control the overall operation of the ISUP layer process. Note: All ISUP timer values are in seconds. Parameter Default Valid values Description MAX_SAPS 1 1 Maximum number of user applications.
PAGE 90
Configuring ISUP NMS SS7 Configuration Manual Parameter Default Valid values Description T19_TIMER 60 0 through 65535 Time to wait for a response to an initial group blocking message that was sent. T20_TIMER 12 0 through 65535 Time to wait for a response to a group unblocking message that was sent. T21_TIMER 60 0 through 65535 Time to wait for a response to an initial group unblocking message that was sent.
PAGE 91
NMS SS7 Configuration Manual Configuring ISUP Parameter Default Valid values Description QCONGABATE1 400 0 through 65535 Queue to the host application congestion level 1 abatement threshold. QCONGONSET2 900 0 through 65535 Queue to the host application congestion level 2 onset. QCONGABATE2 700 0 through 65535 Queue to the host application congestion level 2 abatement threshold. QCONGONSET3 1200 0 through 65535 Queue to the host application congestion level 3 onset.
PAGE 92
Configuring ISUP NMS SS7 Configuration Manual Parameter Default Valid values Description END N/A N/A Marks the end of the general section. This parameter is required. SAP parameters The service access point (SAP) parameters define the characteristics of the ISUP layer presented to the user applications. Note: The ISUP layer software allows for configuration of only a single ISUP user SAP. Therefore, only one application can use NMS ISUP at a time.
PAGE 93
NMS SS7 Configuration Manual Configuring ISUP Parameter Default Valid values Description T16_TIMER 12 0 through 65535 Time to wait for a response to a reset message sent. T17_TIMER 12 (300) 0 through 65535 Time to wait for a response to initial reset message sent. T27_TIMER 240 0 through 65535 Time to wait for a continuity check request after ensuing continuity check failure indication is received. See the TCCR_TIMER field.
PAGE 94
Configuring ISUP NMS SS7 Configuration Manual NSAP parameters The NSAP parameters define the characteristics of the ISUP interface to the MTP 3 layer: Parameter Default Valid values Description NSAP None 1 through 32 Name of the NSAP section for the rest of the parameters. SWITCH_TYPE ANSI92 ITU ITUWHITE ITUBLUE ITU97 ETSIV2 ETSIV3 Q767 ANSI88 ANSI92 ANSI95 JNTT Protocol variant employed for this MTP interface. Must match one of the switch types defined in the MTP 3 NSAP definition section.
PAGE 95
NMS SS7 Configuration Manual Configuring ISUP Parameter Default Valid values Description ALT_OPC 0 N/A Originating Point code for this set of circuits. If not present, the OPC is set to OPC from the NSAP. This needs to be used carefully with the appropriate MTP configuration changes. CIRCUIT_TYPE INCOMING INCOMING OUTGOING BOTHWAY Direction of calls allowed on this circuit group. CONTROL_TYPE NONE NONE ALL ODD_EVEN Dual seizure control.
PAGE 96
PAGE 97
7 Configuring SCCP SCCP configuration overview The SCCP (Signaling Connection Control Part) layer builds on the services of the MTP layer to provide SS7 applications with a higher level transport subsystem. SCCP adds the following services to those provided by the MTP layers: • The ability to address individual applications or databases, known as subsystems, at a signaling point through a SCCP-level address consisting of a point code and a subsystem number.
PAGE 98
Configuring SCCP NMS SS7 Configuration Manual The following illustration shows the concept of user SAPs. When the application interfaces with the TCAP layer, the TCAP SAPs map one-for-one with an SCCP user SAP. SCCP TCAP application application SCCP TCAP SAP n-2 application SAP 0 SSN 5 SAP 1 SSN 8 User SAPs SAP 2 SSN 9 ... SAP n-2 SSN 11 TCAP SAP n-1 SAP n-1 SSN 254 NSAP 1 SIO x83 NSAP 0 NSAP 1 SIO x83 MTP NSAPs ...
PAGE 99
NMS SS7 Configuration Manual Configuring SCCP Creating the SCCP configuration NMS SS7 provides sample SCCP files for ANSI standalone and redundant configurations and ITU standalone and redundant configurations that you can modify for your specifications. To learn the location of the sample configuration files, see Sample SS7 configurations on page 9. The NMS SCCP configuration utility, sccpcfg, runs as part of the initial board configuration with ss7load.
PAGE 100
Configuring SCCP SOG_THRESH NMS SS7 Configuration Manual 3 # # # # # for conn window to open Minimum number of SCCP buffers that must be available for SOR request from replicated (backup) subsystem to be accepted # Note all timer values are in seconds (0 disables timer) XREFFRZ_TIMER 2 # wait before reusing local reference #ASMB_TIMER 0 # wait for all segments of # segmented XUDT (ITU-92 only) FREEZE_TIMER 2 # wait before reusing connection reference CONN_TIMER 180 # wait for response to connection re
PAGE 101
NMS SS7 Configuration Manual SWITCH_TYPE #BACKUP_PC ANSI92 1.2.3 Configuring SCCP # one of ITU92, ITU88, ITU96, ANSI92, ANSI88, ANSI96 # this application not replicated for now # Concerned point codes (Nodes to be notified of Apps availability) up to 8 CONC_PC 1.1.
PAGE 102
Configuring SCCP ADJACENT TRANSLATOR #BACKUP_PC NMS SS7 Configuration Manual TRUE FALSE x.y.z # this dest directly adjacent # not a translator node # this node not currently replicated #define all subsystems of interest at 1.1.1 (up to 8) SSN 3 # first subsystem at 1.1.2 SSN_SNR TRUE # normal routed SSN_ACC TRUE # initially accessable #SSN_BPC x.y.
PAGE 103
NMS SS7 Configuration Manual Configuring SCCP Using default routing The SCCP default routing feature enables routing of SCCP packets generated by local applications, either directly with SCCP or through the TCAP layer, to signaling points whose point codes and subsystem numbers are not preconfigured. This feature is primarily intended for applications that act as databases, or servers, in an SS7 network and cannot be preconfigured with the point codes of all clients that access the server.
PAGE 104
Configuring SCCP NMS SS7 Configuration Manual Impact of default routing on SCCP message routing With default routing enabled, routing of outbound messages by the SCCP layer is performed as follows: 1. Global title translation, if necessary, is performed on the outbound message. 2. The SCCP layer checks for an explicit route to the destination point code. If an explicit route exists, the status of the destination signaling point and subsystem, if known, is checked.
PAGE 105
NMS SS7 Configuration Manual Configuring SCCP SCCP limitations when default routing is enabled The use of default routing effectively disables the SCCP layer management functions for those signaling points not explicitly configured with route entries.
PAGE 106
Configuring SCCP NMS SS7 Configuration Manual Configuring global title translations The SCCP layer supports global title translation, enabling applications to address messages with a string of digits such as a telephone number or a mobile identification number. Applications can rely on the network configuration to route the message to the correct destination signaling point and subsystem.
PAGE 107
NMS SS7 Configuration Manual • Configuring SCCP The configured address translation for both 800 and 900 numbers specifies a routing indicator of route by global title to indicate to the gateway STP to perform global title translation. It also indicates that the original global digits are not to be replaced in the outgoing message so that the gateway STP can perform the subsequent translation. # # Sample configuration of Global Title Translation < ...
PAGE 108
Configuring SCCP NMS SS7 Configuration Manual Multiple originating point codes (OPC) The SCCP layer can be configured to support multiple OPCs to both single networks or multiple networks. The SCCP layer will receive SCCP messages, both connectionless and connection-oriented, addressed to any of the configured OPC values. SCCP subsystem management messages for each OPC are also supported. MTP multiple OPC configuration The MTP layer must be configured correctly for multiple OPC emulation.
PAGE 109
NMS SS7 Configuration Manual Configuring SCCP Configuring multiple OPC emulation to multiple networks The SCCP layer can be configured to emulate a different OPC to each of two different networks. In this example, the SCCP layer emulates OPC 0.0.2 to the DPC 0.0.1, and emulates OPC 0.0.4 to the DPC 0.0.3.
PAGE 110
Configuring SCCP NMS SS7 Configuration Manual SCCP configuration reference This topic presents the SCCP configuration file parameters: • General parameters • User SAP parameters • Network SAP parameters • Address translation parameters • Route parameters General parameters The general parameters define the operational characteristics of the SCCP layer, such as upper bounds for internal data structures (these determine the amount of memory used by the SCCP layer), queue thresholds, and various pr
PAGE 111
NMS SS7 Configuration Manual Configuring SCCP Parameter Default Valid values Description DEF_ROUTING FALSE TRUE FALSE If TRUE, enables default routing. PC_FORMAT DEFAULT DFLT INTL JNTT Point code format. TRUE FALSE If TRUE, retains connections when destination inaccessible. SAVE_CONNS FALSE DFLT = Point codes are interpreted and displayed as 24bit 8.8.8 values. INTL = Point codes are interpreted and displayed as 14bit 3.8.3 values.
PAGE 112
Configuring SCCP NMS SS7 Configuration Manual Parameter Default Valid values Description COORD_TIMER 30 seconds 0 through 65535 Time to wait for response to coordinated state change request. XREFFRZ_TIMER 1 second 0 through 65535 Time to freeze an XUDT local reference before reusing it (ITU-92 only). ASMB_TIMER 20 seconds 0 through 65535 Maximum time for reassembling all segments of an XUDT message (ITU-92 only).
PAGE 113
NMS SS7 Configuration Manual Configuring SCCP Parameter Default Valid values Description SCCP_ALARM_LEVEL 1 1 2 3 Desired level of alarms generated by SCCP layer. 1 = (Normal) Normal service impacting alarms. 2 = (Debug) All normal alarms plus all messages in or out. 3 = (Detail) All debug alarms plus detailed events. MEM_THRESH_1 10 0 through 99 Percentage of board memory available at which memory congestion level 1 starts.
PAGE 114
Configuring SCCP NMS SS7 Configuration Manual Parameter Default Valid values Description ADDR_MASK FFF...F N/A ASCII string describing which digits of the global title to match when performing global title translation. As many as four ADDR_MASK entries are allowed per user SAP. Note: Address masks are ASCII strings containing a 0 (zero) or F in each character position to determine whether the corresponding global title digit is used in the match.
PAGE 115
NMS SS7 Configuration Manual Configuring SCCP Network SAP parameters The network service access point (SAP) defines the point at which the SCCP layer accesses the network (MTP 3) layer. One network SAP is defined for each supported switch type (ANSI or ITU-T). The NSAP number assigned in this section (NSAP number statement) must match a valid NSAP number defined in the NSAP section (NSAP number statement) of the MTP 3 configuration file.
PAGE 116
Configuring SCCP NMS SS7 Configuration Manual Parameter Default Valid values Description SCCP_NI_IND 0 (ITU) 1 (ANSI) 0 1 National or international indicator in the called or calling party address parameter of the outgoing SCCP management messages. END N/A N/A Denotes the end of the section. This parameter is required. Address translation parameters Address entries define how the SCCP layer translates global titles.
PAGE 117
NMS SS7 Configuration Manual Configuring SCCP Parameter Default Valid values Description GT_FORMAT 0 0 1 2 3 4 Structure of the outgoing global title. Use only when REPLACE_GLT parameter is TRUE. 0 = No global title translation. 1 = (ANSI) Outgoing global title includes translation type, numbering plan, and encoding scheme. (ITU) Outgoing global title includes nature of address indicator. 2 = (ANSI and ITU) Outgoing global title includes translation type only.
PAGE 118
Configuring SCCP NMS SS7 Configuration Manual Parameter Default Valid values Description ADJACENT TRUE TRUE FALSE If TRUE, this signaling point is adjacent for SCCP point code and subsystem management procedures. BACKUP_PC None Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101). Backup point code. If not present, signaling point is not replicated. ALT_OPC None Use dotted notation (such as 2.45.
PAGE 119
8 Configuring TCAP TCAP configuration overview The TCAP (Transaction Capabilities Application Part) layer adds transaction services onto the connectionless data transfer service provided by SCCP. Transactions in the SS7 network are typically database queries and responses or requests to activate services in remote switching points. TCAP can be configured for either ANSI (see ANSI T1.114) or ITU-T (see Q.771 Q.775) operation, on a per-application basis.
PAGE 120
Configuring TCAP NMS SS7 Configuration Manual Creating the TCAP configuration NMS SS7 provides sample TCAP files for ANSI standalone and redundant configurations and ITU standalone and redundant configurations that you can modify for your specifications. To learn the location of the sample configuration files, see Sample SS7 configurations on page 9. The NMS TCAP configuration utility, tcapcfg, runs as part of the initial board configuration with ss7load.
PAGE 121
NMS SS7 Configuration Manual Configuring TCAP TCAP configuration reference This topic presents the TCAP configuration file parameters: • General parameters • User SAP parameters General parameters The general parameters define the upper bounds for internal data structures, which determine the amount of memory used by the TCAP layer: Parameter Default Valid values Description MAX_TCAP_USERS 4 1 through 512 Maximum number of user SAPs.
PAGE 122
Configuring TCAP NMS SS7 Configuration Manual Parameter Default Valid values Description TCMEM_THRESH_3 10 1 through 99 Percentage of memory available in default message buffer pool below which congestion level 1 is triggered. Must be less than TCMEM_THRESH_2. END N/A N/A Marks the end of this section. This parameter is required. User SAP parameters Define one user SAP for each application or subsystem using the TCAP layer services.
PAGE 123
NMS SS7 Configuration Manual Configuring TCAP Parameter Default Valid values Description SWITCH_TYPE ANSI92 ITU88 ITU92 ITU97 ANSI88 ANSI92 ANSI96 Protocol variant used on this SAP. TCAP_T1 60 1 through 32767 Default invocation timer, in seconds (time to wait for response to invoke). TCAP_T2 60 1 through 32767 Time to wait for reject of a non-invoke component, in seconds, before considering operation successful (where applicable).
PAGE 124
PAGE 125
9 Configuring TUP TUP configuration overview Like the ISUP layer, the TUP (Telephone User Part) layer provides an interface for applications to establish, maintain, and clear circuit switched connections with the SS7 network. The TUP layer is also responsible for circuit group management, such as blocking, unblocking, and resetting of circuits and circuit groups. The TUP layer operates in accordance with the CCITT (ITU-T) recommendations Q.721 - Q.
PAGE 126
Configuring TUP NMS SS7 Configuration Manual The following illustration shows the concept of user SAPs and NSAPs: TUP application User SAPs User SAP SCCP TUP layer layer TUP NSAP NSAP 0 SIO x84 SCCP NSAP MTP 3 NSAPs NSAP 1 SIO x83 MTP 3 layer Creating the TUP configuration NMS SS7 provides sample TUP files for both ITU-T and China configurations that you can modify for your specifications. To learn the location of the sample configuration files, see Sample SS7 configurations on page 9.
PAGE 127
NMS SS7 Configuration Manual Configuring TUP Sample TUP configuration file The following example configures board 1 for ITU-T: # TUP Configuration File # General configuration parameters MAX_SAPS 1 MAX_NSAPS 2 MAX_CIRCUITS 2048 MAX_GROUPS 16 !max number of circuit groups MAX_DPCS 16 !max number of dest.
PAGE 128
Configuring TUP NMS SS7 Configuration Manual TUP configuration reference This topic presents the TUP configuration file parameters: • General parameters • User SAP parameters • Network SAP parameters • Circuit and circuit group parameters General parameters The general parameters control the overall operation of the TUP layer process. Parameter Default Valid values Description MAX_SAPS 1 1 Maximum number of user applications.
PAGE 129
NMS SS7 Configuration Manual Configuring TUP Parameter Default Valid values Description PC_FORMAT DEFAULT DFLT INTL JNTT Point code format. DFLT = Point codes are interpreted and displayed as 24-bit 8.8.8 values. INTL = Point codes are interpreted and displayed as 14-bit 3.8.3 values. JNTT = Point codes are interpreted and displayed as 16-bit mcode.scode.ucode values with the U-code in the most significant 7 bits, the S-code in the next 4 bits, and the Mcode in the least significant 5 bits.
PAGE 130
Configuring TUP NMS SS7 Configuration Manual Parameter Default Valid values Description T33_TIMER 60 0 through 65535 Time to wait to send another hardware failure group block signal. T34_TIMER 15 0 through 65535 Time to wait for a response to a hardware failure group unblock signal. Use 4 through 15 seconds. T35_TIMER 60 0 through 65535 Time to wait to send another hardware failure group unblock signal.
PAGE 131
NMS SS7 Configuration Manual Configuring TUP User SAP parameters The SAP parameters define the characteristics of the TUP layer presented to the user applications. NMS TUP allows for configuration of only a single TUP user SAP. Only one application can use NMS TUP at a time. Parameter Default Valid values Description USER_SAP None 0 through MAX_SAPS SAP number. SWITCH_TYPE ITU-T ITU-T CHINA Protocol variant employed for this application.
PAGE 132
Configuring TUP NMS SS7 Configuration Manual Circuit and circuit group parameters The circuit set parameters specify the characteristics of each of the circuit sets to be managed by the TUP layer, including the circuit identification codes (CICs) and destination point code (DPC) at the other end of the circuits. One entry is made for each circuit set. Any set can be designated as a predefined group by adding a group number to this definition.
PAGE 133
NMS SS7 Configuration Manual Configuring TUP Parameter Default Valid values Description T7_TIMER 60 0 through 65535 Time to stop sending clear forward signals. T8_TIMER 2 0 through 65535 Time to wait for a backward check-tone. Do not exceed 2 seconds. T9_TIMER 5 0 through 65535 Time to delay a start first-time continuity recheck. Use 1 through 10 seconds. T10_TIMER 180 0 through 65535 Time to delay for multiple retests of continuity. Use 60 through 180 seconds.
PAGE 134
PAGE 135
10 Downloading the configurations Starting txalarm Use the txalarm utility as the primary tool to monitor what is happening on the links as you download configurations to the board and bring the links up. txalarm captures messages from the boards, displays them on the screen, and optionally saves them to a file. Run txalarm from a separate window according to the following syntax: txalarm [-f filename] where filename specifies the file to which alarms are copied.
PAGE 136
Downloading the configurations NMS SS7 Configuration Manual Using ss7load ss7load contains commands to download and configure all the SS7 layers, but only the MTP layer is activated. To enable the optional SS7 layers, edit ss7load to remove the comment symbols from the desired layers. You can also modify the script to change the file names, the path names, or both as you modify the sample configuration files to meet your system needs.
PAGE 137
NMS SS7 Configuration Manual Downloading the configurations 2. Downloads the appropriate communications processor tasks using the cplot utility. • For TX 3220/C boards, downloads the mvip.lot and t1e1mgr.lot tasks to the board. These manager tasks enable use of the MVIP switching and T1/E1 configuration and control functions. If your system does not use these functions, you can remove these commands from ss7load. For TX 4000/C boards, these tasks are part of the on-board operating system.
PAGE 138
Downloading the configurations NMS SS7 Configuration Manual if errorlevel 4000 goto boot4000 if errorlevel 3220 goto boot3220 echo ERROR! TX board number %BRD% not available. goto end REM *************************************************************************** REM Perform board type-specific boot for TX 3220 or TX 3220C REM :boot3220 set TASKTYPE=lot REM Reset TX board (and verify TX flash image in sync with installed software) %TXUTIL%\txflash -s %TXCP%\cpk3220.
PAGE 139
NMS SS7 Configuration Manual Downloading the configurations REM Load MTP task REM %TXUTIL%\cplot -c %BRD% -f %TXCP%\mtp.%TASKTYPE% REM REM REM REM REM REM -n mtp -p 20 -a -s 12000 Enable the following downloads for SS7 layers you do use %TXUTIL%\cplot %TXUTIL%\cplot %TXUTIL%\cplot %TXUTIL%\cplot -c -c -c -c %BRD% %BRD% %BRD% %BRD% -f -f -f -f %TXCP%\sccp.%TASKTYPE% %TXCP%\isup.%TASKTYPE% %TXCP%\tup.%TASKTYPE% %TXCP%\tcap.
PAGE 140
Downloading the configurations NMS SS7 Configuration Manual Sample ss7load for UNIX #!/bin/ksh #****************************************************************************** # TX Series COMMUNICATIONS PROCESSOR BOOT FILE # # Execute this file to perform the following: # - Reset the TX board # - Synchronize the on-board flash image with the installed software # - Download TDM configuration # - Download all TX-based tasks # - Configure SS7 #******************************************************************
PAGE 141
NMS SS7 Configuration Manual Downloading the configurations ;; esac #***************************************************************************** # Reset TX board (and verify TX flash image in sync with installed software) # $TXUTIL/txflash -s $TXBASE/$FLASH -b$BRD #***************************************************************************** # Perform TX board type-specific load # if [ $BOARDTYPE = "TX 3220" ] then # Perform board type-specific boot for TX 3220 or TX 3220C TASKTYPE=lot # load the diagno
PAGE 142
Downloading the configurations #$TXUTIL/cplot -c $BRD -f $TXBASE/tcap.$TASKTYPE NMS SS7 Configuration Manual -n tcap -p 23 -a # ISUP only: Enable the download of the ISUP database # required for your configuration. # #$TXUTIL/cplot -c $BRD -f $TXBASE/itublue.$TASKTYPE -n itublue -p 15 -a #$TXUTIL/cplot -c $BRD -f $TXBASE/ituwhite.$TASKTYPE -n ituwhite -p 15 -a #$TXUTIL/cplot -c $BRD -f $TXBASE/q767.$TASKTYPE -n q767 -p 15 -a #$TXUTIL/cplot -c $BRD -f $TXBASE/ansi88.
PAGE 143
NMS SS7 Configuration Manual Downloading the configurations Monitoring link status After the configuration files are downloaded to the boards, the links are aligned (brought up through layer 2). When MTP layer 2 achieves link alignment, MTP layer 3 brings the links into service through an exchange of signaling link test messages (SLTMs) with its peer MTP 3 on the other board. When this signaling link test successfully completes, each board generates a message indicating that the link is up (in service).
PAGE 144
Downloading the configurations NMS SS7 Configuration Manual Troubleshooting link problems If a link does not come into service shortly after downloading the configuration files to the board, determine the cause of the problem from the txalarm messages.
PAGE 145
Index A H A_CLOCK 16 high speed links (HSL) 70 alarms 135 I alignment failure 144 ISUP configuration 85 B circuit groups 89 B_CLOCK 16 general 89 binary file 46 Japan-NTT 88 board download 135 Japan-TTC 88 C NSAPs 89 channel definition 34, 45 parameters reference 89 circuit framing 27, 44 sample file 86 clock command 24, 43 SAPs 89 clock fallback 21, 25 isupcfg utility 86 clock master 16, 25 J clock slave 16, 25 J1 configuration 27 clocking configuration 24, 43 J1 options 27
PAGE 146
Index NMS SS7 Configuration Manual linksets 71 S multiple OPC emulation 59 sample configurations 9 non-adjacent signaling points 53 SCCP configuration 97 NSAPs 71 address translation 110 parameters reference 71 default routing 103 priorities 55 general 110 routing 71 global title translations 106 routing masks 57 network SAPs 110 sample file 49, 66, 68 parameters reference 110 mtp.elf 135 routes 110 mtp.
PAGE 147
NMS SS7 Configuration Manual Index T1/E1 44 general 128 TDM configuration (TX 4000/C) 13 network SAPs 128 clocking 24 parameters reference 128 ports 34 sample file 126 sample file 13 user SAPs 128 T1/E1/J1 27 tupcfg utility 126 tdmcfg utility 46 txalarm utility 11, 135, 135 timeslot configuration 34, 45 txconfig utility 13 timing references 17, 20 txflash utility 135 trunk configuration 27, 44 V TUP configuration 125 V.