Pure Logic GMLC Quick Start Guide

1. Installation
1.1 Download and unpack the tar file gmlc.tar.[version].gz tar xvf gmlc.tar.[version].gz 1.2 Install GMLC cd gmlc sudo ./install This installs the Dialogic Signalling Environment /opt/DSI, and the run-time libraries required by GMLC in /usr/local/lib. 1.3 Install MySql e.g. On Debian/Ubuntu systems: sudo apt-get install mysql-server On RedHat/CentOS/Fedora: yum install mysql-server

GMLC should now be installed and ready to configure.

To remove GMLC completely, or before attempting to re-install, run the uninstall script from the gmlc directory: sudo ./uninstall

2. Configuration
2.1 Configure the Dialogic Signalling Environment Select ASP or Gateway configuration cd /opt/DSI ln sf config.txt.asp config.txt OR ln sf config.txt.sgw config.txt Edit the Point Codes and IP addresses in config.txt Settings in the shipped version are: Local point code Remote point code Local IP address Remote IP address 1212 1207 192.168.0.12 192.168.0.7 # ASP config # Gateway config

These should be set appropriately for your system (occurrences as shown below). * Local IP Address CNSYS:IPADDR=192.168.0.12,per=0; * * SIGTRAN / MTP3 Configuration * * Local Application Server SNAPI:AS=1,OPC=1212,RC=1,TRMD=ls; * * Link to HLR/MSC SNSLI:SNLINK=1,IPADDR=192.168.0.7,SNEND=C,SNTYPE=M3UA,PPORT=2905, HPORT=2905; SNRAI:RAS=1,RC=1,DPC=1207; SNALI:SNAL=1,RAS=1,SNLINK=1; SNLBI:SNLB=1,AS=1,RAS=1; * MTP_USER_PART 0x03 0x33 * * SCCP Configuration: SCCP_CONFIG 1212 0x0c 0x102 1 * * Remote System: SCCP_SSR 1 RSP 1207 0 0 SCCP_SSR 2 RSS 1207 0x06 0 SCCP_SSR 3 RSS 1207 0x08 0

2.2 Configure MySql Start the MySql daemon: Debian/Ubuntu: RedHat/CentOS/Fedora: sudo /etc/init.d/mysql start sudo /etc/init.d/mysqld start

Run the MySql secure installation script, to set a password for the root user and remove any anonymous users created by default (answer Y to all questions after setting the root password): sudo mysql_secure_installation

You will then need to create a user with access to the database gmlc. You can use the script db_create_user, which creates a user gmlc with password gmlc. Return to the GMLC home directory (gmlc) and type: mysql uroot p < db_create_user [Enter MySql root password]

Create the gmlc database: mysqladmin ugmlc p create gmlc [Enter gmlc password]

Set up the tables required in the gmlc database, using the script db_setup: mysql ugmlc p < db_setup [Enter gmlc password] The db_setup script creates an LCS client test with password test. These values should be used in OMA-MLP location requests sent to the GMLC.

2.3 Configure the GMLC Configure the licence file In the Back End configuration file (be.cfg) and the Front End configuration file (fe.cfg), set the licence_file parameter to the name of your GMLC licence file: licence_file = licence-file-name Configure the network point codes In the Back End configuration file (be.cfg) set the local and remote point codes for your system (parameters gmlc_addr.pc and sp_0.pc). In the shipped version these are set to 1212 and 1207: # GMLC's own address gmlc_addr { pc = 1212 # Point Code - optional (default not used) ssn = 0x91 # SSN - optional (default 0x91 = GMLC) } # Associated Signalling Points sp_0 { link_id = 0 # M3UA link-id pc = 1207 # Point Code ssn_0 = 6 # HLR ssn_1 = 8 # MSC } GMLC is now configured and should be ready to run.

3. Running GMLC
3.1 Start the Dialogic Signalling Environment cd /opt/DSI sudo b ./gctload 3.2 Start the GMLC Back End. For first use you may want to run the process in foreground mode with the logging output sent directly to the terminal, in which case the command (in the gmlc directory) is: ./be If the Signalling Environment is configured correctly and can connect to the ASP/Gateway, the Back End should report that the ASP (or Route, for Gateway configuration) is Up. For background mode, typical usage is: ./be cbe.cfg olog/be.log & SELinux If your Linux distribution has Security-enhanced Linux (SELinux) enabled, you may get error : cannot restore segment prot after reloc: Permission denied. This error occurs because the GMLC library libsg.so requires text relocation, but the SELinux policy on your machine prevents this. The solution is either to disable SELinux, or change the SELinux policy to allow text relocation by the GMLC library, by running (as root): chcon -t texrel_shlib_t /usr/local/lib/libsg.so

3.3 Start the GMLC Front End. For first use you will probably want to run in foreground with output to terminal, , in which case the command (in the gmlc directory) is: ./fe If the configuration is correct, the Front End should report a status of Up received from the Back End. The Front End is then ready to receive LCS requests. For background mode, typical usage is: ./fe cfe.cfg olog/fe.log & 3.4 Ensure that the OMA-MLP port 9210 is not blocked by the firewall on your system.

GMLC should now be up and running and ready to receive OMA-MLP requests.

4. GMLC Management
4.1 GMLC Admin Tool sgcli The tool sgcli can be used to show process status, to change the logging level of a running process, and (with the Front End) to perform database administration for LCS clients. sgcli can connect to either Front End or Back End, using the TCP/IP port defined by admin_port in the respective configuration file. For the Back End: ./sgcli localhost 6001 For the Front End: ./sgcli localhost 6002 Type h to see a list of available commands in each case. 4.1 Logging and Statistics The Back and Front End processes log to files specified on the command line with the o option. By default the log files are saved hourly and a new one started. This can be changed to daily by the rollover parameter in the logging configuration block. By default, logging level is set 1, meaning all messages passing in and out of the process are traced. In a busy system this could lead to excessive logging, in which case a level of 0 (error and information messages only) is recommended. A debug level of 2 is also provided for troubleshooting. These levels can be changed at any time using the sgcli tool. Run-time statistics are provided by both Back and Front End processes, and are written to the files specified by the file parameter in the statistics configuration block (be.stats and fe.stats by default). Statistics are gathered over a time period specified by the interval parameter. Like the logging files, the statistics files can be rotated hourly or daily according to rollover. The Back End reports the number of inbound and outbound MAP messages (per RSI link if using Dialogic Signalling Servers), and concurrent TCAP dialogues. The Front End reports the number of each type of MLP request and response, messages sent and received from each connected Back End, round trip time, number of client connections and connections refused.