TSP Lab	GyX_SS7 - The SS7 (PCM) interface module	GyX_SS7

The SS7 (PCM) interface module
`("GyX_SS7")`

Features

Provides signaling interface for a main functional module
Connects to the signaling network using SS7 connection over PCM
Acts as an active element of the SS7 network
Receives queries with input parameters via TCP/IP from the main module
Transfers queries to the SS7 network
Sends received answers with output parameters to the main module

Basic operation

Uses Sga47 interface card(s) for connecting to the SS7 signaling network
Maintains MTP1-2 functions
Maintains mid-level SS7 functions (SLTM, SNM, etc.)
Logs queries and responses
Creates SNMP traps

User interface

The main menu

Menu	Menuitem	Shortcut(s)	Meaning
[Log]
	Find line containing...	(Ctrl-F)	Finds text in log window
	Find next matching line	(F3)	Finds next occurrence of text in log window
	Details		Detail level of logging (Off, Normal, Detailed, or Debug)
[SS7]
	A: Allow MTP2 auto-connecting	(left-side )	Allows automatic (re-)connecting to the MSC on SS7 channel A
	A: Disconnect MTP2 now		Immediately disconnects SS7 channel A
	B: Allow MTP2 auto-connecting	(right-side )	Allows automatic (re-)connecting to the MSC on SS7 channel B
	B: Disconnect MTP2 now		Immediately disconnects SS7 channel B
[TCP Connection]
	Disconnect		Shutting down of all active connections
	Zero counters		Request and answer counters of TCP connection will be cleared on the status bar
[Options]
	Auto scroll	()	Allows automatic scrolling of the log screen
	Save settings		Saves actual settings into the configuration (`INI`) file
[Debug]		Items in this menu are only for debug and test purposes!
	Show DSP debug info for SS7(A) now		Shows debug information for SS7 channel A in the status line of the program window
	Show DSP debug info for SS7(B) now		Shows debug information for SS7 channel B in the status line of the program window
	Clear debug info line		Clears the debug information from the status line of the program window

Status-line of SS7 links

PCM: status of the PCM frame in the receiver connection (its color is gray in normal works, red refers to error)
MTP2: SS7/MTP2 status of the connection (its color is gray in normal works, red refers to error)
bps: Message bits received in the last second
permil: idle time of the given program thread in the last second (ms)
Rx/Tx: The number of messages received and sent on the SS7 interface
Error counters:
- pcm: number of PCM disconnections
- mtp2: number of SS7/MTP2 disconnections
- dsp: number of communication errors between DSPs of the Sga47 card and the program
- msu: received an uninterpretable or misaddressed MSU (wrong Point Code)
- tcap: number of wrong TCAP messages
MSU's buffered for Tx: The number of MSU's buffered for transmitting.
TCP connection: State of the TCP connection. It becomes gray after the main module connected.
Rx/Tx: The number of messages received and sent on the TCP interface.
RxBuffered: Number of messages in the receive buffer.
RxOverrun: Number of those messages which arrived when the TCP buffer is full.
Uptime: time elapsed since module has been started up

Configuration (INI) file settings

Section	Entry	Example	Meaning
[Position]
	iLeft	140	Position of the program module on the display screen
	iTop	72	Position of the program module on the display screen
	iWidth	995	Position of the program module on the display screen
	iHeight	694	Position of the program module on the display screen
[Options]
	bAutoScroll	True	(Refer to the `[Options]/Auto scroll` menu item!)
[SGA-47 Card]
	wBaseAddress	0xD800	The I/O address of the SGA-47 Card, selected with DIP switches
	sMTP2ObjectFile	MTP2_47 (+00 dB 120 Ohm).obj	The file name of the DSP program
[SS7]
	bAllowMTP2AutoConnectA	True	(Refer to the `[SS7]/A: Allow MTP2 auto-connecting` menu item!)
	bAllowMTP2AutoConnectB	True	(Refer to the `[SS7]/B: Allow MTP2 auto-connecting` menu item!)
	bEmergencyMTP2Startup	False	Uses or not "Emergency" mode on making up SS7/MTP2 connection
	byTimeSlotA	1	SS7 Time slot on the link A
	byTimeSlotB	1	SS7 Time slot on the link B
	wTxRLDPCIfRemotelyNotSetA	201	The point code of the remote SS7 device on association A if it is not set by the main module
	wTxRLDPCIfRemotelyNotSetB	201	The point code of the remote SS7 device on association B if it is not set by the main module
	wTxRLOPCIfRemotelyNotSetA	13	Local point code used on association A if it is not set by the main module
	wTxRLOPCIfRemotelyNotSetB	200	Local point code used on association B if it is not set by the main module
[RemoteRequest]
	wLocalTCPPort	3000	Port number, where the remote modules can connect
	bSuppressDisconnectTrap	True	When it is true traps on disconnecting TCP connection are suppressed
	sRemoteIPAddress	127.0.0.1	The main module with this IP address can connect to the GyX module Used for station restriction, leave it empty for no restriction.
[Advanced]
	wLogDetailLevel	3	(Equals to the listed order; refer to the `[Log]/Details` menu item!)
	dwMaxLinesInLogWindow	1000	Number of lines in the log window on screen
	sLogFilesPath	d:\LogFiles	Path for the LOG files
	sTrapFilesPath	d:\TrapFiles	Path for the SNMP Trap files to be sent
	bAlternateTrapUID	False	Allows using fixed UIDs in SNMP traps (See SNMP trap list below for details)
	wThreadPeriod	100	Time period when idle threads are given CPU time slice (given in milliseconds)

SNMP trap list

UID	Type	Text	Remarks	To Do
If `bAlternateTrapUID` is set to TRUE
9	CEA	`'GyX_SS7 v0.91' module is started.`	Send a welcome message; indication of module start-up
9	CRI	`'GyX_SS7 v0.91' module has been shut down by operator.`	Send a farewell warning message; indication of module shut-down	Start the `'GyX_SS7 v0.91'` module
90	CEA	`SS7(A)/MTP2 connection is up.`
90	CRI	`SS7(A)/MTP2 connection has died.`	Connection is down; indicating MTP problem at either end	Check if the point codes are correct or the other side device works properly
90	CRI	`SS7(A)/MTP2 connection has died. (operator)`	Connection is down; operator cut the line at MTP level	Set `A:MTP2` auto-connecting to be true (`[SS7]/A: Allow MTP2 auto-connecting` menuitem)
90	CRI	`SS7(A)/MTP2 connection has died. (PCM also)`	Connection is down; indicating PCM problem	Check that PCM connection is correct
91	CEA	`SS7(B)/MTP2 connection is up.`
91	CRI	`SS7(B)/MTP2 connection has died.`	Connection is down; indicating MTP problem at either end	Check if the point codes are correct or the other side device works properly
91	CRI	`SS7(B)/MTP2 connection has died. (operator)`	Connection is down; operator cut the line at MTP level	Set `B:MTP2` auto-connecting to be true (`[SS7]/B: Allow MTP2 auto-connecting` menuitem)
91	CRI	`SS7(B)/MTP2 connection has died. (PCM also)`	Connection is down; indicating PCM problem	Check that PCM connection is correct
92	INF	`TCP connection: Up.`	First incoming TCP connection. Only if `[RemoteRequest]/bSuppressDisconnectTrap=False`.
92	ERR	`TCP connection: Closed by operator.`	Operator shut TCP connection down by the `[TCP connection]/Disconnect` menu item. Only if `[RemoteRequest]/bSuppressDisconnectTrap=False`.	Connection will automatically be re-established by the main module.
92	CEA	`TCP connection: Closed (i.e., up again).`	Main module has established connection after a disconnection. Only if `[RemoteRequest]/bSuppressDisconnectTrap=False`.
92	ERR	`TCP connection: Closed by the remote side.`	The main module is shut down or the network connection broke down.	Start the main module or check the network connection between `GyX_SS7` and the main module.
94	WAR	`Received an unexpected MSU, or its format is unknown.`	Badly formatted MSU or the of the arrived MSU is not recognized	Check if the MSU traffic directed to this device is addressed and formatted properly
If `bAlternateTrapUID` is set to FALSE
0	INF	`'GyX_SS7 v0.91' module is started.`	Send a welcome message; indication of module start-up
0	WAR	`'GyX_SS7 v0.91' module has been shut down by operator.`	Send a farewell warning message; indication of module shut-down	Start the 'GyX_SS7 v0.91' module
0	INF	`SS7(A/B)/MTP2 connection is up.`	Connection A/B is up for the very first time; subsequent ones are indicated with the corresponding CEA
++N	CRI	`SS7(A/B)/MTP2 connection has died.`	Connection A/B is down; indicating MTP problem at either end	Check the SS7 connection
++N	CRI	`SS7(A/B)/MTP2 connection has died. (operator)`	Connection A/B is down; operator cut the line at MTP level	Try to set MTP2 auto-connecting to be true to enable the connection (`[SS7]/(A\|B): Allow MTP2 auto-connecting` menuitem)
++N	CRI	`SS7(A/B)/MTP2 connection has died. (PCM also)`	Connection A/B is down; indicating PCM problem	Check that PCM connections are correct
++N	CEA	`SS7(A/B)/MTP2 connection has died.`	When connection A/B is up after a down
0	INF	`TCP connection: Up.`	Given TCP connection is up for the very first time; subsequent ones are indicated with the corresponding CEA
++N	ERR	`TCP connection: Closed by the remote side.`	Given TCP connection is down; other side closed the connection
++N	ERR	`TCP connection: Closed by operator.`	Given TCP connection is down; operator closed the connection
N	CEA	`TCP connection: Closed (i.e., up again).`	TCP connection is up after a down
++N	ERR	`TCP connection: Received %u bytes of illegible request - dropping connection.`	Illegal request has been received	Check if the remote module works properly or the TCP connection is reliable. Possibly not an appropriate version of main module is used or an illegal connection was made up.
++N	ERR	`TCP connection: Received and calculated CRC do not match - dropping connection.`	Illegal request has been received	Check if the remote module works properly or the TCP connection is reliable. Possibly not an appropriate version of main module is used or an illegal connection was made up.
++N	ERR	`TCP connection: Received request with bad MagicCode - dropping connection.`	Illegal request has been received	Check if the remote module works properly or the TCP connection is reliable. Possibly not an appropriate version of main module is used or an illegal connection was made up.

Checking Sga47 card

On the back of the Sga47 card a LED signs the state of connected PCM. (The lower LED is the relevant one, the other is indifferent, without reference its state)
Right after the PC power up, the led is uninitialized, it is in random state and its color has no meaning. After the Sga-STRF program has initialized the card, the meanings of LED are the followings:

no light - there is no PCM signal on the cable at all
red - PCM signal is OK on direction 0, but no PCM on direction 1 (on the user interface of the program the A side PCM is grey, the B side is red)
green - PCM signal is OK on direction 1, but no PCM on direction 0 (on the user interface of the program the A side PCM is red, the B side is grey)
amber - PCM signal is OK on both directions (on the user interface of the program boh of the PCMs are grey)

Version history

v0.91

(c) More sophisticated checksum in TCP communication.
(n) More sophisticated checking of DSP kernel and firmware download; logged if all went well.

v0.90

First official release.

The SS7 (PCM) interface module("GyX_SS7")