Technical Helpweb

Dialogic® Distributed Signaling Interface (DSI) - Signaling and SS7 Products

Configuring SS7 Boards for Monitoring

 Summary
 
Configuring Dialogic® Distributed Signaling Interface (DSI) SS7 Boards for a monitoring solution requires modification of the config.txt and system.txt files. In addition, the Dialogic® Global Call SS7 configuration file (gcss7.cfg) needs to be modified if the monitoring application is designed to record the audio for the monitored calls.

This article describes example config.txt, system.txt and gcss7.cfg files that you will need to change in order to address your requirements. Both T1 and E1 configuration parameters are covered.

Note: The files supplied with this article are examples that are relevant to the situations described in this article. The files will need to be modified by you to match your specific configuration and requirements. 
 
Config.txt - example config.txt

This file is loaded when the gctload environment is started. 

The following line loads the ss7.dc4 driver and sets its run level to Monitor (MON):   
SS7_BOARD 0 SS7HDC 0x0043 ss7.dc4 MON

The following line is forE1 trunks and is used to configure the signaling ports terminating trunks connected to the signaling network.
 

LIU_CONFIG 0 2 6 1 2 2 

The following line is the equivalent for a T1 environment:

 LIU_CONFIG 0 2 4 4 7 4  

The Board ID and LIU_ID (the first and second values) are identical for both T1 and E1 environments. 

The remaining values, line code, frame format and crc mode are documented in the Dialogic® DSI SS7HD Programmer's Guide which provides values and definitions. The last lines in the config.txt file define the specifics about the SS7 trunks being monitored.  For example:

MONITOR_LINK 1 0 0-1 2 16 0x3d 0 0 0x00

 identifies link 1 with channel 16 used for signaling and an application with an ID value of 0x3d used to process signaling messages monitored.

System.txt - example system.txt

The system.txt file is used to identify the sub-systems to be loaded and where they will run, either on the host server or on a DSI Signaling Board. In addition to the s7_mgt and s7_log modules, the system.txt file identifies the monitoring application ID and the application ID for Global Call SS7. 

The following lines are the entries for these two modules. 

LOCAL 0x3d * Monitor app
LOCAL 0x4d * global call ss7

Four MTP2 modules are then redirected to send messages to the SS7 driver SSDH in the following lines: 

REDIRECT 0x81 0x20 * MTP2 module_id for SP 0 (SS7HD boards only)
REDIRECT 0x91 0x20 * MTP2 module_id for SP 1 (SS7HD boards only)
REDIRECT 0xe1 0x20 * MTP2 module_id for SP 2 (SS7HD boards only)
REDIRECT 0xf1 0x20 * MTP2 module_id for SP 3 (SS7HD boards only) 

The following line redirects traffic to the logger to help with debugging:

0xef * LIU/MTP2 status messages -> s7_log

gcss7.cfg - example gcss7.cfg

The following entry causes the DSI SS7 Board to appear in, and be under control of, Dialogic® Configuration Manager (DCM):

System.Configuration = "Card"


The following line causes DCM to both start the signaling software and activate the links.
 

Service.GCTLOAD_Control = "YES"

The "Service.GCTLOAD_Path" and the "SeptelCard.ConfigDir" entries should be set to the  directory (or directories) containing the config.txt and system.txt files.

Finally, the "ClearGrp dkBx" lines identify which  channels of the trunk carry signaling.

The following line indicates that signaling is located on channel 24 of the trunks and that no call control is provided by the Dialogic® Global Call SS7 API:
 

ClearGrp dkB1 0x7fffffff

Product List

The techniques defined herein apply to Dialogic Distributed Signaling Interface (DSI) SS7 Boards such as Dialogic® DSI SS7HDP Network Interface Boards (PCI) and Dialogic® DSI SS7HDC Network Interface Boards (Compact PCI).


Glossary of Acronyms / Terms

Monitoring - the process of passively observing signaling traffic on one or more trunks without acting on that traffic.

Related Documentation
Dialogic® Distributed Signaling Interface (DSI) SS7HD Programmer's Manual







Feedback

Please rate the usefulness of this page:  
0 - not useful at all
1 - potentially useful
2 - quite useful
3 - very useful
4 - exactly the information I needed     

Please enter a comment about this page: